WO2011134397A1

WO2011134397A1 - Method, system and apparatus for identifying terminal

Info

Publication number: WO2011134397A1
Application number: PCT/CN2011/073370
Authority: WO
Inventors: 艾明; 熊春山
Original assignee: 电信科学技术研究院
Priority date: 2010-04-30
Filing date: 2011-04-27
Publication date: 2011-11-03
Also published as: CN102083212A

Abstract

The present invention, related to wireless communications technology, especially related to a method, system and apparatus for identifying a terminal, is for solving the problem existed in the prior art that a plurality of Machine Type Communications (MTC) devices are unable to be identified in 3^rd Generation Partnership Project (3GPP) system. The embodiments of the present invention include the following steps: a network node determines a device identity, and determines the corresponding MTC device according to the device identity; wherein, the device identity includes the International Mobile Equipment Identity (IMEI) corresponding to the MTC device and the International Mobile Subscriber Identity (IMSI) corresponding to the Subscriber Identity Module (SIM) or Universal Subscriber Identity Module (USIM) in the MTC device. With the method provide by the embodiments of the present invention, MTC devices can be identified in 3GPP system, because an MTC device is identified with the combined IMSI and IMEI, and the MTC device subscription is identified. Further, the embodiments of the present invention can also identify an MTC user subscription with the IMSI identity, and identify an MTC group composed by MTC devices in an MTC user subscription with a Mobile Subscriber ISDN (MSISDN).

Description

Method, system and device for identifying terminal The application is submitted to the Chinese Patent Office on April 30, 2010, the application number is 201010164443.6, and the invention name is

The priority of the Chinese Patent Application, which is incorporated herein by reference. Technical field

The present invention relates to wireless communication technologies, and in particular, to a method, system and apparatus for identifying a terminal. Background technique

In the system prior to the 3rd Generation Partnership Project (3GPP) Release 10 (RIO), the primary communication entity is the User Terminal (UE) serving the human. A UE usually includes a Subscriber Identity Module (SIM) card or a Universal Subscriber Identity Module (USIM) card. The card contains an International Mobile Subscriber Identity (IMSI) that identifies the card. This IMSI global unique landmark i only this signed SIM or USIM, that is, a SIM/USIM corresponds to a unique IMSI.

A UE includes a mobile device (Mobile Equipment, ME), and the ME includes an IMEI (International Mobile Equipment Identity), and the IMEI uniquely identifies the ME globally.

In a 3GPP system, a SIM card or a USIM card can only be placed in one ME at a time, but can be used in different MEs at different times.

When the UE is registered to the 3GPP system, the 3GPP system performs identity authentication on the UE according to the IMSI in the UE or the IMSI in the USIM. After the UE passes the authentication of the 3GPP system, the UE can access the 3GPP system, and Based on its contract data, it determines the services that the 3GPP system that it contracts to use can provide.

The communication function supporting a large number of Machine Type Communications (MTC) devices has been introduced in the R10 system of 3GPP. Since the number of MTC devices is currently communicating Two orders of magnitude for the terminal. If the SIM or USIM in the MTC device is still allocated based on the current IMSI allocation, the IMSI length is insufficient. That is, in the R10 system of 3GPP, the SIM or USIM in the MTC device is allocated for the manner in which the MTC device cannot allocate based on the current IMSI.

In summary, currently, in the R10 system of 3GPP, a large number of MTC devices cannot be identified. Summary of the invention

The embodiment of the invention provides a method, a system and a device for identifying a terminal, which are used to solve the problem that a large number of MTC devices cannot be identified in the 3GPP R10 system existing in the prior art.

A method for identifying a terminal according to an embodiment of the present invention, the method includes:

The network node determines the device identifier;

Determining, by the network node, a corresponding machine type communication MTC device according to the device identifier; wherein the device identifier includes an international mobile device identifier IMEI corresponding to the MTC device and the

The subscriber identity module in the MTC device SIM or the global subscriber identity module IMSI corresponding to the USIM.

A system for identifying a terminal according to an embodiment of the present invention includes: a plurality of network nodes; each network node is configured to: determine a device identifier, and determine, according to the device identifier, a corresponding machine type communication MTC device;

The device identifier includes an international mobile device identifier IMEI corresponding to the MTC device and an international mobile subscriber identity IMSI corresponding to the subscriber identity module SIM or the global subscriber identity module USIM in the MTC device.

A network side device, where the network side device includes:

An identifier determining module, configured to determine a device identifier;

a device determining module, configured to determine, according to the device identifier, a corresponding machine type communication MTC device;

The device identifier includes an international mobile device identifier IMEI corresponding to the MTC device, and an international mobile device corresponding to the subscriber identity module SIM or the global subscriber identity module USIM in the MTC device. User ID IMSI.

In the embodiment of the present invention, the network node determines the corresponding MTC device according to the device identifier. The device identifier includes the IMEI corresponding to the MTC device and the SIMSI corresponding to the SIM or USIM in the MTC device. Since the embodiment of the present invention binds an IMSI and an IMEI to identify an MTC device, an IMSI can be used to sign an MTC device, thereby increasing the number of available identification information in the R10 system of the 3GPP, thereby clearly identifying a large number of The MTC equipment improves system efficiency. DRAWINGS

1 is a schematic structural diagram of a first network side device according to an embodiment of the present invention;

2 is a schematic structural diagram of a second network side device according to an embodiment of the present invention;

