CN102238534B

CN102238534B - Terminal identifier notification and maintenance methods and equipment

Info

Publication number: CN102238534B
Application number: CN201110198663.5A
Authority: CN
Inventors: 田野
Original assignee: China Academy of Telecommunications Technology CATT
Current assignee: China Academy of Telecommunications Technology CATT; Datang Mobile Communications Equipment Co Ltd
Priority date: 2011-07-15
Filing date: 2011-07-15
Publication date: 2014-05-07
Anticipated expiration: 2031-07-15
Also published as: CN102238534A

Abstract

The embodiment of the invention discloses a terminal identifier notification method, terminal identifier notification equipment, a terminal identifier maintenance method and terminal identifier maintenance equipment, which relate to the technical field of wireless communication and are used for realizing the binding of an external identifier of a machine type communication (MTC) terminal and an internal identifier of the MTC terminal. The terminal identifier notification method comprises that: core network equipment acquires the external identifier of the MTC terminal; and the core network equipment transmits the internal and external identifiers of the MTC terminal to a network edge. The terminal identifier maintenance method comprises that: the network edge receives the internal and external identifiers of the MTC terminal from the core network equipment; and the network edge locally establishes and maintains mapping relationships between the internal and external identifiers of the MTC terminal. By the scheme, the binding of the internal and external identifiers of the MTC terminal is realized at the network edge.

Description

Terminal identification notification and maintenance method and equipment

Technical Field

The invention relates to the field of wireless communication, in particular to a terminal identifier notification and maintenance method and device.

Background

To support Machine-to-Machine (M2M) communication, 3GPP organizations currently propose an MTC communication architecture as shown in fig. 1. From the aspect of function level, the system mainly comprises three parts, namely a Machine Type Communication (MTC) Server (MTC Server), a 3GPP mobile Communication network and an MTC terminal (MTC Device). The MTC Server is outside the range of a 3GPP network system and is controlled by a network operator or a third-party service provider, and the 3GPP network provides network connection for the MTC terminal to the MTC Server.

An MTC-interworking function (MTC-IWF) entity is a network edge node and shields the details of 3GPP network topology. The entity carries out control signaling interaction with the MTC Server through a newly defined MTCsp interface, calls a specific function provided by a 3GPP network through relaying or converting a signaling protocol on the MTCsp interface, and provides transparent operation control service for the MTC Server.

Through the MTCsp control signaling interface, the MTC Server can send a control signaling to the 3GPP network to request operations such as triggering, controlling, managing, and maintaining the terminal, thereby implementing MTC service characteristics. For example, for an MTC terminal triggering (MTC device triggering) feature, the MTC Server may send a trigger request to the MTC-IWF entity through the MTCsp interface to request the network to initiate triggering on the target terminal, so that the target terminal establishes communication with the MTC Server. When sending an operation instruction to an MTC terminal, the MTCServer needs to be able to uniquely identify a destination MTC terminal involved in the operation.

In a 3GPP network, a subscription between a Subscriber and a network operator uses an International Mobile Subscriber Identity (IMSI), which is stored in a Universal Subscriber Identity Module (USIM) card. When the terminal inserted with the USIM card accesses the network, the terminal can use the IMSI to identify the identity of the terminal. However, in order to protect the privacy of the user, the system radio interface should in principle minimize the use of the IMSI of the user. Therefore, in an Evolved Packet System (EPS) System, a Mobility Management Entity (MME) allocates a Globally Unique Temporary identifier (Globally Unique Temporary ID, GUTI) to a terminal for protecting an IMSI of a user, and the GUTI can also identify an EPS network and the MME that provide services for the user. Roughly a GUTI consists mainly of two parts: the method includes the steps that GUTI is GUMMEI + M-TMSI, GUMMEI is a Globally Unique MME Identity (Global Unique MME Identity) used for uniquely identifying an MME which allocates GUTI for a terminal, and M-TMSI is an MME Temporary Mobile subscriber Identity (MME-Mobile subscriber Identity) used for uniquely identifying the terminal in the MME.

In order to be able to communicate with MTC terminals, an MTC Server first needs to be able to uniquely identify a destination MTC terminal. One straightforward and feasible solution is: the MTC Server identifies the destination terminal using the IMSI. However, directly using the IMSI on the external interface from the network to the MTC Server presents a security risk of IMSI theft. When in use, higher safety and reliability requirements are put forward for a system interface. In addition, when the MTC Server is managed by a third-party service provider, the MTC Server is allowed to directly use the IMSI, which is a security risk of IMSI exposure, and is not beneficial to protecting the privacy of the user.

Therefore, in the current standard discussion process, it is proposed to divide the terminal identity into an external identity and an internal identity. The internal Identifier mainly refers to IMSI (though there may be other identifiers), and the external Identifier may have various forms, such as a full Domain Name (FQDN), a Uniform Resource Name (URN), a Uniform Resource Identifier (SIP URI), and the like, and the internal Identifier is mainly used for facilitating the memory and use of the user.

In the process of implementing the invention, the inventor finds that the following technical problems exist in the prior art:

in order to support the solution of the terminal identification problem, the MTC-IWF and the MTC Server need to be able to bind the external identification of the MTC terminal with the IMIS/GUTI of the MTC terminal. However, this problem is not discussed in standard meetings at present, nor is a solution to this problem given in existing protocols.

Disclosure of Invention

The embodiment of the invention provides a terminal identifier notification and maintenance method and equipment, which are used for realizing the binding of an external identifier of an MTC terminal and an internal identifier of the MTC terminal.

A terminal identification notification method, the method comprising:

after receiving an attachment request message sent by an MTC terminal, an MME acquires an external identifier of the MTC terminal;

the MME acquires an International Mobile Subscriber Identity (IMSI) of the MTC terminal and sends an identity notification message carrying the external identity and the IMSI of the MTC terminal to network edge equipment; or after the globally unique temporary identifier GUTI is allocated to the MTC terminal, the MME sends an identification notification message to network edge equipment, wherein the identification notification message carries the external identifier of the MTC terminal and the allocated GUTI, or carries the external identifier of the MTC terminal, the IMSI and the allocated GUTI;

or,

after receiving the location updating request message, the HSS acquires the external identifier and the IMSI of the MTC terminal from user subscription data stored by the HSS; and the HSS sends an identifier notification message carrying the external identifier and the IMSI of the MTC terminal to the network edge equipment.

A terminal identification notification method, the method comprising:

the MTC terminal receives an attachment acceptance message sent by the MME;

the MTC terminal sends an external identifier of the MTC terminal and an internal identifier of the MTC terminal to an MTC server;

after the MTC terminal sends the external identifier of the MTC terminal and the internal identifier of the MTC terminal to the MTC server, the method further includes: the MTC terminal receives a GUTI re-allocation command sent by the MME, wherein the GUTI re-allocation command carries a new GUTI allocated to the MTC terminal;

the MTC terminal sends an identification updating message to the MTC server, wherein the identification updating message carries the old GUTI and the new GUTI of the MTC terminal, or carries the external identification and the new GUTI of the MTC terminal.

A method for maintaining terminal identification comprises the following steps:

the method comprises the steps that network edge equipment receives an external identifier of an MTC terminal and an internal identifier of the MTC terminal sent by core network equipment;

the network edge equipment establishes and maintains a mapping relation between the external identifier of the MTC terminal and the internal identifier of the MTC terminal locally; or the network edge equipment sends the external identifier of the MTC terminal and the internal identifier of the MTC terminal to an MTC server;

after the network edge device locally establishes and maintains the mapping relationship between the external identifier of the MTC terminal and the internal identifier of the MTC terminal, the method further includes: the network edge equipment receives an identification updating message sent by the MME; if the identifier update message carries the old GUTI and the new GUTI of the MTC terminal, the network edge equipment updates the old GUTI in the maintained mapping relation to the new GUTI; if the identifier update message carries the external identifier of the MTC terminal and the new GUTI, the network edge equipment updates the GUTI corresponding to the external identifier in the maintained mapping relation to the new GUTI;

after the network edge device sends the external identifier of the MTC terminal and the internal identifier of the MTC terminal to the MTC server, the method further includes: the network edge equipment receives an identification updating message sent by an MME, wherein the identification updating message carries an old GUTI and a new GUTI of the MTC terminal, or carries an external identification and a new GUTI of the MTC terminal; and the network edge equipment sends the identification updating message to the MTC server.

A method for maintaining terminal identification comprises the following steps:

the MTC server receives an external identifier of the MTC terminal and an internal identifier of the MTC terminal sent by network edge equipment or the MTC terminal;

the MTC server locally establishes and maintains a mapping relation between an external identifier of the MTC terminal and an internal identifier of the MTC terminal;

