Abstract: A method enabling migration of a subscription from a source device to a destination device is disclosed. The method may be performed in a migration entity and comprises: receiving, from the source device, a confirmation of a first profile associated with the subscription having been deleted in the source device, securing a second profile associated with the subscription to be provisioned onto the eUICC of the destination device, wherein at least one piece of subscription information is the same for the first and second profiles, and providing an activation code for use in migration of the subscription to the destination device. A method in a source device, migration entity, source device, computer programs and computer program products are also provided.

Abstract: There is provided mechanisms for remote provision of a subscriber entity. The method is performed by the subscriber entity. A method comprises providing a request for download of a profile for remote provisioning of the subscriber entity to a subscription management entity. The method comprises verifying, using a profile handling unit of the subscriber entity, that the subscription management entity possesses a valid certificate for downloading the profile. The method comprises allowing download of the profile for remote provisioning of the subscriber entity only when the subscription management entity possesses the valid certificate.

Abstract: There is provided mechanisms for handling a subscription profile for a subscriber entity. A method is performed by a subscription management entity. The method comprises obtaining a request from a mobile network operator entity to configure the subscription profile for the subscriber entity. The method comprises configuring the subscription profile with a customized PIN/PUK code for the subscriber entity. The method comprises providing an indication of the customized PIN/PUK code being configured in the subscription profile in a response to the mobile network operator entity.

Abstract: There is provided mechanisms for enabling management of a subscriber entity. A method is performed by the subscriber entity. The method comprises obtaining a message from a subscription server. The message comprises an event record. The event record is addressed to the subscriber entity and comprises a pointer to a primary entity. The method comprises establishing a connection to the primary entity for management of the subscriber entity.

Abstract: A technique for operating an RSP node (100), which is configured for remote subscriber identity module, SIM, provisioning, RSP, and comprises or is connectable to an interface (502) for communication with an MNO node (200) of a mobile network operator, MNO, is described. As to a method aspect of the technique, a download order message from the MNO node (200) is received through the interface (502). The download order message includes data (604) for generating a SIM profile (602). The SIM profile (602) is generated in response to the download order message according to the data (604) received for generating the SIM profile (602). A result (606) of the SIM profile generation is sent through the interface (502) to the MNO node (200).

Abstract: There is provided mechanisms for handling network subscriptions of a subscriber entity having a network subscription locked to a source subscription management entity. A method is performed by a profile handling entity. The method comprises obtaining a request message for download of a new network subscription handled by a target subscription management entity, the request message comprising identity information of the target subscription management entity. The method comprises transmitting, when there is a mismatch between the identity information and reference identity information, a release request message of the network subscription to the source subscription management entity via the target subscription management entity. The method comprises receiving, from the source subscription management entity via the target subscription management entity, a release response message of the network subscription.

Abstract: A method, performed by a server, for determining token scope information so that a client can obtain a scoped token for a cloud service is disclosed. The method comprises requesting and receiving data of a cloud service from another server, receiving a token scope information request for an operation of the cloud service from a client and deriving token scope information based on the data for said operation. The method further comprises sending token scope information to the client so that the client can request a scoped token with capabilities enabling them to access the operation of the cloud service.

Abstract: There is provided mechanisms for remote provision of a secondary subscriber entity. A method is performed by a primary subscriber entity. The method comprises providing a selected subscription type for the secondary subscriber entity to a subscription portal of the primary subscriber entity during an authenticated session between the primary subscriber entity and the subscription portal. The method comprises receiving an activation code for a new network subscription of the selected subscription type from the subscription portal. The method comprises providing the activation code to the secondary subscriber entity to remotely provision the secondary subscriber entity.

Abstract: A method (30) of ending a subscription performed in a network entity (20) is disclosed. The method (30) comprises receiving (33), from a device (10) comprising an Embedded Universal Integrated Circuit Card, eUICC, (14), a signed confirmation of a profile having been deleted in the device (10), the profile being associated with a subscription for the device (10); sending (34), to a Subscription Manager Data Preparation entity (19), a command for deletion of the profile; and deleting (35) the user subscription and related profile in case an acknowledgement of the deletion of the profile is received from the Subscription Manager Data Preparation entity (19). Method (60) in a device (10), method (90) in a Subscription Manager Data Preparation entity, devices and entities, computer programs and computer program products are also provided.

Abstract: There is provided mechanisms for remote provision of a subscriber entity. The method is performed by the subscriber entity. A method comprises providing a request for download of a profile for remote provisioning of the subscriber entity to a subscription management entity. The method comprises verifying, using a profile handling unit of the subscriber entity, that the subscription management entity possesses a valid certificate for downloading the profile. The method comprises allowing download of the profile for remote provisioning of the subscriber entity only when the subscription management entity possesses the valid certificate.