3 is a schematic structural diagram of a third network side device according to an embodiment of the present invention;

4 is a schematic structural diagram of a fourth network side device according to an embodiment of the present invention;

FIG. 5 is a schematic structural diagram of a fifth network side device according to an embodiment of the present invention;

FIG. 6 is a schematic flowchart of a method for identifying a terminal according to an embodiment of the present invention. detailed description

In the embodiment of the present invention, the network node determines the corresponding MTC device according to the device identifier. The device identifier includes the IMEI corresponding to the MTC device and the SIMSI corresponding to the SIM or USIM in the MTC device. Since the embodiment of the present invention binds an IMTC and an IMEI to identify an MTC device, the number of available identification information is increased in the R10 system of the 3GPP, so that a large number of MTC devices can be clearly identified.

Further, the embodiment of the present invention can also identify an MTC Subscriber's Subscription by using an IMSI, thereby enabling the MTC subscriber to be identified in the R10 system of the 3GPP. The so-called MTC subscriber refers to a legal entity, which has a contractual relationship with the network operator. The network operator provides services for one or more MTC subscribers, and the so-called MTC subscriber subscription can be understood as between the MTC subscriber and the network operator. Signed the service content that can be provided Agreement of the Department. Further, the IMSI and the IMEI can be used to identify the MTC device subscription, the SIM/USIM, and the context of the MTC device in the IMC and the IMEI. Any of the so-called device subscriptions can be understood as the subscription data associated with the device stored by the network operator in the HSS/HLR.

Further, the embodiment of the present invention may further identify an MTC group in the MTC subscriber subscription and all the MTC devices constituting the MTC group by using a mobile subscriber integrated service data network (MSISDN number).

The embodiment of the present invention can be applied to the R10 system of the 3GPP and the subsequent system, and can also be applied to other systems including the MTC device.

The embodiments of the present invention are further described in detail below with reference to the accompanying drawings.

As shown in FIG. 1 , the system for identifying a terminal in the embodiment of the present invention includes multiple network nodes: each network node is configured to: determine a device identifier, and determine a corresponding MTC device according to the device identifier;

The device identifier includes an IMEI corresponding to the MTC device and an IMSI corresponding to the SIM or the USIM in the MTC device.

If the network node (ie, the network side device) in the embodiment of the present invention is a core network device, the network node may be a node in an IP Multimedia System (IMS), and a Home Subscriber Server (Home Subscriber Server, HSS), Home Location Register (HLR), Mobile Service Switch Center (MSC), Visitor Location Register (VLR), Serving GPRS Support Node (SGSN) ), Gateway GPRS Support Node (GGSN), Serving GW (S-GW), Packet Data Gateway (PDN GW, P-GW), Policy and Charging Rules Function , PCRF) Entity, Mobility Management Entity (MME) and Application Function (AF) One of the entities;

If the network node (ie, the network side device) of the embodiment of the present invention is a RAN device, the network node may be a radio network controller (RNC), a base station (ENB), and a base station controller (Base Station Controller, BSC). In one of the base stations, the base station can also be a home base station of the home type.

For details of the specific network node, refer to FIG. 2 to FIG. 5, and details are not described herein again.

As shown in FIG. 1, the first network side device of the embodiment of the present invention includes: an identifier determining module 10 and a device determining module 20.

An identifier determining module 10, configured to determine a device identifier;

The device determining module 20 is configured to determine, according to the device identifier determined by the identifier determining module 10, a corresponding MTC device;

The following describes each scene separately.

Scene 1, initial registration.

When the MTC device needs to perform initial registration, the device determining module 20 is based on the received

The device identification of the MTC device determines the MTC device to be initially registered.

Referring to FIG. 2, the network side device of the embodiment of the present invention may further include: a receiving module 30. The receiving module 30 is configured to receive IMEI and IMSI from the MTC device.

If the MTC device sends IMEI and IMSI at the same time of initial registration, the receiving module 30 receives the IMEI and the IMSI at the same time;

If the MTC device only sends IMSI at the initial registration, the receiving module 30 receives the

The IMSI of the MTC device, and determining that the IMSI is assigned to an MTC subscriber, sends an IMEI message to the MTC device; the MTC device sends an IMEI after receiving the IMEI message; and the receiving module 30 receives the IMEI from the MTC device.

There are many ways for the receiving module 30 to determine whether the IMSI is assigned to an MTC subscriber, and several types are listed below. Method 1: IMSI uses a specific code.

The operator can set the IMSI of a certain interval, such as the Mobile Subscriber Identification Number (MSIN) in the IMSI, a certain number of segments or a specific starting number, for example, the MSIN corresponding to the number 140. IMSI] is used for MTC communication without being assigned to ordinary users. After receiving the IMSI, the receiving module 30 determines that the IMSI is assigned to an MTC subscriber if the IMSI is in a certain area.

Method 2, internal search.

The IMSI assigned by the MTC subscriber when signing the contract is recorded in the database, and the receiving module 30 checks the database through internal retrieval. If the received IMSI is in the database, it is determined that the IMSI is assigned to an MTC subscriber subscription.

In addition, when an entity such as a VLR, SGSN, or MME sends an authentication information request message or an authentication data request message to the HSS or the HLR, only the IMSI is included in the message, and the IMEI is not included. The HSS or HLR finds that the IMSI is assigned to an MTC subscriber subscription through internal retrieval, and the HSS or HLR sends an authentication information response message or an authentication data response message to an entity such as a VLR, SGSN or MME when the IMSI is recorded in the MTC device subscription. In this message it is indicated that this IMSI is assigned to an MTC subscriber subscription.

