Classifications

• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L63/00—Network architectures or network communication protocols for network security
  • H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
  • H04L41/28—Restricting access to network management systems or functions, e.g. using authorisation function to access network configuration
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L12/00—Data switching networks
  • H04L12/02—Details
  • H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
  • H04L12/1403—Architecture for metering, charging or billing
  • H04L12/1407—Policy-and-charging control [PCC] architecture
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L63/00—Network architectures or network communication protocols for network security
  • H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
  • H04L63/0823—Network architectures or network communication protocols for network security for authentication of entities using certificates
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
  • H04W12/04—Key management, e.g. using generic bootstrapping architecture [GBA]
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
  • H04W12/06—Authentication
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
  • H04W12/30—Security of mobile devices; Security of mobile applications
  • H04W12/35—Protecting application or service provisioning, e.g. securing SIM application provisioning

Definitions

• the present invention relates generally to the management of network devices utilizing an authorization token.
• UICCs universal integrated circuit cards
• MNO mobile network operator
• UICCs universal integrated circuit cards
• MNO mobile network operator
• the network device e.g., a cell phone
• MNO mobile network operator
• MNO mobile network operator
• the network device owner needs to remove the UICC and put in a new UICC from the new service provider (e.g., another MNO).
• M2M machine-to- machine
• Embedded universal integrated circuit cards are currently being considered for use in network devices (e.g., cell phones, tablets, M2M devices, etc.) which may reduce costs and eliminates the need to remove and replace UICCs from network devices.
• embedded UICCs eUICCs
• eUICCs embedded UICCs
• techniques to prevent unauthorized entities from loading, enabling, disabling, and/or deleting services and profiles need to be addressed as well as techniques to allow authorized entities to enable services and manage profiles. This is pertinent both for user-controlled network devices (e.g., cell phones) as well as M2M devices that a user typically does not physically interact with.
• aspects of the invention may relate to an apparatus, system, and method for the management of network devices utilizing an authorization token.
• an authorization token received from a service provider may be verified using an authorization credential to determine if the service provider is authorized to perform requested operations with the network device. Further, operation privileges may be enforced that are contained in the authorization token.
• FIG. 1 is block diagram of a system in which embodiments of the invention related to the management of network devices utilizing an authorization token may be practiced.
• FIG. 2 is a flow diagram illustrating a process implemented by a network device to utilize an authorization token.
• FIG. 3 is block diagram particularly showing a network device utilizing an authorization token.
• FIG. 1 is a block diagram of a system 100 in which embodiments of the invention may be practiced.
• a network device 102 that includes an interface 103, a processor 104, and a memory 105 that may store an authorization credential(s) 110 and an authorization token(s) 114.
• the processor 104 and the memory 105 may be configured in an embedded universal integrated circuit card (eUICC) 115.
• eUICC embedded universal integrated circuit card
• the eUICC 115 may include some or all of the components regularly utilized by an UICC.
• processor 104 may execute functions including: generating an authorization token 114 using an authorization credential 110; commanding the transmission of the authorization token 114 to a device management authority 118 or to a service provider 134,130 (if authorized by the device management authority 118) via the network interface (I/F) 103 through a link; verifying the authorization token 114 received back from the service provider 134,130 using the authorization credential 110 to determine if the service provider 134,130 is authorized to perform requested operations with the network device 102; and enforcing operation privileges contained in the authorization token 114.
• the device management authority 118 generally refers to the owner of the network device 102 or an entity that has the authority to authorize another entity to manage the data or service on the eUICC 115 or the network device 102.
• network device 102 may be any type of suitable network device (e.g. laptop computer, mobile device, non-mobile device, smart phone, cell phone, tablet, personal digital assistant (PDA), machine-to-machine (M2M) device, personal computer, server computer, etc.) having a processor 104 and a memory 105 to implement the previously described functionality and the hereinafter to be described functionality.
• network device 102 may include a user interface 120 which may be any suitable type of input mechanism, e.g., keyboard, keypad, touch-screen, voice recognition, microphone, etc.
• I/F 103 may be a suitable wireless interface and may include suitable transceiver components (e.g.
• network device 102 may include a display device 112, such as, a commonly used display device that is implemented with a network device.
• an authorization token 114 of a network device 102 may be used to authorize an entity (e.g., a service provider 134,130) to provide a service for the network device 102 and to specify its operation privileges with the network device, as will be described in detail hereinafter.
• entity e.g., a service provider 134,130
• network device 102 may communicate via various links with service providers 134,130.
• a service provider may be a mobile network operator (MNO) 134.
• MNO mobile network operator
• an authorization credential 110 may be selected and programmed into the memory 105 of the eUICC 115 and an authorization token 114 may also be stored in memory 105.
• authorization credentials 110 may be at least one of a binary string, a password, a secret key, a public key, or a combination thereof.
• FIG. 2 is a flow diagram illustrating a process 200 to generate and verify an authorization token 114.
• processor 104 may generate an authorization token 114 that may be based upon an authorization credential 110.
• processor 104 may command a transmission of the authorization token 114 to a device management authority 118 or to a service provider 134,130 if authorized by the device management authority 118.
• processor 104 may verify the authorization token 114 from the service provider using the authorization credential 110 to determine if the service provider is authorized to perform requested operations with the network device 102.
• processor 104 may enforce operation privileges contained in the authorization token.
• processor 104 may further execute functions to specify operation privileges associated with services that are allowable from the service provider 134,130 that are contained and transmitted in the authorization token 114.
• operation privileges may include loading, deleting, enabling, or disabling a set of data or services of the service provider 134,130.
• an authorization credential 110 is typically created and stored in the eUICC 115 such that only the device management authority 118 may access it.
• a copy of the authorization credential 306 may be given to the device management authority 118 such that the device management authority 118 may use the authorization credential 306 without access to the network device 102.
• the manufacturer 307 of the eUICC 115 may create the authorization credential 306 and store it in the eUICC 115 or the network device 102 as shown as authorization credential 110.
• the authorization credential 306 may also be provided to the device management authority 118 which may hold a copy. Again, the device management authority 118 is considered to be the "owner" of the eUICC 115 and/or the network device 102.
• the device management authority 118 may generate an authorization token 114 for use by the service provider 134,130.
• the device management authority 118 may authorize the network device 102 to generate the authorization token 114 and transmit it to the service provider 134,130 while subscribing to the service from the service provider 134,130. Later the service provider 134,130 may transmit the authorization token 114 to its associated subscription manager 119,132.
• the subscription manager 119,132 While the subscription manager 119,132 is trying to access the network device 102 or the eUICC 115 to manage the service on the eUICC 115 or the network device 102, it will present the authorization token 114 to the eUICC 115 to prove that it is authorized by the device management authority 118.
• the eUICC 115 will use the authorization credential 110 to verify the authorization token 114 and to confirm that the subscription manager 119, 132 is authorized by the device management authority 118.
• the device management authority 118 may specify the operation privileges 117 for the service provider 134,130.
• the authorization token 114 may be created with the device management authority's authorization credential 306 such that only the device management authority 118 can create this authorization token 114.
• the device management authority 118 needs to authorize a service provider 134,130 to access the eUICC 115 (e.g., when the device management authority 118 wants to subscribes to a new service provided by the service provider 134,130)
• network device 102 via I/F 103 transmits the authorization token 114 to the service provider 134,130.
• the device management authority 118 or the network device 102 may transmit the authorization token 114.
• the service provider 134,130 transmits the authorization token 114 to the eUICC 115 of the network device 102 and the eUICC may verify the authorization token using the device management authority's authorization token 114 stored in the eUICC.
• the network device 102 can verify the authorization token 114 from the service provider 134,130 using the authorization credential 110 to determine if the service provider is authorized to perform requested operations with the network device.
• the authorization token 114 may be generated outside of the network device 102, such as by the device management authority 118 using the authorization credential 306.
• the device management authority 118 may include a copy of the authorization credential 306 (e.g., stored in a secure memory) and may input the authorization credential 306 into a computer program to generate the authorization token 114. And then the device management authority 118 may transmit the authorization token 114 to the service provider 134,130, as an example, when the authorization token 114 is not transmitted to the service provider by the network device 102.
• the service provider 134,130 may transmit the authorization token 114 to the eUICC 115 directly or via the subscription manager 119,132 to prove to the eUICC 115 that the device management authority 118 has authorized the service provider 134,130 or the subscription manager 119, 132 to provide service on the eUICC 115.
• the device management authority 118 i.e., the owner of the network device
• the authorization token 114 may also be directly transmitted by the network device 102 to the service provider 134,130.
• authorization token 114 generation may occur at the network device 102 itself, but authorization token 114 generation may also occur outside the network device 102.
• the management authority 118 may make a copy of the authorization credential 306 and store it securely. In this way, many network devices 102 may be managed by the device management authority 118 at the same time without accessing each network device 102.
• the device management authority 118 sets the same authorization credential 110 in many network devices 102, one authorization token 114 may be used for all the network devices 102 that have the same authorization credential 110.
• the device management authority 118 can generate the authorization token 114 without having to access/connect to the network device.
• the device management authority 118 can use the stored authorization credential 306 to generate an authorization token 114 to give to a new service provider (e.g. MNO 134) to load an operational profile 127 to the eUICC 115 to enable the new network service for the network device 102.
• a new service provider e.g. MNO 134
• the operational privileges 117 stored in the authorization token 114 are set by the device management authority 118 to provide the rules to specify what a service provider is allowed to do.
• the operational profile 127 may be a set of data that may be used to enable a service.
• the operation profile 127 may be loaded by the subscription manager 132,119 and/or the service provider 134,130 into the eUICC 115 to enable the service, as will be described in more detail hereinafter.
• a service provider 134 may be a mobile network operator (MNO), for example, to provide cell-phone service to a network device 102.
• MNO mobile network operator
• a service provider 130 may be a music company that provides music to a network device 102.
• Service providers may provide services to a device with a user physically controlling the device (e.g., cell phone, smart phone, laptop computer, tablet, etc.) or a device generally without a user physically controlling the device such as a smart meter.
• service providers 134,130 typically cooperate with subscription managers 119,132 (which may be managed by the service provider itself or by another company) to manage the subscriptions, profiles, and operations for a network device's use of services. Therefore, service providers 134,130 in cooperation subscription managers 119,132 may provide a wide variety of services, such as: mobile network connectivity services, music services, texting services, video services, storage services, etc. In particular, for M2M network devices, such services may include global positioning system (GPS), traffic reporting and mapping services for cars, and dynamic meter reading service for smart meters.
• GPS global positioning system
• traffic reporting and mapping services for cars
• dynamic meter reading service for smart meters.
• Embodiments of the invention generally relate to the owner's or device management authority's 118 authorization and security for an eUICC 115 of a network device 102 by utilizing an authorization token 114 to authorize a service provider 134,130 to provide a service for the network device 102 and to specify the service providers' operation privileges 117 with the network device 102.
• the network device 102 may communicate via various links with service providers 134,130 and subscription managers 119,132.
• an authorization credential 110 may be selected and programmed into the eUICC 115 and an authorization token 114 may also be stored in the eUICC 115.
• the operation privileges 117 may be specified in the authorization token 114 and the eUICC 115 may verify the operation privileges and make sure that service provider's rights are not beyond the privileges specified by the device management authority 118. Therefore, a plurality of different services may be useable by a network device 102 from various service providers and the operation privileges can be controlled by the device management authority 118. Also, as will be described in more detail hereinafter, the validity 121 of the operation privileges 117 (e.g., how long authorization remains valid (e.g., an expiration time)) may be specified in the authorization token 114.
• the authorization token 114 may have other attributes that are stored in the authorization token 114 such as: service entity attribute 123 that specifies what service provider is authorized; and a one-time or multiple time attribute 125 that indicates whether the authorization token is a one-time use authorization token or a multiple-time use authorization token.
• service entity attribute 123 that specifies what service provider is authorized
• a one-time or multiple time attribute 125 that indicates whether the authorization token is a one-time use authorization token or a multiple-time use authorization token.
• a usage counter may be utilized to count how many times the token has been used.
• a utility company may be the device management authority 118 and may be the owner of a huge amount of network devices 102 (e.g., smart meters).
• the utility company 118 does not want to manage the operational profile 127 (which contains the network access information to obtain needed cellular services from an MNO service provider 134) on the eUICC 115. Therefore, if utility company 118 wants to subscribe to the service of the MNO service provider's 134, it will generate an authorization token 114 for the MNO service provider's 134 subscription manager 119 to load MNO's operational profile 127 into the network device's 102 eUICC 115 to give to the MNO 134.
• subscription manager 119 When, subscription manager 119 transmits its operational profile 127 to the eUICC 115, it may also get the authorization token 114 from the MNO 134 and transmit it to the eUICC 115 to request the ability to load the operational profile 127 so that the services can be enabled. Once the eUICC 115 verifies that the authorization token 114 has been issued by the utility company/owner 118 to MNO 134 and its subscription manager 119, then the eUICC 115 will allow the subscription manager 119 to load and install the operational profile 127 of the MNO 134. Otherwise, the operational profile 127 cannot be loaded and consequently the service cannot be enabled.
• an authorization credential 110 may be set for the network device 102 and, in particular, may be set inside the eUICC 115 of the network device 102.
• a manufacturer 307 may set the authorization credential 110 into the network device 102.
• the authorization credential 110 may be a binary string, a password, a secret key, a public key, or a Root CA certificate that contains a public key, etc.
• the authorization credential 110 may be set by the device manufacture 307 or by the device management authority 118.
• Network device 102 or the eUICC 115 should protect this authorization credential 110 securely.
• the authorization credential 110 may be stored in the eUICC 115 and the device management authority 118 may be provided with a password to access it. This allows device management authority 118 to change the password and the authorization credential 110.
• device management authority 118 may store the authorization credential 306 locally on a computing device (e.g., a desktop, lap-top, other mobile device, etc.) as a securely stored authorization credential 306.
• the manufacturer 307 may provide an application running on the computer or mobile device/cell-phone to protect the authorization credential and to help generate the authorization credential 110.
• device management authority 118 may authenticate itself to the network device 102 via a password.
• the manufacturer 307 may provide an online service to help the device management authority 118 manage the authentication credential 306.
• the manufacturer 307 may encrypt an authorization credential 306 and store it in the cloud where it can be accessed by the device management authority 118. In this way, authentication credential decryption and authorization token generation may be accomplished on the client side.
• the device management authority 118 may login into the eUICC 115 of the network device 102 to generate an authorization token 114 via a secure connection such as using transport layer security/secure sockets layer protocol (TLS/SSL) (as an example). This may be done before deploying the network device 102. Further, when using the authorization credential 110 on the network device 102 or on a web server, the device management authority 118 may log onto the network device 102 or its corresponding web account. In this way, the authorization token 114 can be emailed to the service provider 130 or uploaded online.
• TLS/SSL transport layer security/secure sockets layer protocol
• the corresponding authorization credential information 306 may be passed to eUICC 115 of the network device 102 (e.g., from a manufacturer 307 or device management authority 118) so that the network device 102 can generate an authorization token 114 that may be used to give an operation privilege to a third party entity (e.g. hereinafter referred to as service provider 134,130).
• a third party entity e.g. hereinafter referred to as service provider 134,130.
• the service provider 134,130 works in cooperation with a subscription manager 119,130.
• device management authority 118 may have the network device 102 generate an authorization token 114 that may be presented to a service provider 134,130. It should be appreciated that if a symmetric key mechanism or password mechanism is utilized that the authorization credential 306 provided to the device management authority 118 may be the same as the authorization credential 110 stored inside the network device 102. If using a public key mechanism, the authorization credential 306 provided to the device management authority 108 may be the pairing part of the authorization credential 110 stored in the eUICC 115 of the network device 102.
• the authorization token 114 of the eUICC 115 of the network device 102 may be a digital token that specifies operation privileges 117 (stored in the authorization token 114) for a specified or unspecified service provider 134,130 and/or subscription manger 119,132. Further, the authorization token 114 received back from service provider 134,130 may be verified by the eUICC 115 of the network device 102 to confirm that the operation privileges are authorized by the device management authority 118. Optionally, if the authorization token 114 is stored in the eUICC 115 already, the service provider 134,130 may not be required to present the token each time when the service provider 134,130 tries to access the eUICC.
• the authorization token 114 may be generated by the owner/device management authority 118 logging into the eUICC 115 of the network device 102 locally or by the device management authority 118 logging into the eUICC 115 of the network device 102 remotely from outside (e.g., via remote access).
• the authorization token 114 may be portable and is beneficial in that it may be transmitted to a service provider 134,130 to obtain pre-defined operation privileges without exposing the authorization credentials 110.
• this data may include: token ID, sequence number, signature data (e.g., digital signature with a public key or message authentication checksum (MAC) with a symmetric key), as well as various optional information.
• Optional information may include: eUICC ID, service provider ID, subscription manager ID, device management authority ID or IDs of authorized profiles, and authorized privileges (e.g., particular profiles, particular management operations, etc.).
• the device management authority 118 may use the authorization credential 110 to generate the authorization token on the eUICC.
• network device 102 may provide management commands for the device management authority 118 to generate authorization token, and device management authority 118 may log into the network device 102 to perform these management commands.
• the device management authority 118 may use the credential (e.g., password) that is owned only by the device management authority to log into the network device 102.
• device management authority 118 may utilize the authorization credential 110 to create an authorization token 114 that may be specified with particular privileges (e.g., operation privileges 117) that may be utilized by a third party for management of the network device 102.
• one of the privileges may be what operations are allowable such as: loading, deleting, enabling, or disabling of a set of data or services of the service provider 134,130.
• Another privilege may be determining which entities (e.g., service providers) can perform operations such as: a list of the IDs of the service providers 134,130 and subscription managers 119,132 that may be utilized.
• the service entity 123 may be specified in the authorization token 114.
• privileges that may be specified relates to the validity of the operation privileges.
• the validity 121 may be specified in the authorization token 114.
• Yet another privilege that may be specified is where operations can be performed, e.g., a list of the eUICC IDs.
• a further example of a privilege that may be specified relates to on which objects the operations can be performed, e.g., which operation profile 127 can be managed by a service provider 134,130 or a subscription manager 119,132.
• An additional operational privilege that may be specified in the authorization token 114 is how many times operations can be performed such as one-time or multiple time use 125, as will be described in more detail hereinafter.
• the authorization token 114 may be provided to the service provider 134,130 that will perform the services via a connection.
• service provider 134,130 may provide the authorization token 114 such that the network device 102 can verify that it is authorized by the device management authority 118 using the authorization credential 110 stored within the network device 102. If verified, the operation privileges specified in the authorization token 114 may be allowed. Otherwise, the services may be rejected.
• device management authority 118 may generate an authorization token 114 that is transmitted via a link to service provider 134.
• Service provider 134 may transmit the authorization token 114 to subscription manager 119 which may then load operation profile 127 into the eUICC 115 of the network device 102 using the authorization token 114.
• the eUICC 115 may utilizes its own authorization credential 110 to verify that the subscription manager 119 is authorized to load the operation profile 127.
• Network device 102 may then utilize services associated with service provider 134.
• the authorization token 114 may be given to a third party (e.g., service provider 134) to use when the device management authority 118 would like to subscribe to a service provided by the service provider 134.
• a third party e.g., service provider 134
• network device 102 may generate an authorization token 114 for the particular MNO (e.g., MNO 134) to allow MNO 134 or the MNO's subscription manager 119 to load operation profile 127 into the eUICC 115 of the network device 102 and consequently manage the loaded operation profile with a credential set by the MNO 134 and the network device can implement various services associated with service provider 134.
• MNO mobile network operator
• the device management authority 118 may submit the authorization token 114 to the website such that MNO 134 can proceed with the authorization token 114 in a similar manner. Meanwhile other MNOs cannot load operation privileges into the eUICC 115 of the network device 102 without the device management authority's authorization.
• the authorization token 114 may be generated either inside the network device 102 or outside the network device 102.
• the device management authority 118 may login to the network device 102 using a password and request that the network device 102 generate the authorization token 114. In this way, the device management authority 118 may only need to know the password and the longer authorization credential 110 may just be stored inside the network device 102.
• the authorization token 114 may be exported from the network device 102 and be given to another entity, as previously described.
• an external application may be used to generate the authorization token 114, as well.
• a utility company may have a secure token to generate the authorization token 114 for all of its smart meters (i.e., network devices 102) using a private key.
• the smart meters can verify this authorization token 114 to determine if an operation is authorized.
• New programs may be loaded onto all of the smart meter network devices 102 based upon the authorization token remotely.
• an authorization token 114 may be utilized for a one-time use or for multiple-time uses which may be specified by one-time/multiple time attribute 125.
• a one-time use token may be used only for one time to authorize a new service provider 130 and subscription manager 132. This may be for an unlimited amount of a time or for a pre-determined period of time.
• the authorization token 114 may be set to be valid only for a certain pre-determined time period, to expire at a specific time, or to be useable until canceled.
• a multiple- time use token can be set for use during multiple specified times.
• the multiple time token may utilize a usage counter to count how many times the token has been used.
• authorization tokens 114 may utilize incremental sequence numbers. Also, once a newer authorization token is used, the older authorization token may be invalidated. Therefore, it should be appreciated that authorization tokens 114 may be revoked or invalidated. For example, authorization tokens 114 may be revoked based upon a token ID number or based upon a sequence number. [0043] Examples of usage cases will now be described.
• manufacturer 307 may provide an authorization credential 306 and password to the device management authority 118 of the network device 102.
• the authorization token 114 is generated with the authorization credential 110.
• the network device 102 via I/F 103 transmits the authorization token 114 via a link to the service provider 134 along with other eUICC 115 information.
• device management authority 118 is providing the authorization token 114 to the service provider 134 and to the subscription manager 119 to provide permission to manage the eUICC 115 of the network device 102.
• This provides a secure environment in that only an authorized service provider 134 and subscription manager 119 have permission to manage the network device 102 such that a secure method for authorization is provided.
• new service providers may be added.
• device management authority 118 may generate an authorization token 114 either by logging into the eUICC 115 of the network device 102 or by generating the authorization token 114 externally.
• the network device 102 transmits the authorization token 114 via I/F 103 through a link to a new service provider 130 in conjunction with other eUICC 115 information.
• the authorization token 114 may be generated at any time without the subscription manager 132 being knowable to the device management authority 118 which provides flexibility in managing the authorization.
• a service provider may be changed.
• the device management authority 118 generates an authorization token 114, either by logging into the eUICC 115 or by generating the authorization token 114 externally.
• the network device 102 transmits the authorization token 114 via I/F 103 through a link to the new service provider 130 along with other eUICC 115 information.
• the authorization token 114 may be generated at any time without knowing the actual subscription manager 132 of the service provider 130. This provides a very flexible method for managing ownership.
• multiple network devices 102 may be controlled.
• a device management authority 118 may generate an authorization token 114, either by logging into the eUICC 115 or it may be generated externally. If multiple eUICC's share the same device management authority credentials, device management authority 118 may provide the same authorization token 114 to a single service provider 134.
• the subscription manager 119 may manage all of the eUICC's 115 of all of the network devices 102 using the same authorization token 114. This provides an efficient methodology for controlling multiple eUICC's 115 of multiple network devices 102.
• an authorization token 114 may be utilized to efficiently and securely manage a network device 102 in association with a service provider 134,130.
• the authorization credential 110 in conjunction with a password to generate an authorization token 114 provides a very secure and robust approach.
• the authorization token 114 approach provides security and improves flexibility for the device management authority 118 to manage the operation privileges on the eUICC 115 of the network device 102 for using 3 rd party service providers 134,130, especially in the case when the subscription manager 119,132 does not need to be known to the device management authority 118.
• circuitry of the network device 102 may operate under the control of a program, routine, or the execution of instructions to execute methods or processes in accordance with embodiments of the invention.
• a program may be implemented in firmware or software (e.g. stored in memory and/or other locations) and may be implemented by processors and/or other circuitry.
• processors microprocessor, circuitry, controller, etc.
• processors refer to any type of logic or circuitry capable of executing logic, commands, instructions, software, firmware, functionality, etc.
• mobile or network devices may communicate via one or more wireless communication links through a wireless network that are based on or otherwise support any suitable wireless communication technology.
• the network may comprise a body area network or a personal area network (e.g., an ultra- wideband network).
• the network may comprise a local area network or a wide area network.
• a network device may support or otherwise use one or more of a variety of wireless communication technologies, protocols, or standards such as, for example, CDMA, TDMA, OFDM, OFDMA, WiMAX, and Wi-Fi.
• a network device may support or otherwise use one or more of a variety of corresponding modulation or multiplexing schemes.
• a network device may thus include appropriate components (e.g., air interfaces) to establish and communicate via one or more wireless communication links using the above or other wireless communication technologies.
• a device may comprise a wireless transceiver with associated transmitter and receiver components (e.g., a transmitter and a receiver) that may include various components (e.g., signal generators and signal processors) that facilitate communication over a wireless medium.
• transmitter and receiver components e.g., a transmitter and a receiver
• various components e.g., signal generators and signal processors
• a mobile network device may therefore wirelessly communicate with other mobile devices, cell phones, other wired and wireless computers, Internet web-sites, etc.
• CDMA Code Division Multiple Access
• TDMA Time division multiple access
• FDMA Frequency Division Multiple Access
• OFDMA Orthogonal Frequency- Division Multiple Access
• SC-FDMA Single Carrier FDMA
• a CDMA system can implement a radio technology such as Universal Terrestrial Radio Access (UTRA), CDMA2000, etc.
• UTRA includes Wideband-CDMA (W-CDMA) and other variants of CDMA.
• CDMA2000 covers Interim Standard (IS)-2000, IS-95 and IS-856 standards.
• a TDMA system can implement a radio technology such as Global System for Mobile Communications (GSM).
• GSM Global System for Mobile Communications
• An OFDMA system can implement a radio technology such as Evolved Universal Terrestrial Radio Access; (Evolved UTRA or E- UTRA), Ultra Mobile Broadband (UMB), Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash- OFDM.RTM., etc.
• Universal Terrestrial Radio Access (UTRA) and E-UTRA are part of Universal Mobile Telecommunication System (UMTS).
• 3 GPP Long Term Evolution (LTE) is an upcoming release of UMTS that uses E-UTRA, which employs OFDMA on the downlink and SC-FDMA on the uplink.
• UTRA, E-UTRA, UMTS, LTE and GSM are described in documents from an organization named "3rd Generation Partnership Project” (3 GPP).
• CDMA2000 and UMB are described in documents from an organization named “3rd Generation Partnership Project 2" (3GPP2).
• teachings herein may be incorporated into (e.g., implemented within or performed by) a variety of apparatuses (e.g., devices).
• a phone e.g., a cellular phone
• PDA personal data assistant
• a tablet e.g., a mobile computer
• a laptop computer e.g., a tablet
• an entertainment device e.g., a music or video device
• a headset e.g., headphones, an earpiece, etc.
• a user I/O device e.g., a computer, a server, a point-of-sale device, an entertainment device, a set-top box, or any other suitable device.
• These devices may have different power and data requirements
• a network device may comprise an access device (e.g., a Wi-Fi access point) for a communication system.
• an access device may provide, for example, connectivity to another network (e.g., a wide area network such as the Internet or a cellular network) via a wired or wireless communication link.
• the access device may enable another device (e.g., a Wi-Fi station) to access the other network or some other functionality.
• another device e.g., a Wi-Fi station
• one or both of the devices may be portable or, in some cases, relatively non-portable.
• DSP digital signal processor
• ASIC application specific integrated circuit
• FPGA field programmable gate array
• a general purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine.
• a processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.
• a software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.
• An exemplary storage medium is coupled to the processor such the processor can read information from, and write information to, the storage medium.
• the storage medium may be integral to the processor.
• the processor and the storage medium may reside in an ASIC.
• the ASIC may reside in a user terminal.
• the processor and the storage medium may reside as discrete components in a user terminal.
• the functions described may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software as a computer program product, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium.
• Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another.
• a storage media may be any available media that can be accessed by a computer.
• such computer-readable media can comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer.
• any connection is properly termed a computer-readable medium.
• the software is transmitted from a web site, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave
• the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium.
• Disk and disc includes compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk and blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer-readable media.

Landscapes

• Engineering & Computer Science (AREA)
• Computer Networks & Wireless Communication (AREA)
• Signal Processing (AREA)
• Computer Security & Cryptography (AREA)
• Computer Hardware Design (AREA)
• Computing Systems (AREA)
• General Engineering & Computer Science (AREA)
• Mobile Radio Communication Systems (AREA)
• Telephonic Communication Services (AREA)

Priority Applications (4)

Applications Claiming Priority (4)

Publications (1)

Family

ID=50882543

Family Applications (1)

Country Status (6)

Cited By (1)

Families Citing this family (38)

Citations (1)

Family Cites Families (41)

• 2013
  • 2013-03-06 US US13/787,522 patent/US9264413B2/en not_active Expired - Fee Related
  • 2013-12-06 JP JP2015545883A patent/JP6335917B2/ja not_active Expired - Fee Related
  • 2013-12-06 KR KR1020157017660A patent/KR20150093737A/ko not_active Withdrawn
  • 2013-12-06 CN CN201380062939.4A patent/CN104823408A/zh active Pending
  • 2013-12-06 WO PCT/US2013/073648 patent/WO2014089474A1/en not_active Ceased
  • 2013-12-06 EP EP13812357.5A patent/EP2929655A1/en not_active Withdrawn

Patent Citations (1)

Also Published As

Similar Documents

Legal Events