after the MTC server locally establishes and maintains the mapping relationship between the external identifier of the MTC terminal and the internal identifier of the MTC terminal, the method further includes: the MTC server receives an identification update message sent by network edge equipment or an MTC terminal; if the identifier updating message carries the old GUTI and the new GUTI of the MTC terminal, the MTC server updates the old GUTI in the maintained mapping relation to the new GUTI; and if the identifier updating message carries the external identifier of the MTC terminal and the new GUTI, the MTC server updates the GUTI corresponding to the external identifier in the maintained mapping relation to the new GUTI.

A terminal identification notification method, the method comprising:

the method comprises the steps that a Home Subscriber Server (HSS) receives a position updating request message which is sent by an MME and used for acquiring an MTC terminal external identifier;

and the HSS sends the stored subscription data of the MTC terminal to the MME, wherein the subscription data comprises the external identifier of the MTC terminal.

A first terminal identification notification apparatus, the apparatus comprising:

the identification acquisition unit is used for acquiring the external identification of the MTC terminal after receiving an attachment request message sent by the MTC terminal;

the identification notification unit is used for acquiring the IMSI of the MTC terminal and sending an identification notification message carrying the external identification and the IMSI of the MTC terminal to network edge equipment; or after the GUTI is allocated to the MTC terminal, sending an identification notification message to network edge equipment, wherein the identification notification message carries the external identification of the MTC terminal and the allocated GUTI, or carries the external identification of the MTC terminal, the IMSI and the allocated GUTI;

or,

the device includes:

the identification acquisition unit is used for acquiring the external identification and the IMSI of the MTC terminal from user subscription data stored by the identification acquisition unit after receiving the position updating request message;

and the identifier notification unit is used for sending an identifier notification message carrying the external identifier and the IMSI of the MTC terminal to the network edge equipment.

An MME, comprising the first terminal identifier notification apparatus.

A second terminal identification notification apparatus, the apparatus comprising:

a message receiving unit, configured to receive an attach accept message sent by an MME;

the MTC terminal comprises an identifier notification unit and an identifier notification unit, wherein the identifier notification unit is used for sending an external identifier of the MTC terminal and an internal identifier of the MTC terminal to an MTC server, and the internal identifier comprises IMSI and/or GUTI;

the device also includes: the identifier updating unit is used for receiving a GUTI reallocation command sent by an MME after sending the external identifier of the MTC terminal and the internal identifier of the MTC terminal to an MTC server, wherein the GUTI reallocation command carries a new GUTI allocated to the MTC terminal; and sending an identification updating message to the MTC server, wherein the identification updating message carries the old GUTI and the new GUTI of the MTC terminal, or carries the external identification and the new GUTI of the MTC terminal.

A first terminal identifier maintenance apparatus, the apparatus comprising:

the MTC terminal comprises an identifier receiving unit, a judging unit and a judging unit, wherein the identifier receiving unit is used for receiving an external identifier of the MTC terminal and an internal identifier of the MTC terminal which are sent by core network equipment;

the identification processing unit is used for locally establishing and maintaining a mapping relation between an external identification of the MTC terminal and an internal identification of the MTC terminal; or the network edge equipment sends the external identifier of the MTC terminal and the internal identifier of the MTC terminal to an MTC server;

the device also includes: the identification updating unit is used for receiving an identification updating message sent by an MME after the mapping relation between the external identification of the MTC terminal and the internal identification of the MTC terminal is locally established and maintained; if the identifier updating message carries the old GUTI and the new GUTI of the MTC terminal, updating the old GUTI in the maintained mapping relation into the new GUTI; if the identifier updating message carries the external identifier of the MTC terminal and the new GUTI, updating the GUTI corresponding to the external identifier in the maintained mapping relation into the new GUTI;

the identification processing unit is further configured to: after the external identifier of the MTC terminal and the internal identifier of the MTC terminal are sent to an MTC server, an identifier update message sent by an MME is received, wherein the identifier update message carries an old GUTI and a new GUTI of the MTC terminal, or carries the external identifier of the MTC terminal and the new GUTI; and sending the identification updating message to an MTC server.

An MTC-IWF entity comprises the first terminal identifier maintenance apparatus.

A second terminal identifier maintenance apparatus, the apparatus comprising:

the MTC terminal comprises an identifier receiving unit, a judging unit and a judging unit, wherein the identifier receiving unit is used for receiving an external identifier of the MTC terminal and an internal identifier of the MTC terminal which are sent by network edge equipment or the MTC terminal;

the identifier maintenance unit is used for locally establishing and maintaining a mapping relation between an external identifier of the MTC terminal and an internal identifier of the MTC terminal;

the device includes:

the identification updating unit is used for receiving an identification updating message sent by network edge equipment or an MTC terminal after the mapping relation between the external identification of the MTC terminal and the internal identification of the MTC terminal is locally established and maintained; if the identifier updating message carries the old GUTI and the new GUTI of the MTC terminal, updating the old GUTI in the maintained mapping relation into the new GUTI; and if the identifier updating message carries the external identifier of the MTC terminal and the new GUTI, updating the GUTI corresponding to the external identifier in the maintained mapping relation into the new GUTI.

An MTC server includes the second terminal identifier maintenance device.

An MTC terminal includes the second terminal identifier notification device.

A fourth terminal identification notification apparatus, comprising:

the request receiving unit is used for receiving a position updating request message which is sent by the MME and used for acquiring the MTC terminal external identifier;

and the identifier notification unit is used for sending the stored subscription data of the MTC terminal to the MME, wherein the subscription data comprises the external identifier of the MTC terminal.

An HSS, comprising the first or fourth terminal identification notifying means.

In the scheme provided by the embodiment of the invention, core network equipment acquires an external identifier of an MTC terminal, the external identifier of the MTC terminal and an internal identifier of the MTC terminal are sent to network edge equipment, and the network edge equipment receives the external identifier of the MTC terminal and the internal identifier of the MTC terminal sent by the core network equipment; and establishing and maintaining a mapping relation between the external identifier of the MTC terminal and the internal identifier of the MTC terminal locally. According to the scheme, the core network equipment informs the network edge equipment of the external identifier and the internal identifier of the MTC terminal, and the scheme that the network edge equipment binds the external identifier and the internal identifier of the MTC terminal is realized.

In the scheme provided by the embodiment of the invention, core network equipment acquires an external identifier of an MTC terminal and sends the external identifier of the MTC terminal and an internal identifier of the MTC terminal to network edge equipment; the network edge equipment sends the external identification of the MTC terminal and the internal identification of the MTC terminal to an MTC server; the MTC server receives an external identifier of an MTC terminal and an internal identifier of the MTC terminal sent by network edge equipment; and establishing and maintaining a mapping relation between the external identifier of the MTC terminal and the internal identifier of the MTC terminal locally. According to the scheme, the core network equipment informs the network edge equipment of the external identifier and the internal identifier of the MTC terminal, and the network edge equipment forwards the external identifier and the internal identifier of the MTC terminal to the MTC server, so that the scheme that the external identifier and the internal identifier of the MTC terminal are bound at the MTC server is realized.

In the scheme provided by the embodiment of the invention, an MTC terminal receives an attachment acceptance message sent by an MME; sending an external identifier of the MTC terminal and an internal identifier of the MTC terminal to an MTC server; the MTC server receives an external identifier of the MTC terminal and an internal identifier of the MTC terminal sent by the MTC terminal; and establishing and maintaining a mapping relation between the external identifier of the MTC terminal and the internal identifier of the MTC terminal locally. According to the scheme, the MTC terminal notifies the MTC server of the external identifier and the internal identifier of the MTC terminal, and the scheme that the MTC server binds the external identifier and the internal identifier of the MTC terminal is realized.

Drawings

FIG. 1 is a diagram of a 3GPP MTC architecture in the prior art;

FIG. 2 is a schematic flow chart of a first method according to an embodiment of the present invention;

FIG. 3 is a schematic flow chart of a second method according to an embodiment of the present invention;

FIG. 4 is a schematic flow chart of a third method according to an embodiment of the present invention;

FIG. 5A is a schematic flow chart of a fourth method according to an embodiment of the present invention;

FIG. 5B is a schematic flow chart of a fifth method according to an embodiment of the present invention;

FIG. 5C is a schematic flow chart of a sixth method provided by an embodiment of the present invention;

FIG. 6A is a schematic flow chart according to a first embodiment of the present invention;

FIG. 6B is a flowchart illustrating a second embodiment of the present invention;

FIG. 6C is a schematic flow chart according to a third embodiment of the present invention;

FIG. 6D is a flowchart illustrating a fourth embodiment of the present invention;

FIG. 7A is a schematic flow chart of a fifth embodiment of the present invention;

FIG. 7B is a schematic flow chart of a sixth embodiment of the present invention;

FIG. 7C is a schematic flow chart of a seventh embodiment of the present invention;

FIG. 7D is a flowchart illustrating an eighth embodiment of the present invention;

FIG. 8A is a flow chart illustrating a ninth embodiment of the present invention;