Scene 2, context.

Referring to FIG. 3, the network side device of the embodiment of the present invention may further include: an adding module 40. The adding module 40 is configured to add the device identifier to the MTC device context corresponding to the device identifier.

Since multiple MTC devices subscribed by the same MTC subscriber can be registered to the same network side device at the same time, the network side device needs to distinguish these different MTC devices, and the IMSI alone cannot be distinguished because they are the same MTC. Different MTC devices in the subscriber's contract. Therefore, these network side devices must use IMEI to distinguish different MTC devices. Therefore, each MTC device context recorded in these network side devices needs to include the IMSI corresponding to the MTC subscriber subscription and its own IMEI.

If the operator signs one or more MTCs in an MTC subscriber identified by this IMSI When the device allocates an MSISDN number, the network node uses the MSISDN number to identify an MTC group formed by the MTC devices in the MTC subscriber subscription, and records the MSISDN number in the MTC device context of each MTC device corresponding to the MTC group. .

Specifically, the network side device of the embodiment of the present invention may further include: an identifier determining module

80.

The identifier determining module 80 is configured to add the MSISDN number to the MTC device context of each MTC device corresponding to an MTC group that allocates the MSISDN number.

If the MTC device and the other MTC devices that are subscribed to the MTC subscribers form an MTC group, and the operator assigns an MSISDN number to the MTC group, the MTC device context of the MTC device also needs to record the identifier of the corresponding MTC group. , ie the MSISDN number. An MTC subscriber contract includes at least one MTC group.

By default, all MTC devices corresponding to an MTC subscriber subscription can form an MTC group. For example, an MTC device can be an MTC group alone, or MTC devices A, B, C, D, and E form an MTC group, while MTC devices F, G, and H form another MTC group. In addition, an MTC device belongs to at least one MTC group. For example, MTC device A can form one of the largest MTC groups GX in all MTC devices in the same MTC subscriber subscription, and MTC device A can also form another MTC group GY with MTC device B.

The network node may be one of a VLR, an SGSN, an MME, an S-GW, a P-GW, a GGSN, an RNC, and an ENB. The MTC device context recorded by the device includes the IMSI and the IMEI of the MTC device. And one or more MSISDN numbers that may be assigned.

The identifier determining module 80 adds the MSISDN number corresponding to each MTC group to which the MTC device belongs to the MTC device context of the MTC device, when an MTC device belongs to multiple MTC groups.

Further, the network side device of the embodiment of the present invention may further include: a processing module 50. The processing module 50 is configured to determine, according to the device identifier in the message, the MTC device context of the MTC device corresponding to the device identifier after receiving the message from the other network side device.

If the above message contains an MSISDN number, but does not contain an IMSI and/or IMEI device In the case of identification, the message is sent to one MTC group in the MTC subscriber subscription determined by the MSISDN number, and all corresponding MTC devices in the MTC group.

When the MTC device context of the MTC device is transmitted between different network side devices, the network side device needs to simultaneously use the IMSI and the IMEI to identify one MTC device, that is, determine the MTC corresponding to the transmitted MTC device context according to the IMSI and the IMEI. device.

Scenario 3: Interface association.

Referring to FIG. 4, the network side device of the embodiment of the present invention may further include: a notification module 60. The notification module 60 is configured to send a message including the device identifier to the other network side device, and notify the other network side device to establish an interface association for the MTC device corresponding to the device identifier, when the network device needs to be associated with the MTC device.

When two different network side devices establish an interface association for one MTC device, the network side devices need to identify one MTC device according to IMSI and IMEI.

For example, when the MME sends a Create Session Request message to the S-GW, if the GTP Control (GTP-C) signaling connection has not been established between the MME and the S-GW, the MME needs to be created. The Session Request message contains the IMSI and IMEI of this MTC device. Similarly, when the GTP-C signaling connection is not established between the S-GW and the P-GW for the MTC device, the Create Session Request message sent by the S-GW to the P-GW includes the IMSI of the MTC device. IMEI. In addition, when an S1-AP signaling connection is established between the MME and the ENB, IMSI and IMEI are also required to identify the MTC device.

When the MTC device is defined as an MTC group, the message also needs to include the MSISDN number to identify the MTC group where the MTC device is located.

Specifically, when one MSISDN number is assigned to one or more MTC devices in an MTC subscriber subscription identified by an IMSI, the identity determining module 80 identifies, by the MSISDN number, an MTC composed of the MTC devices in the MTC subscriber subscription. group.

If the device identifier in the message includes the MSISDN number but does not include the IMSI and/or the IMEI device identifier, the message is sent to an MTC group in the MTC subscriber subscription determined by the MSISDN number, and all corresponding to the MTC group. MTC device. Scene 4, signing.

Referring to FIG. 5, the network side device of the embodiment of the present invention may further include: an establishing module 70. The establishing module 70 is configured to: when the MTC subscriber performs a subscription of the MTC service, assign an IMSI that the operator assigns to the MTC subscriber to the subscription data of the MTC subscriber, wherein the IMSI is used to identify the MTC subscriber subscription.

And setting an MTC device subscription data for each MTC device subscribed by the MTC subscriber according to the IMSI of the MTC subscriber subscription and the IMEI of the MTC device, and recording the IMSI and the IMEI corresponding to each MTC device in the MTC device subscription data, and The serial number Sequence Number (SQN) and the random number ( RAND ) in the system message are separately generated for each MTC device contract.