Abstract: There is provided mechanisms for remote provision of a secondary subscriber entity. A method is performed by a primary subscriber entity. The method comprises providing a selected subscription type for the secondary subscriber entity to a subscription portal of the primary subscriber entity during an authenticated session between the primary subscriber entity and the subscription portal. The method comprises receiving an activation code for a new network subscription of the selected subscription type from the subscription portal. The method comprises providing the activation code to the secondary subscriber entity to remotely provision the secondary subscriber entity.

Abstract: There is provided mechanisms for handling network subscriptions of a subscriber entity having a network subscription locked to a source subscription management entity. A method is performed by a profile handling entity. The method comprises obtaining a request message for download of a new network subscription handled by a target subscription management entity, the request message comprising identity information of the target subscription management entity. The method comprises transmitting, when there is a mismatch between the identity information and reference identity information, a release request message of the network subscription to the source subscription management entity via the target subscription management entity. The method comprises receiving, from the source subscription management entity via the target subscription management entity, a release response message of the network subscription.

Abstract: A method enabling migration of a subscription from a source device to a destination device is disclosed. The method may be performed in a migration entity and comprises: receiving, from the source device, a confirmation of a first profile associated with the subscription having been deleted in the source device, securing a second profile associated with the subscription to be provisioned onto the eUICC of the destination device, wherein at least one piece of subscription information is the same for the first and second profiles, and providing an activation code for use in migration of the subscription to the destination device. A method in a source device, migration entity, source device, computer programs and computer program products are also provided.

Abstract: Systems and methods for distributing software licenses based on geographical location are provided. In one exemplary embodiment, a method performed by a local interface device in a network for distributing licenses for software applications comprises authenticating the local interface device to a license server in the network for receipt of licenses. Further, use of the authentication of the local interface device to obtain a license from the license server is limited to user devices that communicate with the local interface device when located less than a predetermined maximum distance from the local interface device for using that authentication to enable the user device to obtain a license.

Abstract: The disclosure relates to a method 30 for handling latency performed in a node 12, 151, 152, 153, . . . , 15n of a distributed cloud 11. The node 12, 151, 152, 153, . . . , 15n is configured to handle a subset of media processing required by a media service and the distributed cloud 11 comprising two or more such nodes 12, 151, 152, 153, . . . , 15n, wherein a communication path for the media service is configured between at least a first and a second communication device 141, 142. The media service is provided by media streams comprising media packets and the communication path involving two or more of the nodes 12, 151, 152, 153, . . . , 15n. The method 30 comprises: determining 31 processing delay of processing the media packet in the node 12, 151, 152, 153, . . .

Abstract: There is described a system for authenticating a client device in a network having a plurality of IDM components. One or more of the IDM components subscribes (using the publish-subscribe message pattern) to authentication requests published by client devices. The client device publishes an authentication request into the network. The most appropriate IDM component to process the published authentication request is selected, and the authentication request forwarded to the selected IDM component. The selected IDM component is then operated to negotiate with and authenticate the client device.

Abstract: Systems and methods for distributing software licenses based on geographical location are provided. In one exemplary embodiment, a method performed by a local interface device in a network for distributing licenses for software applications comprises authenticating the local interface device to a license server in the network for receipt of licenses. Further, use of the authentication of the local interface device to obtain a license from the license server is limited to user devices that communicate with the local interface device when located less than a predetermined maximum distance from the local interface device for using that authentication to enable the user device to obtain a license.

Abstract: A method, performed by a server, for determining token scope information so that a client can obtain a scoped token for a cloud service is disclosed. The method comprises requesting and receiving data of a cloud service from another server, receiving a token scope information request for an operation of the cloud service from a client and deriving token scope information based on the data for said operation. The method further comprises sending token scope information to the client so that the client can request a scoped token with capabilities enabling them to access the operation of the cloud service.

Abstract: A system is described for a license provider to distribute licenses for software applications. A license server (102) is operated by the license provider to distribute licenses to user devices (110). At least one local interface device such as an NFC pad (104) is provided at a known geographical location, configured to communicate with the license server, and further configured to communicate with a user device (110) when located less than a predetermined maximum distance from the local interface device. The local interface device is configured to be authenticated to the license server and provides a mechanism for a user device (110) communicating with the local interface device (104) to use the authentication of the local interface device to obtain a license from the license server (102).

Abstract: The disclosure relates to a method 30 for handling latency performed in a node 12, 151, 152, 153, . . . , 15n of a distributed cloud 11. The node 12, 151, 152, 153, . . . , 15n is configured to handle a subset of media processing required by a media service and the distributed cloud 11 comprising two or more such nodes 12, 151, 152, 153, . . . , 15n, wherein a communication path for the media service is configured between at least a first and a second communication device 141, 142. The media service is provided by media streams comprising media packets and the communication path involving two or more of the nodes 12, 151, 152, 153, . . . , 15n. The method 30 comprises: determining 31 processing delay of processing the media packet in the node 12, 151, 152, 153, . . .