FIG. 8B is a flowchart illustrating a tenth embodiment of the present invention;

fig. 9 is a schematic structural diagram of a first apparatus according to an embodiment of the present invention;

fig. 10 is a schematic structural diagram of a second apparatus according to an embodiment of the present invention;

fig. 11 is a schematic structural diagram of a third apparatus according to an embodiment of the present invention;

fig. 12 is a schematic structural diagram of a fourth apparatus according to an embodiment of the present invention;

fig. 13 is a schematic structural diagram of a fifth apparatus according to an embodiment of the present invention;

fig. 14 is a schematic structural diagram of a sixth apparatus according to an embodiment of the present invention.

Detailed Description

In order to implement a scheme for binding an external identifier of an MTC terminal with an internal identifier of the MTC terminal, embodiments of the present invention provide a method for notifying and maintaining a terminal identifier.

In the method, core network equipment acquires an external identifier of an MTC terminal, and sends the external identifier of the MTC terminal and an internal identifier of the MTC terminal to network edge equipment, wherein the internal identifier can comprise IMSI and/or GUTI; the method comprises the steps that network edge equipment receives an external identifier of an MTC terminal and an internal identifier of the MTC terminal sent by core network equipment; and establishing and maintaining a mapping relation between the external identifier of the MTC terminal and the internal identifier of the MTC terminal locally. Or,

the method comprises the steps that core network equipment acquires an external identifier of an MTC terminal, and sends the external identifier of the MTC terminal and an internal identifier of the MTC terminal to network edge equipment, wherein the internal identifier comprises IMSI and/or GUTI; the network edge equipment sends the external identification of the MTC terminal and the internal identification of the MTC terminal to an MTC server; the MTC server receives an external identifier of an MTC terminal and an internal identifier of the MTC terminal sent by network edge equipment; and establishing and maintaining a mapping relation between the external identifier of the MTC terminal and the internal identifier of the MTC terminal locally. Or,

the MTC terminal receives an attachment acceptance message sent by the MME; sending an external identifier of the MTC terminal and an internal identifier of the MTC terminal to an MTC server, wherein the internal identifier comprises IMSI and/or GUTI; the MTC server receives an external identifier of the MTC terminal and an internal identifier of the MTC terminal sent by the MTC terminal; and establishing and maintaining a mapping relation between the external identifier of the MTC terminal and the internal identifier of the MTC terminal locally.

The following describes the implementation method of each device:

referring to fig. 2, the method for notifying a terminal identifier according to the embodiment of the present invention includes the following steps:

step 20: the method comprises the steps that core network equipment obtains an external identifier of the MTC terminal;

step 21: and the core network equipment sends the external identifier of the MTC terminal and the internal identifier of the MTC terminal to network edge equipment, wherein the internal identifier comprises IMSI and/or GUTI.

As an embodiment, when the core network device is an MME, the specific implementation of step 20 is: after receiving an attach request message sent by an MTC terminal, an MME acquires an external identifier of the MTC terminal.

Accordingly, the specific implementation of step 21 may be one of the following ways:

firstly, MME acquires IMSI of the MTC terminal and sends an identifier notification message carrying the external identifier and IMSI of the MTC terminal to network edge equipment;

secondly, after allocating the GUTI to the MTC terminal, the MME sends an identification notification message to network edge equipment, wherein the identification notification message carries the external identification of the MTC terminal and the allocated GUTI, or carries the external identification of the MTC terminal, the IMSI and the allocated GUTI.

The MME obtains the external identifier of the MTC terminal, and the specific implementation may be: and the MME acquires the external identifier of the MTC terminal from the user subscription data stored by the HSS or the attachment request message.

The MME obtains the IMSI of the MTC terminal, and may specifically implement one of the following two ways:

firstly, MME acquires IMSI of the MTC terminal from the attach request message;

secondly, the MME acquires the IMSI of the MTC terminal from the old context information of the MTC terminal according to the old GUTI of the MTC terminal.

Preferably, after the MME sends the identifier notification message to the network edge device, when the MME allocates a new GUTI to the MTC terminal, the MME sends an identifier update message to the network edge device, where the identifier update message carries the old GUTI and the new GUTI of the MTC terminal, or carries the external identifier, the new GUTI, and the IMSI of the MTC terminal.

As another embodiment, when the core network device is an HSS, the specific implementation of step 20 is: after receiving the location updating request message, the HSS acquires the external identifier and the IMSI of the MTC terminal from user subscription data stored by the HSS;

accordingly, the step 21 is implemented as follows: and the HSS sends an identifier notification message carrying the external identifier and the IMSI of the MTC terminal to the network edge equipment.

Referring to fig. 3, an embodiment of the present invention provides a terminal identifier notification method, including the following steps:

step 30: the MTC terminal receives an attachment acceptance message sent by the MME;

step 31: the MTC terminal sends an external identifier of the MTC terminal and an internal identifier of the MTC terminal to an MTC server, wherein the internal identifier comprises IMSI and/or GUTI.

In step 31, the MTC terminal sends the external identifier of the MTC terminal and the IMSI of the MTC terminal or sends the external identifier of the MTC terminal and the GUTI of the MTC terminal to the MTC server according to the indication information of the IMSI or GUTI sent to the MTC server by the MTC terminal carried in the attach accept message. For example, when the attach accept message carries indication information for sending the IMSI to the MTC server, the MTC terminal sends the external identifier of the MTC terminal and the IMSI of the MTC terminal to the MTC server; and when the attachment acceptance message carries the indication information for sending the GUTI to the MTC server, the MTC terminal sends the external identifier of the MTC terminal and the GUTI of the MTC terminal to the MTC server.

In step 31, the MTC terminal sends the external identifier of the MTC terminal and the internal identifier of the MTC terminal to the MTC server when determining that the identifier mapping information of the MTC terminal needs to be sent to the MTC server according to the indication information of whether the identifier mapping information of the MTC terminal needs to be sent to the MTC server, which is carried in the attach accept message. For example, if the attach accept message carries indication information that the identifier mapping information of the MTC terminal needs to be sent to an MTC server, the MTC terminal determines that the identifier mapping information of the MTC terminal needs to be sent to the MTC server; otherwise, the MTC terminal determines that the identification mapping information of the MTC terminal does not need to be sent to an MTC server.

In step 31, the MTC terminal sends the external identifier of the MTC terminal and the internal identifier of the MTC terminal to the MTC server through the serving gateway and the packet data gateway. That is, the MTC terminal sends the external identifier of the MTC terminal and the internal identifier of the MTC terminal to the MTC server through the user plane.

Preferably, after the MTC terminal sends the external identifier of the MTC terminal and the internal identifier of the MTC terminal to the MTC server, the MTC terminal receives a GUTI reallocation command sent by the MME, where the GUTI reallocation command carries a new GUTI allocated to the MTC terminal; the MTC terminal sends an identification updating message to the MTC server, wherein the identification updating message carries the old GUTI and the new GUTI of the MTC terminal, or carries the external identification and the new GUTI of the MTC terminal.

Further, after the MTC terminal receives the GUTI reallocation command sent by the MME and before the MTC terminal sends the identifier update message to the MTC server, the MTC terminal may determine whether the identifier mapping information in the MTC server needs to be updated according to the indication information of whether the identifier mapping information in the MTC server needs to be updated, which is carried in the GUTI reallocation command, or the IMSI or GUTI sent to the MTC server, which is carried in the attach accept message, and the indication information of whether the identifier mapping information of the MTC terminal needs to be sent to the MTC server; and when the MTC terminal determines that the identifier mapping information in the MTC server needs to be updated, the MTC terminal sends the identifier updating message to the MTC server. For example, if the GUTI reallocation command carries indication information that the identifier mapping information in the MTC server needs to be updated, the MTC terminal determines that the identifier mapping information in the MTC server needs to be updated; otherwise, the MTC terminal determines that the identifier mapping information in the MTC server does not need to be updated. For another example, if the attach accept message carries indication information for sending a GUTI to the MTC server and for needing to send identifier mapping information of the MTC terminal to the MTC server, the MTC terminal determines that the identifier mapping information in the MTC server needs to be updated; otherwise, the MTC terminal determines that the identifier mapping information in the MTC server does not need to be updated.

Specifically, the MTC terminal may send the identifier update message to the MTC server through the serving gateway and the packet data gateway. Namely, the MTC terminal sends the identification updating message to the MTC server through the user plane.

Referring to fig. 4, an embodiment of the present invention provides a method for maintaining a terminal identifier, including the following steps:

step 40: the method comprises the steps that network edge equipment receives an external identifier of an MTC terminal and an internal identifier of the MTC terminal sent by core network equipment; the internal identifier comprises IMSI and/or GUTI;