For example, the home environment (HE) (eg, HSS or HLR) independently generates SQN and RAND for each MTC device contract corresponding to each IMEI contracted by the MTC subscriber.

Since this MTC subscriber subscription is provided by one or more MTC devices, MTC subscribers also need to provide the number of MTC devices and the IMEI of each MTC device to the operator. These data are recorded as part of the MTC subscriber subscription data in each MTC device subscription data corresponding to the MTC subscriber subscription.

When the MTC subscriber subscribes, when the operator allocates an MSISDN number to one or more MTC devices in an MTC subscriber subscription identified by an IMSI, the MSISDN number identifies one of the MTC devices in the MTC subscriber subscription. MTC group. And the module 70 needs to record the MSISDN number in the MTC device subscription data of each MTC device in the MTC group that the MTC subscriber subscribes to. An MTC subscriber contract includes at least one MTC group. By default, all MTC devices corresponding to an MTC subscriber subscription form an MTC group.

For example, one MTC device can be an MTC group alone, or MTC devices A, B, C, D, and E form one MTC group, while MTC devices F, G, and H form another MTC group. In addition, one MTC device belongs to at least one MTC group. For example, the MTC device A may be in a largest MTC group GX composed of all other MTC devices in the same MTC subscriber subscription, and at the same time, the MTC device A may also form another MTC group GY with the MTC device B. When an MTC group consisting of one or more MTC devices, the operator needs to allocate an MSISDN number for the MTC user to conveniently identify the MTC group, and the MSISDN number can identify the MTC group and the corresponding MTC group. All MTC devices. In this case, the MSISDN number needs to be added to each MTC device subscription data corresponding to this MTC group. For each MTC device in the MTC group, this MSISDN number needs to be written into the SIM/USIM of the MTC device. Since one MTC device can belong to one or more MTC groups, one or more MSISDN numbers exist in the MTC device subscription data of the MTC device, the MTC device context, and the MTC device SIM/USIM.

Specifically, the identifier determining module 80 is configured to add the MSISDN number to the MTC device subscription data and the MTC device SIM/USIM file of each MTC device corresponding to the MTC group that allocates the MSISDN number.

For example, when the VLR, the SGSN, and the MME are registered to the HSS/HLR, the HSS/HLR transmits the MTC device subscription data of an MTC device to the VLR, the SGSN, and the MME by using a message, and the MTC device subscription data includes the device of the MTC device. Identifies the IMSI and IMEI. Then, the VLR, the SGSN, and the MME update the MTC device context corresponding to the MTC device, and the MTC device context includes one or more MSISDN numbers and other subscription data corresponding to the MTC device. If the MTC device subscription data is changed, the HSS/HLR transmits the new MTC device subscription data of the MTC device to the VLR, the SGSN, and the MME by using a message, and the message includes the device identifiers IMSI and IMEI of the MTC device.

Scenario 5, Certification (AKA) process.

The device determining module 20 determines the MTC device that needs to be authenticated according to the device identifier when the MTC device needs to be authenticated.

For example, in the authentication and key agreement (AKA) process of the MTC device in the 3G and LTE systems, the authentication data request message sent by the VLR, the SGSN, and the MME to the HE carries the IMSI and the IMEI. Correspondingly, the HE can determine the MTC device that needs to be authenticated according to the MSI and the IMEI, and then respond to the VLR, SGSN, and MME with an Authentication Data Response message to provide an authentication vector. Similarly, when the VLR, the SGSN, and the MME update the dynamic information in the HE (for example, the identifier of the serving node) by using an Update Location message sent to the HE, the IMSI and the IMEI are carried in the messages; correspondingly, the HE is based on the MSI and The IMEI can determine the MTC device subscription data of the MTC device, and then respond to the VLR, SGSN, and MME with corresponding messages.

In the AKA authentication process, the SIM or USIM in all the MTC devices corresponding to the same MTC subscriber contract uses the MTC subscriber to sign the corresponding IMSI;

The SIM or USIM in each MTC device uses the same permanent key or a different permanent key.

Specifically, the AKA process uses a permanent root key K based on the IMSI subscription. For multiple MTC devices subscribed by the same MTC subscriber, because the IMSI is the same, these MTC devices can share the same permanent root key K based on one IMSI. It is also possible to use a separate permanent key K based on the IMEI of each MTC device.

Manner 1: When multiple MTC devices subscribed by the same MTC subscriber use a permanent root key based on the same IMSI, an MTC user signs an agreement with an operator to subscribe to the MTC subscriber, and obtains N (quantity) SIM or USIM. These SIM or USIM cards can be placed in any of the N designated MTC devices. There is no requirement that a SIM or USIM card must be placed on a specific corresponding MTC device.

Manner 2: When multiple MTC devices subscribed by the same MTC subscriber each use a different permanent root key K, the above SIM or USIM card needs to be placed on the corresponding IMEI MTC device. Otherwise, in the AKA process. An authentication failure will occur.

In the first mode, the SIM or USIM card can be placed in the N designated MTC devices, which improves the flexibility. The second mode is more secure than the mode one. Therefore, in the specific implementation process, you can determine which method to use according to your needs. For example, in a secure, trusted environment, the first way to sign up for an MTC subscriber subscription can be used. In an unsafe or untrusted environment, the MTC subscribers contracted by Mode 2 will be signed.

