WO2011029299A1 - 一种变更机器到机器设备的归属网络运营商的方法和系统 - Google Patents
一种变更机器到机器设备的归属网络运营商的方法和系统 Download PDFInfo
- Publication number
- WO2011029299A1 WO2011029299A1 PCT/CN2010/071401 CN2010071401W WO2011029299A1 WO 2011029299 A1 WO2011029299 A1 WO 2011029299A1 CN 2010071401 W CN2010071401 W CN 2010071401W WO 2011029299 A1 WO2011029299 A1 WO 2011029299A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- m2me
- sho
- new
- mcim
- old
- Prior art date
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/60—Subscription-based services using application servers or record carriers, e.g. SIM application toolkits
-
- 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
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/50—Service provisioning or reconfiguring
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
- H04W12/10—Integrity
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/70—Services for machine-to-machine communication [M2M] or machine type communication [MTC]
Definitions
- the present invention relates to a M2M (Machine to Machine) communication technology, and more particularly to a method and system for SHO (Selected Home Operator) change of M2ME (Machine to Machine Equipment).
- M2M Machine to Machine
- SHO Select Home Operator
- M2M communication is a general term for a series of technologies and combinations that implement wireless communication technology to realize data communication and communication between machines and machines, machines and people.
- M2M has two meanings: The first layer is the machine itself, which is called smart device in the embedded field. The second layer means the connection between the machine and the machine, connecting the machines together through the network.
- Machine-based communication is used in a wide range of applications, such as intelligent measurement, remote monitoring, tracking, medical, etc., to make human life more intelligent.
- M2ME Machine to Machine Equipment, M2M equipment
- M2M equipment Machine to Machine Equipment
- M2M In M2M communication, the main long-distance connection technologies include GSM/GPRS/UMTS, and the short-distance connection technologies mainly include 802.1 lb/g, Bluetooth, Zigbee, and RFID.
- M2M is a device-oriented service. Because M2M integrates wireless communication and information technology, it can be used for two-way communication, such as collecting information, setting parameters and sending commands over long distances, thus enabling different application scenarios, such as security monitoring, vending, Cargo tracking, etc. Almost all the equipment involved in daily life is likely to become a potential customer. M2M provides a simple means of establishing real-time data between devices, between remote devices, or with individuals.
- a MCIM application is a set of M2M security data and functions for accessing a 3GPP network (which may also be an IMS network).
- the MCIM can be located on a UICC (Universal Integrated Circuit Card) or in a TRE (The Trusted Environment) functional entity. When the MCIM is located on the UICC, MCIM refers to the USIM. (Universal Subscriber Identity Module) or ISIM (IP Multimedia Services Identity Module).
- the TRE functional entity refers to the functional entity of the trusted environment provided by the M2ME.
- a TRE functional entity can be authenticated by an authorized external proxy whenever needed.
- the MCIM can be installed in the TRE functional entity.
- the M2ME provides hardware and software protection and isolation for the MCIM through the TRE functional entity.
- M2ME provides M2M services in two ways: based on UICC or based on TRE functional entities.
- M2ME provides M2M services based on UICC
- how to change the subscription data remotely that is, change the home network operator of the M2M device, there are two options:
- the remotely provided MCIM is installed in the TRE functional entity through the initial connection provided by the TRE functional entity.
- the disadvantage is that the protection of the MCIM depends on the security of the TRE functional entity. Since the TRE functional entity is implemented on the M2ME, the security of the TRE functional entity is lower than that of the UICC, so the security of the MCIM in the TRE functional entity is not high; Based on the TRE functional entity's solution to change the home network operator of the M2M device, the problem remains that the security of the MCIM is more difficult to guarantee after the MCIM is provided to the TRE functional entity. Summary of the invention
- the technical problem to be solved by the present invention is to propose a method and system for changing the home network operator of the M2M device, and combining the TRE functional entity with the UICC to implement the change of the M2ME home network operator.
- the present invention provides a method for changing a home-to-machine (M2M) device home network operator, including:
- the new Home Network Operator receives the Machine to Machine (M2ME) parameters, and after the M2ME is verified by the Platform Verification Authority (PVA), the M2ME and the registered carrier provided by the old SHO a (RO) connection, providing a new SHO Machine Communication Identity Module (MCIM) to the M2ME; the M2ME installing the new MCIM on a Universal Integrated Circuit Card (UICC); or
- PVA Platform Verification Authority
- MCIM Machine Communication Identity Module
- Manner 2 The new SHO receives the parameters of the M2ME, and after the M2ME is verified by the PVA, the M2ME established by the trusted environment (TRE) functional entity is connected to the RO, and the MCIM of the new SHO is provided to the M2ME; The M2ME installs the new MCIM on the UICC;
- TRE trusted environment
- the UICC and the TRE functional entity are all located on the M2ME.
- the step of the new SHO receiving the M2ME, and the step of providing the MCIM to the M2ME includes:
- the M2ME subscriber sends the M2ME parameters to the new SHO and notifies the M2ME to perform the MCIM re-provisioning;
- the new SHO MCIM is sent to the RO;
- the RO sends the new MCIM to the M2ME over the connection provided by the old SHO.
- the above method can also have the following characteristics:
- the M2ME After the step of the RO sending the new MCIM to the M2ME, the M2ME performs the step of installing the new MCIM on the UICC before performing the step:
- the M2ME deletes the information of the old SHO on the M2ME, and the information of the old SHO includes the MCIM of the old SHO.
- the step of the new SHO receiving the M2ME, and the step of providing the MCIM to the M2ME includes:
- the M2ME subscriber sends the M2ME parameters to the new SHO, and notifies the M2ME to perform the MCIM re-provisioning, and sends the new SHO information and the M2ME parameters to the RO; the RO activates the TRE functional entity on the M2ME;
- the M2ME establishes a connection with the RO through the TRE functional entity, and the RO registers the M2ME in the new SHO;
- the M2ME After the step of the TRE function entity of the RO activation M2ME is performed, before the step of establishing the connection between the M2ME and the RO by the TRE function entity, the M2ME further performs: deleting the information of the old SHO on the M2ME by the M2ME; Or,
- the M2ME After the step of the RO to send the new MCIM to the M2ME, before the step of installing the new MCIM on the UICC by the M2ME, the M2ME further performs: deleting the M2ME on the M2ME Old SHO information;
- the information of the old SHO includes the MCIM of the old SHO.
- the step of the new SHO receiving the M2ME, and the step of providing the MCIM to the M2ME includes:
- the M2ME subscription user sends the M2ME parameters to the new SHO, and notifies the M2ME to perform the MCIM re-provisioning, and sends the new SHO information and the M2ME parameters to the RO;
- the old SHO activates the TRE function entity on the M2ME by means of wireless download (OTA);
- the M2ME establishes a connection with the RO through the TRE functional entity, and the RO is registered in the new SHO.
- the RO sends the new MCIM to the M2ME through a connection established by the TRE functional entity.
- the step of the new SHO receiving the M2ME, and the step of providing the MCIM to the M2ME includes:
- the M2ME subscription user sends the M2ME parameters to the new SHO, and notifies the M2ME to perform the MCIM re-provisioning, and sends the new SHO information and the M2ME parameters to the old SHO;
- the old SHO activates the TRE functional entity on the M2ME by using the OTA mode; the M2ME establishes a connection with the RO through the TRE functional entity, and the RO registers the M2ME in the new SHO;
- the RO sends the new MCIM to the connection through a connection established by the TRE functional entity
- the old SHO In the step of the old SHO activating the TRE function entity on the M2ME, the old SHO also deletes the information of the old SHO on the M2ME; or
- the M2ME Before the step of installing the new MCIM on the UICC, the M2ME further performs: deleting, by the M2ME, the information of the old SHO on the M2ME;
- the information of the old SHO includes the MCIM of the old SHO.
- the M2ME establishes a connection with the RO through the TRE functional entity, and the RO registers the M2ME in the new SHO.
- the steps include:
- the M2ME passes the TRE functional entity with an arbitrarily selected visited network operator (VNO) Establish an initial connection;
- VNO visited network operator
- the VNO contacts the RO, and sends a temporary connection identifier (PCID) received from the M2ME to the RO;
- PCID temporary connection identifier
- the RO generates a set of authentication vectors for the PCID, and sends the same to the VNO;
- the VNO authenticates the PCID and the M2ME by using the authentication vector, and after the authentication is passed, the VNO provides the M2ME with an IP connection to the RO;
- the M2ME contacts the RO through an IP connection provided by the VNO;
- the RO is a new SHO found by the M2ME, or the M2ME discovers a new SHO through the RO;
- the RO connects the new SHO and registers the M2ME at the new SHO.
- the present invention provides a system for changing a home network operator of a machine to machine (M2M) device, including: a machine to machine device (M2ME), a new home network operator (SHO), an old SHO, Platform Verification Authorization Center (PVA) and Registry Operator (RO), where:
- the new SHO is set to receive the parameters of the M2ME, and after the M2ME is verified by the PVA, the connection between the M2ME and the RO provided by the old SHO or the connection between the M2ME and the RO established by the trusted environment (TRE) functional entity is , the new SHO MCIM is provided to the M2ME;
- the M2ME is configured to install the new MCIM onto a universal integrated circuit card (UICC);
- UICC universal integrated circuit card
- the UICC and the TRE functional entity are all located on the M2ME.
- the new SHO is further configured to: after the PVA verifies that the M2ME passes, send the MCIM of the new SHO to the RO;
- the RO is configured to send the new MCIM to the M2ME through a connection provided by an old SHO;
- the M2ME is also arranged to delete information of the old SHO on the M2ME.
- the above system can also have the following characteristics:
- the RO is configured to activate a TRE function entity on the M2ME after receiving the information of the new SHO and the parameter of the M2ME sent by the M2ME subscription user; and the RO is further set to a connection established by the TRE function entity, a new MCIM is sent to the M2ME;
- the M2ME is further configured to establish a connection with the RO through the TRE functional entity, and delete the information of the old SHO on the M2ME;
- the new SHO is further configured to authorize the RO to provide a new SHO MCIM after the M2ME is verified by the PVA.
- the RO is further configured to notify the old SHO that the M2ME changes the SHO after receiving the information of the new SHO sent by the M2ME subscription user and the parameter of the M2ME; and the RO is further set to a connection established by the TRE functional entity, Sending the new MCIM to the M2ME;
- the old SHO is configured to activate a TRE functional entity on the M2ME by means of a wireless download (OTA);
- OTA wireless download
- the M2ME is further configured to establish a connection with the RO through the TRE functional entity, and delete the information of the old SHO on the M2ME;
- the new SHO is further configured to authorize the RO to provide a new SHO MCIM after the M2ME is verified by the PVA.
- the old SHO is configured to activate the TRE functional entity on the M2ME by using the OTA method after receiving the new SHO information and the M2ME parameters sent by the M2ME subscription user;
- the M2ME is further configured to establish a connection with the RO through the TRE functional entity, and delete the information of the old SHO on the M2ME;
- the new SHO is further configured to authorize the RO to provide a new SHO MCIM after the M2ME is verified by the PVA;
- the RO is set to send the new MCIM to the M2ME through a connection established by the TRE functional entity.
- the invention enables the M2M device to combine the initial connection provided by the TRE functional entity and the high security of the UICC to implement the change of the home network operator of the M2ME and ensure the security of the MCIM.
- FIG. 1 is a schematic diagram of an M2ME architecture of a UICC (a TRE functional entity on an M2ME) according to an embodiment of the present invention
- FIG. 2 is a schematic diagram of an M2M system architecture of a UICC (TRE functional entity on the M2ME) according to an embodiment of the present invention
- connection change M2M device home network operator provided by an old SHO according to an embodiment of the present invention
- Embodiment 4 is a schematic diagram of a process of changing a home network operator of an M2M device by RO according to an embodiment of the present invention ( Embodiment 1);
- FIG. 5 is a schematic diagram of a process of changing a home network operator of an M2M device by RO according to an embodiment of the present invention ( Embodiment 2);
- Embodiment 6 is a schematic diagram of a process of changing an M2M device home network operator by using an OTA (Over The Air) method according to an embodiment of the present invention ( Embodiment 1);
- FIG. 7 is a schematic flowchart of a method for changing an M2M device home network operator by using an OTA method according to an embodiment of the present invention (Embodiment 2);
- FIG. 8 is a schematic flowchart of a method for changing an M2M device to a network operator by using an old SHO and an OTA method according to an embodiment of the present invention ( Embodiment 1);
- FIG. 9 is a schematic flowchart of changing an M2M device to a network operator by using an old SHO and an OTA method according to an embodiment of the present invention (Embodiment 2).
- the TRE functional entity and the UICC are combined to implement the change of the M2ME home network operator and ensure the security of the MCIM.
- the SHO can be changed in two ways: Method 1: The new SHO receives the parameters of the M2ME, and the PVA (Platform Validation) After the M2ME is authenticated, the M2ME provides a new SHO MCIM to the M2ME through the connection between the M2ME and the RO (Registration Operator) provided by the old SHO; the M2ME will The new MCIM is installed on a Universal Integrated Circuit Card (UICC);
- UICC Universal Integrated Circuit Card
- Manner 2 The new SHO receives the parameters of the M2ME, and after the M2ME passes the P2, the M2ME and the RO established by the TRE function entity are connected to the M2ME, and the new SHO MCIM is provided to the M2ME; MCIM is installed on the UICC;
- the UICC is located on the M2ME, and the TRE functional entity is located on the M2ME.
- FIG. 1 it is a schematic diagram of an M2ME architecture based on UICC (the TRE functional entity is located on the M2ME) according to an embodiment of the present invention.
- the TRE functional entity is located on the M2ME
- the UICC is installed on the M2ME.
- FIG. 2 it is a schematic diagram of an M2M system architecture based on UICC (the TRE functional entity is located on the M2ME) according to an embodiment of the present invention.
- the M2ME uses PICD (Provisional Connectivity Identity) as its private identity.
- PICD Provisional Connectivity Identity
- the TRE functional entity refers to the trusted environment provided by M2ME. It provides hardware and software-based protection and isolation for provisioning, storing, executing and managing MCIM.
- the security of PCID is also guaranteed by TRE functional entities, such as PCID security. Storage, retrieval and use are all implemented by the TRE functional entity.
- a TRE functional entity can be authenticated by an authorized external agent whenever needed.
- the UICC is installed on the M2ME.
- VNO Visit Network Operator
- RO it can have the following functions:
- DPF Discovery and Registration Function
- ICF Initial Connection Function
- SHO which provides operational services for M2ME, authorizes DPF to provide M2ME with SHO-generated or DPF-represented MCIM generated by SHO.
- PVA used for insurance certificate M2ME.
- the MCIM when the MCIM is located on the UICC, the MCIM refers to the USIM/ISIM.
- MCIM is used instead of USIM/ISIM regardless of whether MCIM is located on the UICC.
- both the UICC and TRE functional entities are located on the M2ME.
- the initial MCIM can be pre-installed on the UICC or it can be installed on the UICC via a remotely provided method.
- the TRE functional entity is used by the M2ME to establish an initial connection with the visited network operator.
- FIG. 3 is a schematic diagram of a flow chart of changing the M2M device home network operator by using the connection provided by the old SHO according to the embodiment of the present invention.
- the UICC and TRE functional entities are located on the M2ME, and the old SHO MCIM is installed on the UICC. Since the M2ME subscription user and the old SHO contract are full or other reasons, the M2ME subscription user wants to change the SHO, the M2ME subscription user contacts the new SHO, and contacts the M2ME to notify the M2ME to perform the MCIM re-provisioning to change the M2ME SHO.
- the specific process of the M2M device belonging to the network operator includes the following steps:
- Step 301 When the M2ME subscription user and the old SHO contract are full or other reasons, the M2ME subscription user wants to change the SHO, the M2ME subscription user contacts the new SHO, and sends the M2ME related parameters.
- Step 302 The M2ME subscription user contacts the M2ME to notify the M2ME to perform the MCIM re-provisioning.
- Step 303 The new SHO requests the PVA to verify the M2ME.
- Step 304 The PVA verifies the M2ME.
- Step 305 If the verification is passed, the PVA reports the verification success status information to the new SHO.
- Step 306 The new SHO sends its MCIM to the RO (DPF function).
- Step 307 The RO uses the connection provided by the old SHO to securely send the new MCIM to the UICC of the M2ME.
- the new MCIM can be downloaded to the UICC of the M2ME through the OTA method.
- a new MCIM is activated.
- the old SHO related information is deleted, including the old SHO's MCIM and credentials.
- Step 308 Before the M2ME provides the downloaded new MCIM to the UICC, the M2ME deletes the information of the old SHO, including the old SHO MCIM, the credential and the like.
- Step 309 The M2ME sends a message to the old SHO, informing the old SHO that the information related to the old SHO has been deleted, including the old SHO MCIM, the credential and the like.
- Step 310 The old SHO returns an acknowledgement message to the M2ME indicating that the above message has been received. If necessary, the old SHO deletes information related to M2ME.
- Step 311 The M2ME sends an acknowledgment message that the old MCIM has been deleted to the RO (DPF function), and forwards it to the new SHO through the RO (DPF function), and performs security filtering when the RO (DPF function) forwards the acknowledgment message to prevent Any sensitive information about the old SHO is obtained by the new SHO.
- Step 312 With the help of RO (DPF function), M2ME installs the new SHO's MCIM onto the UICC.
- RO can help M2ME install the new SHO MCIM on the UICC, and can use various methods of the prior art, which will not be described in detail here.
- Step 313 RO (DPF function) reports the success/failure status information to the new SHO.
- FIG. 4 is a schematic diagram of a second embodiment of the present invention, in which a UICC-based M2M device home network operator is changed by RO (Embodiment 1).
- the UICC and TRE functional entities are all located on the M2ME, and the old SHO MCIM is installed on the UICC.
- the M2ME subscription user contacts the new SHO and RO, and the M2ME notifies the M2ME to perform the re-provisioning of the MCIM to change the home network operation of the M2ME, because the M2ME subscription user is in agreement with the old SHO or other reasons, the M2ME subscription user wants to change the SHO. Business.
- the process of specifically changing the home network operator of the M2M device includes the following steps:
- Step 401 When the M2ME subscription user and the old SHO contract are full, and want to change the SHO, the M2ME subscription user contacts the new SHO, and sends the M2ME related parameters.
- Step 402 The M2ME subscription user contacts the M2ME to notify the M2ME to perform the MCIM re-provisioning.
- Step 403 The M2ME subscription user contacts the RO, and sends the M2ME newly signed SHO information and
- Step 404 The RO contacts the M2ME through the connection provided by the old SHO, and activates the TRE functional entity on the M2ME.
- Step 405 The RO helps the M2ME to delete the old SHO information on the UICC; for example, delete the old SHO credential and delete the old SHO MCIM.
- M2ME can also delete the old SHO information on the UICC after the TRE is activated; for example, delete the old SHO credential and delete the old SHO MCIM.
- Step 406 The RO sends a message to the old SHO to notify the old SHO that the M2ME has been deleted.
- Step 407 The old SHO returns an acknowledgement message to the RO, which is used to indicate that the old SHO has received the above information.
- Step 408 The M2ME establishes an initial connection with the arbitrarily selected VNO through the TRE functional entity. M2ME decodes network information and attaches to any VNO through standard GSM/UMTS principles. In the attach message, the M2ME sends a temporary connection ID (PCID, Provisional Connectivity ID) to the VNO.
- PCID Provisional Connectivity ID
- Step 409 The VNO contacts the RO (ICF function) and sends the PCID to the RO (ICF function). can) . Note that in some cases, the RO can be located at the VNO.
- Step 410 After receiving the PCID, the RO (ICF function) generates a set of authentication vectors (AVs) for the PCID.
- AVs authentication vectors
- Step 411 The RO sends the generated authentication vector (AVs) to the VNO.
- Step 412 The VNO uses the authentication vector to authenticate the PCID/M2ME, which may be, but is not limited to, AKA (Authentication and Key Agreement) authentication.
- AKA Authentication and Key Agreement
- Step 413 After the authentication is successful, the VNO provides the M2ME with an IP connection to the RO. The VNO assigns an IP address to the M2ME.
- Step 414 The M2ME contacts the RO through the IP connection provided by the VNO network.
- Step 415 M2ME finds a new SHO through the help of RO, or RO itself is
- the new SHO discovery process can use the OMA (Open Mobile Alliance) BOOTSTRAP (Bootstrap Protocol).
- OMA Open Mobile Alliance
- BOOTSTRAP Bootstrap Protocol
- Step 416 The RO connects to the new SHO and registers with the new SHO to connect to the M2ME of the new SHO network.
- Step 417 The new SHO requests the PVA (or requests the PVA through the RO) to verify the authenticity and integrity of the M2ME.
- Step 418 The PVA verifies the authenticity and integrity of the M2ME.
- Step 419 The PVA sends the verification result to the new SHO.
- Step 420 If the verification is successful, the new SHO contacts the RO (DPF function) and authorizes the RO (DPF function) to provide the MCIM to the M2ME.
- Step 421 RO (DPF function) sends a new SHO MCIM to the M2ME.
- Step 422 The M2ME installs the new SHO MCIM to the UICC.
- Step 423 The M2ME supplies the MCIM success/failure status information to the RO (DPF function) 4 report.
- Step 424 RO (DPF function) supplies MCIM success/failure status information to the new SHO.
- FIG. 5 is a schematic flowchart of a method for changing a UICC-based M2M device home network operator by using RO according to an embodiment of the present invention (Embodiment 2).
- the UICC and TRE functional entities are all located on the M2ME, and the old SHO MCIM is installed on the UICC.
- the M2ME subscription user and the old SHO contract are full or other reasons, the M2ME subscription user wants to change the SHO, the M2ME subscription user contacts the new SHO and RO, and simultaneously contacts the M2ME to notify the M2ME to perform the MCIM re-provisioning to change the M2ME SHO.
- the process of the M2M device belonging to the network operator includes the following steps:
- Step 501 When the M2ME subscription user and the old SHO contract are full, and want to change the SHO, the M2ME subscription user contacts the new SHO, and sends the M2ME related parameters.
- Step 502 The M2ME subscription user contacts the M2ME to notify the M2ME to perform the MCIM re-provisioning.
- Step 503 The M2ME subscription user contacts the RO, and sends the M2ME newly signed SHO information and the M2ME related parameters.
- Step 504 The RO contacts the M2ME through the connection provided by the old SHO, and activates the TRE functional entity on the M2ME.
- Step 505 The M2ME establishes an initial connection with the arbitrarily selected VNO through the TRE functional entity. M2ME decodes network information and attaches to any VNO through standard GSM/UMTS principles. In the attach message, the M2ME sends a PCID to the VNO.
- Step 506 The VNO contacts the RO (ICF function) and sends the PCID to the RO (ICF function). Note that in some cases, the RO can be located at VNO.
- Step 507 After receiving the PCID, the RO (ICF function) generates a set of authentication vectors (AVs) for the PCID.
- AVs authentication vectors
- Step 508 The RO sends the generated authentication vector (AVs) to the VNO.
- Step 509 The VNO uses the authentication vector to authenticate the PCID/M2ME, which may be, but is not limited to, AKA authentication.
- Step 510 After the authentication is successful, the VNO provides the M2ME with an IP connection to the RO. The VNO assigns an IP address to the M2ME. Step 511: The M2ME contacts the RO through an IP connection provided by the VNO network.
- Step 512 The M2ME discovers the new SHO through the help of the RO, or the RO itself discovers the new SHO for the M2ME.
- the new SHO discovery process can use OMA BOOTSTRAP.
- Step 513 The RO connects to the new SHO and registers the M2ME to connect to the new SHO network in the new SHO.
- Step 514 The new SHO requests the PVA (or requests the PVA through the RO) to verify the authenticity and integrity of the M2ME.
- Step 515 The PVA verifies the authenticity and integrity of the M2ME.
- Step 516 The PVA sends the verification result to the new SHO.
- Step 517 If the verification is successful, the new SHO contacts the RO (DPF function) and authorizes the RO
- DPF function Provides MCIM to M2ME.
- Step 518 RO (DPF function) sends the new SHO's MCIM to the M2ME.
- Step 519 Before installing the MCIM obtained from the new SHO, the M2ME deletes the old SHO information on the UICC, such as the old SHO credential, and deletes the old SHO MCIM.
- Step 520 After deleting the old MCIM on the UICC, the M2ME sends a message to the old SHO that the old MCIM has been deleted through the RO.
- Step 521 The old SHO returns an acknowledgement message to the M2ME through the RO, which is used to indicate that the old SHO has received the above information. If necessary, the RO forwards the confirmation message to the new SHO. Privacy filtering is performed before the RO forwards the acknowledgment message to prevent sensitive information about the old SHO from being obtained by the new SHO.
- Step 522 The M2ME installs the MCIM onto the UICC either directly or with the help of the RO (DPF).
- Step 523 After the M2ME directly installs the MCIM on the UICC, the M2ME sends the MCIM success/failure status information to the RO (the DPF function is installed. If the M2ME is installed with the MCIM on the UICC with the help of the RO (DPF), then RO ( DPF ) already knows if MCIM has been successfully installed on the UICC.
- Step 524 RO (DPF function) to supply MCIM success/failure status to the new SHO report Information.
- FIG. 6 is a schematic diagram of a process for changing a home network operator of an M2M device by using an OTA (Over The Air) method in the RO mode according to the embodiment of the present invention (Embodiment 1).
- OTA Over The Air
- the UICC and TRE functional entities are all located on the M2ME, and the old SHO MCIM is installed on the UICC.
- the M2ME subscription user and the old SHO contract are full or other reasons, the M2ME subscription user wants to change the SHO, the M2ME subscription user contacts the new SHO and RO, and simultaneously contacts the M2ME to notify the M2ME to perform the MCIM re-provisioning to change the M2ME SHO.
- the process of the M2M device belonging to the network operator includes the following steps:
- Step 601 When the M2ME subscription user and the old SHO contract are full, and want to change the SHO, the M2ME subscription user contacts the new SHO and sends the M2ME related parameters.
- Step 602 The M2ME subscription user contacts the M2ME to notify the M2ME to perform the MCIM re-provisioning.
- Step 603 The M2ME subscription user contacts the RO, and sends the M2ME newly signed SHO information and the M2ME related parameters.
- Step 604 The RO contacts the old SHO, and informs the old SHO to change the M2ME related information of the home network operator.
- Step 605 The old SHO activates the TRE functional entity on the M2ME by means of OTA. And delete the old SHO information on the M2ME UICC, such as the old SHO credential, and delete the old SHO MCIM.
- Step 606 The M2ME establishes an initial connection with the arbitrarily selected VNO through the TRE functional entity. M2ME decodes network information and attaches to any VNO through standard GSM/UMTS principles. In the attach message, the M2ME sends a PCID to the VNO.
- Step 607 The VNO contacts the RO (ICF function) and sends the PCID to the RO (ICF function). Note that in some cases, the RO can be located at VNO.
- Step 608 After receiving the PCID, the RO (ICF function) generates a set of authentication vectors (AVs) for the PCID.
- AVs authentication vectors
- Step 609 The RO sends the generated authentication vector (AVs) to the VNO.
- Step 611 After the authentication is successful, the VNO provides the M2ME with an IP connection to the RO. The VNO assigns an IP address to the M2ME.
- Step 612 The M2ME contacts the RO through an IP connection provided by the VNO network.
- Step 613 The M2ME discovers the new SHO through the help of the RO, or the RO itself discovers the new SHO for the M2ME.
- the new SHO discovery process can use OMA BOOTSTRAP.
- Step 614 The RO connects to the new SHO and registers with the new SHO to connect to the M2ME of the new SHO network.
- Step 615 The new SHO requests the PVA (or requests the PVA through the RO) to verify the authenticity and integrity of the M2ME.
- Step 616 The PVA verifies the authenticity and integrity of the M2ME.
- Step 617 The PVA sends the verification result to the new SHO.
- Step 618 If the verification is successful, the new SHO contacts the RO (DPF function) and authorizes the RO (DPF function) to provide the MCIM to the M2ME.
- Step 619 RO (DPF function) sends the new SHO's MCIM to the M2ME.
- Step 620 The M2ME installs the new SHO MCIM to the UICC.
- Step 621 The M2ME reports the MCIM success/failure status information to the RO (DPF function).
- Step 622 RO (DPF function) supplies MCIM success/failure status information to the new SHO.
- FIG. 7 is a schematic diagram of a process for changing a home network operator of an M2M device by using an OTA method according to an embodiment of the present invention (Embodiment 2).
- the UICC and TRE functional entities are all located on the M2ME, and the old SHO MCIM is installed on the UICC.
- the M2ME subscription user and the old SHO contract are full or other reasons, the M2ME subscription user wants to change the SHO, the M2ME subscription user contacts the new SHO and RO, and contacts the M2ME to notify the M2ME to perform the MCIM re-provisioning to change the M2ME SHO.
- the process of specifically changing the home network operator of the M2M device includes the following steps:
- Step 701 When the M2ME subscription user and the old SHO contract are full, and want to change the SHO, the M2ME subscription user contacts the new SHO, and sends the M2ME related parameters.
- Step 702 The M2ME subscription user contacts the M2ME to notify the M2ME to perform the MCIM re-provisioning.
- Step 703 The M2ME subscription user contacts the RO, and sends the M2ME newly signed SHO information and the M2ME related parameters.
- Step 704 The RO contacts the old SHO, notifying the old SHO to change the M2ME related information of the SHO.
- Step 705 The old SHO activates the TRE functional entity on the M2ME by means of OTA.
- Step 706 The M2ME establishes an initial connection with the arbitrarily selected VNO through the TRE functional entity. M2ME decodes network information and attaches to any VNO through standard GSM/UMTS principles. In the attach message, the M2ME sends a PCID to the VNO.
- Step 707 The VNO contacts the RO (ICF function) and sends the PCID to the RO (ICF function). Note that in some cases, the RO can be located at VNO.
- Step 708 After receiving the PCID, the RO (ICF function) generates a set of authentication vectors (AVs) for the PCID.
- AVs authentication vectors
- Step 709 The RO sends the generated authentication vector (AVs) to the VNO.
- Step 710 The VNO uses the authentication vector to authenticate the PCID/M2ME, which may be, but is not limited to, AKA authentication.
- Step 711 After the authentication is successful, the VNO provides the M2ME with an IP connection to the RO. The VNO assigns an IP address to the M2ME.
- Step 712 The M2ME contacts the RO through an IP connection provided by the VNO network.
- Step 713 M2ME discovers the new SHO through the help of RO, or RO itself is
- M2ME found a new SHO.
- the new SHO discovery process can use OMA BOOTSTRAP.
- Step 714 The RO connects to the new SHO and registers with the new SHO to connect to the new SHO network. M2ME.
- Step 715 The new SHO requests the PVA (or requests the PVA through the RO) to verify the authenticity and integrity of the M2ME.
- Step 716 The PVA verifies the authenticity and integrity of the M2ME.
- Step 717 The PVA sends the verification result to the new SHO.
- Step 718 If the verification is successful, the new SHO contacts the RO (DPF function) and authorizes the RO (DPF function) to provide the MCIM to the M2ME.
- Step 719 RO (DPF function) sends the new SHO's MCIM to the M2ME.
- Step 720 Before installing the MCIM obtained from the new SHO, the M2ME deletes the old SHO information on the UICC, such as the old SHO credential, and deletes the old SHO MCIM.
- Step 721 After deleting the old MCIM on the UICC, the M2ME sends a message to the old SHO that the old MCIM has been deleted through the RO.
- Step 722 The old SHO returns an acknowledgement message to the M2ME through the RO, which is used to indicate that the old SHO has received the above information. If necessary, the RO forwards the confirmation message to the new SHO. Privacy filtering is performed before the RO forwards the acknowledgment message to prevent sensitive information about the old SHO from being obtained by the new SHO.
- Step 723 The M2ME installs the MCIM onto the UICC either directly or with the help of the RO (DPF).
- Step 724 After the M2ME directly installs the MCIM on the UICC, the M2ME sends the MCIM success/failure status information to the RO (the DPF function is installed. If the M2ME is installed with the MCIM on the UICC with the help of the RO (DPF), then RO ( DPF ) already knows if MCIM has been successfully installed on the UICC.
- Step 725 RO (DPF function) supplies MCIM success/failure status information to the new SHO report.
- FIG. 8 is a schematic diagram of a second embodiment of the present invention, in which the M2M device home network operator is changed by the old SHO and the OTA method (Embodiment 1).
- the UICC and TRE functional entities are all located on the M2ME, and the old SHO MCIM is installed on the UICC.
- the M2ME subscription user contacts the new SHO and RO when the M2ME subscription user wants to change the home network operator, and the M2ME notifies the M2ME to perform the re-provisioning of the MCIM to change the M2ME.
- SHO The process of specifically changing the home network operator of the M2M device includes the following steps:
- Step 801 When the M2ME subscription user is full of the old SHO contract and wants to change the SHO, the M2ME subscription user contacts the new SHO and sends the M2ME related parameters.
- Step 802 The M2ME subscription user contacts the M2ME to notify the M2ME to perform the MCIM re-provisioning.
- Step 803 The M2ME subscription user contacts the old SHO, and sends the M2ME newly signed SHO information and the M2ME related parameters.
- Step 804 The old SHO activates the TRE functional entity on the M2ME by means of OTA. And delete the old SHO information on the M2ME UICC, such as the old SHO credential, and delete the old SHO MCIM.
- Step 805 The M2ME establishes an initial connection with the arbitrarily selected VNO through the TRE functional entity.
- M2ME decodes network information and attaches to any VNO through standard GSM/UMTS principles.
- the M2ME sends a PCID to the VNO.
- Step 806 The VNO contacts the RO (ICF function) and sends the PCID to the RO (ICF function). Note that in some cases, the RO can be located at VNO.
- Step 807 After receiving the PCID, the RO (ICF function) generates a set of authentication vectors (AVs) for the PCID.
- AVs authentication vectors
- Step 808 The RO sends the generated authentication vector (AVs) to the VNO.
- Step 809 The VNO uses the authentication vector to authenticate the PCID/M2ME, which may be, but is not limited to, AKA authentication.
- Step 810 After the authentication is successful, the VNO provides the M2ME with an IP connection to the RO. VNO is
- M2ME assigns an IP address.
- Step 811 The M2ME contacts the RO through the IP connection provided by the VNO network.
- Step 812 The M2ME discovers the new SHO through the help of the RO, or, RO itself is M2ME discovered a new SHO.
- the new SHO discovery process can use OMA BOOTSTRAP.
- Step 813 The RO connects to the new SHO and registers the M2ME to connect to the new SHO network in the new SHO.
- Step 814 The new SHO requests the PVA (or requests the PVA through the RO) to verify the authenticity and integrity of the M2ME.
- Step 815 The PVA verifies the authenticity and integrity of the M2ME.
- Step 816 The PVA sends the verification result to the new SHO.
- Step 817 If the verification is successful, the new SHO contacts the RO (DPF function) and authorizes the RO (DPF function) to provide the new MCIM to the M2ME.
- Step 818 RO (DPF function) sends the new SHO's MCIM to the M2ME.
- Step 819 The M2ME installs the new SHO MCIM onto the UICC.
- Step 820 The M2ME reports the MCIM success/failure status information to the RO (DPF function).
- Step 821 RO (DPF function) supplies MCIM success/failure status information to the new SHO report.
- FIG. 9 is a schematic diagram of a process for changing a home network operator of an M2M device by using an old SHO using an OTA method according to an embodiment of the present invention (Embodiment 2).
- the UICC and TRE functional entities are all located on the M2ME, and the old SHO MCIM is installed on the UICC.
- the M2ME subscription user and the old SHO contract are full or other reasons, the M2ME subscription user wants to change the SHO, the M2ME subscription user contacts the new SHO and RO, and simultaneously contacts the M2ME to notify the M2ME to perform the MCIM re-provisioning to change the M2ME SHO.
- the process of the M2M device belonging to the network operator includes the following steps:
- Step 901 When the M2ME subscription user and the old SHO contract are full, and want to change the SHO, the M2ME subscription user contacts the new SHO, and sends the M2ME related parameters.
- Step 902 The M2ME subscription user contacts the M2ME to notify the M2ME to perform MCIM re-provisioning.
- Step 903 The M2ME subscription user contacts the old SHO, and sends the M2ME newly signed SHO information and the M2ME related parameters.
- Step 904 The old SHO activates the TRE functional entity on the M2ME by means of OTA.
- Step 905 The M2ME establishes an initial connection with the arbitrarily selected VNO through the TRE functional entity.
- M2ME decodes network information and attaches to any VNO through standard GSM/UMTS principles.
- the M2ME sends a PCID to the VNO.
- Step 906 The VNO contacts the RO (ICF function) and sends the PCID to the RO (ICF function). Note that in some cases, the RO can be located at VNO.
- Step 907 After receiving the PCID, the RO (ICF function) generates a set of authentication vectors (AVs) for the PCID.
- AVs authentication vectors
- Step 908 The RO sends the generated authentication vector (AVs) to the VNO.
- Step 909 The VNO uses the authentication vector to authenticate the PCID/M2ME, which may be, but is not limited to, AKA authentication.
- Step 910 After the authentication is successful, the VNO provides an IP connection to the RO for the M2ME. VNO is
- M2ME assigns an IP address.
- Step 911 The M2ME contacts the RO through the IP connection provided by the VNO network.
- Step 912 The M2ME discovers the new SHO through the help of the RO, or the RO itself discovers the new SHO for the M2ME.
- the new SHO discovery process can use OMA BOOTSTRAP.
- Step 913 The RO connects to the new SHO and registers the M2ME to connect to the new SHO network in the new SHO.
- Step 914 The new SHO requests the PVA (or requests the PVA through the RO) to verify the authenticity and integrity of the M2ME.
- Step 915 The PVA verifies the authenticity and integrity of the M2ME.
- Step 916 The PVA sends the verification result to the new SHO.
- Step 917 If the verification is successful, the new SHO contacts the RO (DPF function) and authorizes the RO (DPF function) to provide the MCIM to the M2ME.
- Step 919 Before installing the MCIM obtained from the new SHO, the M2ME deletes the old SHO information on the UICC, such as the old SHO credential, and deletes the old SHO MCIM.
- Step 920 After deleting the old MCIM on the UICC, the M2ME sends a message to the old SHO that the old MCIM has been deleted through the RO.
- Step 921 The old SHO returns an acknowledgement message to the M2ME through the RO, which is used to indicate that the old SHO has received the above information. If necessary, the RO forwards the confirmation message to the new SHO. Privacy filtering is performed before the RO forwards the acknowledgment message to prevent sensitive information about the old SHO from being obtained by the new SHO.
- Step 922 The M2ME installs the MCIM onto the UICC either directly or with the help of the RO (DPF).
- Step 923 After the M2ME directly installs the MCIM on the UICC, the M2ME sends the MCIM success/failure status information to the RO (the DPF function is installed. If the M2ME is installed with the MCIM on the UICC with the help of the RO (DPF), then RO ( DPF ) already knows if MCIM has been successfully installed on the UICC.
- Step 924 RO (DPF function) supplies MCIM success/failure status information to the new SHO report.
- the system for changing the home network operator of the M2M device in the embodiment of the present invention includes: M2ME, new SHO, old SHO, PVA, and RO,
- the new SHO is set to receive the parameters of the M2ME, and after the M2ME is verified by the PVA, the connection between the M2ME and the RO provided by the old SHO or the connection between the M2ME and the RO established by the TRE functional entity, the new SHO MCIM is provided to M2ME;
- the M2ME is configured to install the new MCIM on the UICC
- the UICC and the TRE functional entity are all located on the M2ME.
- the new SHO is also set to verify that the M2ME passes after the PVA, and the new SHO will be
- the MCIM is sent to the RO; the RO is set to send the new MCIM to the M2ME through a connection provided by the old SHO; the M2ME is further configured to delete information of the old SHO on the M2ME, such as Old MCIM.
- the RO is configured to activate the TRE function entity on the M2ME after receiving the information of the new SHO and the parameter of the M2ME sent by the M2ME subscription user; and the connection established by the RO through the TRE function entity, the new MCIM Sending to the M2ME; the M2ME is further configured to establish a connection with the RO through the TRE functional entity, and set to delete information of the old SHO on the M2ME, such as the old MCIM; the new SHO is also set to After the M2ME is verified by the PVA, the RO is authorized to provide the MCIM of the new SHO.
- the RO is configured to notify the old SHO of the M2ME to change the SHO after receiving the information of the new SHO and the parameter of the M2ME sent by the M2ME subscription user; and the connection established by the RO through the TRE function entity, the new The MCIM is sent to the M2ME; the old SHO is set to activate a TRE functional entity on the M2ME by means of an OTA method; the M2ME is further configured to establish a connection with the RO through the TRE functional entity, and is configured to delete the M2ME The old SHO information; the new SHO is further configured to authorize the RO to provide the MCIM of the new SHO after the M2ME is verified by the PVA.
- the old SHO is configured to activate the TRE functional entity on the M2ME by using the OTA mode after receiving the new SHO information and the M2ME parameter sent by the M2ME subscription user; the M2ME is further configured to establish a connection with the RO through the TRE functional entity. And, configured to delete information of the old SHO on the M2ME, such as the old MCIM; the new SHO is further configured to authorize the RO to provide the MCIM of the new SHO after the M2ME is verified by the PVA; The new MCIM is sent to the M2ME through a connection established by the TRE functional entity.
- the present invention provides a method and a system for changing a home network operator of an M2M device.
- the M2M device implements the change of the home network operator of the M2ME and ensures the security of the MCIM. Sex.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Mobile Radio Communication Systems (AREA)
Description
一种变更机器到机器设备的归属网络运营商的方法和系统
技术领域
本发明涉及 M2M ( Machine to Machine, 机器到机器) 的通信技术, 尤 其涉及一种 M2ME ( Machine to Machine Equipment, M2M设备) 的 SHO ( Selected Home Operator , 归属网络运营商) 变更的方法和系统。
背景技术
M2M通信是指应用无线通信技术, 实现机器与机器、机器与人之间的数 据通信和交流的一系列技术及其组合的总称。 M2M有两层含义: 第一层是机 器本身, 在嵌入式领域称为智能设备。 第二层意思是机器和机器之间的连接, 通过网络把机器连接在一起。 机器类通信的应用范围非常广泛, 例如智能测 量、 远程监控、 跟踪、 医疗等, 使人类生活更加智能化。 与传统的人与人之 间的通信相比, M2ME ( Machine to Machine Equipment, M2M设备)数量 巨大, 应用领域广泛, 具有巨大的市场前景。
在 M2M通信中, 主要的远距离连接技术包括 GSM/GPRS/UMTS, 近距 离连接技术主要有 802.1 lb/g、 蓝牙、 Zigbee、 RFID等。 M2M属于针对设备 的业务, 由于 M2M整合了无线通信和信息技术, 可用于双向通信, 如远距 离收集信息、 设置参数和发送指令, 因此可实现不同的应用方案, 如安全监 测、 自动售货、 货物跟踪等。 几乎所有日常生活中涉及到的设备都有可能成 为潜在的服务对象。 M2M提供了设备实时数据在系统之间、 远程设备之间、 或与个人之间建立无线连接的简单手段。
M2M通信的一个挑战是部署的 M2M设备的远程安全管理。 为此, 我们 需要解决如何为 M2ME远程提供签约数据即 MCIM (机器通信身份模块, Machine Communication Identity Module ) , 并防止 MCIM在供应过程中被攻 击者获得并使用。 MCIM应用是一组为接入 3GPP网络(也可以是 IMS网络) 的 M2M安全数据和功能。 MCIM可以位于 UICC ( Universal Integrated Circuit Card, 通用集成电路卡 )上, 也可以位于一个 TRE ( The Trusted environment, 可信环境)功能实体中。 当 MCIM位于 UICC上时, MCIM即是指 USIM
( Universal Subscriber Identity Module , 通用用户身份模块) 或 ISIM ( IP Multimedia Services Identity Module, IP 多媒体服务身份模块)。 TRE功能实 体是指 M2ME提供的可信环境的功能实体, 一个 TRE功能实体可以在任何 需要的时候被授权的外部代理验证。 MCIM 可以安装在 TRE功能实体中, M2ME通过 TRE功能实体为 MCIM提供软硬件保护和隔离。
目前, M2ME提供 M2M服务通常釆用两种方式:基于 UICC或基于 TRE 功能实体。
当 M2ME基于 UICC来提供 M2M服务时, 如何远程改变签约数据, 即 变更 M2M设备归属网络运营商, 有两种方案:
1、 不能远程改变签约数据的方案, 这种方案虽然可以方便地为 M2ME 提供 M2M服务,但是, 当 M2M服务签约用户想改变 M2M服务的运营商时, 必须更换 UICC, 这使得 M2ME的维护非常困难, 即使可能, 也是代价高昂, 因此这种方案无法实现对 M2ME的 MCIM的远程管理;
2、 可以远程改变签约数据的方案, 这种方案当 UICC发布时就确定归属 网络运营商的话, 不存在 MCIM的初始提供问题, 但当 UICC在发布后再确 定归属网络运营商的话,初始提供 MCIM给 UICC是需要解决的问题; 另夕卜, 这种方案通过改变 IMSI ( International Mobile Subscriber Identity, 国际移动用 户识别码) 的方式来改变运营商, 这样虽然可以方便地管理 M2ME, 但这种 方案涉及 IMSI在不同移动运营商网络之间的传递, 从而增加了 M2ME签约 数据的安全风险; 同时在改变 IMSI的过程中, UICC可能中断与任何运营商 的连接;
当 M2ME基于 TRE功能实体来提供 M2M服务时 , 通过 TRE功能实体 提供的初始连接, 将远程提供的 MCIM安装在 TRE功能实体中。 其缺点是 MCIM的保护有赖于 TRE功能实体的安全性, 由于 TRE功能实体是 M2ME 上实现, 使得 TRE功能实体的安全性比 UICC要低, 因此 MCIM在 TRE功 能实体中的安全性并不高; 基于 TRE功能实体的变更 M2M设备的归属网络 运营商的解决方案, 问题仍然在于 MCIM提供给 TRE功能实体后, MCIM的 安全性比较难以得到保证。
发明内容
本发明要解决的技术问题就是提出一种 M2M设备归属网络运营商变更 的方法和系统,将 TRE功能实体和 UICC结合起来, 实现变更 M2ME归属网 络运营商。
为了解决上述技术问题, 本发明提供一种机器到机器 ( M2M )设备归属 网络运营商变更的方法, 包括:
方式一: 新的归属网络运营商(SHO )接收到机器到机器设备 ( M2ME ) 的参数,经平台验证授权中心( PVA )验证所述 M2ME通过后,通过旧的 SHO 提供的 M2ME与注册运营商 (RO ) 的连接, 将新的 SHO的机器通信身份模 块( MCIM )提供给所述 M2ME; 所述 M2ME将所述新的 MCIM安装到通用 集成电路卡(UICC )上; 或者,
方式二: 新的 SHO接收到 M2ME的参数 , 经 PVA验证所述 M2ME通 过后, 通过可信环境(TRE )功能实体建立的 M2ME与 RO的连接, 将新的 SHO的 MCIM提供给所述 M2ME; 所述 M2ME将所述新的 MCIM安装到 UICC上;
其中, 所述 UICC和 TRE功能实体均位于所述 M2ME上。
在所述方式一中, 所述新的 SHO接收 M2ME的参数,将 MCIM提供给 所述 M2ME的步骤包括:
M2ME签约用户将 M2ME的参数发送给新的 SHO , 并通知 M2ME执行 MCIM重新供应;
新的 SHO经 PVA验证所述 M2ME通过后, 将新的 SHO的 MCIM发送 给 RO;
RO通过旧的 SHO提供的连接, 将所述新的 MCIM发送给所述 M2ME。 上述方法还可具有以下特点:
在 RO将新的 MCIM发送给所述 M2ME的步骤执行之后, 所述 M2ME 将所述新的 MCIM安装到 UICC上的步骤执行之前, 还执行:
所述 M2ME删除所述 M2ME上的旧的 SHO的信息, 所述旧的 SHO的 信息包括旧的 SHO的 MCIM。
在所述方式二中 , 所述新的 SHO接收 M2ME的参数 , 将 MCIM提供给 所述 M2ME的步骤包括:
M2ME签约用户将 M2ME的参数发送给新的 SHO , 并通知 M2ME执行 MCIM重新供应, 以及, 将新的 SHO的信息和 M2ME的参数发送给 RO; 所述 RO激活 M2ME上的 TRE功能实体;
所述 M2ME通过 TRE功能实体与 RO建立连接, RO在新的 SHO注册 所述 M2ME;
所述新的 SHO经 PVA验证所述 M2ME通过后,授权 RO提供新的 SHO 的 MCIM;
所述 RO通过 TRE功能实体建立的连接,将所述新的 MCIM发送给所述
M2ME。
上述方法还可具有以下特点:
在所述 RO激活 M2ME上的 TRE功能实体的步骤执行之后,所述 M2ME 通过 TRE功能实体与 RO建立连接的步骤执行之前, 还执行: 所述 M2ME 删除所述 M2ME上的旧的 SHO的信息; 或者,
在所述 RO将所述新的 MCIM发送给所述 M2ME的步骤执行之后,所述 M2ME将所述新的 MCIM安装到 UICC上的步骤执行之前, 还执行: 所述 M2ME删除所述 M2ME上的旧的 SHO的信息;
其中, 所述旧的 SHO的信息包括旧的 SHO的 MCIM。
在所述方式二中, 所述新的 SHO接收 M2ME的参数, 将 MCIM提供给 所述 M2ME的步骤包括:
M2ME签约用户将 M2ME的参数发送给新的 SHO , 并通知 M2ME执行 MCIM重新供应, 以及, 将新的 SHO的信息和 M2ME的参数发送给 RO;
RO通知旧的 SHO所述 M2ME变更 SHO;
所述旧的 SHO通过无线下载( OTA )方式激活 M2ME上的 TRE功能实 体;
所述 M2ME通过 TRE功能实体与 RO建立连接, RO在新的 SHO注册
所述 M2ME;
所述新的 SHO经 PVA验证所述 M2ME通过后,授权 RO提供新的 SHO 的 MCIM;
RO 通过 TRE 功能实体建立的连接, 将所述新的 MCIM发送给所述 M2ME。
在所述方式二中, 所述新的 SHO接收 M2ME的参数, 将 MCIM提供给 所述 M2ME的步骤包括:
M2ME签约用户将 M2ME的参数发送给新的 SHO , 并通知 M2ME执行 MCIM重新供应,以及,将新的 SHO的信息和 M2ME的参数发送给旧的 SHO;
所述旧的 SHO通过 OTA方式激活 M2ME上的 TRE功能实体; 所述 M2ME通过 TRE功能实体与 RO建立连接, RO在新的 SHO注册 所述 M2ME;
所述新的 SHO经 PVA验证所述 M2ME通过后,授权 RO提供新的 SHO 的 MCIM;
RO 通过 TRE 功能实体建立的连接, 将所述新的 MCIM发送给所述
M2ME。
上述方法还可具有以下特点:
在旧的 SHO激活 M2ME上的 TRE功能实体的步骤中, 所述旧的 SHO 还同时删除所述 M2ME上的旧的 SHO的信息; 或者,
在所述 RO将所述新的 MCIM发送给所述 M2ME的步骤执行之后,所述
M2ME将所述新的 MCIM安装到 UICC上的步骤执行之前, 还执行: 所述 M2ME删除所述 M2ME上的旧的 SHO的信息;
其中, 所述旧的 SHO的信息包括旧的 SHO的 MCIM。
上述方法还可具有以下特点:
所述 M2ME通过 TRE功能实体与 RO建立连接, RO在新的 SHO注册 所述 M2ME的步骤包括:
所述 M2ME通过 TRE功能实体与任意选择的拜访网络运营商 ( VNO )
建立初始连接;
所述 VNO联系 RO , 并将从所述 M2ME接收到的临时连接标识( PCID ) 发送给所述 RO;
所述 RO针对所述 PCID生成一组认证向量, 并发送给所述 VNO;
所述 VNO使用所述认证向量对所述 PCID和 M2ME进行认证, 认证通 过后 , VNO为所述 M2ME提供到 RO的 IP连接;
所述 M2ME通过 VNO提供的 IP连接联系 RO;
所述 RO为 M2ME发现新的 SHO, 或者, 所述 M2ME通过 RO发现新 的 SHO;
所述 RO连接所述新的 SHO, 并在所述新的 SHO注册所述 M2ME。
为了解决上述技术问题, 本发明提供一种机器到机器(M2M )设备归属 网络运营商变更的系统, 包括: 机器到机器设备(M2ME ) 、 新的归属网络 运营商( SHO )、 旧的 SHO、平台验证授权中心( PVA )和注册运营商( RO ) , 其中:
所述新的 SHO设置成接收到 M2ME的参数, 经 PVA验证所述 M2ME 通过后,通过旧的 SHO提供的 M2ME与 RO的连接或者通过可信环境( TRE ) 功能实体建立的 M2ME与 RO的连接,将新的 SHO的 MCIM提供给 M2ME;
所述 M2ME设置成将所述新的 MCIM安装到通用集成电路卡( UICC ) 上;
其中, 所述 UICC和 TRE功能实体均位于所述 M2ME上。
上述系统还可具有以下特点:
所述新的 SHO还设置成经 PVA验证所述 M2ME通过后, 将新的 SHO 的 MCIM发送给 RO;
所述 RO设置成通过旧的 SHO提供的连接,将所述新的 MCIM发送给所 述 M2ME;
所述 M2ME还设置成删除所述 M2ME上的旧的 SHO的信息。
上述系统还可具有以下特点:
所述 RO设置成接收到 M2ME签约用户发送的新的 SHO的信息和 M2ME 的参数后, 激活 M2ME上的 TRE功能实体; 以及, 所述 RO还设置成通过 TRE功能实体建立的连接, 将所述新的 MCIM发送给所述 M2ME;
所述 M2ME还设置成通过 TRE功能实体与 RO建立连接, 以及,删除所 述 M2ME上的旧的 SHO的信息;
所述新的 SHO还设置成经 PVA验证所述 M2ME通过后, 授权 RO提供 新的 SHO的 MCIM。
上述系统还可具有以下特点:
所述 RO还设置成接收到 M2ME签约用户发送的新的 SHO 的信息和 M2ME的参数后, 通知旧的 SHO所述 M2ME变更 SHO; 以及, 所述 RO还 设置成通过 TRE功能实体建立的连接,将所述新的 MCIM发送给所述 M2ME;
所述旧的 SHO设置成通过无线下载( OTA )方式激活 M2ME上的 TRE 功能实体;
所述 M2ME还设置成通过 TRE功能实体与 RO建立连接, 以及,删除所 述 M2ME上的旧的 SHO的信息;
所述新的 SHO还设置成经 PVA验证所述 M2ME通过后, 授权 RO提供 新的 SHO的 MCIM。
上述系统还可具有以下特点:
所述旧的 SHO设置成接收到 M2ME签约用户发送的新的 SHO的信息和 M2ME的参数后 , 通过 OTA方式激活 M2ME上的 TRE功能实体;
所述 M2ME还设置成通过 TRE功能实体与 RO建立连接, 以及,删除所 述 M2ME上的旧的 SHO的信息;
所述新的 SHO还设置成经 PVA验证所述 M2ME通过后, 授权 RO提供 新的 SHO的 MCIM;
RO设置成通过 TRE功能实体建立的连接, 将所述新的 MCIM发送给所 述 M2ME。
本发明使 M2M设备结合 TRE功能实体提供的初始连接和 UICC的高安 全性, 实现变更 M2ME的归属网络运营商, 并保证 MCIM的安全性。 附图概述
图 1 是本发明实施例的 UICC ( TRE功能实体在 M2ME上 ) 的 M2ME 架构示意图;
图 2是本发明实施例的 UICC ( TRE功能实体在 M2ME上 ) 的 M2M系 统架构示意图;
图 3是本发明实施例的使用旧的 SHO提供的连接变更 M2M设备归属网 络运营商的流程示意图;
图 4 是本发明实施例的通过 RO变更 M2M设备归属网络运营商的流程 示意图 (实施方式 1 ) ;
图 5是本发明实施例的 通过 RO变更 M2M设备归属网络运营商的流程 示意图 (实施方式 2 ) ;
图 6 是本发明实施例的通过 RO釆用 OTA ( Over The Air, 无线下载) 方式变更 M2M设备归属网络运营商的流程示意图 (实施方式 1 ) ;
图 7 是本发明实施例的通过 RO釆用 OTA方式变更 M2M设备归属网络 运营商的流程示意图 (实施方式 2 ) ;
图 8 是本发明实施例的通过旧的 SHO釆用 OTA方式变更 M2M设备归 属网络运营商的流程示意图 (实施方式 1 ) ;
图 9 是本发明实施例的通过旧的 SHO釆用 OTA方式变更 M2M设备归 属网络运营商的流程示意图 (实施方式 2 ) 。
本发明的较佳实施方式
在本发明中,将 TRE功能实体和 UICC结合起来, 实现变更 M2ME归属 网络运营商, 并保证 MCIM的安全性。 其中, 可釆用两种方式变更 SHO: 方式一: 新的 SHO接收到 M2ME的参数, 经 PVA ( Platform Validation
Authority, 平台验证授权中心)验证所述 M2ME通过后 , 通过旧的 SHO提供 的 M2ME与 RO ( Registration Operator, 注册运营商) 的连接, 将新的 SHO 的 MCIM提供给 M2ME; 所述 M2ME将所述新的 MCIM安装到通用集成电 路卡(UICC ) 上;
方式二: 新的 SHO接收到 M2ME的参数, 经 PVA验证所述 M2ME通 过后 ,通过 TRE功能实体建立的 M2ME与 RO的连接,将新的 SHO的 MCIM 提供给 M2ME; 所述 M2ME将所述新的 MCIM安装到 UICC上;
其中,所述 UICC位于所述 M2ME上,所述 TRE功能实体位于所述 M2ME 上。
下面结合附图及具体实施例对本发明进行详细说明。
如图 1所示, 是本发明实施例的基于 UICC ( TRE功能实体位于 M2ME 上 )的 M2ME架构示意图。 在该架构中 TRE功能实体位于 M2ME上, 以及, UICC安装在 M2ME上。
如图 2所示, 是本发明实施例的基于 UICC ( TRE功能实体位于 M2ME 上) 的 M2M系统架构示意图。
M2ME以 PICD ( Provisional Connectivity Identity, 临时连接身份)作为 其私有标识。 为了使 M2ME注册到与将来选择的归属运营商无关的 3GPP网 络, PCID需要通过供应商安装在 M2ME上。 PCID的格式与 IMSI相同。 其 中, TRE功能实体是指 M2ME提供的可信环境, 它为供应、 存储、 执行和管 理 MCIM提供了基于硬件和软件的保护和隔离, PCID的安全也由 TRE功能 实体来保证, 如 PCID的安全存储、 检索和使用都由 TRE功能实体实现。 一 个 TRE功能实体可以在任何需要的时候被授权的外部代理验证。 UICC安装 在 M2ME上。
VNO ( Visited Network Operator, 拜访网络运营商) , 它为 M2ME提供 初始连接, 用于初始注册、 MCIM和信任状的提供。
RO, 它可以具有如下功能:
1 ) MCIM的下载和提供功能(DPF, MCIM Download and Provisioning Function ) ;
2 )发现和注册功能(DRF, Discovery and Registration Function ) ;
3 )初始连接功能(ICF, Initial Connectivity Function ) 。
SHO, 为 M2ME提供运营服务,授权 DPF为 M2ME提供 SHO生成的或 DPF代表 SHO生成的 MCIM。
PVA, 用于险证 M2ME。
在本发明中, 当 MCIM位于 UICC上时, MCIM即是指 USIM/ISIM。 为 了描述方便, 在本发明中, 无论 MCIM是否位于 UICC上, 都只使用 MCIM, 而不用 USIM/ISIM。
在本发明中, UICC和 TRE功能实体都位于 M2ME上。 初始 MCIM可 以预安装在 UICC上, 也可以通过远程提供的方法安装 UICC上。 当通过远 程提供的方法将初始 MCIM安装在 UICC上时, TRE功能实体用于 M2ME 与拜访网络运营商建立初始连接。
图 3是本发明实施例的釆用方式一,使用旧的 SHO提供的连接变更 M2M 设备归属网络运营商的流程示意图。
如图 3所示, UICC和 TRE功能实体均位于 M2ME上, UICC上安装有 旧的 SHO的 MCIM。 由于 M2ME签约用户与旧的 SHO合约满或其它原因, M2ME签约用户想改变 SHO时, M2ME签约用户联系新的 SHO , 同时联系 M2ME通知 M2ME执行 MCIM的重新供应 , 以改变 M2ME的 SHO。 具体变 更 M2M设备归属网络运营商的流程包括以下步骤:
步骤 301: 由于 M2ME签约用户与旧的 SHO合约满或其它原因, M2ME 签约用户想改变 SHO时, 则 M2ME签约用户联系新的 SHO , 并发送 M2ME 相关参数。
步骤 302: M2ME签约用户联系 M2ME,通知 M2ME执行 MCIM重新供 应。
步骤 303: 新的 SHO请求 PVA验证 M2ME。
步骤 304: PVA验证 M2ME。
步骤 305: 如果验证通过, 则 PVA向新 SHO报告验证成功状态信息。 步骤 306: 新的 SHO将它的 MCIM发送给 RO ( DPF功能) 。
步骤 307: RO利用旧的 SHO提供的连接, 安全的将新的 MCIM发送到 M2ME的 UICC上。
具体, 可以通过 OTA方式将新的 MCIM下载到 M2ME的 UICC上。 在
OTA过程的最后阶段, 激活新的 MCIM。 同时删除旧的 SHO相关信息, 包 括旧的 SHO的 MCIM和信任状等信息。
步骤 308: 在 M2ME将下载的新的 MCIM提供给 UICC之前, M2ME删 除其上旧的 SHO的信息, 包括旧的 SHO的 MCIM, 信任状等信息。
步骤 309: M2ME向旧的 SHO发送消息, 通知旧的 SHO已经删除了与 旧的 SHO有关的信息, 包括旧的 SHO的 MCIM, 信任状等信息。
步骤 310: 旧的 SHO向 M2ME返回确认消息,用于指示已经收到以上消 息。 必要的话, 旧的 SHO删除与 M2ME相关的信息。
步骤 311 : M2ME向 RO ( DPF功能 )发送已经删除旧的 MCIM的确认 消息, 并通过 RO ( DPF功能 )转发给新的 SHO , 在 RO ( DPF功能)转发确 认消息时要进行安全过滤,以防止任何关于旧的 SHO的敏感信息被新的 SHO 获得。
步骤 312: 在 RO ( DPF功能 ) 的帮助下, M2ME将新的 SHO的 MCIM 安装到 UICC上。
其中, RO如何帮助 M2ME将新的 SHO的 MCIM安装到 UICC上,可釆 用现有技术的多种方式, 此处不再详述。
步骤 313: RO ( DPF功能) 向新的 SHO报告供应成功 /失败状态信息。 步骤 314: SHO向 RO ( DRF功能 )发送消息,用来登记新 SHO与 M2ME 的签约信息, 用于今后的发现查询。
图 4是本发明实施例的釆用方式二,通过 RO变更基于 UICC的 M2M设 备归属网络运营商的流程示意图 (实施方式 1 ) 。
如图 4所示, UICC和 TRE功能实体均位于 M2ME上, UICC上安装有 旧的 SHO的 MCIM。 由于 M2ME签约用户与旧的 SHO合约满或其它原因, M2ME签约用户想改变 SHO时, M2ME签约用户联系新的 SHO和 RO , 同 时联系 M2ME通知 M2ME执行 MCIM的重新供应 , 以改变 M2ME的归属网 络运营商。 具体变更 M2M设备归属网络运营商的流程包括以下步骤:
步骤 401: M2ME签约用户与旧的 SHO合约满,想改变 SHO时,则 M2ME 签约用户联系新的 SHO, 并发送 M2ME相关参数。
步骤 402: M2ME签约用户联系 M2ME,通知 M2ME执行 MCIM重新供 应。
步骤 403: M2ME签约用户联系 RO, 发送 M2ME新签约的 SHO信息和
M2ME相关参数。
步骤 404: RO通过旧的 SHO提供的连接联系 M2ME, 激活 M2ME上的 TRE功能实体。
步骤 405: RO帮助 M2ME删除 UICC上旧的 SHO信息;如删除旧的 SHO 的信任状, 同时删除旧的 SHO的 MCIM。
M2ME也可以在 TRE激活后自行删除 UICC上旧的 SHO信息; 如删除 旧的 SHO的信任状, 同时删除旧的 SHO的 MCIM。
其中, RO如何帮助 M2ME删除 UICC上旧的 SHO信息, 可釆用现有技 术的多种方式, 此处不再详述。
步骤 406: RO向旧的 SHO发送消息通知旧的 SHO , M2ME已经删除了
UICC上旧的 SHO的 MCIM。
步骤 407: 旧的 SHO向 RO返回确认消息, 用于指示旧的 SHO收到了上 述信息。
步骤 408: M2ME通过 TRE功能实体与任意选择的 VNO建立初始连接。 M2ME通过标准的 GSM/UMTS 原则来解码网络信息并且附着到任意一个 VNO。 在附着消息中, M2ME 向 VNO 发送一个临时连接标识 (PCID, Provisional Connectivity ID ) 。
步骤 409: VNO联系 RO ( ICF功能) , 并将 PCID发送给 RO ( ICF功
能) 。 注意, 在某些情况下, RO可以位于 VNO。
步骤 410: RO ( ICF功能)收到 PCID之后, 针对该 PCID生成一组认证 向量(AVs ) 。
步骤 411 : RO将生成的认证向量(AVs )发送给 VNO。
步骤 412: VNO使用认证向量对 PCID/M2ME进行认证, 可以但不限于 釆用 AKA ( Authentication and Key Agreement, 认证和密钥协商 )认证。
步骤 413: 认证成功后, VNO为 M2ME提供到 RO的 IP连接。 VNO为 M2ME分配 IP地址。
步骤 414: M2ME通过 VNO网络提供的 IP连接联系 RO。
步骤 415: M2ME通过 RO的帮助, 发现新的 SHO, 或者, RO 自己为
M2ME发现新的 SHO。 新的 SHO发现过程可以使用 OMA ( Open Mobile Alliance,开放的移动联盟)BOOTSTRAP(即 Bootstrap Protocol,引导协议)。
步骤 416: RO连接新的 SHO并在新的 SHO注册要连接新的 SHO网络 的 M2ME。
步骤 417: 新的 SHO请求 PVA (或通过 RO请求 PVA )验证 M2ME的 真实性和完整性。
步骤 418: PVA验证 M2ME的真实性和完整性。
步骤 419: PVA将验证结果发送给新的 SHO。
步骤 420: 如果验证成功, 新的 SHO联系 RO ( DPF功能), 并授权 RO ( DPF功能 )提供 MCIM给 M2ME。
步骤 421: RO ( DPF功能 )发送新的 SHO的 MCIM给 M2ME。
步骤 422: M2ME将新的 SHO的 MCIM安装到 UICC上。
步骤 423: M2ME向 RO ( DPF功能 ) 4艮告供应 MCIM成功 /失败状态信 息。
步骤 424: RO ( DPF功能 ) 向新的 SHO 告供应 MCIM成功 /失败状态 信息。
图 5是本发明实施例的釆用方式二,通过 RO变更基于 UICC的 M2M设 备归属网络运营商的流程示意图 (实施方式 2 ) 。
如图 5所示, UICC和 TRE功能实体均位于 M2ME上, UICC上安装有 旧的 SHO的 MCIM。 由于 M2ME签约用户与旧的 SHO合约满或其它原因, M2ME签约用户想改变 SHO时, M2ME签约用户联系新的 SHO和 RO , 同 时联系 M2ME通知 M2ME执行 MCIM的重新供应 , 以改变 M2ME的 SHO。 具体变更 M2M设备归属网络运营商的流程包括以下步骤:
步骤 501: M2ME签约用户与旧的 SHO合约满,想改变 SHO时,则 M2ME 签约用户联系新的 SHO, 并发送 M2ME相关参数。
步骤 502: M2ME签约用户联系 M2ME ,通知 M2ME执行 MCIM重新供 应。
步骤 503: M2ME签约用户联系 RO, 发送 M2ME新签约的 SHO的信息 和 M2ME相关参数。
步骤 504: RO通过旧的 SHO提供的连接联系 M2ME, 激活 M2ME上的 TRE功能实体。
TRE功能实体激活后, 旧的 MCIM将停止工作。
步骤 505: M2ME通过 TRE功能实体与任意选择的 VNO建立初始连接。 M2ME通过标准的 GSM/UMTS 原则来解码网络信息并且附着到任意一个 VNO。 在附着消息中 , M2ME向 VNO发送一个 PCID。
步骤 506: VNO联系 RO ( ICF功能) , 并将 PCID发送给 RO ( ICF功 能) 。 注意, 在某些情况下, RO可以位于 VNO。
步骤 507: RO ( ICF功能)收到 PCID之后, 针对该 PCID生成一组认证 向量(AVs ) 。
步骤 508: RO将生成的认证向量(AVs )发送给 VNO。
步骤 509: VNO使用认证向量对 PCID/M2ME进行认证, 可以但不限于 釆用 AKA认证。
步骤 510: 认证成功后, VNO为 M2ME提供到 RO的 IP连接。 VNO为 M2ME分配 IP地址。
步骤 511 : M2ME通过 VNO网络提供的 IP连接联系 RO。
步骤 512: M2ME通过 RO的帮助, 发现新的 SHO, 或者, RO 自己为 M2ME发现新的 SHO。 新的 SHO发现过程可以使用 OMA BOOTSTRAP。
步骤 513: RO连接新的 SHO并在新的 SHO注册要连接新的 SHO网络 的 M2ME。
步骤 514: 新的 SHO请求 PVA (或通过 RO请求 PVA )验证 M2ME的 真实性和完整性。
步骤 515: PVA验证 M2ME的真实性和完整性。
步骤 516: PVA将验证结果发送给新的 SHO。
步骤 517: 如果验证成功, 新的 SHO联系 RO ( DPF功能), 并授权 RO
( DPF功能 )提供 MCIM给 M2ME。
步骤 518: RO ( DPF功能)发送新的 SHO的 MCIM给 M2ME。
步骤 519: 在安装从新的 SHO处获得的 MCIM之前, M2ME删除 UICC 上旧的 SHO的信息, 如旧的 SHO的信任状, 同时删除旧的 SHO的 MCIM。
步骤 520: 在删除 UICC上旧的 MCIM后, M2ME通过 RO向旧的 SHO 发送已经删除旧的 MCIM的消息。
步骤 521: 旧的 SHO通过 RO向 M2ME返回一条确认消息, 用于指示旧 的 SHO收到了上述信息。 如果必要, RO将该确认消息转发给新的 SHO。 在 RO转发确认消息之前要进行私密性过滤, 用来防止关于旧的 SHO的敏感信 息被新的 SHO获得。
步骤 522: M2ME直接或在 RO ( DPF )的帮助下,将 MCIM安装到 UICC 上。
步骤 523: 当 M2ME直接将 MCIM安装到 UICC上之后, M2ME向 RO ( DPF功能 告供应 MCIM成功 /失败状态信息。如果 M2ME是在 RO( DPF ) 的帮助下, 将 MCIM安装到 UICC上的, 则 RO ( DPF ) 已经知道 MCIM是 否已经成功安装在 UICC上。
步骤 524: RO ( DPF功能) 向新的 SHO报告供应 MCIM成功 /失败状态
信息。
图 6是本发明实施例的釆用方式二, 通过 RO釆用 OTA ( Over The Air, 无线下载)方式变更 M2M设备归属网络运营商的流程示意图(实施方式 1 )。
如图 6所示, UICC和 TRE功能实体均位于 M2ME上, UICC上安装有 旧的 SHO的 MCIM。 由于 M2ME签约用户与旧的 SHO合约满或其它原因, M2ME签约用户想改变 SHO时, M2ME签约用户联系新的 SHO和 RO , 同 时联系 M2ME通知 M2ME执行 MCIM的重新供应 , 以改变 M2ME的 SHO。 具体变更 M2M设备归属网络运营商的流程包括以下步骤:
步骤 601: M2ME签约用户与旧的 SHO合约满,想改变 SHO时,则 M2ME 签约用户联系新的 SHO, 并发送 M2ME相关参数。
步骤 602: M2ME签约用户联系 M2ME,通知 M2ME执行 MCIM重新供 应。
步骤 603: M2ME签约用户联系 RO, 发送 M2ME新签约的 SHO的信息 和 M2ME相关参数。
步骤 604: RO联系旧的 SHO , 通知旧的 SHO要改变归属网络运营商的 M2ME相关信息。
步骤 605: 旧的 SHO通过 OTA方式激活 M2ME上的 TRE功能实体。 并 删除 M2ME的 UICC上旧的 SHO的信息, 如旧的 SHO的信任状, 同时删除 旧的 SHO的 MCIM。
步骤 606: M2ME通过 TRE功能实体与任意选择的 VNO建立初始连接。 M2ME通过标准的 GSM/UMTS 原则来解码网络信息并且附着到任意一个 VNO。 在附着消息中 , M2ME向 VNO发送一个 PCID。
步骤 607: VNO联系 RO ( ICF功能) , 并将 PCID发送给 RO ( ICF功 能) 。 注意, 在某些情况下, RO可以位于 VNO。
步骤 608: RO ( ICF功能)收到 PCID之后, 针对该 PCID生成一组认证 向量(AVs ) 。
步骤 609: RO将生成的认证向量(AVs )发送给 VNO。
步骤 610: VNO使用认证向量对 PCID/M2ME进行认证, 可以但不限于 釆用 AKA认证。
步骤 611 : 认证成功后, VNO为 M2ME提供到 RO的 IP连接。 VNO为 M2ME分配 IP地址。
步骤 612: M2ME通过 VNO网络提供的 IP连接联系 RO。
步骤 613: M2ME通过 RO的帮助, 发现新的 SHO, 或者, RO 自己为 M2ME发现新的 SHO。 新的 SHO发现过程可以使用 OMA BOOTSTRAP。
步骤 614: RO连接新的 SHO并在新的 SHO注册要连接新的 SHO网络 的 M2ME。
步骤 615: 新的 SHO请求 PVA (或通过 RO请求 PVA )验证 M2ME的 真实性和完整性。
步骤 616: PVA验证 M2ME的真实性和完整性。
步骤 617: PVA将验证结果发送给新的 SHO。
步骤 618: 如果验证成功, 新的 SHO联系 RO ( DPF功能), 并授权 RO ( DPF功能 )提供 MCIM给 M2ME。
步骤 619: RO ( DPF功能)发送新的 SHO的 MCIM给 M2ME。
步骤 620: M2ME将新的 SHO的 MCIM安装到 UICC上。
步骤 621 : M2ME向 RO ( DPF功能 ) 告供应 MCIM成功 /失败状态信 息。
步骤 622: RO ( DPF功能) 向新的 SHO 告供应 MCIM成功 /失败状态 信息。
图 7是本发明实施例的釆用方式二, 通过 RO釆用 OTA方式变更 M2M 设备归属网络运营商的流程示意图 (实施方式 2 ) 。
如图 7所示, UICC和 TRE功能实体均位于 M2ME上, UICC上安装有 旧的 SHO的 MCIM。 由于 M2ME签约用户与旧的 SHO合约满或其它原因, M2ME签约用户想改变 SHO时, M2ME签约用户联系新的 SHO和 RO , 同 时联系 M2ME通知 M2ME执行 MCIM的重新供应, 以改变 M2ME的 SHO。
具体变更 M2M设备归属网络运营商的流程包括以下步骤:
步骤 701: M2ME签约用户与旧的 SHO合约满,想改变 SHO时,则 M2ME 签约用户联系新的 SHO, 并发送 M2ME相关参数。
步骤 702: M2ME签约用户联系 M2ME,通知 M2ME执行 MCIM重新供 应。
步骤 703: M2ME签约用户联系 RO, 发送 M2ME新签约的 SHO的信息 和 M2ME相关参数。
步骤 704: RO联系旧的 SHO, 通知旧的 SHO要改变 SHO的 M2ME相 关信息。
步骤 705: 旧的 SHO通过 OTA方式激活 M2ME上的 TRE功能实体。
TRE功能实体激活后, 旧的 MCIM将停止工作。
步骤 706: M2ME通过 TRE功能实体与任意选择的 VNO建立初始连接。 M2ME通过标准的 GSM/UMTS 原则来解码网络信息并且附着到任意一个 VNO。 在附着消息中 , M2ME向 VNO发送一个 PCID。
步骤 707: VNO联系 RO ( ICF功能) , 并将 PCID发送给 RO ( ICF功 能) 。 注意, 在某些情况下, RO可以位于 VNO。
步骤 708: RO ( ICF功能)收到 PCID之后, 针对该 PCID生成一组认证 向量(AVs ) 。
步骤 709: RO将生成的认证向量(AVs )发送给 VNO。
步骤 710: VNO使用认证向量对 PCID/M2ME进行认证,可以但不限于釆 用 AKA认证。
步骤 711 : 认证成功后, VNO为 M2ME提供到 RO的 IP连接。 VNO为 M2ME分配 IP地址。
步骤 712: M2ME通过 VNO网络提供的 IP连接联系 RO。
步骤 713: M2ME通过 RO的帮助, 发现新的 SHO, 或者, RO 自己为
M2ME发现新的 SHO。 新的 SHO发现过程可以使用 OMA BOOTSTRAP。
步骤 714: RO连接新的 SHO并在新的 SHO注册要连接新的 SHO网络
的 M2ME。
步骤 715: 新的 SHO请求 PVA (或通过 RO请求 PVA )验证 M2ME的 真实性和完整性。
步骤 716: PVA验证 M2ME的真实性和完整性。
步骤 717: PVA将验证结果发送给新的 SHO。
步骤 718: 如果验证成功, 新的 SHO联系 RO ( DPF功能), 并授权 RO ( DPF功能 )提供 MCIM给 M2ME。
步骤 719: RO ( DPF功能 )发送新的 SHO的 MCIM给 M2ME 。
步骤 720: 在安装从新的 SHO处获得的 MCIM之前, M2ME删除 UICC 上旧的 SHO的信息, 如旧的 SHO的信任状, 同时删除旧的 SHO的 MCIM。
步骤 721: 在删除 UICC上旧的 MCIM后, M2ME通过 RO向旧的 SHO 发送已经删除旧的 MCIM的消息。
步骤 722: 旧的 SHO通过 RO向 M2ME返回一条确认消息, 用于指示旧 的 SHO收到了上述信息。 如果必要, RO将该确认消息转发给新的 SHO。 在 RO转发确认消息之前要进行私密性过滤, 用来防止关于旧的 SHO的敏感信 息被新的 SHO获得。
步骤 723: M2ME直接或在 RO ( DPF )的帮助下,将 MCIM安装到 UICC 上。
步骤 724: 当 M2ME直接将 MCIM安装到 UICC上之后, M2ME向 RO ( DPF功能 告供应 MCIM成功 /失败状态信息。如果 M2ME是在 RO( DPF ) 的帮助下, 将 MCIM安装到 UICC上的, 则 RO ( DPF ) 已经知道 MCIM是 否已经成功安装在 UICC上。
步骤 725: RO ( DPF功能 ) 向新的 SHO报告供应 MCIM成功 /失败状态 信息。
图 8是本发明实施例的釆用方式二, 通过旧的 SHO釆用 OTA方式变更 M2M设备归属网络运营商的流程示意图 (实施方式 1 ) 。
如图 8所示, UICC和 TRE功能实体均位于 M2ME上, UICC上安装有 旧的 SHO的 MCIM。 由于 M2ME签约用户与旧的 SHO合约满或其它原因, M2ME签约用户想改变归属网络运营商时, M2ME签约用户联系新的 SHO 和 RO,同时联系 M2ME通知 M2ME执行 MCIM的重新供应 ,以改变 M2ME 的 SHO。 具体变更 M2M设备归属网络运营商的流程包括以下步骤:
步骤 801: M2ME签约用户与旧的 SHO合约满,想改变 SHO时,则 M2ME 签约用户联系新的 SHO, 并发送 M2ME相关参数。
步骤 802: M2ME签约用户联系 M2ME,通知 M2ME执行 MCIM重新供 应。
步骤 803: M2ME签约用户联系旧的 SHO, 发送 M2ME新签约的 SHO 的信息和 M2ME相关参数。
步骤 804: 旧的 SHO通过 OTA方式激活 M2ME上的 TRE功能实体。 并 删除 M2ME的 UICC上旧的 SHO的信息, 如旧的 SHO的信任状, 同时删除 旧的 SHO的 MCIM。
步骤 805: M2ME通过 TRE功能实体与任意选择的 VNO建立初始连接。
M2ME通过标准的 GSM/UMTS 原则来解码网络信息并且附着到任意一个 VNO。 在附着消息中 , M2ME向 VNO发送一个 PCID。
步骤 806: VNO联系 RO ( ICF功能) , 并将 PCID发送给 RO ( ICF功 能) 。 注意, 在某些情况下, RO可以位于 VNO。
步骤 807: RO ( ICF功能)收到 PCID之后, 针对该 PCID生成一组认证 向量(AVs ) 。
步骤 808: RO将生成的认证向量(AVs )发送给 VNO。
步骤 809: VNO使用认证向量对 PCID/M2ME进行认证, 可以但不限于 釆用 AKA认证。
步骤 810: 认证成功后, VNO为 M2ME提供到 RO的 IP连接。 VNO为
M2ME分配 IP地址。
步骤 811 : M2ME通过 VNO网络提供的 IP连接联系 RO。
步骤 812: M2ME通过 RO的帮助, 发现新的 SHO, 或者, RO 自己为
M2ME发现新的 SHO。 新的 SHO发现过程可以使用 OMA BOOTSTRAP。 步骤 813: RO连接新的 SHO并在新的 SHO注册要连接新的 SHO网络 的 M2ME。
步骤 814: 新的 SHO请求 PVA (或通过 RO请求 PVA )验证 M2ME的 真实性和完整性。
步骤 815: PVA验证 M2ME的真实性和完整性。
步骤 816: PVA将验证结果发送给新的 SHO。
步骤 817: 如果验证成功, 新的 SHO联系 RO ( DPF功能), 并授权 RO ( DPF功能 )提供新 MCIM给 M2ME。
步骤 818: RO ( DPF功能)发送新的 SHO的 MCIM给 M2ME。
步骤 819: M2ME将新的 SHO的 MCIM安装到 UICC上。
步骤 820: M2ME向 RO ( DPF功能) 告供应 MCIM成功 /失败状态信 息。
步骤 821 : RO ( DPF功能 ) 向新的 SHO报告供应 MCIM成功 /失败状态 信息。
图 9是本发明实施例的釆用方式二, 通过旧的 SHO釆用 OTA方式变更 M2M设备归属网络运营商的流程示意图 (实施方式 2 ) 。
如图 9所示, UICC和 TRE功能实体均位于 M2ME上, UICC上安装有 旧的 SHO的 MCIM。 由于 M2ME签约用户与旧的 SHO合约满或其它原因, M2ME签约用户想改变 SHO时, M2ME签约用户联系新的 SHO和 RO , 同 时联系 M2ME通知 M2ME执行 MCIM的重新供应 , 以改变 M2ME的 SHO。 具体变更 M2M设备归属网络运营商的流程包括以下步骤:
步骤 901: M2ME签约用户与旧的 SHO合约满,想改变 SHO时,则 M2ME 签约用户联系新的 SHO, 并发送 M2ME相关参数。
步骤 902: M2ME签约用户联系 M2ME,通知 M2ME执行 MCIM重新供 应。
步骤 903: M2ME签约用户联系旧的 SHO, 发送 M2ME新签约的 SHO 的信息和 M2ME相关参数。
步骤 904: 旧的 SHO通过 OTA方式激活 M2ME上的 TRE功能实体。
TRE功能实体激活后, 旧的 MCIM将停止工作。
步骤 905: M2ME通过 TRE功能实体与任意选择的 VNO建立初始连接。
M2ME通过标准的 GSM/UMTS 原则来解码网络信息并且附着到任意一个 VNO。 在附着消息中 , M2ME向 VNO发送一个 PCID。
步骤 906: VNO联系 RO ( ICF功能) , 并将 PCID发送给 RO ( ICF功 能) 。 注意, 在某些情况下, RO可以位于 VNO。
步骤 907: RO ( ICF功能)收到 PCID之后, 针对该 PCID生成一组认证 向量(AVs ) 。
步骤 908: RO将生成的认证向量(AVs )发送给 VNO。
步骤 909: VNO使用认证向量对 PCID/M2ME进行认证, 可以但不限于 釆用 AKA认证。
步骤 910: 认证成功后, VNO为 M2ME提供到 RO的 IP连接。 VNO为
M2ME分配 IP地址。
步骤 911 : M2ME通过 VNO网络提供的 IP连接联系 RO。
步骤 912: M2ME通过 RO的帮助, 发现新的 SHO, 或者, RO 自己为 M2ME发现新的 SHO。 新的 SHO发现过程可以使用 OMA BOOTSTRAP。
步骤 913: RO连接新的 SHO并在新的 SHO注册要连接新的 SHO网络 的 M2ME。
步骤 914: 新的 SHO请求 PVA (或通过 RO请求 PVA )验证 M2ME的 真实性和完整性。
步骤 915: PVA验证 M2ME的真实性和完整性。
步骤 916: PVA将验证结果发送给新的 SHO。
步骤 917: 如果验证成功, 新的 SHO联系 RO ( DPF功能), 并授权 RO ( DPF功能)提供 MCIM给 M2ME。
步骤 918: RO ( DPF功能)发送新的 SHO的 MCIM给 M2ME。
步骤 919: 在安装从新的 SHO处获得的 MCIM之前, M2ME删除 UICC 上旧的 SHO的信息, 如旧的 SHO的信任状, 同时删除旧的 SHO的 MCIM。
步骤 920: 在删除 UICC上旧的 MCIM后, M2ME通过 RO向旧的 SHO 发送已经删除旧的 MCIM的消息。
步骤 921: 旧的 SHO通过 RO向 M2ME返回一条确认消息, 用于指示旧 的 SHO收到了上述信息。 如果必要, RO将该确认消息转发给新的 SHO。 在 RO转发确认消息之前要进行私密性过滤, 用来防止关于旧的 SHO的敏感信 息被新的 SHO获得。
步骤 922: M2ME直接或在 RO ( DPF )的帮助下,将 MCIM安装到 UICC 上。
步骤 923: 当 M2ME直接将 MCIM安装到 UICC上之后, M2ME向 RO ( DPF功能 告供应 MCIM成功 /失败状态信息。如果 M2ME是在 RO( DPF ) 的帮助下, 将 MCIM安装到 UICC上的, 则 RO ( DPF ) 已经知道 MCIM是 否已经成功安装在 UICC上。
步骤 924: RO ( DPF功能 ) 向新的 SHO报告供应 MCIM成功 /失败状态 信息。
本发明实施例的 M2M设备归属网络运营商变更的系统, 包括: M2ME、 新的 SHO、 旧的 SHO、 PVA和 RO,
所述新的 SHO设置成接收到 M2ME的参数, 经 PVA验证所述 M2ME 通过后, 通过旧的 SHO提供的 M2ME与 RO的连接或者通过 TRE功能实体 建立的 M2ME与 RO的连接, 将新的 SHO的 MCIM提供给 M2ME;
所述 M2ME设置成将所述新的 MCIM安装到 UICC上;
其中, 所述 UICC和 TRE功能实体均位于所述 M2ME上。
所述新的 SHO还设置成经 PVA验证所述 M2ME通过后, 将新的 SHO
的 MCIM发送给 RO; 所述 RO设置成通过旧的 SHO提供的连接 , 将所述新 的 MCIM发送给所述 M2ME; 所述 M2ME还设置成删除所述 M2ME上的旧 的 SHO的信息, 如旧的 MCIM。
所述 RO设置成接收到 M2ME签约用户发送的新的 SHO的信息和 M2ME 的参数后, 激活 M2ME上的 TRE功能实体; 以及, 所述 RO通过 TRE功能 实体建立的连接, 将所述新的 MCIM发送给所述 M2ME; 所述 M2ME还设 置成通过 TRE功能实体与 RO建立连接, 以及,设置成删除所述 M2ME上的 旧的 SHO的信息, 如旧的 MCIM; 所述新的 SHO还设置成经 PVA验证所述 M2ME通过后, 授权 RO提供新的 SHO的 MCIM。
所述 RO设置成接收到 M2ME签约用户发送的新的 SHO的信息和 M2ME 的参数后, 通知旧的 SHO所述 M2ME变更 SHO; 以及, 所述 RO通过 TRE 功能实体建立的连接,将所述新的 MCIM发送给所述 M2ME; 所述旧的 SHO 设置成通过 OTA方式激活 M2ME上的 TRE功能实体;所述 M2ME还设置成 通过 TRE功能实体与 RO建立连接, 以及,设置成删除所述 M2ME上的旧的 SHO的信息; 所述新的 SHO还设置成经 PVA验证所述 M2ME通过后,授权 RO提供新的 SHO的 MCIM。
所述旧的 SHO设置成接收到 M2ME签约用户发送的新的 SHO的信息和 M2ME的参数后 ,通过 OTA方式激活 M2ME上的 TRE功能实体;所述 M2ME 还设置成通过 TRE功能实体与 RO建立连接, 以及, 设置成删除所述 M2ME 上的旧的 SHO的信息, 如旧的 MCIM; 所述新的 SHO还设置成经 PVA验证 所述 M2ME通过后,授权 RO提供新的 SHO的 MCIM; RO设置成通过 TRE 功能实体建立的连接, 将所述新的 MCIM发送给所述 M2ME。
尽管本发明结合特定实施例进行了描述, 但是对于本领域的技术人员来 说, 可以在不背离本发明的精神或范围的情况下进行修改和变化。 这样的修 改和变化被视作在本发明的范围和附加的权利要求书范围之内。
工业实用性
本发明提供一种 M2M设备归属网络运营商变更的方法和系统, 通过使 M2M设备结合 TRE功能实体提供的初始连接和 UICC的高安全性, 实现变 更 M2ME的归属网络运营商, 并保证 MCIM的安全性。
Claims
1、 一种机器到机器(M2M )设备归属网络运营商变更的方法, 包括: 方式一: 新的归属网络运营商(SHO )接收到机器到机器设备 ( M2ME ) 的参数,经平台验证授权中心( PVA )验证所述 M2ME通过后,通过旧的 SHO 提供的 M2ME与注册运营商 ( RO ) 的连接, 将新的 SHO的机器通信身份模 块( MCIM )提供给所述 M2ME; 所述 M2ME将所述新的 MCIM安装到通用 集成电路卡(UICC )上; 或者,
方式二: 新的 SHO接收到 M2ME的参数 , 经 PVA验证所述 M2ME通 过后, 通过可信环境(TRE )功能实体建立的 M2ME与 RO的连接, 将新的 SHO的 MCIM提供给所述 M2ME; 所述 M2ME将所述新的 MCIM安装到 UICC上;
其中, 所述 UICC和 TRE功能实体均位于所述 M2ME上。
2、 如权利要求 1所述的方法, 其中: 在所述方式一中, 所述新的 SHO 接收 M2ME的参数, 将 MCIM提供给所述 M2ME的步骤包括:
M2ME签约用户将 M2ME的参数发送给新的 SHO , 并通知 M2ME执行
MCIM重新供应;
新的 SHO经 PVA验证所述 M2ME通过后, 将新的 SHO的 MCIM发送 给 RO;
RO通过旧的 SHO提供的连接, 将所述新的 MCIM发送给所述 M2ME。
3、 如权利要求 2所述的方法, 其中:
在 RO将新的 MCIM发送给所述 M2ME的步骤执行之后, 所述 M2ME 将所述新的 MCIM安装到 UICC上的步骤执行之前, 还执行:
所述 M2ME删除所述 M2ME上的旧的 SHO的信息, 所述旧的 SHO的 信息包括旧的 SHO的 MCIM。
4、 如权利要求 1 所述的方法, 其中: 在所述方式二中, 所述新的 SHO 接收 M2ME的参数, 将 MCIM提供给所述 M2ME的步骤包括: M2ME签约用户将 M2ME的参数发送给新的 SHO , 并通知 M2ME执行 MCIM重新供应, 以及, 将新的 SHO的信息和 M2ME的参数发送给 RO; 所述 RO激活 M2ME上的 TRE功能实体;
所述 M2ME通过 TRE功能实体与 RO建立连接, RO在新的 SHO注册 所述 M2ME;
所述新的 SHO经 PVA验证所述 M2ME通过后,授权 RO提供新的 SHO 的 MCIM;
所述 RO通过 TRE功能实体建立的连接,将所述新的 MCIM发送给所述 M2ME。
5、 如权利要求 4所述的方法, 其中:
在所述 RO激活 M2ME上的 TRE功能实体的步骤执行之后,所述 M2ME 通过 TRE功能实体与 RO建立连接的步骤执行之前, 还执行: 所述 M2ME 删除所述 M2ME上的旧的 SHO的信息; 或者,
在所述 RO将所述新的 MCIM发送给所述 M2ME的步骤执行之后,所述 M2ME将所述新的 MCIM安装到 UICC上的步骤执行之前, 还执行: 所述 M2ME删除所述 M2ME上的旧的 SHO的信息;
其中, 所述旧的 SHO的信息包括旧的 SHO的 MCIM。
6、 如权利要求 1 所述的方法, 其中: 在所述方式二中, 所述新的 SHO 接收 M2ME的参数, 将 MCIM提供给所述 M2ME的步骤包括:
M2ME签约用户将 M2ME的参数发送给新的 SHO , 并通知 M2ME执行
MCIM重新供应, 以及, 将新的 SHO的信息和 M2ME的参数发送给 RO;
RO通知旧的 SHO所述 M2ME变更 SHO;
所述旧的 SHO通过无线下载( OTA )方式激活 M2ME上的 TRE功能实 体;
所述 M2ME通过 TRE功能实体与 RO建立连接, RO在新的 SHO注册 所述 M2ME; 所述新的 SHO经 PVA验证所述 M2ME通过后 ,授权 RO提供新的 SHO 的 MCIM;
RO 通过 TRE 功能实体建立的连接, 将所述新的 MCIM发送给所述 M2ME。
7、 如权利要求 1 所述的方法, 其中: 在所述方式二中, 所述新的 SHO 接收 M2ME的参数, 将 MCIM提供给所述 M2ME的步骤包括:
M2ME签约用户将 M2ME的参数发送给新的 SHO , 并通知 M2ME执行 MCIM重新供应,以及,将新的 SHO的信息和 M2ME的参数发送给旧的 SHO;
所述旧的 SHO通过 OTA方式激活 M2ME上的 TRE功能实体; 所述 M2ME通过 TRE功能实体与 RO建立连接, RO在新的 SHO注册 所述 M2ME;
所述新的 SHO经 PVA验证所述 M2ME通过后,授权 RO提供新的 SHO 的 MCIM;
RO 通过 TRE 功能实体建立的连接, 将所述新的 MCIM发送给所述 M2ME。
8、 如权利要求 6或 7所述的方法, 其中:
在旧的 SHO激活 M2ME上的 TRE功能实体的步骤中, 所述旧的 SHO 还同时删除所述 M2ME上的旧的 SHO的信息; 或者,
在所述 RO将所述新的 MCIM发送给所述 M2ME的步骤执行之后,所述 M2ME将所述新的 MCIM安装到 UICC上的步骤执行之前, 还执行: 所述 M2ME删除所述 M2ME上的旧的 SHO的信息;
其中, 所述旧的 SHO的信息包括旧的 SHO的 MCIM。
9、 如权利要求 4 ~ 7中任意一项所述的方法, 其中:
所述 M2ME通过 TRE功能实体与 RO建立连接, RO在新的 SHO注册 所述 M2ME的步骤包括:
所述 M2ME通过 TRE功能实体与任意选择的拜访网络运营商 ( VNO ) 建立初始连接;
所述 VNO联系 RO , 并将从所述 M2ME接收到的临时连接标识( PCID ) 发送给所述 RO;
所述 RO针对所述 PCID生成一组认证向量, 并发送给所述 VNO;
所述 VNO使用所述认证向量对所述 PCID和 M2ME进行认证, 认证通 过后 , VNO为所述 M2ME提供到 RO的 IP连接;
所述 M2ME通过 VNO提供的 IP连接联系 RO;
所述 RO为 M2ME发现新的 SHO, 或者, 所述 M2ME通过 RO发现新 的 SHO;
所述 RO连接所述新的 SHO, 并在所述新的 SHO注册所述 M2ME。
10、 一种机器到机器(M2M )设备归属网络运营商变更的系统, 包括: 机器到机器设备 ( M2ME ) 、 新的归属网络运营商 (SHO ) 、 旧的 SHO、 平 台验证授权中心 (PVA )和注册运营商 (RO ) , 其中:
所述新的 SHO设置成接收到 M2ME的参数, 经 PVA验证所述 M2ME 通过后,通过旧的 SHO提供的 M2ME与 RO的连接或者通过可信环境( TRE ) 功能实体建立的 M2ME与 RO的连接,将新的 SHO的 MCIM提供给 M2ME;
所述 M2ME设置成将所述新的 MCIM安装到通用集成电路卡( UICC ) 上;
其中, 所述 UICC和 TRE功能实体均位于所述 M2ME上。
11、 如权利要求 10所述的系统, 其中:
所述新的 SHO还设置成经 PVA验证所述 M2ME通过后, 将新的 SHO 的 MCIM发送给 RO;
所述 RO设置成通过旧的 SHO提供的连接,将所述新的 MCIM发送给所 述 M2ME;
所述 M2ME还设置成删除所述 M2ME上的旧的 SHO的信息。
12、 如权利要求 10所述的系统, 其中: 所述 RO设置成接收到 M2ME签约用户发送的新的 SHO的信息和 M2ME 的参数后, 激活 M2ME上的 TRE功能实体; 以及, 所述 RO还设置成通过 TRE功能实体建立的连接, 将所述新的 MCIM发送给所述 M2ME;
所述 M2ME还设置成通过 TRE功能实体与 RO建立连接, 以及,删除所 述 M2ME上的旧的 SHO的信息;
所述新的 SHO还设置成经 PVA验证所述 M2ME通过后, 授权 RO提供 新的 SHO的 MCIM。
13、 如权利要求 10所述的系统, 其中:
所述 RO还设置成接收到 M2ME签约用户发送的新的 SHO 的信息和 M2ME的参数后, 通知旧的 SHO所述 M2ME变更 SHO; 以及, 所述 RO还 设置成通过 TRE功能实体建立的连接,将所述新的 MCIM发送给所述 M2ME;
所述旧的 SHO设置成通过无线下载( OTA )方式激活 M2ME上的 TRE 功能实体;
所述 M2ME还设置成通过 TRE功能实体与 RO建立连接, 以及,删除所 述 M2ME上的旧的 SHO的信息;
所述新的 SHO还设置成经 PVA验证所述 M2ME通过后, 授权 RO提供 新的 SHO的 MCIM。
14、 如权利要求 10所述的系统, 其中:
所述旧的 SHO设置成接收到 M2ME签约用户发送的新的 SHO的信息和 M2ME的参数后 , 通过 OTA方式激活 M2ME上的 TRE功能实体;
所述 M2ME还设置成通过 TRE功能实体与 RO建立连接, 以及,删除所 述 M2ME上的旧的 SHO的信息;
所述新的 SHO还设置成经 PVA验证所述 M2ME通过后, 授权 RO提供 新的 SHO的 MCIM;
RO设置成通过 TRE功能实体建立的连接, 将所述新的 MCIM发送给所 述 M2ME。
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US13/395,881 US20120178418A1 (en) | 2009-09-14 | 2010-03-30 | Method and System for Changing a Selected Home Operator of a Machine to Machine Equipment |
EP10814901.4A EP2466759B1 (en) | 2009-09-14 | 2010-03-30 | Method and system for changing a selected home operator of a machine to machine equipment |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN200910173202.5A CN102026149B (zh) | 2009-09-14 | 2009-09-14 | 一种m2m设备归属网络运营商变更的方法和系统 |
CN200910173202.5 | 2009-09-14 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2011029299A1 true WO2011029299A1 (zh) | 2011-03-17 |
Family
ID=43731963
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2010/071401 WO2011029299A1 (zh) | 2009-09-14 | 2010-03-30 | 一种变更机器到机器设备的归属网络运营商的方法和系统 |
Country Status (4)
Country | Link |
---|---|
US (1) | US20120178418A1 (zh) |
EP (1) | EP2466759B1 (zh) |
CN (1) | CN102026149B (zh) |
WO (1) | WO2011029299A1 (zh) |
Families Citing this family (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
ATE461594T1 (de) * | 2005-10-13 | 2010-04-15 | Mitsubishi Electric Corp | Verfahren zum verbinden einer basisstation mit einem drahtlosen telekommunikationsnetz |
EP2596654A4 (en) * | 2010-07-23 | 2016-12-21 | ERICSSON TELEFON AB L M (publ) | MEDIATION SERVER, METHOD OF CONTROLLING THE SAME, COMMUNICATION DEVICE, CONTROL METHOD THEREFOR, ACCOUNT SUPPLY SERVER, AND ASSOCIATED METHOD |
EP2721849A4 (en) * | 2011-06-15 | 2015-03-04 | Ericsson Telefon Ab L M | PROVISION OF CONNECTIVITY SERVICE DATA IN A TELECOMMUNICATIONS NETWORK |
JP5942354B2 (ja) * | 2011-07-22 | 2016-06-29 | ソニー株式会社 | 無線通信装置、情報処理装置、通信システムおよび無線通信装置の制御方法 |
JP6035713B2 (ja) * | 2011-08-12 | 2016-11-30 | ソニー株式会社 | 情報処理装置、通信システムおよび情報処理装置の制御方法 |
CN103634791B (zh) * | 2012-08-27 | 2018-03-09 | 华为终端(东莞)有限公司 | 切换运营商网络的方法、用户设备及远程管理平台 |
CN103702377B (zh) * | 2012-09-27 | 2017-04-12 | 华为终端有限公司 | 一种网络切换方法和设备 |
CN104703170B (zh) | 2013-12-05 | 2017-04-12 | 华为终端有限公司 | 下载运营商的文件的方法及设备 |
CN106465107B (zh) * | 2014-07-07 | 2020-12-01 | 华为技术有限公司 | 嵌入式通用集成电路卡管理的授权方法及装置 |
CN108235302A (zh) * | 2016-12-14 | 2018-06-29 | 中兴通讯股份有限公司 | 智能卡的远程签约管理平台切换方法及装置、智能卡、sm-sr |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101489214A (zh) * | 2009-01-23 | 2009-07-22 | 电信科学技术研究院 | 一种检测用户端设备的方法、装置及系统 |
WO2009092115A2 (en) * | 2008-01-18 | 2009-07-23 | Interdigital Patent Holdings, Inc. | Method and apparatus for enabling machine to machine communication |
WO2009103623A2 (en) * | 2008-02-22 | 2009-08-27 | Telefonaktiebolaget L M Ericsson (Publ) | Methods and apparatus for wireless device registration |
Family Cites Families (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20090191857A1 (en) * | 2008-01-30 | 2009-07-30 | Nokia Siemens Networks Oy | Universal subscriber identity module provisioning for machine-to-machine communications |
KR101508576B1 (ko) * | 2008-09-24 | 2015-04-08 | 인터디지탈 패튼 홀딩스, 인크 | 홈 노드-b 장치 및 보안 프로토콜 |
US8578153B2 (en) * | 2008-10-28 | 2013-11-05 | Telefonaktiebolaget L M Ericsson (Publ) | Method and arrangement for provisioning and managing a device |
-
2009
- 2009-09-14 CN CN200910173202.5A patent/CN102026149B/zh not_active Expired - Fee Related
-
2010
- 2010-03-30 EP EP10814901.4A patent/EP2466759B1/en active Active
- 2010-03-30 WO PCT/CN2010/071401 patent/WO2011029299A1/zh active Application Filing
- 2010-03-30 US US13/395,881 patent/US20120178418A1/en not_active Abandoned
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2009092115A2 (en) * | 2008-01-18 | 2009-07-23 | Interdigital Patent Holdings, Inc. | Method and apparatus for enabling machine to machine communication |
WO2009103623A2 (en) * | 2008-02-22 | 2009-08-27 | Telefonaktiebolaget L M Ericsson (Publ) | Methods and apparatus for wireless device registration |
CN101489214A (zh) * | 2009-01-23 | 2009-07-22 | 电信科学技术研究院 | 一种检测用户端设备的方法、装置及系统 |
Non-Patent Citations (1)
Title |
---|
See also references of EP2466759A4 * |
Also Published As
Publication number | Publication date |
---|---|
CN102026149B (zh) | 2015-08-12 |
EP2466759A1 (en) | 2012-06-20 |
EP2466759A4 (en) | 2016-11-16 |
CN102026149A (zh) | 2011-04-20 |
EP2466759B1 (en) | 2019-09-11 |
US20120178418A1 (en) | 2012-07-12 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2011035572A1 (zh) | 一种m2m设备归属网络运营商变更的方法和系统 | |
WO2011029299A1 (zh) | 一种变更机器到机器设备的归属网络运营商的方法和系统 | |
US9831903B1 (en) | Update of a trusted name list | |
US11184769B2 (en) | Method and apparatus for discussing digital certificate by ESIM terminal and server | |
KR102040231B1 (ko) | 이동 통신에서 가입 사업자 변경 제한 정책을 지원하는 정책 적용 방법 및 장치 | |
CN117651271A (zh) | 支持无线通信系统中设备间简档转移的方法和装置 | |
KR101474096B1 (ko) | 가입자 디바이스들의 네트워크 개인화를 위한 방법 및 장치 | |
KR102439686B1 (ko) | 디바이스의 피처들의 세트의 사용을 위한 인가를 검증 | |
AU2016247689A2 (en) | Technique for managing profile in communication system | |
WO2009124835A2 (en) | Method of authenticating home operator for over-the-air provisioning of a wireless device | |
WO2013067772A1 (zh) | 一种mtc设备与uicc绑定的方法、装置及系统 | |
JP2016506152A (ja) | タグ付けによるデバイスの認証 | |
WO2009092115A2 (en) | Method and apparatus for enabling machine to machine communication | |
WO2012094879A1 (zh) | 一种mtc服务器共享密钥的方法及系统 | |
WO2012062077A1 (zh) | 基于通用引导架构的机器类通信设备分组管理方法及系统 | |
WO2011029296A1 (zh) | 向机器到机器设备提供机器通信身份模块的系统及方法 | |
US20120102207A1 (en) | Registration of ad-hoc group members into an infrastructure network | |
WO2013071707A1 (zh) | 移动用户身份识别卡与机器类通信设备绑定的方法及装置 | |
WO2012151941A1 (zh) | 终端组的移动性管理实体选择方法及系统 | |
WO2011029308A1 (zh) | 一种m2m设备归属网络运营商变更的方法和系统 | |
CN102209317A (zh) | 提供签约数据的方法及系统 | |
WO2011029297A1 (zh) | 向机器到机器设备提供机器通信身份模块的系统及方法 | |
WO2010124569A1 (zh) | 用户接入控制方法和系统 | |
WO2015100874A1 (zh) | 家庭网关接入管理方法和系统 | |
KR101263998B1 (ko) | 3 gpp기반의 개인 네트워크(pn)에서 개인 네트워크 장치(pne)의 해제를 위한 장치 및 방법 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 10814901 Country of ref document: EP Kind code of ref document: A1 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 13395881 Country of ref document: US Ref document number: 2010814901 Country of ref document: EP |
|
NENP | Non-entry into the national phase |
Ref country code: DE |