step 41: the network edge equipment establishes and maintains a mapping relation between the external identifier of the MTC terminal and the internal identifier of the MTC terminal locally; or the network edge equipment sends the external identifier of the MTC terminal and the internal identifier of the MTC terminal to an MTC server.

Further, after the network edge device establishes and maintains the mapping relationship between the external identifier of the MTC terminal and the internal identifier of the MTC terminal locally, the network edge device receives a control signaling sent by an MTC server for the MTC terminal; the control signaling carries an external identifier of the MTC terminal; and the network edge equipment determines an internal identifier corresponding to the external identifier carried in the control signaling according to the maintained mapping relation, determines a service MME of the MTC terminal according to the internal identifier, and sends the control signaling to the service MME.

Specifically, the determining the serving MME of the MTC terminal according to the internal identifier may specifically be: if the internal identifier is the IMSI, the network edge equipment acquires the routing information of the MTC terminal corresponding to the IMSI from the HSS, and determines a service MME of the MTC terminal according to the routing information; or, if the internal identifier is a GUTI, the network edge device determines the serving MME of the MTC terminal according to the GUMMEI in the GUTI.

Preferably, after the network edge device establishes and maintains the mapping relationship between the external identifier of the MTC terminal and the internal identifier of the MTC terminal locally, the network edge device receives an identifier update message sent by an MME; if the identifier update message carries the old GUTI and the new GUTI of the MTC terminal, the network edge equipment updates the old GUTI in the maintained mapping relation to the new GUTI; and if the identifier updating message carries the external identifier of the MTC terminal and the new GUTI, the network edge equipment updates the GUTI corresponding to the external identifier in the maintained mapping relation to the new GUTI. Or,

preferably, after the network edge device sends the external identifier of the MTC terminal and the internal identifier of the MTC terminal to the MTC server, the network edge device receives an identifier update message sent by an MME, where the identifier update message carries an old GUTI and a new GUTI of the MTC terminal, or carries the external identifier of the MTC terminal and the new GUTI; and the network edge equipment sends the identification updating message to the MTC server.

Referring to fig. 5A, an embodiment of the present invention provides a method for maintaining a terminal identifier, where the method includes:

step 50: the MTC server receives an external identifier of the MTC terminal and an internal identifier of the MTC terminal sent by network edge equipment or the MTC terminal; the internal identifier comprises IMSI and/or GUTI;

step 51: and the MTC server locally establishes and maintains a mapping relation between the external identifier of the MTC terminal and the internal identifier of the MTC terminal.

Further, after the MTC server locally establishes and maintains the mapping relationship between the external identifier of the MTC terminal and the internal identifier of the MTC terminal, the MTC server receives a control signaling sent by an MTC application to the MTC terminal; the control signaling carries an external identifier of the MTC terminal; and the MTC server determines an internal identifier corresponding to the external identifier carried in the control signaling according to the maintained mapping relation, and sends the control signaling carrying the internal identifier to the network edge equipment.

Preferably, after the MTC server locally establishes and maintains the mapping relationship between the external identifier of the MTC terminal and the internal identifier of the MTC terminal, the MTC server receives an identifier update message sent by a network edge device or an MTC terminal; if the identifier updating message carries the old GUTI and the new GUTI of the MTC terminal, the MTC server updates the old GUTI in the maintained mapping relation to the new GUTI; and if the identifier updating message carries the external identifier of the MTC terminal and the new GUTI, the MTC server updates the GUTI corresponding to the external identifier in the maintained mapping relation to the new GUTI.

Referring to fig. 5B, an embodiment of the present invention further provides a terminal identifier notification method, including the following steps:

step 510: the MTC terminal acquires an external identifier of the MTC terminal from information stored in the MTC terminal;

step 511: and the MTC terminal sends an attachment request message to the MME, wherein the attachment request message carries the external identifier.

Referring to fig. 5C, an embodiment of the present invention further provides a terminal identifier notification method, including the following steps:

step 520: the HSS receives a request message for acquiring an MTC terminal external identifier sent by an MME;

step 521: and the HSS sends the external identifier of the MTC terminal to the MME according to the request message.

Specifically, when the request message is a location update request message, the HSS sends the stored subscription data of the MTC terminal to the MME, where the subscription data includes an external identifier of the MTC terminal.

The invention is illustrated below in specific examples:

the first embodiment is as follows:

when signing a contract, the network operator writes the IMSI and the external identifier of the MTC terminal into MTC terminal signing data recorded by the HSS. When the MTC terminal is attached to a network, the MME may obtain an external identifier of the terminal from the subscription data or from the terminal report information, may obtain an IMSI of the terminal from the terminal report information or from the old context of the terminal according to the old GUTI provided by the terminal, and the MME may optionally allocate a new GUTI to the terminal. Thus, the MME will have the IMSI, GUTI and external identification information of the MTC terminal at the same time. Therefore, based on the MME notification, the MTC-IWF can obtain necessary information required so as to establish the binding relationship between the external identifier and the IMSI/GUTI.

This approach requires an additional interface between the MTC-IWF and the MME entity for the transmission of control plane signaling.

As shown in fig. 6A, the method is implemented as follows.

Step 1, when the MTC terminal attaches to the network according to the attach procedure defined in 3GPP TS23.401, the MME acquires the external identity of the terminal. Specifically, there may be two methods: firstly, a terminal reports. The terminal reports the external identification of the terminal to the MME through the attachment request message; second, subscription data acquisition. When the MTC terminal initiates an attachment process, the MME acquires subscription data of the terminal from the HSS through a position updating process, and further acquires an external identifier of the MTC terminal from the subscription data.

When the attach procedure is successfully executed, the MME optionally allocates a GUTI to the terminal and sends the allocated GUTI to the terminal via an attach accept message.

Step 2, for the scene needing to bind the external identifier and the IMSI, the MME sends an identifier notification message to the MTC-IWF, wherein the identifier notification message comprises the information of the IMSI and the external identifier of the MTC terminal; here, the MME may obtain the IMSI identity of the terminal by using the following two methods: firstly, obtaining IMSI of an MTC terminal from an attach request message; secondly, acquiring the IMSI of the MTC terminal from the old context information of the MTC terminal according to the old GUTI of the MTC terminal;

for the scene that the external identifier needs to be bound with the GUTI, when the MME allocates a new GUTI for the MTC terminal, the MME sends an identifier notification message to the MTC-IWF, wherein the identifier notification message contains the information of the new GUTI and the external identifier of the MTC terminal. Optionally, the identifier notification message may also include an IMSI of the MTC terminal.

And 3, the MTC-IWF establishes a mapping relation between the external identifier of the MTC terminal and the IMSI or GUTI according to the received identifier notification message, and locally stores and maintains the mapping relation.

And step 4, the MTC-IWF sends an identification notification response message to the MME to confirm that the identification is bound.

The method needs to add an interface between the MTC-IWF and the MME for transmitting control plane signaling.

Example two:

the IMSI is a permanent identifier obtained by the MTC terminal after subscription, and cannot be easily changed, so the MTC-IWF can be used for a long period of time after the mapping relationship between the external identifier of the MTC terminal and the IMSI is established at one time. However, the GUTI is a temporary identifier allocated by the MME to the terminal, and may be reallocated at any time as required during the use process. Therefore, for the case of using GUTI as the MTC terminal internal identifier, there is also a need for an identifier binding update method as shown in fig. 6B.

Step 1, when the MME allocates a new GUTI for the MTC terminal, the MME sends an identification update message to the MTC-IWF to inform the MTC-IWF that the GUTI of the MTC terminal is changed. The identifier update message contains the old GUTI and the new GUTI information of the MTC terminal, or the identifier update message contains the external identifier and the new GUTI information of the MTC terminal. Optionally, the identifier update message may also include the IMSI of the MTC terminal.

And 2, updating the mapping relation between the external identifier of the MTC terminal and the GUTI and storing and maintaining the mapping relation by using the old GUTI or the external identifier of the MTC terminal as an index by the MTC-IWF according to the received identifier updating message.

And step 3, the MTC-IWF sends an identification updating response message to the MME to confirm that the identification binding relationship is updated.

Example three:

considering that the IMSI is a permanent identifier stored in the HSS by the MTC terminal after subscription, for a scenario in which an external identifier needs to be bound with the IMSI, a method for mapping the external identifier and the IMSI of the MTC terminal at the MTC-IWF based on HSS notification is proposed herein.

When signing a contract, the network operator writes the IMSI and the external identifier of the MTC terminal into MTC terminal signing data recorded by the HSS. When the MTC terminal initiates an attachment process to attach to the network, the MME sends a location update request to the HSS. After receiving the message, HSS sends an identification notification message to MTC-IWF, and notifies the MTC-IWF of the IMSI and the external identification of the MTC terminal, so that the MTC-IWF establishes the binding relationship between the external identification and the IMSI.

This approach requires an additional interface between the MTC-IWF and the HSS entity for the transport of control plane signalling.