Further, the permanent key used by the MTC device is the same as the permanent key used by the network side device HE corresponding to the MTC device. It should be noted that different modules involve different modules, but in specific implementations, the above modules may all be disposed in the same network side device; or some of the above mentioned modules may be combined according to the needs of the device functions. In the same network side device.

As shown in FIG. 6, the method for identifying a terminal in the embodiment of the present invention includes the following steps:

Step 301: The network node determines the device identifier, where the device identifier includes an IMEI corresponding to the MTC device and an IMSI corresponding to the SIM or the USIM in the MTC device. Step 302: The network node determines the corresponding MTC device according to the device identifier.

The following describes each scene separately.

Scene 1, initial registration.

In step 302, when the MTC device needs to perform initial registration, the network node determines, according to the received device identifier from the MTC device, the MTC device that performs initial registration.

Correspondingly, before step 301, the method further includes:

The network node receives the IMEI and IMSI from the MTC device.

If the MTC device sends IMEI and IMSI at the same time of initial registration, the network node will receive IMEI and IMSI at the same time;

If the MTC device only sends the IMSI when the initial registration, the network node receives the IMSI from the MTC device, and determines that the IMSI is assigned to an MTC subscriber subscription, sends an IMEI message to the MTC device; the MTC device receives the IMEI message. The IMEI is then sent; the network node receives the IMEI from the MTC device.

Among them, there are many ways for the network node to determine whether IMSI is assigned to an MTC subscriber, and several types are listed below.

Method 1: IMSI uses a specific code.

The operator can use the IMSI of a certain interval (such as the MSIN in the IMSI, a certain number segment or a specific starting number, such as the IMSI corresponding to the MSIN starting with the number 140) for the MTC communication, without being assigned to the common user. After receiving the IMSI, the network node determines that the IMSI is assigned to an MTC subscriber to sign up if the IMSI is in a certain area. Method 2, internal search.

The database records the IMSI assigned by the MTC subscriber when signing the contract. The network node checks the database through internal retrieval. If the received IMSI is in the database, it determines that the IMSI is assigned to an MTC subscriber.

In addition, when an entity such as a VLR, SGSN, or MME sends an authentication information request message or an authentication data request message to the HSS or the HLR, only the IMSI is included in the message, and the IMEI is not included. The HSS or HLR finds that the IMSI is assigned to an MTC subscriber subscription through internal retrieval, and the HSS or HLR sends an authentication information response message or an authentication data response to an entity such as a VLR, SGSN or MME when the IMSI is recorded in a plurality of MTC device subscriptions. A message indicating in this message that this IMSI is assigned to an MTC subscriber subscription.

When the network side allocates the temporary mobile subscriber identity to the MTC device, the MTC device only needs to provide the temporary mobile subscriber identity in the subsequent mobility management process, and does not need to provide IMEI and IMSI. That is, in the Circuit Switched (CS) domain, the Temporary Mobile Subscriber Identity (TMSI) and the Location Area Identity (LAI) uniquely identify the MTC device, and for GPRS, the packet TMSI (Packet TMSI, P-TMSI) and Routing Area Identity (RAI) uniquely identify this MTC device; for Evolved Packet System (EPS), Globally Unique Temporary Identity (Globally Unique Temporary Identity, GUTI) uniquely identifies this MTC device.

Scene 2, context.

After step 302, the method further includes:

The network node adds the device identifier to the MTC device context corresponding to the device identifier.

Since multiple MTC devices subscribed by the same MTC subscriber can be registered to the same network node at the same time, the network node needs to distinguish these different MTC devices. The IMSI alone cannot be distinguished because they are contracted by the same MTC subscriber. Different MTC devices in the middle. Therefore, these network nodes must use IMEI to distinguish different MTC devices, so each MTC device context recorded in these network nodes needs to include the associated MTC subscriber sign. About the corresponding IMSI and its own IMEI.

If the MTC device and the other MTC devices that are subscribed to the MTC subscriber form an MTC group, and the operator assigns an MSISDN number to the MTC group, the network node uses the MSISDN number to identify one of the MTC devices in the MTC subscriber subscription. The MTC group, and the MTC device context of each MTC device in this MTC group also needs to record this MSISDN number. At least one MTC group is included in an MTC subscriber subscription.

By default, an MTC group consisting of all MTC devices corresponding to an MTC subscriber subscription. For example, an MTC device can be an MTC group alone, or MTC devices A, B, C, D, and E form an MTC group, while MTC devices F, G, and H form another MTC group. In addition, one MTC device belongs to at least one MTC group. For example, MTC device A can form a largest MTC group GX with all other MTC devices in the same MTC subscriber subscription, and MTC device A can also form another MTC device B with another. MTC group GY.

When an MTC device belongs to multiple MTC groups at the same time, the network node adds the MSISDN number corresponding to each MTC group to which the MTC device belongs to the MTC device context of the MTC device.

Further, after step 302, the method further includes:

After receiving the message from the other network node, the network node determines the MTC device context of the MTC device corresponding to the device identifier according to the device identifier in the message.

If the above message contains an MSISDN number, but does not include the IMSI and/or IMEI device identifier, the message is sent to one MTC group in the MTC subscriber subscription determined by the MSISDN number, and all corresponding MTCs in the MTC group. device.

