Profile information sharing

1. An apparatus comprising at least one processor; and at least one memory including computer program code for one or more programs, the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus to perform at least the following:

receive profile information associated with a user and at least one device connected to a first local private network,

provide a profile information transaction comprising the profile information associated with the user and the at least one device to a first private distributed ledger in response to successful authentication of the at least one device,

provide a profile availability transaction to a public distributed ledger, the profile availability transaction comprising an availability indication of the profile information,

receive a profile request transaction, based on the profile availability transaction, for profile information associated with the user via a public distributed network of nodes storing the public distributed ledger, and

in response to validation of the profile request transaction, cause transmission of at least some of the profile information in the first private distributed ledger to a requesting node of the public distributed network.

2. The apparatus of claim 1 , wherein the apparatus is further caused to perform:

receive a join request of the at least one device connected to the first local private network to join the first private distributed ledger,

authenticate the at least one device, and

provide a join transaction to the first private distributed ledger to add the at least one device into the first private distributed ledger.

3. The apparatus of claim 1 , wherein the profile request indicates a request for profile transfer for the user visiting a second local private network, and the requesting node is a configured to provide at least some of the profile information for at least one device connected to the second local private network for configuring operation of the at least one device connected to the second local private network according to the profile information.

4. An apparatus comprising at least one processor; and at least one memory including computer program code for one or more programs, the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus to perform at least the following:

detect a need for providing profile information for a user by a node of a second local private network,

provide, on the basis of a profile availability transaction associated with the user and stored in a public distributed ledger, a profile request transaction to a public distributed ledger for obtaining profile information associated with the user, the profile availability transaction comprising an availability indication of the profile information,

receive profile information associated with the user from a providing node capable of connecting a first local private network and accessing a first private distributed ledger storing the profile information; and

cause provision of at least some of the received user profile information for at least one device connected to the second local private network.

5. The apparatus of claim 4 , wherein a second private distributed ledger is maintained by nodes of the second local private network, and wherein the apparatus is further caused to perform:

provide the received user profile information to the second distributed ledger, and

cause removal of the user profile information in the second distributed ledger in response a trigger condition.

6. The apparatus of claim 5 , wherein the apparatus is further caused to perform:

receive a request from a user device associated with the user to join the second private distributed ledger,

authenticate the user device, and

provide a join transaction to the first private distributed ledger to add the user device into the second private distributed ledger.

7. The apparatus of claim 4 , wherein the apparatus is further caused to perform:

identify the profile availability transaction associated with the user amongst transactions stored in the public distributed ledger, and

the profile request transaction identifies the profile availability transaction.

8. The apparatus of claim 4 , wherein a user input indicating profile information to be requested is received, and

an indication of the requested profile information is included in the profile request transaction on the basis of the received input.

9. The apparatus of claim 4 , wherein the apparatus is further caused to perform:

provide at least one transaction indicative of the profile information transmission to the private distributed ledger and/or the public distributed ledger.

10. The apparatus of claim 4 , wherein the profile information comprises one or more of configuration parameters for configuring operation of one or more IoT devices of the private network for the user, access data for accessing one or more devices of the private network, and access data for accessing services or applications by the one or more devices of the private network.

11. The apparatus of claim 4 , wherein the distributed ledgers are blockchain ledgers.

12. A method, comprising:

receiving profile information associated with a user and at least one device connected to a first local private network,

providing a profile information transaction comprising the profile information associated with the user and the at least one device device to a first private distributed ledger in response to successful authentication of the at least one device,

providing a profile availability transaction to a public distributed ledger, the profile availability transaction comprising an availability indication of the profile information,

receiving a profile request transaction, based on the profile availability transaction, for profile information associated with the user via a public distributed network of nodes storing the public distributed ledger, and

in response to validation of the profile request transaction, causing transmission of at least some of the profile information in the first private distributed ledger to a requesting node of the public distributed network.

13. The method of claim 12 , further comprising:

receiving a join request of the at least one device connected to the first local private network to join the first private distributed ledger,

authenticating the at least one device, and

providing a join transaction to the first private distributed ledger to add the at least one device into the first private distributed ledger.

14. The method of claim 12 , wherein the profile request indicates a request for profile transfer for the user visiting a second local private network, and the requesting node is a configured to provide at least some of the profile information for at least one device connected to the second local private network for configuring operation of the at least one device connected to the second local private network according to the profile information.

15. The method of claim 12 , further comprising:

providing at least one transaction indicative of the profile information transmission to the private distributed ledger and/or the public distributed ledger.

16. The method of claim 12 , wherein the profile information comprises one or more of configuration parameters for configuring operation of one or more IoT devices of the private network for the user, access data for accessing one or more devices of the private network, and access data for accessing services or applications by the one or more devices of the private network.

17. The method of claim 12 , wherein the distributed ledgers are blockchain ledgers.

18. A method, comprising:

detecting need for providing profile information for a user by a node of a second local private network,

providing, on the basis of profile availability transaction associated with the user and stored in a public distributed ledger, a profile request transaction to a public distributed ledger for obtaining profile information associated with the user, the profile availability transaction comprising an availability indication of the profile information,

receiving profile information associated with the user from a providing node capable of connecting a first local private network and accessing a first private distributed ledger storing the profile information; and

causing provision of at least some of the received user profile information for at least one device connected to the second local private network.

19. The method of claim 18 , wherein a second private distributed ledger is maintained by nodes of the second local private network, and the method further comprising:

providing the received user profile information to the second distributed ledger, and

causing removal of the user profile information in the second distributed ledger in response a trigger condition.

20. The method of claim 18 , further comprising:

receiving a request from a user device associated with the user to join the second private distributed ledger,

authenticating the user device, and

providing a join transaction to the first private distributed ledger to add the user device into the second private distributed ledger.