As shown in fig. 6C, the specific implementation of the method is as follows:

step 1, in the process that the MTC terminal is attached to the network according to the flow defined in 3GPP TS23.401, the MME sends a location update request message to the HSS.

And step 2, after receiving the position updating request message, the HSS sends an identification notification message to the MTC-IWF to notify the MTC-IWF of the identification information of the MTC terminal, wherein the identification notification message comprises the IMSI and the external identification information of the MTC terminal.

And 3, the MTC-IWF establishes a mapping relation between the IMSI of the MTC terminal and the external identifier according to the received identifier notification message, and locally stores and maintains the mapping relation.

And step 4, the MTC-IWF sends an identification notification response message to the HSS to confirm that the identification is bound.

Example four:

after the mapping relationship between the external identifier and the internal identifier of the MTC terminal is established at the MTC-IWF according to the first to third embodiments, the MTC-IWF sends the control signaling according to the following scheme, as shown in fig. 6D:

step 1: the MTC-IWF receives a control signaling sent by an MTC server to the MTC terminal; the control signaling carries an external identifier of the MTC terminal;

step 2: the MTC-IWF determines an internal identification corresponding to the external identification carried in the control signaling according to the maintained mapping relation between the external identification and the internal identification of the MTC terminal, and determines a service MME of the MTC terminal according to the internal identification; the MTC-IWF also performs the necessary protocol conversion and adaptation for the control signaling as needed.

Specifically, if the internal identifier is an IMSI, the MTC-IWF obtains routing information of the MTC terminal corresponding to the IMSI from the HSS, and determines a serving MME of the MTC terminal according to the routing information; and if the internal identifier is GUTI, the MTC-IWF determines a service MME of the MTC terminal according to GUMMEI in the GUTI.

And step 3, the MTC-IWF sends a control signaling after protocol conversion and adaptation to a service MME of the MTC terminal. And the service MME executes the operation related to the MTC terminal according to the control signaling.

Example five:

when signing a contract, the network operator writes the IMSI and the external identifier of the MTC terminal into MTC terminal signing data recorded by the HSS. When the MTC terminal is attached to a network, the MME may obtain an external identifier of the terminal from the subscription data or from the terminal report information, may obtain an IMSI of the terminal from the terminal report information or from the old context of the terminal according to the old GUTI provided by the terminal, and the MME may optionally allocate a new GUTI to the terminal. Thus, the MME will have the IMSI, GUTI and external identification information of the MTC terminal at the same time. Therefore, based on the MME notification, the MTC Server can obtain necessary information required, so as to establish the binding relationship between the external identifier and the IMSI/GUTI.

As shown in fig. 7A, the specific implementation of the method is as follows:

step 1, when the MTC terminal attaches to the network according to the attach procedure defined in 3GPP TS23.401, the MME acquires the external identity of the terminal. Specifically, there may be two methods: firstly, a terminal reports. The terminal reports the external identification of the terminal to the MME through the attachment request message; second, subscription data acquisition. When the MTC terminal initiates an attachment process, the MME acquires the subscription data of the terminal from the HSS through a position updating process, and further acquires the external identifier of the MTC terminal from the subscription data.

And 3, the MTC-IWF forwards the received identification notification message to the MTC Server.

Specifically, for a scenario that an external identifier needs to be bound with an IMSI, the MTC-IWF forwards a received identifier notification message directly.

For the scenario that the external identifier needs to be bound with the GUTI, for security, if the identifier notification message sent by the MME includes the IMSI, the identifier notification message forwarded does not carry the IMSI information of the MTC terminal in order to not expose the IMSI to the external interface between the 3GPP network and the MTC Server. The MTC-IWF can be reserved for other purposes by the IMSI information in the identification notification message sent by the MME.

And step 4, the MTC Server establishes a mapping relation between the external identifier of the MTC terminal and the IMSI or GUTI according to the received identifier notification message, and locally stores and maintains the mapping relation.

And 5, the MTC Server sends an identification notification response message to the MTC-IWF to confirm that the identification is bound.

And 6, the MTC-IWF forwards an identification notification response message to the MME to confirm that the identification is bound.

Example six:

the IMSI is a permanent identifier obtained by the MTC terminal after subscription, and cannot be easily changed, so the MTC Server can be used for a long period of time after the mapping relationship between the external identifier of the MTC terminal and the IMSI is established at one time. However, the GUTI is a temporary identifier allocated by the MME to the terminal, and may be reallocated at any time as required during the use process. Therefore, for the case of using GUTI as the MTC terminal identifier, there is also a need for an identifier binding update method as shown in fig. 7B.

Step 1, when the MME allocates a new GUTI for the MTC terminal, the MME sends an identification updating message to the MTC-IWF to inform the MTC Server that the GUTI of the MTC terminal is changed. The identifier update message contains the old GUTI and the new GUTI information of the MTC terminal, or the identifier update message contains the new GUTI and the external identifier information of the MTC terminal. Optionally, the identifier update message may also include IMSI information of the MTC terminal.

And step 2, the MTC-IWF forwards the identification updating message to the MTC Server. For security reasons, if the identity update message sent by the MME includes the IMSI, the forwarded identity update message does not carry the IMSI information of the MTC terminal in order to not expose the IMSI to the external interface between the 3GPP network and the MTC Server. And the MTC-IWF can be reserved for other purposes by the IMSI information in the identification updating message sent by the MME.

And 3, the MTC Server updates the mapping relation between the external identifier of the MTC terminal and the GUTI and stores and maintains the mapping relation by taking the old GUTI or the external identifier of the MTC terminal as an index according to the received identifier updating message.

And step 4, the MTC Server sends an identification updating response message to the MTC-IWF to confirm that the identification binding relationship is updated.

And step 5, the MTC-IWF forwards an identification updating response message to the MME to confirm that the identification binding relationship is updated.

Example seven:

considering that the IMSI is a permanent identifier stored in the HSS by the MTC terminal after subscription, for a scenario in which an external identifier needs to be bound with the IMSI, a method for mapping the MTC terminal external identifier and the IMSI at the MTC Server based on HSS notification is proposed herein.

When signing a contract, the network operator writes the IMSI and the external identifier of the MTC terminal into MTC terminal signing data recorded by the HSS. When the MTC terminal initiates an attachment process to attach to the network, the MME sends a location update request to the HSS. After receiving the message, the HSS sends an identification notification message to the MTC-IWF for further notifying the MTC Server of the IMSI and the external identification information of the MTC terminal, so that the MTCServer establishes the binding relationship between the external identification and the IMSI.

As shown in fig. 7C, the method is implemented as follows.

And step 4, the MTC Server establishes a mapping relation between the IMSI of the MTC terminal and the external identifier according to the received identifier notification message, and locally stores and maintains the mapping relation.

And 6, the MTC-IWF forwards an identification notification response message to the HSS to confirm that the identification is bound.

Example eight:

after the MTC Server establishes the mapping relationship between the external identifier and the internal identifier of the MTC terminal according to the fifth to seventh embodiments, the MTC Server sends the control signaling according to the following scheme, as shown in fig. 7D:

step 1, an MTC server receives a control signaling for an MTC terminal sent by an MTC application; the control signaling carries an external identifier of the MTC terminal;

step 2, the MTC server determines an internal identification corresponding to the external identification carried in the control signaling according to the maintained mapping relation between the external identification and the internal identification of the MTC terminal;

and step 3: and the MTC server sends a control signaling carrying the internal identification to the MTC-IWF.

And 4, step 4: and after the MTC-IWF receives the control signaling, determining a service MME of the MTC terminal according to the internal identification carried in the control signaling. The MTC-IWF also performs the necessary protocol conversion and adaptation for the control signaling as needed. And then sending a control signaling to the service MME, and executing the operation related to the MTC terminal by the service MME according to the received control signaling.

Example nine:

besides the above-mentioned implementation of terminal identifier binding at the MTC Server through control plane signaling, the MTC terminal may also implement the method of mapping the external identifier of the MTC terminal with IMSI/GUTI at the MTCServer through user plane message transmission by using PDN connection established when attaching to the network.

As shown in fig. 8A, a specific implementation of the method is as follows.

Step 1, the MTC terminal attaches to the network according to the procedure defined in 3GPP TS 23.401. And when the attachment process is successfully executed, the MME optionally allocates the GUTI to the MTC terminal and sends the allocated GUTI to the MTC terminal through the attachment acceptance message.

Indication information may be added to the attach accept message for indicating to the MTC terminal: whether the MTC terminal needs to inform the MTC Server of the MTC Server identifier mapping information through the user plane and whether the MTC Server needs to bind the external identifier with the IMSI or the GUTI.