When the MTC device context of the MTC device is transmitted between different network side devices, the network side device needs to simultaneously use the IMSI and the IMEI to identify one MTC device, that is, determine the MTC corresponding to the transmitted MTC device context according to the IMSI and the IMEI. device. Scenario 3: Interface association.

After step 302, the method further includes:

When the network node needs to establish an interface association with the other network node for the MTC device, the network node sends a message including the device identifier to the other network node, and notifies the other network node to establish an interface association for the MTC device corresponding to the device identifier.

Wherein, when two different network nodes establish an interface association for an MTC device, the network nodes need to identify an MTC device according to IMSI and IMEI.

For example, when the MME sends a Create Session Request message to the S-GW, if the GTP-C signaling connection has not been established between the MME and the S-GW, the MME needs to include the IMSI and IMEI of the MTC device in the Create Session Request message. . Similarly, when the GTP-C signaling connection is not established between the S-GW and the P-GW for the MTC device, the Create Session Request message sent by the S-GW to the P-GW includes the IMSI of the MTC device. IMEI. In addition, when establishing an S1-AP signaling connection between the MME and the ENB, IMSI and IMEI are also required to identify the MTC device.

When the MTC device is defined as a group, the message also needs to include the MSISDN number to identify the MTC group where the MTC device is located.

Specifically, when one MSISDN number is assigned to one or more MTC devices in an MTC subscriber subscription identified by an IMSI, the network node uses the MSISDN number to identify an MTC group formed by the MTC subscribers in the MTC subscriber subscription.

If the device identifier in the message includes the MSISDN number but does not include the IMSI and/or the IMEI device identifier, the message is sent to an MTC group in the MTC subscriber subscription determined by the MSISDN number, and all corresponding to the MTC group. MTC device.

Certainly, when the network node allocates a temporary identifier or other identifier that can identify the MTC device to the MTC device, the network node uses a temporary identifier or other identifier that can identify the MTC device as the identifier of the MTC device. For example, when the SGSN allocates a Packet Temporary Mobile Station Identity (P-TMSI) to the MTC device, when the MTC device performs Tracking Area Update (TAU) in the MME, the MTC device is in the TAU Request. In the message, P-TMSI and RAI are mapped to globally unique (user) temporary targets. After the mapping of the mapped GUTI to the P-TMSI and the Routing Area Identity (RAI), the MME sends a Context Request message to the original SGSN, and the Context Request message includes the original SGSN allocation. P-TMSI and RAI for MTC devices. The Context Response message sent by the SGSN to the MME includes the IMSI and IMEI of the MTC device in the context data of the SGSN and one or more MSISDN numbers of the identified MTC device group that may be allocated.

When the network pages the MTC device, the temporary identifier of the MTC device can still be used. When the MTC device has no temporary identifier or its temporary identifier is unavailable, the network uses the IMEI of the MTC device to page the MTC device.

When an operator allocates an MSISDN number to one or more MTC devices in an MTC subscriber subscription identified by an IMSI, the network node identifies, by the MSISDN number, an MTC group consisting of MTC devices in the MTC subscriber subscription, and uses the MSI group The MSISDN number identifies all the MTC devices corresponding to the MTC group, and the MSISDN number included in the paging message is used to indicate that all the MTC devices corresponding to the MTC group are paged. At this time, there may be many MTC devices. Performing a paging response operation. In this case, in order to prevent a large number of MTC devices from accessing the network at the same time, the amount of network signaling is greatly increased. After receiving the paging message with the MSISDN number as the paging identifier, the MTC device may延时 Delay the access by means of random delay, etc., so as to avoid simultaneous access to the network.

Scene 4, signing.

After step 302, the method further includes:

When the MTC subscriber makes a contract for the MTC service, the Home Environment (HE), such as an HSS or HLR that records the subscriber subscription data, assigns an IMSI recorded by the operator to the MTC subscriber to record at the MTC subscriber. In the subscription data, wherein the IMSI is used to identify the MTC subscriber subscription.

According to the IMSI of the MTC subscriber subscription and the IMEI of the MTC device, the network node (such as HE) establishes an MTC device subscription data for each MTC device subscribed by the MTC subscriber, and records the IMSI and each MTC in the MTC device subscription data. The device corresponds to the IMEI, and for each Each MTC device contract generates SQN and RAND separately.

For example, the HE signifies the MTC device corresponding to each IMEI that the MTC subscriber subscribes to independently generates SQN and RANDo.

Since this MTC subscriber subscription is provided by one or more MTC devices, MTC subscribers also need to provide the number of MTC devices and the IMEI of each MTC device to the operator. These data are also recorded as part of the MTC subscriber subscription data in each MTC device subscription data corresponding to the MTC subscriber subscription.

When the MTC subscriber subscribes, when the operator allocates an MSISDN number to one or more MTC devices in an MTC subscriber subscription identified by an IMSI, the MSISDN number identifies one of the MTC devices in the MTC subscriber subscription. MTC group. And the module 70 needs to record the MSISDN number in the MTC device subscription data of each MTC device in the MTC group that the MTC subscriber subscribes to. An MTC subscriber contract includes at least one MTC group. By default, an MTC group consisting of all MTC devices corresponding to an MTC subscriber subscription.

For example, an MTC device can be an MTC group alone, or MTC devices A, B, C, D, and E form an MTC group, while MTC devices F, G, and H form another MTC group. In addition, an MTC device belongs to at least one MTC group. For example, MTC device A can be in the largest MTC group GX composed of all other MTC devices in the same MTC subscriber contract, and MTC device A can also form another MTC group GY with MTC device B.