And 2, according to the indication information in the attachment acceptance message, the MTC terminal determines whether to notify the terminal identification information and what identification information to notify through the user-oriented MTC Server. And under the condition that the terminal identification information needs to be notified to the MTCServer, the MTC terminal sends an identification notification message to the S-GW for notifying the MTC Server of the identification information of the MTC terminal. According to different indication information, the identifier notification message may include the IMSI and the external identifier of the MTC terminal, or include the GUTI and the external identifier of the MTC terminal.

And step 3, the S-GW forwards the identification notification message to the P-GW.

And 4, the P-GW forwards the identification notification message to the MTC Server.

And step 5, the MTC Server establishes a mapping relation between the IMSI and the external identifier or between the GUTI and the external identifier of the MTC terminal according to the received identifier notification message, and locally stores and maintains the mapping relation.

And 6, the MTC Server forwards an identification notification response message to the P-GW to confirm that the identification is bound.

And step 7, the P-GW transmits an identification notification response message to the S-GW to confirm that the identification is bound.

And step 8, the S-GW forwards an identification notification response message to the MTC terminal and confirms that the identification is bound.

Example ten:

the GUTI is a temporary identifier allocated by the MME for the terminal, and may be reallocated at any time as required during the use process. Therefore, for the case of using GUTI as the MTC terminal identifier, there is also a need for an identifier binding update method as shown in fig. 8B.

Step 1, as required, the MME may initiate a GUTI reallocation procedure according to the procedure defined in 3GPP TS23.401, to reallocate a new GUTI to the MTC terminal.

Indication information can be added in the GUTI re-allocation command and used for indicating the MTC terminal: and whether the terminal needs to update the identification mapping information of the MTC Server through the user plane by itself or not is judged.

And 2, the MTC terminal determines whether the identification mapping information of the MTC Server needs to be updated through the user plane according to the indication information carried in the GUTI reallocation command or the indication information carried in the attachment acceptance message recorded by the terminal in the attachment process. Specifically, when determining whether the identifier mapping information of the MTC Server needs to be updated through the user plane according to the indication information carried in the attach accept message, if the indication information indicates that the terminal needs to notify the identifier mapping information through the user plane to the MTC Server and the MTC Server needs to bind the external identifier with the GUTI, the MTC terminal determines that the identifier mapping information of the MTC Server needs to be updated through the user plane.

And the MTC terminal sends an identification updating message to the S-GW under the condition that the identification mapping information of the MTC Server needs to be updated through the user plane, and the identification updating message is used for informing the MTC Server that the GUTI of the MTC terminal is changed. The identifier update message contains the old GUTI and the new GUTI information of the MTC terminal, or the identifier update message contains the new GUTI and the external identifier information of the MTC terminal.

And step 3, the S-GW forwards the identification updating message to the P-GW.

And 4, the P-GW forwards the identification updating message to the MTC Server.

And step 5, the MTC Server updates the mapping relation between the external identifier of the MTC terminal and the GUTI and stores and maintains the mapping relation by taking the old GUTI or the external identifier of the MTC terminal as an index according to the received identifier updating message.

And 6, the MTC Server forwards the identification updating response message to the P-GW to confirm that the identification is updated.

And step 7, the P-GW forwards an identification updating response message to the S-GW to confirm that the identification is updated.

And step 8, the S-GW forwards an identification updating response message to the MTC terminal and confirms that the identification is updated.

Example eleven:

after the MTC Server establishes the mapping relationship between the external identifier and the internal identifier of the MTC terminal according to the ninth to tenth embodiments, the MTC Server sends the control signaling in the same manner as in the eighth embodiment, which is not described herein again.

An embodiment of the present invention further provides a wireless communication system, including:

the core network equipment is used for acquiring an external identifier of a Machine Type Communication (MTC) terminal and sending the external identifier of the MTC terminal and an internal identifier of the MTC terminal to network edge equipment, wherein the internal identifier comprises an International Mobile Subscriber Identity (IMSI) and/or a Globally Unique Temporary Identifier (GUTI);

the network edge equipment is used for receiving an external identifier of the MTC terminal and an internal identifier of the MTC terminal sent by the core network equipment; and establishing and maintaining a mapping relation between the external identifier of the MTC terminal and the internal identifier of the MTC terminal locally.

the network edge equipment is used for sending the external identifier of the MTC terminal and the internal identifier of the MTC terminal to an MTC server;

the MTC server is used for receiving an external identifier of the MTC terminal and an internal identifier of the MTC terminal sent by network edge equipment; and establishing and maintaining a mapping relation between the external identifier of the MTC terminal and the internal identifier of the MTC terminal locally.

the MTC terminal is used for receiving an attachment acceptance message sent by the MME; sending an external identifier of the MTC terminal and an internal identifier of the MTC terminal to an MTC server, wherein the internal identifier comprises IMSI and/or GUTI;

the MTC server is used for receiving an external identifier of the MTC terminal and an internal identifier of the MTC terminal sent by the MTC terminal; and establishing and maintaining a mapping relation between the external identifier of the MTC terminal and the internal identifier of the MTC terminal locally.

Referring to fig. 9, an embodiment of the present invention further provides a terminal identifier notification apparatus, where the apparatus includes:

an identifier obtaining unit 90, configured to obtain an external identifier of the MTC terminal;

an identifier notification unit 91, configured to send an external identifier of the MTC terminal and an internal identifier of the MTC terminal to a network edge device, where the internal identifier includes an international mobile subscriber identity IMSI and/or a globally unique temporary identifier GUTI.

The identifier obtaining unit 90 is configured to: after receiving an attachment request message sent by an MTC terminal, acquiring an external identifier of the MTC terminal;

the identification notification unit 91 is configured to: obtaining the IMSI of the MTC terminal, and sending an identifier notification message carrying the external identifier and the IMSI of the MTC terminal to network edge equipment; or,

and after the GUTI is distributed to the MTC terminal, sending an identification notification message to network edge equipment, wherein the identification notification message carries the external identification of the MTC terminal and the distributed GUTI, or carries the external identification of the MTC terminal, the IMSI and the distributed GUTI.

The identifier obtaining unit 90 is configured to: after receiving the location updating request message, acquiring the external identifier and the IMSI of the MTC terminal from user subscription data stored by the MTC terminal;

the identification notification unit 91 is configured to: and sending an identifier notification message carrying the external identifier and the IMSI of the MTC terminal to network edge equipment.

The identifier obtaining unit 90 is configured to: and acquiring the external identifier of the MTC terminal from the user subscription data stored by the HSS or the attachment request message.

The identification notification unit 91 is configured to: acquiring the IMSI of the MTC terminal from the attach request message; or,

and acquiring the IMSI of the MTC terminal from the old context information of the MTC terminal according to the old GUTI of the MTC terminal.

The device also includes:

an identifier updating unit 92, configured to send an identifier updating message to the network edge device after sending the identifier notification message to the network edge device, when a new GUTI is allocated to the MTC terminal, where the identifier updating message carries an old GUTI and a new GUTI of the MTC terminal, or carries an external identifier, a new GUTI, and an IMSI of the MTC terminal.

An embodiment of the present invention further provides an MME, where the MME includes the terminal identifier notification apparatus shown in fig. 9.

An embodiment of the present invention further provides an HSS, where the MME includes the terminal identifier notification apparatus shown in fig. 9.

Referring to fig. 10, an embodiment of the present invention further provides a terminal identifier notification apparatus, where the apparatus includes:

a message receiving unit 101, configured to receive an attach accept message sent by an MME;

an identifier notification unit 102, configured to send, to an MTC server, an external identifier of the MTC terminal and an internal identifier of the MTC terminal, where the internal identifier includes an IMSI and/or a GUTI.

The identification notification unit 102 is configured to: and sending the external identifier of the MTC terminal and the IMSI of the MTC terminal to the MTC server or sending the external identifier of the MTC terminal and the GUTI of the MTC terminal to the MTC server according to the indicating information of the IMSI or the GUTI sent to the MTC server carried in the attachment receiving message.

The identification notification unit 102 is configured to: and when determining that the identifier mapping information of the MTC terminal needs to be sent to the MTC server according to the indication information whether the identifier mapping information of the MTC terminal needs to be sent to the MTC server or not, which is carried in the attachment acceptance message, sending an external identifier of the MTC terminal and an internal identifier of the MTC terminal to the MTC server.

The identification notification unit 102 is configured to: and sending the external identifier of the MTC terminal and the internal identifier of the MTC terminal to an MTC server through a service gateway and a packet data gateway.

The device also includes: an identifier updating unit 103, configured to receive a GUTI reallocation command sent by an MME after sending an external identifier of the MTC terminal and an internal identifier of the MTC terminal to an MTC server, where the GUTI reallocation command carries a new GUTI allocated to the MTC terminal; and sending an identification updating message to the MTC server, wherein the identification updating message carries the old GUTI and the new GUTI of the MTC terminal, or carries the external identification and the new GUTI of the MTC terminal.