When an MTC group consisting of one or more MTC devices, the operator needs to allocate an MSISDN number for the MTC user to conveniently identify the MTC group, and the MSISDN number can identify the MTC group and the corresponding MTC group. All MTC devices. In this case, the MSISDN number needs to be added to each MTC device subscription data corresponding to this MTC group. For each MTC device in the MTC group, this MSISDN number needs to be written into the SIM/USIM of the MTC device. Since one MTC device can belong to one or more MTC groups, one or more MSISDN numbers exist in the MTC device subscription data of the MTC device, the MTC device context, and the MTC device SIM/USIM. Specifically, the network node adds the MSISDN number to the MTC device subscription data and the MTC device SIM/USIM file of each MTC device corresponding to the MTC group that allocates the MSISDN number.

Scenario 5, Certification (AKA) process.

When the MTC device needs to be authenticated, the network node determines the MTC device that needs to be authenticated according to the device identifier.

For example, in the AKA process of the MTC device in the 3G and LTE systems, the authentication data request message sent by the VLR, the SGSN, and the MME to the HE carries the IMSI and the IMEI. Accordingly, the HE can determine the MTC device to be authenticated according to the MSI and the IMEI. The VLR, SGSN, and MME are then replied to an Authentication Data Response message, providing an authentication vector. Similarly, when the VLR, the SGSN, and the MME update the dynamic information in the HE (eg, the identity of the serving node) by using an Update Location message sent to the HE, the IMSI and the IMEI are carried in the messages; correspondingly, the HE is based on the MSI and The IMEI can determine the MTC device subscription data of the MTC device, and then respond to the VLR, SGSN, and MME with corresponding messages.

Specifically, the AKA process uses a permanent root key K based on the IMSI subscription for the same MTC. Multiple MTC devices subscribed by the subscriber. Because the IMSI is the same, these MTC devices can share the same permanent root key K based on one IMSI, or can use a different permanent key based on the IMEI of each MTC device separately. K.

Further, the permanent key used by the MTC device is the same as the permanent key used by the network node HE corresponding to the MTC device.

Those skilled in the art will appreciate that embodiments of the present invention can be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment, or a combination of software and hardware. Moreover, the invention can be embodied in the form of one or more computer program products embodied on a computer-usable storage medium (including but not limited to disk storage, CD-ROM, optical storage, etc.) in which computer usable program code is embodied.

The present invention has been described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (system), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flowchart illustrations and/or FIG. These computer program instructions can be provided to a general purpose computer, a special purpose computer, An embedded processor or processor of another programmable data processing device to generate a machine such that instructions executed by a processor of a computer or other programmable data processing device are generated for implementation in a flow or a flow of flowcharts and/or Or a block diagram of a device in a box or a function specified in a plurality of boxes.

The computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device. The apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.

These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device. The instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.

Although the preferred embodiment of the invention has been described, it will be apparent to those skilled in the < Therefore, the appended claims are intended to be interpreted as including the preferred embodiments and the modifications and modifications

It can be seen from the above embodiments that: the network node determines the device identifier according to the embodiment of the present invention; the network node determines the corresponding MTC device according to the device identifier; wherein the device identifier includes the IMEI corresponding to the MTC device and the SIM or USIM in the MTC device. Corresponding IMSI.

Since the embodiment of the present invention binds an IMSI and an IMEI to identify an MTC device, an IMSI can be used to sign an MTC device, thereby increasing the number of available identification information in the R10 system of the 3GPP, thereby clearly identifying a large number of The MTC equipment improves system efficiency. The spirit and scope of the invention. Thus, it is intended that the present invention cover the modifications and variations of the inventions

Claims

Rights request

A method for identifying a terminal, the method comprising:

The network node determines a device identifier, where the device identifier includes an international mobile device identifier IMEI corresponding to the MTC device, and an international mobile subscriber identity IMSI corresponding to the subscriber identity module SIM or the global subscriber identity module USIM in the MTC device;

The network node determines a corresponding machine type communication MTC device according to the device identifier.

The method according to claim 1, wherein the determining, by the network node, the corresponding MTC device according to the device identifier includes:

The network node determines, according to the determined device identifier provided by the MTC device, the corresponding MTC device that performs initial registration.

3. The method according to claim 2, wherein the determining, by the network node, the device identifier further comprises:

Receiving, by the network node, IMEI and IMSI provided by the MTC device; or

The network node receives the IMSI provided by the MTC device, and when determining that the IMSI is assigned to an MTC subscriber subscription, sends an IMEI message to the MTC device and receives an IMEI from the MTC device.

The method according to claim 1, wherein the determining, by the network node, the corresponding MTC device according to the device identifier further includes:

The network node adds the device identification to the context of the MTC device.

The method of claim 4, after the adding, by the network node, the device identifier to the context of the corresponding MTC device, the method further includes:

After receiving the message from the other network node, the network node determines the context of the MTC device corresponding to the device identifier according to the device identifier in the message.

The method according to any one of claims 1 to 5, wherein after the determining, by the network node, the device identifier, the method further includes:

When the network node needs to establish an interface association with another network node for the MTC device, The other node sends a message containing the device identifier of the MTC device to notify other network nodes to establish an interface association for the MTC device corresponding to the device identifier.