The identity updating unit 103 is further configured to: after receiving a GUTI reallocation command sent by an MME and before sending an identification updating message to an MTC server, determining whether the identification mapping information in the MTC server needs to be updated according to indication information carried in the GUTI reallocation command, whether IMSI or GUTI needs to be sent to the MTC server, and whether the identification mapping information of the MTC terminal needs to be sent to the MTC server, wherein the indication information is carried in the GUTI reallocation command; and when the determination is yes, sending the identification updating message to an MTC server.

The identity updating unit 103 is configured to: and sending the identification updating message to the MTC server through the serving gateway and the packet data gateway.

An embodiment of the present invention further provides an MTC terminal, where the MTC terminal includes a terminal identifier notification device as shown in fig. 10.

Referring to fig. 11, an embodiment of the present invention further provides a terminal identifier maintenance apparatus, where the apparatus includes:

an identifier receiving unit 110, configured to receive an external identifier of an MTC terminal and an internal identifier of the MTC terminal sent by a core network device; the internal identifier comprises IMSI and/or GUTI;

the identifier processing unit 111 is configured to locally establish and maintain a mapping relationship between an external identifier of the MTC terminal and an internal identifier of the MTC terminal; or the network edge equipment sends the external identifier of the MTC terminal and the internal identifier of the MTC terminal to an MTC server.

The device also includes: a signaling sending unit 112, configured to receive a control signaling sent by an MTC server to the MTC terminal after locally establishing and maintaining a mapping relationship between an external identifier of the MTC terminal and an internal identifier of the MTC terminal; the control signaling carries an external identifier of the MTC terminal; and determining an internal identifier corresponding to an external identifier carried in the control signaling according to the maintained mapping relation, determining a service Mobility Management Entity (MME) of the MTC terminal according to the internal identifier, and sending the control signaling to the service MME.

The signaling sending unit 112 is configured to: when the internal identifier is IMSI, obtaining the routing information of the MTC terminal corresponding to the IMSI from HSS, and determining a service MME of the MTC terminal according to the routing information; or,

and when the internal identifier is GUTI, determining a service MME of the MTC terminal according to GUMMEI in the GUTI.

The device also includes: an identifier updating unit 113, configured to receive an identifier update message sent by an MME after a mapping relationship between an external identifier of the MTC terminal and an internal identifier of the MTC terminal is locally established and maintained; if the identifier update message carries the old GUTI and the new GUTI of the MTC terminal, the network edge equipment updates the old GUTI in the maintained mapping relation to the new GUTI; and if the identifier updating message carries the external identifier of the MTC terminal and the new GUTI, the network edge equipment updates the GUTI corresponding to the external identifier in the maintained mapping relation to the new GUTI.

The identification processing unit 111 is further configured to: after the external identifier of the MTC terminal and the internal identifier of the MTC terminal are sent to an MTC server, an identifier update message sent by an MME is received, wherein the identifier update message carries an old GUTI and a new GUTI of the MTC terminal, or carries the external identifier of the MTC terminal and the new GUTI; and sending the identification updating message to an MTC server.

An embodiment of the present invention further provides an MTC-IWF entity, where the MTC-IWF entity includes a terminal identifier maintenance apparatus as shown in fig. 11.

Referring to fig. 12, an embodiment of the present invention further provides a terminal identifier maintenance apparatus, where the apparatus includes:

an identifier receiving unit 120, configured to receive an external identifier of an MTC terminal and an internal identifier of the MTC terminal sent by a network edge device or the MTC terminal; the internal identifier comprises IMSI and/or GUTI;

an identifier maintenance unit 121, configured to locally establish and maintain a mapping relationship between an external identifier of the MTC terminal and an internal identifier of the MTC terminal.

The device also includes: a signaling sending unit 122, configured to receive a control signaling sent by an MTC application for the MTC terminal after locally establishing and maintaining a mapping relationship between an external identifier of the MTC terminal and an internal identifier of the MTC terminal; the control signaling carries an external identifier of the MTC terminal; and determining an internal identifier corresponding to the external identifier carried in the control signaling according to the maintained mapping relation, and sending the control signaling carrying the internal identifier to the network edge equipment.

The device also includes: an identifier updating unit 123, configured to receive an identifier update message sent by a network edge device or an MTC terminal after locally establishing and maintaining a mapping relationship between an external identifier of the MTC terminal and an internal identifier of the MTC terminal; if the identifier updating message carries the old GUTI and the new GUTI of the MTC terminal, the MTC server updates the old GUTI in the maintained mapping relation to the new GUTI; and if the identifier updating message carries the external identifier of the MTC terminal and the new GUTI, the MTC server updates the GUTI corresponding to the external identifier in the maintained mapping relation to the new GUTI.

An embodiment of the present invention further provides an MTC server, where the MTC server includes a terminal identifier maintenance device as shown in fig. 12.

Referring to fig. 13, an embodiment of the present invention further provides a terminal identifier notification apparatus, where the apparatus includes:

an identification acquisition unit 130 for acquiring an external identification of itself;

an identifier notifying unit 131, configured to send an attach request message to the MME, where the attach request message carries the external identifier.

An embodiment of the present invention further provides an MTC terminal, where the MTC terminal includes a terminal identifier notification device as shown in fig. 13.

Referring to fig. 14, an embodiment of the present invention further provides a terminal identifier notification apparatus, where the apparatus includes:

a request receiving unit 140, configured to receive a request message for acquiring an MTC terminal external identifier sent by an MME;

an identifier notification unit 141, configured to send the external identifier of the MTC terminal to the MME according to the request message.

The identification notifying unit 141 is configured to: and when the request message is a location updating request message, sending the stored subscription data of the MTC terminal to the MME, wherein the subscription data comprises the external identifier of the MTC terminal.

An embodiment of the present invention further provides an HSS, where the HSS includes a terminal identifier notification apparatus as shown in fig. 14.

In the invention, the network edge device may be a machine type communication interworking function (MTC-IWF) entity. The external identifier of the MTC terminal may be: a full domain name (FQDN), or a Uniform Resource Name (URN), or a uniform resource identifier (SIP URI).

In conclusion, the beneficial effects of the invention include:

in the scheme provided by the embodiment of the invention, core network equipment acquires an external identifier of an MTC terminal and sends the external identifier of the MTC terminal and an internal identifier of the MTC terminal to network edge equipment; the method comprises the steps that network edge equipment receives an external identifier of an MTC terminal and an internal identifier of the MTC terminal sent by core network equipment; and establishing and maintaining a mapping relation between the external identifier of the MTC terminal and the internal identifier of the MTC terminal locally. According to the scheme, the core network equipment informs the network edge equipment of the external identifier and the internal identifier of the MTC terminal, and the scheme that the network edge equipment binds the external identifier and the internal identifier of the MTC terminal is realized.

The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

While preferred embodiments of the present invention have been described, additional variations and modifications in those embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. Therefore, it is intended that the appended claims be interpreted as including preferred embodiments and all such alterations and modifications as fall within the scope of the invention.

It will be apparent to those skilled in the art that various changes and modifications may be made in the present invention without departing from the spirit and scope of the invention. Thus, if such modifications and variations of the present invention fall within the scope of the claims of the present invention and their equivalents, the present invention is also intended to include such modifications and variations.

Claims

1. A method for notifying a terminal identifier, the method comprising:

or,

2. The method of claim 1, wherein the MME acquiring the external identity of the MTC terminal comprises:

and the MME acquires the external identifier of the MTC terminal from the user subscription data stored by the HSS or the attachment request message.

3. The method of claim 1, wherein obtaining, by an MME, an IMSI for the MTC terminal comprises:

the MME acquires the IMSI of the MTC terminal from the attachment request message; or,

and the MME acquires the IMSI of the MTC terminal from the old context information of the MTC terminal according to the old GUTI of the MTC terminal.

4. The method of claim 1, wherein after the MME sends an identity notification message to the network edge device, the method further comprises:

and when the MME allocates a new GUTI to the MTC terminal, sending an identification updating message to network edge equipment, wherein the identification updating message carries the old GUTI and the new GUTI of the MTC terminal, or carries the external identification, the new GUTI and the IMSI of the MTC terminal.

5. A method for notifying a terminal identifier, the method comprising:

the MTC terminal receives an attachment acceptance message sent by the MME;

after the MTC terminal sends the external identifier of the MTC terminal and the internal identifier of the MTC terminal to the MTC server, the method further includes: the MTC terminal receives a GUTI re-allocation command sent by the MME, wherein the GUTI re-allocation command carries a new GUTI allocated to the MTC terminal; the MTC terminal sends an identification updating message to the MTC server, wherein the identification updating message carries the old GUTI and the new GUTI of the MTC terminal, or carries the external identification and the new GUTI of the MTC terminal.

6. The method of claim 5, wherein the MTC terminal sending the external identity of the MTC terminal and the internal identity of the MTC terminal to an MTC server comprises:

and the MTC terminal sends the external identifier of the MTC terminal and the IMSI of the MTC terminal to the MTC server or sends the external identifier of the MTC terminal and the GUTI of the MTC terminal to the MTC server according to the indication information of the IMSI or the GUTI, which is sent to the MTC server and carried in the attachment receiving message.

7. The method of claim 5, wherein the MTC terminal sending the external identity of the MTC terminal and the internal identity of the MTC terminal to an MTC server comprises:

and the MTC terminal sends the external identifier of the MTC terminal and the internal identifier of the MTC terminal to the MTC server when determining that the identifier mapping information of the MTC terminal needs to be sent to the MTC server according to the indication information whether the identifier mapping information of the MTC terminal needs to be sent to the MTC server or not, wherein the indication information is carried in the attachment acceptance message.

8. The method of claim 5, wherein an MTC terminal sends the external identity of the MTC terminal and the internal identity of the MTC terminal to an MTC server through a serving gateway and a packet data gateway.

9. The method of claim 5, wherein after the MTC terminal receives the GUTI reallocation command sent by the MME and before sending an identity update message to the MTC server, the method further comprises:

the MTC terminal determines whether the identifier mapping information in the MTC server needs to be updated according to the indication information whether the identifier mapping information in the MTC server needs to be updated or the indication information whether the IMSI or the GUTI is sent to the MTC server or not, and whether the identifier mapping information of the MTC terminal needs to be sent to the MTC server or not, wherein the indication information is carried in the GUTI reallocation command;

the sending the identifier update message to the MTC server comprises:

and when the MTC terminal determines that the identifier mapping information in the MTC server needs to be updated, the MTC terminal sends the identifier updating message to the MTC server.

10. The method of claim 5, wherein the MTC terminal sends the identity update message to an MTC server through a serving gateway and a packet data gateway.

11. A method for maintaining a terminal identifier is characterized by comprising the following steps:

12. The method of claim 11, wherein after a network edge device locally establishes and maintains a mapping relationship between an external identifier of the MTC terminal and an internal identifier of the MTC terminal, the method further comprises;

the method comprises the steps that network edge equipment receives a control signaling sent by an MTC server to an MTC terminal; the control signaling carries an external identifier of the MTC terminal;

and the network edge equipment determines an internal identifier corresponding to the external identifier carried in the control signaling according to the maintained mapping relation, determines a service Mobility Management Entity (MME) of the MTC terminal according to the internal identifier, and sends the control signaling to the service MME.

13. The method of claim 12, wherein the determining the serving MME for the MTC terminal according to the internal identity comprises:

if the internal identifier is the IMSI, the network edge equipment acquires the routing information of the MTC terminal corresponding to the IMSI from the HSS, and determines a service MME of the MTC terminal according to the routing information; or,

and if the internal identifier is a GUTI, the network edge equipment determines a service MME of the MTC terminal according to the GUMMEI in the GUTI.

14. A method for maintaining a terminal identifier is characterized by comprising the following steps:

15. The method of claim 14, wherein after an MTC server locally establishes and maintains a mapping relationship between an external identity of the MTC terminal and an internal identity of the MTC terminal, the method further comprises;

the MTC server receives a control signaling sent by an MTC application to the MTC terminal; the control signaling carries an external identifier of the MTC terminal;

and the MTC server determines an internal identifier corresponding to the external identifier carried in the control signaling according to the maintained mapping relation, and sends the control signaling carrying the internal identifier to the network edge equipment.

16. A method for notifying a terminal identifier, the method comprising:

17. A terminal identification notification apparatus, characterized in that the apparatus comprises:

or,

the device includes:

18. The apparatus of claim 17, wherein the identity acquisition unit is to:

and acquiring the external identifier of the MTC terminal from the user subscription data stored by the HSS or the attachment request message.

19. The apparatus of claim 17, wherein the identification notification unit is to:

acquiring the IMSI of the MTC terminal from the attach request message; or,

20. The apparatus of claim 17, further comprising:

and the identifier updating unit is used for sending an identifier updating message to the network edge device after sending the identifier notification message to the network edge device and when a new GUTI is allocated to the MTC terminal, wherein the identifier updating message carries the old GUTI and the new GUTI of the MTC terminal, or carries the external identifier, the new GUTI and the IMSI of the MTC terminal.

21. A terminal identification notification apparatus, characterized in that the apparatus comprises:

22. The apparatus of claim 21, wherein the identification notification unit is to:

and sending the external identifier of the MTC terminal and the IMSI of the MTC terminal to the MTC server or sending the external identifier of the MTC terminal and the GUTI of the MTC terminal to the MTC server according to the indicating information of the IMSI or the GUTI sent to the MTC server carried in the attachment receiving message.

23. The apparatus of claim 21, wherein the identification notification unit is to:

and when determining that the identifier mapping information of the MTC terminal needs to be sent to the MTC server according to the indication information whether the identifier mapping information of the MTC terminal needs to be sent to the MTC server or not, which is carried in the attachment acceptance message, sending an external identifier of the MTC terminal and an internal identifier of the MTC terminal to the MTC server.

24. The apparatus of claim 21, wherein the identification notification unit is to:

and sending the external identifier of the MTC terminal and the internal identifier of the MTC terminal to an MTC server through a service gateway and a packet data gateway.

25. The apparatus as recited in claim 21, wherein said identification update unit is further configured to:

after receiving a GUTI reallocation command sent by an MME and before sending an identification updating message to an MTC server, determining whether the identification mapping information in the MTC server needs to be updated according to indication information carried in the GUTI reallocation command, whether IMSI or GUTI needs to be sent to the MTC server, and whether the identification mapping information of the MTC terminal needs to be sent to the MTC server, wherein the indication information is carried in the GUTI reallocation command; and when the determination is yes, sending the identification updating message to an MTC server.

26. The apparatus of claim 21, wherein the identification update unit is to: and sending the identification updating message to the MTC server through the serving gateway and the packet data gateway.

27. A terminal identification maintenance apparatus, characterized in that the apparatus comprises:

the MTC terminal comprises an identifier receiving unit, a judging unit and a judging unit, wherein the identifier receiving unit is used for receiving an external identifier of the MTC terminal and an internal identifier of the MTC terminal which are sent by core network equipment; the internal identifier comprises IMSI and/or GUTI;

the identification processing unit is used for locally establishing and maintaining a mapping relation between an external identification of the MTC terminal and an internal identification of the MTC terminal; or, sending the external identifier of the MTC terminal and the internal identifier of the MTC terminal to an MTC server;

28. The apparatus of claim 27, further comprising:

the signaling sending unit is used for receiving a control signaling sent by an MTC server to the MTC terminal after locally establishing and maintaining a mapping relation between an external identifier of the MTC terminal and an internal identifier of the MTC terminal; the control signaling carries an external identifier of the MTC terminal;

and determining an internal identifier corresponding to an external identifier carried in the control signaling according to the maintained mapping relation, determining a service Mobility Management Entity (MME) of the MTC terminal according to the internal identifier, and sending the control signaling to the service MME.

29. The apparatus of claim 28, wherein the signaling unit is configured to:

when the internal identifier is IMSI, obtaining the routing information of the MTC terminal corresponding to the IMSI from HSS, and determining a service MME of the MTC terminal according to the routing information; or,

30. A terminal identification maintenance apparatus, characterized in that the apparatus comprises:

the MTC terminal comprises an identifier receiving unit, a judging unit and a judging unit, wherein the identifier receiving unit is used for receiving an external identifier of the MTC terminal and an internal identifier of the MTC terminal which are sent by network edge equipment or the MTC terminal; the internal identifier comprises IMSI and/or GUTI;

the device includes:

31. The apparatus of claim 30, wherein the apparatus comprises:

the signaling sending unit is used for receiving a control signaling sent by an MTC application to the MTC terminal after locally establishing and maintaining a mapping relation between an external identifier of the MTC terminal and an internal identifier of the MTC terminal; the control signaling carries an external identifier of the MTC terminal;

and determining an internal identifier corresponding to the external identifier carried in the control signaling according to the maintained mapping relation, and sending the control signaling carrying the internal identifier to the network edge equipment.

32. A terminal identification notification apparatus, characterized in that the apparatus comprises:

33. A mobility management entity, MME, characterized in that it comprises a terminal identity notification apparatus according to any of claims 17-20.

34. A home subscriber server, HSS, characterized in that the HSS comprises a terminal identity notification apparatus as claimed in any one of claims 17 and 32.

35. An MTC terminal, characterized in that the MTC terminal comprises the terminal identity notification device according to any one of claims 21 to 26.

36. A machine type communication interworking function, MTC-IWF, entity, characterized in that the MTC-IWF entity comprises a terminal identity maintenance apparatus according to any of claims 27 to 29.

37. An MTC server, characterized in that the MTC server comprises the terminal identity maintenance device according to any of claims 30 to 31.