The method according to any one of claims 1 to 5, further comprising: the network node home environment HE according to the MSI subscribed to the IMSI and the IMEI of the MTC device for each MTC subscribed by the MTC subscriber The device establishes an MTC device subscription data, and records the IMEI corresponding to the IMSI and the MTC device in the MTC device subscription data;

The network node HE separately generates a serial number SQN and a random number RAND for each MTC device contract;

The IMSI is allocated to the MTC subscriber when the MTC subscriber performs a subscription of the MTC service, and the IMSI is used to identify the MTC subscriber subscription.

The method according to claim 1, wherein the determining, by the network node, the corresponding MTC device according to the device identifier, includes:

When the MTC device needs to be authenticated, the network node determines, according to the device identifier, an MTC device that needs to be authenticated.

The method of claim 7, wherein the SIM or USIM of all MTC devices corresponding to the same MTC subscriber contract uses the MTC subscriber to sign the corresponding IMSI;

The method according to claim 9, wherein the permanent key used by the SIM or the USIM in the MTC device is the same as the permanent key used for the subscription in the network node HE corresponding to the MTC device.

The method according to any one of claims 1 to 5, wherein the operator assigns a mobile subscriber integrated service data network MSISDN number to one or more MTC devices in an MTC subscriber subscription identified by an IMSI. The network node uses the MSISDN number to identify an MTC group consisting of the MTC devices in the MTC subscriber subscription, and uses the MSISDN number to identify all the MTC devices corresponding to the MTC group.

12. The method of claim 11 wherein an MTC subscriber signs a contract to Excluding one MTC group; one MTC device belongs to at least one MTC group;

By default, all MTC devices corresponding to an MTC subscriber subscription form an MTC group.

13. The method according to claim 11, wherein the network node adds the MSISDN number to a context, a SIM/USIM file, and an MTC device subscription of each MTC device in the MTC group identified by the MSISDN number. In the data;

When an MTC device belongs to a plurality of different MTC groups at the same time, the network node adds the MSISDN number corresponding to each MTC group to the MTC device subscription data, the SIM/USIM file, and the MTC device context of the MTC device.

The method according to claim 5 or 13, wherein if the message includes an MSISDN number and does not include an IMSI and an IMEI device identifier, the network node sends the message to the MTC subscriber subscription determined by the MSISDN number. An MTC group, and all corresponding MTC devices in the MTC group; when the MTC device receives the paging message with the MSISDN number as the paging identifier, delays access to the network.

A system for identifying a terminal, the system comprising: a plurality of network nodes; each network node is configured to: determine a device identifier, and determine a corresponding machine type communication MTC device according to the device identifier;

16. A network side device, where the network side device includes:

The identifier determining module is configured to determine a device identifier, where the device identifier includes an international mobile device identifier IMEI corresponding to the MTC device, and an international mobile subscriber identity IMSI corresponding to the subscriber identity module SIM or the global subscriber identity module USIM in the MTC device;

And a device determining module, configured to determine, according to the device identifier, a corresponding machine type communication MTC device.

The network side device according to claim 16, wherein the device determining module Specifically used for:

Based on the determined device identification from the MTC device, the corresponding MTC device that performs the initial registration is determined.

The network side device according to claim 17, wherein the network side device further comprises:

a receiving module, configured to receive an IMEI and an IMSI from the MTC device; or receive an IMSI from the MTC device, and send an IMEI message to the MTC device when the IMSI is determined to be assigned to an MTC subscriber, and receive IMEI from the MTC device.

The network side device according to claim 16, wherein the network side device further comprises:

The adding module is configured to add the device identifier to the context of the MTC device corresponding to the device identifier after the device determining module determines the corresponding MTC device according to the device identifier.

The network side device according to claim 19, wherein the network side device further comprises:

a processing module, after the adding module adds the device identifier to the context of the corresponding MTC device, after receiving the message from the other network node, determining the MTC corresponding to the device identifier according to the device identifier in the message The context of the device.

The network side device according to any one of claims 16 to 20, wherein the network side device further includes:

The notification module is configured to send a message including the device identifier of the MTC device to the other network node, and notify the other network node to establish an interface association for the MTC device corresponding to the device identifier.

The network side device according to any one of claims 16 to 20, wherein the network side device further comprises:

Establishing a module, when the MTC subscriber performs a subscription of the MTC service, assigning an IMSI to the MTC subscriber to sign, and establishing an MTC device subscription data for each MTC device subscribed by the MTC subscriber, and recording in the MTC device subscription data IMSI and MTC devices IMEI, and separately generate serial number SQN and random number RANDo in system message for each MTC device subscription

The network side device according to claim 16, wherein the device determining module is specifically configured to:

When the MTC device needs to be authenticated, the MTC device that needs to be authenticated is determined according to the device identifier.

An identifier determining module, configured to identify, by using an MSISDN number, an MTC device in an MTC subscriber subscription when assigning a mobile subscriber integrated service data network MSISDN number to one or more MTC devices in an MTC subscriber subscription identified by an IMSI One MTC group, and all MTC devices corresponding to this MTC group.

The network side device according to claim 24, wherein the identifier determining module is further configured to:

Adding the MSISDN number to the context, the SIM/USIM file, and the MTC device subscription data of the MTC device of each MTC device corresponding to one MTC group that is signed by the MTC subscriber number identified by the MSI subscriber number; when an MTC device belongs to multiple In a different MTC group, the network node adds the MSISDN number corresponding to each MTC group to the MTC device subscription data, the SIM/USIM file of the MTC device, and the context of the MTC device.