WO2012100674A1

WO2012100674A1 - A signaling optimization method and system for machine type communication (mtc) devices setting together

Info

Publication number: WO2012100674A1
Application number: PCT/CN2012/070196
Authority: WO
Inventors: 李勉; 吴昊; 梁爽; 卢飞
Original assignee: 中兴通讯股份有限公司
Priority date: 2011-01-26
Filing date: 2012-01-10
Publication date: 2012-08-02
Also published as: CN102625271B; CN102625271A

Abstract

Disclosed in the present invention area signaling optimization method and system for Machine Type Communication (MTC) devices setting together, wherein a Representative-Machine Device (R-MD) and a Machine Type Communication User Equipment (MTC UE) which are setting together are directed to the same mobile management unit, and associated relationship between the R-MD and MTCUE is established; based on the associated relationship, the R-MD replaces the MTC UE to perform the subsequent mobility management flow; the R-MD is used to represent the MTC UE, and is similar to the MTC UE terminal. For the MTC UE setting together, the method and system in the present invention can realize optimization for signaling associated with mobility management according to characteristic of MTC, save the mobility management signaling and reduce the signaling peak value and the electrical loss of the terminals, at the same time MTC devices can communicate with the respective MTC servers independently.

Description

Signaling optimization method and system for jointly setting MTC equipment

The present invention relates to the field of communications, and in particular, to a signaling optimization method and system for a machine type communication (MTC) device. Background technique

With the emergence of the World Interoperability for Microwave Access (WiMax) technology, the third generation of mobile communication systems must maintain their competitiveness in the field of mobile communications, and must improve their network performance and reduce network construction and operation. cost. Therefore, the Standardization Working Group of the 3rd Generation Partnership Project (3GPP) is currently working on PS Core (Packet Switch Core) and UTRAN (Universal Mobile Telecommunication System Radio Access Network, global). Evolution of mobile communication system radio access networks). The research topic is called System Architecture Evolution (SAE), which aims to enable Evolved Packet Core (EPC) to provide higher transmission rates, shorter transmission delays, optimized packetization, and support. Mobility management between E-UTRAN (Evolved UTRAN, Evolved UTRAN), UTRAN, Wireless Local Area Network (WLAN), and other non-3GPP access networks.

The architecture of the current SAE is as shown in FIG. 1. The network element included in the Evolved Universal Terrestrial Radio Access Network (E-UTRAN) is an Evolved NodeB (eNodeB). , used to provide wireless resources for user access; Packet Data Network (PDN) is a network that provides services for users; EPC provides lower latency and allows more wireless access systems to access, It includes the following network elements: The Mobility Management Entity (MME) is a control plane function entity that temporarily stores user data. It is responsible for managing and storing the context of user equipment (User Equipment, UE) (such as user identity, mobility management status, and user). Security parameters, etc.), assigning a temporary identifier to the user, when the UE is camped in the tracking area or the network, is responsible for authenticating the user; processing all non-access stratum messages between the MME and the UE; triggering the search in the SAE call. The MME is a mobility management entity of the SAE system. In the Universal Mobile Telecommunications System (UMTS), the mobility management entity is a General Packet Radio Service (GPRS) support node (Serving GPRS Support Node). , SGSN).

The Serving Gateway (SGW) is a user plane entity responsible for user plane data routing processing, terminating the downlink data of the UE in the idle (ECM_IDLE) state, and managing and storing the SAE bearer context of the UE, such as IP bearer service parameters and network internal routing information. The SGW is the anchor point of the internal user plane of the 3GPP system. A user can only have one SGW at a time.

The packet data network gateway (PDN Gateway, PGW) is the gateway responsible for the UE accessing the PDN, and can allocate the user IP address; and is also the mobility anchor of the 3GPP and non-3GPP access systems. The functions of the PGW also include policy implementation and billing support. Users can access multiple PGWs at the same time. The Policy and Charging Enforcement Function (PCEF) entity is also located in the PGW.

The Policy and Charging Rules Function (PCRF) entity is responsible for providing policy control and charging rules to the PCEF.

The Home Subscriber Server (HSS) is responsible for permanently storing user subscription data. The content stored in the HSS includes the International Mobile Subscriber Identification (IMSI) of the UE and the IP address of the PGW.

Physically, the SGW and the PGW may be unified, and the EPC system user plane network element includes the SGW. And PGW.

The definition in the narrow sense of M2M is machine-to-machine communication. Broadly defined is a networked application and service centered on intelligent interaction of machine terminals. It is based on intelligent machine terminals, and uses various communication methods as access means to provide customers with information solutions to meet customers' information needs in monitoring, command and dispatch, data acquisition and measurement.

The development of wireless technology is an important factor in the development of the M2M market. It breaks through the space-time constraints and geographical barriers of traditional communication methods, freeing enterprises and the public from cable restraints, enabling customers to more effectively control costs, reduce installation costs, and is simple and convenient to use. . In addition, the growing demand is driving M2M to move forward: Contrary to the growing ability of information processing and network bandwidth, the means of information acquisition are far behind. And M2M satisfies people's needs very well, through which people can monitor the external environment in real time and achieve large-scale, automated information collection. Therefore, M2M can be applied to industrial applications, home applications, personal applications, and the like. Industry applications such as: traffic monitoring, warning systems, marine rescue, vending machines, car payment, etc.; home applications such as: automatic meter reading, temperature control, etc.; personal applications such as: life detection, remote diagnosis.

The communication objects of M2M are machine-to-machine and human-to-machine. Data communication between one or more machines is defined as Machine Type Communication (MTC), in which case less human interaction is required. A machine participating in MTC, defined as an MTC device. The MTC device is the terminal of the MTC user and can communicate with the MTC device and the MTC server through the PLMN network. Mobile Equipment (ME) is a function block attached to the MTC device. This function block is used to connect the MTC device to the EPS system. The MTC Server manages and monitors MTC devices. FIG. 2 is a schematic diagram of a ME accessing an EPS through an EUTRAN in the prior art.

Since MTC devices are mostly for specific applications, such as automatic meter reading and life detection, different devices are used. Different applications of MTC equipment have different characteristics, such as elevators and other elevator equipment with low mobility, PS only attributes, while monitoring, alarm equipment in addition to low mobility, PS In addition, it also has attributes such as low data transfer and high availability. Therefore, different system optimizations for different application MTC devices can effectively manage, monitor, and pay for MTC devices.

In practical applications, there are some MTC devices that, although independently applied to different services, ie, communicate with different MTC servers, these MTC devices have features of substantially simultaneous co-directional motion for certain periods of time. For example, in order to facilitate tracking of goods, the courier company will label each cargo. The tag can be an MTC device and communicate with the courier company's server at any time, such as: transmitting data or reporting location information. Different courier companies may use the same logistics and transportation company to transport the goods, so the same truck of the logistics company will be loaded with goods from different courier companies, each of which passes the MTC equipment as the label and the corresponding courier company. The server performs data communication; for example: In the vehicle dispatch management application, different MTC devices can be applied to different functions, such as reporting the specific location of the vehicle to the vehicle dispatch center, vehicle reservation, vehicle navigation, vehicle fault detection, etc. The MTC devices are mounted on the vehicle, moving simultaneously in the same direction as the vehicle is running, and these MTC devices independently communicate data with their respective MTC servers. In the above practical application, the number of such MTC equipments moving in the same direction may be as large as 4, such as a large number of express goods on a truck or cargo ship of a logistics company; or a large traffic flow in a vehicle dispatch management application. Intensive places, such as train stations, hotels or tourist attractions, there will be a lot of concentrated vehicles, and the total amount of MTC equipment on these vehicles will be 4 inches. When a large number of these MTC devices move in the same direction at the same time and perform signaling interaction with the network to perform the mobility management process, the mobility management signaling peaks, which imposes a large load on the network. And for such a joint (for example, temporary assembly or permanent assembly of simultaneous simultaneous movement) MTC devices, from the point of view of the mobility of the terminal to the network, their movement direction and time are consistent, this kind of In this case, the mobility management process of each MTC device is still caused to waste the air interface resources and the terminal power loss. Summary of the invention

In view of this, the main purpose of the present invention is to provide a signaling optimization for a common MTC device. The method and system optimize the mobility management related signaling for the common MTC UE, so that the MTC device can save mobility management signaling while being able to communicate with the respective MTC server independently.

In order to achieve the above object, the technical solution of the present invention is achieved as follows:

A signaling optimization method for a common machine type communication MTC device, including:

The radio access network side network element directs the common R-MD and the MTC user equipment UE to the same mobility management unit, and the mobility management unit establishes an association relationship between the R-MD and the MTC UE; the mobility management process includes : Performing a periodic or aperiodic routing area or an update or tracking area or update procedure by the R-MD instead of the MTC UE.

The method further includes:

Establishing a local connection between the R-MD and the MTC UE and exchanging identifiers for subsequent associations;

The R-MD notifies the mobility management unit of the opening of the related function by using the network access request message; and the identifier of the R-MD is carried in the RRC parameter of the RRC parameter when the area update request or the tracking area update request is received by the wireless connection The network side network element selects, for the MTC UE, a mobility management unit currently serving the R-MD.

The method for establishing the association relationship is:

The MTC UE carries, in the attach request, the routing area update request, or the tracking area update request message, an identifier that is required to be associated with the R-MD to the mobility management unit, where the mobility management unit locally uses the R-MD The MTC UE is associated.

The association is embodied in the form of an association table;

Synchronizing the R-MD with the routing area update timer or the tracking area update timer of the MTC UE by the mobility management unit; The mobility management unit notifies the MTC UE not to initiate a subsequent routing area update request or a tracking area update request in the network access request response message of the MTC UE.

When the R-MD performs the periodic routing area update or tracking area update process, the mobility management unit simultaneously updates the contexts of all MTC UEs in the association relationship table, and synchronizes the R-MD and the MTC. The routing area update timer or tracking area update timer of the UE.

When the R-MD performs the aperiodic routing area update or the tracking area update process, the new mobility management unit obtains the GPRS support node SGSN context update request/response message or the context request/response message from the original mobility management unit. The association table between the R-MD and the MTC UE and the context of the MTC UE are saved locally.

The R-MD performs the aperiodic routing area update or the tracking area update process, and simultaneously updates the control plane bearer information of the R-MD and all the MTC UEs on the new mobility management unit and the gateway unit, Includes:

The update of the control plane bearer information is performed by a PDP context update request message, a bearer modification request message, or a session creation request message.

When the R-MD performs the aperiodic routing area update or the tracking area update process, the new identity identifier allocated to the R-MD and the MTC UE is compression-encoded and sent to the R-MD. The R-MD; the issuing method includes:

The mobility management unit delivers the new identity to the R-MD by using a routing area update accept message or a tracking area update accept message.

After the R-MD receives the new identity identifier delivered by the mobility management unit, the R-MD further includes:

And sending, by the R-MD, the new identity to the MTC UE by using a local connection. The method further includes:

The R-MD updates or tracks periodic or non-periodic routing areas through local connections. Whether the zone or update process is successful is notified to the MTC UE.

The method further includes: the MTC UE determining that the local connection is disconnected, notifying the network to delete the association relationship with the R-MD, and independently performing the normal mobility management process;

Alternatively, the MTC UE determines that the network connection is disconnected, and notifies the network to delete the association relationship with the R-MD.

A signaling optimization system for jointly setting up an MTC device, comprising a common set-up unit, a co-located unit, and a common mobility management unit;

The common setting unit is configured to direct the common R-MD and the MTC UE to the same mobile management unit;

The association unit is configured to establish an association relationship between the R-MD and the MTC UE, and the common mobility management unit is configured to control the R-MD to perform subsequent mobility management instead of the MTC UE based on the association relationship. The process includes: replacing, by the R-MD, the periodic or aperiodic routing area update or tracking area update process by the MTC UE.

The R-MD is further configured to establish a local connection with the MTC UE and exchange identifiers for subsequent association with each other, and notify the mobility management unit of the opening of the related function by using a network access request message;

The MTC UE is further configured to: after acquiring the identifier of the R-MD, carry the identifier of the R-MD in an RRC parameter, triggering a wireless, when an attach request, a routing area update request, or a tracking area update request The access network side network element selects, for the MTC UE, a mobility management unit currently serving the R-MD.

Wherein, when the association unit establishes the association relationship, it is used to:

The control MTC UE carries an identifier that is required to be associated with the R-MD to the mobility management unit in an attach request, a routing area update request, or a tracking area update request message, and triggers the mobility management unit to locally perform the R- The MD is associated with the MTC UE.

The association is embodied in the form of an association table; The mobility management unit is further configured to locally synchronize the routing area update timer or the tracking area update timer of the R-MD with the MTC UE, and notify the network access request response message of the MTC UE The MTC UE does not initiate a subsequent routing area update request or a tracking area update request.

When the R-MD performs the periodic routing area update or the tracking area update process, the R-MD is further configured to trigger the mobility management unit to simultaneously update the contexts of all MTC UEs in the association relationship table, and synchronize the R-MD. And a routing area update timer or a tracking area update timer of the MTC UE.

When the R-MD performs an aperiodic routing area update or tracking area update process, the new mobility management unit is configured to obtain the foregoing from the original mobility management unit by using an SGSN context update request/response message or a context request/response message. The association table of the R-MD with the MTC UE and the context of the MTC UE are saved locally.

When the R-MD performs the aperiodic routing area update or the tracking area update process, the R-MD is also used to simultaneously update the R-MD and all the MTC UEs on the new mobility management unit and the gateway unit. On-board information; when the R-MD performs the update, it is used to:

When the R-MD performs the aperiodic routing area update or the tracking area update process, the mobility management unit is further configured to: use the coding mode to assign the new identity to the R-MD and the MTC UE. The identifier is compression-encoded and sent to the R-MD; when the mobile management unit performs the update, it is used to:

The new identity is sent to the R-MD by a routing area update accept message or a tracking area update accept message.

Wherein, the R-MD is further used for:

Assigning the mobility management unit to the identity of the MTC UE by a local connection And sent to the MTC UE.

Wherein, the R-MD is further used for:

The MTC UE is notified by the local connection whether the periodic or aperiodic routing area update or the tracking area update process is successful.

The MTC UE is further configured to:

Determining that the local connection is disconnected, notifying the network to delete the association relationship with the R-MD and independently performing the normal mobility management process;

Or, it is determined that the network connection is disconnected, and the network is notified to delete the association relationship with the R-MD.

The method and system of the present invention can optimize the mobility management related signaling according to the characteristics of the MTC for the common MTC UE, so that the MTC device can save mobility management signaling while being able to communicate with the respective MTC server independently. Reduce signaling peaks and reduce terminal electrical losses. DRAWINGS

1 is a schematic diagram of an EPC system and an access network architecture in the prior art;

2 is a schematic diagram of an MTC UE accessing an EPC system through an EUTRAN in the prior art; FIG. 3 is a schematic diagram of directing an R-MD and an MTC UE to a same MME and establishing an R-MD by the MME according to the first embodiment of the present invention; Flowchart 1 of the association relationship of the MTC UE;

4 is a flowchart 2 of the second embodiment of the present invention, in which the R-MD and the MTC UE are directed to the same MME, and the association relationship between the R-MD and the MTC UE is established by the MME;

5 is a flowchart of a subsequent R-MD replacing a MTC UE for subsequent periodic tracking area update according to Embodiment 3 of the present invention; a flow chart of domain update; a flowchart of domain update;

FIG. 8 is a schematic diagram of the sixth embodiment of the present invention, after detecting that the local connection is disconnected, the MTC UE notifies the network to delete A flowchart of the relationship between the R-MD and the normal tracking area update; FIG. 9 is a flowchart of the relationship between the network deletion and the R-MD after the MTC UE detects that the network connection is disconnected according to the seventh embodiment of the present invention;

FIG. 10 is a schematic diagram of a signaling optimization process of a common MTC device according to an embodiment of the present invention; FIG. 11 is a schematic diagram of a signaling optimization system for a common MTC device according to an embodiment of the present invention. detailed description

In order to implement signaling optimization for communication of the MTC device, a terminal similar to the MTC UE may be introduced to establish an association with the MTC UE, and the mobility management process may be replaced by the MTC UE. Such a terminal may be referred to as a representative MTC UE, and may be simply referred to as an R-MD. The R-MD may be a terminal completely different from the MTC device, or may be an MTC terminal, as long as the R-MD can associate with the MTC UE. And can replace the MTC UE for mobility management process. In addition, the MTC UEs actually participating in the communication may be one or more.

In an actual application, the network may direct the common R-MD and the MTC UE to the same mobility management unit (such as the MME), and the mobility management unit establishes an association relationship between the R-MD and the MTC UE, and the R-MD is established by the mobile management unit. Subsequent mobility management processes are performed instead of MTC UEs. among them:

Further, the R-MD establishes a local connection with the MTC UE and exchanges identifiers for subsequent associations;

Further, the identifier for the subsequent association may be a global unique temporary identifier (GUTI) of the R-MD, a packet temporary mobile subscriber identity (P-TMSI: Packet Temporary Mobile Subscriber Identity), or a group Identify the Group ID;

Further, the MTC UE does not initiate an access request to the network before acquiring the identifier of the R-MD;

Further, the access request includes: an attach request, a routing area update request, or a tracking area update request; Further, the R-MD notifies the mobility management unit of the opening of the related function by using a network access request message;

Further, the network access request message may be an attach request message, a routing area update request message, or a tracking area update request message;

Further, the MTC UE carries the identifier of the R-MD in a radio resource control (RRC) parameter when an attach request, a routing area update request, or a tracking area update request, where the radio access network side network element is The MTC UE selects a mobility management unit currently serving the R-MD;

Further, the radio access network side network element may be an RNC or an eNB; further, the MTC UE carries a request and the R- in an attach request, a routing area update request, or a tracking area update request message. The MD performs an association identifier to the mobility management unit, where the mobility management unit locally associates the R-MD with the MTC UE;

P-TMSI, which can also be a group identifier Group ID;

Further, the mobility management unit locally associates the R-MD with the MTC UE, where: the mobility management unit locally establishes an association relationship table between the R-MD and the MTC UE;

Further, the mobility management unit locally associates the R-MD with the MTC UE, and further includes: the mobility management unit locally synchronizes a routing area update timer of the R-MD and the MTC UE Or tracking the area update timer;

Further, the mobility management unit notifies the MTC UE not to initiate a subsequent routing area update request or a tracking area update request in the network access request response message of the MTC UE;

Further, the network access request response message of the MTC UE includes: an attach accept message, a routing area update accept message, or a tracking area update accept message; further

Zone or update or trace area or update process;

further

The area update or tracking area update process includes: when the R-MD performs a periodic routing area update or a tracking area update process, the mobility management unit simultaneously updates the context of all MTC UEs in the association relationship table, and synchronizes the R - MD and a routing area update timer or a tracking area update timer of the MTC UE;

further

The area update or the tracking area update process further includes: when the R-MD performs the aperiodic routing area update or the tracking area update process, the new mobility management unit acquires the R-MD and the MTC UE from the original mobility management unit. The association table and the context of the MTC UE;

Further, when the R-MD performs the aperiodic routing area update or the tracking area update process, the association relationship between the R-MD and the MTC UE and the context of the MTC UE are obtained from the original mobility management unit, including: The new mobility management unit acquires the association relationship table by using an SGSN context update request/response message or a context request/response message;

Further, when the R-MD performs the aperiodic routing area update or the tracking area update process, the association between the R-MD and the MTC UE and the context of the MTC UE are obtained from the original mobility management unit, and the method further includes: The mobility management unit locally saves the association relationship table, and updates the context of all the MTC UEs in the association relationship table in a subsequent periodic routing area update or tracking area update process, and synchronizes the R-MD And a routing area update timer or a tracking area update timer of the MTC UE; the area update or tracking area update process, further includes: when the R-MD performs an aperiodic routing area update or tracking area update process, the new mobile The management unit and the gateway unit simultaneously update the control plane bearer information of the R-MD and all the MTC UEs; Further, the simultaneously updating the control plane bearer information of the R-MD and all the MTC UEs includes: triggering, by using a message, control plane bearer information of all associated MTC UEs to be updated;

Further, the simultaneously updating the control plane bearer information of the R-MD and all the MTC UEs further includes: performing, by using a PDP context update request message, a bearer modification request message, or a session creation request message, the control plane bearer The update of the information; the area update or the tracking area update process, the method further includes: when the R-MD performs the aperiodic routing area update or the tracking area update process, the mobility management unit will be the R-MD and the The new identity assigned by the MTC UE is compression-encoded and sent to the R-MD;

Further, the new identity identifier allocated by the mobility management unit to the R-MD and the MTC UE includes: GUTI, P-TMSI;

Further, the mobility management unit performs compression coding on the R-MD and the MTC UE, and sends the new identity to the R-MD, including: the mobility management unit The area update accept message or the tracking area update accept message sends the new identity to the R-MD; the area update or tracking area update process, further includes: the R-MD newly assigns the mobility management unit to the local connection The identifier of the MTC UE is sent to the MTC UE; the area update or the tracking area update process, and the method further includes: the R-MD updating or tracking the periodic or aperiodic routing area through a local connection Whether the update process is successful, and notifying the MTC UE;

Further, the MTC UE determines that the local connection is disconnected, notifies the network to delete the association relationship with the R-MD, and independently performs the normal mobility management process; Further, the MTC UE determines that the network connection is disconnected, and notifies the network to delete the association relationship with the R-MD;

Further, the mobility management unit may include: an MME, an SGSN.

Further, the gateway unit may include: an S-GW, a GGSN.

The technical solutions of the present invention are further described in detail below with reference to the accompanying drawings and specific embodiments to enable those skilled in the art to understand the invention. .

Embodiment 1: Directing a common R-MD and an MTC UE to the same MME, and

The MME establishes an association between the R-MD and the MTC UE, as shown in FIG. 3.

The process shown in Figure 3 specifically includes the following steps:

Step 301: The representative function of the R-MD is optionally signed as the subscription data in the HSS; Step 302: The R-MD may be designed to have multiple functions other than the representative function, and the R-MD needs to enable the representative function;

Step 303: After the R-MD is enabled to perform the function, if the R-MD is not attached to the network, the R-MD initiates an attach request message to the MME. If the R-MD is attached to the network, the TAU request message is sent to the MME, where the start representative is carried. Identification of functions;

Step 304: If the representative function of the R-MD needs to be signed, the MME performs a subscription check on the function in the process of acquiring the subscription data between the MME and the HSS. If the check fails, the attached process or TAU process fails. Optionally, the R-MD may notify the MTC UE of the failure of the attach process or the TAU process by using a local connection, and the MTC UE may choose to perform the subsequent TAU process independently; Step 305: The MME has been upgraded to identify the R-MD representative function identifier. And support the response operation of this function;

Step 306: The R-MD performs a subsequent attach process or a TAU process.

Step 307: The local connection is established between the R-MD and the MTC UE to be co-located with the R-MD, and the identifier for the subsequent association is exchanged with each other. The identifier may be: in the LTE network, the R-MD and the The GUTI of the MTC UE; in the 3G network, the P-TMSI of the R-MD and the MTC UE; if the R-MD and the MTC UE have a predetermined group relationship, the identifier may also be a group identifier Group ID. If the identifier is GUTI or P-TMSI, the R-MD needs to send the latest GUTI or P-TMSI obtained from the network to the MTC UE;

Step 308: The MTC UE detects that there is a local connection with the R-MD and receives an identifier for subsequent association from the R-MD.

Step 309: If the MTC UE is not attached to the network, initiate an attach request message to the network side; if the MTC UE is attached to the network, initiate a TAU request message to the network side. In the RRC parameter except the attach request message or the TAU request message, the identifier for the subsequent association obtained from the R-MD is carried, and the identifier may be: in the LTE network, the GUTI of the R-MD; in the 3G network, For the R-MD P-TMSI; if the R-MD and the MTC UE have a predetermined group relationship, the identifier may also be a group identifier Group ID, in order to enable the E-UTRAN network to select the service for the MTC UE. - MME of MD. At the same time, the identifier for the subsequent association that is obtained from the R-MD is also carried in the attach request or the TAU request NAS message, and the identifier may be: in the LTE network, the GUTI of the R-MD; in the 3G network, the R - P-TMSI of the MD; if the R-MD and the MTC UE have a predetermined group relationship, the identifier may also be a group identifier Group ID, in order to enable the E-UTRAN network to select and serve the R-MD for the MTC UE. MME;

Step 310: The E-UTRAN selects an MME serving the R-MD for the MTC UE according to the identifier obtained from the R-MD in the received RRC parameter.

Step 311: The E-UTRAN forwards the MTC UE attach request or the TAU request NAS message to the MME serving the R-MD. The NAS message carries the identifier obtained from the R-MD for subsequent association.

Step 312: Perform a subscription information acquisition process between the MME and the HSS.

Step 313: The MME associates the MTC UE with the R-MD according to the identifier used for association, and synchronizes the TAU timers of the MTC UE and the R-MD. Step 314: The MTC UE performs a subsequent attach process or a TAU process.

Step 315: The MME sends an attach accept message or a TAU accept message to the MTC UE, and notifies the MTC UE not to perform the subsequent TAU procedure.

It should be noted that the embodiment is also applicable to a 3G network. In a 3G network: the radio access network is UTRAN/GERAN, the mobility management unit is SGSN, the user subscription database is HLR, and the location update process is a routing area update process. The temporary side identifier is P-TMSI, and the other inventions related to the present invention are not changed, and are not described herein again.

Embodiment 2: The R-MD and the MTC UE are directed to the same MME, and the association relationship between the R-MD and the MTC UE is established by the MME, as shown in FIG. 4 .

The process shown in Figure 4 specifically includes the following steps:

Step 401: Establish a local connection between the R-MD and the MTC UE to be co-located with the R-MD. In this case, if the identifier used for the subsequent association is the temporary identity of the R-MD, that is, the GUTI in the LTE network, in the 3G If the network is P-TMSI, the R-MD does not send the temporary identity to the MTC UE when the R-MD is not attached or the R-MD does not obtain the latest temporary identity, and the MTC UE only receives the R- After the identification of the MD, the subsequent steps 410 to 416 are initiated; optionally, the identifier of the MTC UE for subsequent association is sent to the R-MD;

Step 402: The representative function of the R-MD is optionally signed in the HSS as the subscription data. Step 403: The R-MD may be designed to have multiple functions other than the representative function, and the R-MD needs to enable the representative function.

Step 404: After the R-MD starts the representative function, if the R-MD is not attached to the network, the R-MD initiates an attach request message to the MME. If the R-MD is attached to the network, the TAU request message is sent to the MME. The identifier carrying the activation representative function;

Step 405: If the representative function of the R-MD needs to be contracted, the MME performs a subscription check on the function during the subscription data acquisition process between the MME and the HSS. If the check fails, the attach process or the TAU process fails; optionally, the R-MD can connect through the local connection Or the TAU process fails, and the MTC UE is notified, and the MTC UE may choose to perform the subsequent TAU process independently;

Step 406: The MME has been upgraded to be able to identify the representative function identifier of the R-MD, and supports the response operation of the function;

Step 407: The R-MD performs a subsequent attach process or a TAU process.

Step 408: The R-MD sends the latest temporary identity identifier obtained from the network to the MTC UE, where the identifier may be: in the LTE network, the GUTI of the R-MD and the MTC UE; in the 3G network, the R-MD And the P-TMSI of the MTC UE; if the R-MD and the MTC UE have a predetermined group relationship, the identifier may also be a group identifier Group ID;

Step 409: The MTC UE detects that there is a local connection with the R-MD and receives an identifier for subsequent association from the R-MD.

Step 410: If the MTC UE is not attached to the network, initiate an attach request message to the network side; if the MTC UE is attached to the network, initiate a TAU request message to the network side. In the RRC parameter except the attach request message or the TAU request message, the identifier for the subsequent association obtained from the R-MD is carried, and the identifier may be: in the LTE network, the GUTI of the R-MD; in the 3G network, For the R-MD P-TMSI; if the R-MD and the MTC UE have a predetermined group relationship, the identifier may also be a group identifier Group ID, in order to enable the E-UTRAN network to select the service for the MTC UE. - MME of MD. At the same time, the identifier for the subsequent association that is obtained from the R-MD is also carried in the attach request or the TAU request NAS message, and the identifier may be: in the LTE network, the GUTI of the R-MD; in the 3G network, the R - P-TMSI of the MD; if the R-MD and the MTC UE have a predetermined group relationship, the identifier may also be a group identifier Group ID, in order to enable the E-UTRAN network to select and serve the R-MD for the MTC UE. MME;

Step 411: The E-UTRAN selects an MME serving the R-MD for the MTC UE according to the identifier obtained from the R-MD in the received RRC parameter.

Step 412: The E-UTRAN turns the MTC UE attach request or the TAU request NAS message Sending to the MME serving the R-MD; the NAS message carries the identifier obtained from the R-MD for subsequent association;

Step 413: Perform a contract information acquisition process between the MME and the HSS.

Step 414: The MME associates the MTC UE with the R-MD according to the identifier used for association, and synchronizes the TAU timers of the MTC UE and the R-MD.

Step 415: The MTC UE performs a subsequent attach process or a TAU process.

Step 416: The MME sends an attach accept message or a TAU accept message to the MTC UE, and notifies the MTC UE not to perform the subsequent TAU procedure.

Embodiment 3: The R-MD replaces the MTC UE to perform a subsequent periodic tracking area update process, as shown in FIG. 5.

The process shown in Figure 5 specifically includes the following steps:

Step 501: The R-MD moves together with the MTC UE, and the R-MD detects that a periodic TAU procedure needs to be performed or detects a tracking area (TA) that is not in the Tracking Area Identification (TAI) list; Step 502: R-MD Direction The MME initiates a TAU request message;

Step 503: After receiving the TAU request message from the R-MD, the MME locally updates the R-MD and the context of the MTC UE associated with it.

Step 504: The R-MD performs a subsequent periodic TAU process.

Step 505: The MME sends a TAU accept message to the R-MD. If the TAU process is caused by the TA change, the BJ MME sends a new TAI list.

Step 506: The R-MD notifies the MTC UE whether the TAU process is successful through a local connection, and the MTC UE performs subsequent operations accordingly. Optionally, the R-MD may allocate the new MME. The TAI list is sent to the MTC UE.

It should be noted that: This embodiment is also applicable to a 3G network. In a 3G network: the radio access network is UTRAN/GERAN, the mobility management unit is SGSN, the user subscription database is HLR, and the location update process is a routing area update process. The content of the invention related to the present invention is not changed and will not be described herein.

Embodiment 4: The R-MD replaces the MTC UE to perform a subsequent aperiodic tracking area update process, as shown in FIG. 6.

The process shown in Figure 6 specifically includes the following steps:

Step 601: The R-MD moves together with the MTC UE, and the R-MD detects that the MME changes. Step 602: The R-MD sends a TAU request message to the new MME, where the identifier of the representative function that starts the R-MD is carried.

Step 603: The new MME has been upgraded to recognize the representative function identifier of the R-MD, and supports operations related to the function;

Step 604: The new MME sends a context request message to the old MME, where the identifier is used to request an association relationship between the latest R-MD and the MTC UE associated with the new MME.

Step 605: The old MME sends a context response message to the new MME, and the context of the latest association table and the R-MD and the MTC UE associated with it is delivered to the new MME.

Step 606: The new MME locally saves the association table of the latest R-MD and the associated MTC UE, and updates it in the subsequent periodic TAU process (the specific update mode refers to the corresponding operation in the third embodiment). The context of all associated MTC UEs in the relationship table; Step 607: Perform a session creation process or a bearer modification process between the new MME and the S-GW, and update the control plane bearer information of all MTC UEs in the R-MD and the association relationship table, Ensure that the data channel is unblocked when the subsequent MTC UE initiates data communication. If the S-GW has not changed, the process is a bearer modification process; if the S-GW changes, the process is a session creation process. Here, considering that the total amount of control plane bearer information of multiple devices is large and the length of the GTP message is limited, Updating the control plane information of all MTC UEs in the R-MD and the association relationship table by means of GTP message fragment transmission or a manner in which the new MME triggers multiple session creation requests or bearer modification request messages at the same time;

Step 608: The R-MD continues to perform the subsequent TAU process. At this time, if there is no R-MD context in the new MME, the new MME performs an R-MD subscription data acquisition process with the HSS. If the representative function of the R-MD is used as the subscription data, the subscription check of the function is performed. If the check fails, the TAU process fails. Optionally, the R-MD can notify the MTC UE of the failure of the TAU process through the local connection. The MTC UE may choose to perform the subsequent TAU process independently;

Step 609: If the TAU process is successful, the new MME sends a TAU accept message to the R-MD, where the new MME is the R-MD and the GUTI of the MTC UE with which it is associated. Considering the length of the GUTI and the length limit of the TAU accept message, since all the devices are served by the same MME at this time, some fields in the GUTI are the same, and the new GUTI of the R-MD and the MTC UE can be encoded. Perform compression coding and send it to the R-MD in the TAU accept message;

Step 610: After receiving the TAU accept message of the new MME, the R-MD restores all the new GUTIs from the message, and sends the new GUTI to the corresponding MTC UE through the local connection to ensure that the subsequent MTC UE initiates data communication. Successfully; and optionally sending a new TAI list allocated by the MME to the MTC UE. As shown in Figure 7.

The process shown in Figure 7 specifically includes the following steps:

Step 701: The R-MD moves together with the MTC UE, and the R-MD detects that the SGSN changes. Step 702: The R-MD sends a RAU request message to the new SGSN, where the identifier of the representative function that starts the R-MD is carried.

Step 703: The new SGSN has been upgraded to a representative function identifier capable of identifying the R-MD, and Hold operations related to this function;

Step 704: The new SGSN sends an SGSN Context Request message to the old SGSN, where the SGSN context request message is sent to request the latest R-MD and the associated relationship table of the MTC UEs. Step 705: The old SGSN sends an SGSN Context Response message to the new SGSN. Transmitting the context of the latest association table and the R-MD and the MTC UE associated with it to the new SGSN; Step 706: The new SGSN locally saves the received latest R-MD and the associated relationship table of the MTC UEs associated with it. And updating the context of all associated MTC UEs in the association table in the subsequent periodic RAU process (refer to the corresponding operation in the third embodiment); Step 707: Performing a PDP context update process between the new SGSN and the GGSN, updating The R-MD and the control planes of all the MTC UEs in the association table carry information to ensure that the data channel is unblocked when the subsequent MTC UE initiates data communication. Here, in consideration of the large amount of control plane bearer information of a plurality of devices and the length limitation of the GTP message, the manner of GTP message fragment transmission or the manner in which the new SGSN simultaneously triggers multiple PDP context update request messages may be adopted, and R is updated. - Control plane bearer information of all MTC UEs in the MD and association table;

Step 708: The R-MD continues to perform the subsequent RAU process. At this time, if there is no R-MD representative function in the new SGSN as the subscription data, the subscription check of the function is performed. If the check fails, the RAU process fails; The R-MD may notify the MTC UE of the failure of the RAU process through a local connection, and the MTC UE may choose to independently perform the subsequent RAU process;

Step 709: If the RAU process is successful, the new SGSN sends an RAU accept message to the R-MD, where the new SGSN carries the R-MD and the P-TMSL of the MTC UE with which it is associated. Considering the length of the P-TMSI and the RAU accepting The length of the message is limited. Since all the devices are served by the same SGSN at this time, some fields in the P-TMSI are the same. The new P-TMSI of the R-MD and the MTC UE can be compression-encoded by using the coding method. Is sent to the R-MD in the RAU accept message; Step 710: After receiving the RAU accept message of the new SGSN, the R-MD restores all the new P-TMSIs from the message, and sends the new P-TMSI to the corresponding MTC UE through the local connection to ensure the subsequent MTC UE. Initiate the success of data communication.

Embodiment 6: After detecting that the local connection is disconnected, the MTC UE notifies the network to delete the association relationship with the R-MD and independently performs the normal tracking area update process, as shown in FIG. 8.

The process shown in Figure 8 specifically includes the following steps:

Step 801: The MTC UE detects that the local connection with the R-MD is disconnected.

Step 802: The MTC UE sends a TAU request message to the MME, where the identifier is carried, and is used to delete the association relationship with the R-MD.

Step 803: After receiving the TAU request message from the MTC UE, the MME deletes the association relationship between the MTC UE and the R-MD from the association relationship table, and does not update the R-MD when the periodic or non-periodic TAU is performed. Information about the MTC UE;

Step 804: The MTC UE completes a subsequent TAU process.

Step 805: The MME sends a TAU accept message to the MTC UE.

Step 806: The MTC UE performs the normal TAU process independently.

It should be noted that the embodiment is also applicable to a 3G network. In a 3G network: the radio access network is UTRAN/GERAN, the mobility management unit is SGSN, the user subscription database is HLR, and the location update process is a routing area update process. The content of the invention related to the present invention is not changed and will not be described herein.

Embodiment 7: After detecting that the network connection is disconnected, the MTC UE notifies the network to delete the association relationship with the R-MD, as shown in FIG. 9.

The process shown in Figure 9 specifically includes the following steps:

Step 901: The MTC UE detects that the connection with the network is disconnected.

Step 902: The MTC UE initiates a detach request message to the MME.

Step 903: After receiving the detach request message from the MTC UE, the MME associates the relationship The association between the MTC UE and the R-MD is deleted in the table, and when the R-MD performs periodic or non-periodic TAU, the information related to the MTC UE is not updated;

Step 904: The MTC UE completes a subsequent detach process;

Step 905: The MME sends a detach accept message to the MTC UE.

It should be noted that the embodiment is also applicable to a 3G network. In the 3G network: the radio access network is UTRAN/GERAN, the mobility management unit is SGSN, and the user subscription database is HLR. Other inventions related to the present invention are unchanged. , will not repeat them here.

As shown in Figure 10, the operation of the signaling optimization of the MTC device can be represented as shown in Figure 10. The process shown in Figure 10 includes the following steps:

Step 1001: Direct the R-MD and the MTC UE to the same mobility management unit, and establish an association relationship between the R-MD and the MTC UE.

Step 1002: Based on the association relationship, the R-MD replaces the MTC UE for a subsequent mobility management process.

In order to ensure the smooth implementation of the above embodiments and operation ideas, the settings shown in FIG. 11 can be performed. Referring to FIG. 11, FIG. 11 is a schematic diagram of a signaling optimization system for a common MTC device according to an embodiment of the present invention, where the system includes a connected co-located relationship maintenance unit and a co-located mobility management unit; wherein, the co-located relationship maintenance unit includes A common unit can be connected to the unit, and an associated unit is provided.

In practical applications, the common set-up unit in the relationship maintenance unit can direct the common R-MD and the MTC UE to the same mobility management unit, and the associated unit can establish the R-MD and the MTC UE. Correlation relationship; The mobility management unit can control the R-MD to perform the subsequent mobility management process instead of the MTC UE based on the association relationship.

In summary, the present invention has a signaling optimization technology for the MTC device, and the MTC UE can optimize the mobility management related signaling according to the characteristics of the MTC, so that the MTC device can be optimized. While being able to communicate independently with the respective MTC servers, it saves mobility management signaling, reduces signaling peaks, and reduces terminal electrical losses. The above is only the preferred embodiment of the present invention and is not intended to limit the scope of the present invention.

Claims

Claim

A signaling optimization method for a machine type communication MTC device, comprising: a radio access network side network element directing a common R-MD and an MTC user equipment UE to a same mobility management unit, and by the mobile The management unit establishes an association relationship between the R-MD and the MTC UE. The mobility management process includes: replacing, by the R-MD, the periodic or non-periodic routing area or the update or tracking area or update process by the MTC UE.

2. The method according to claim 1, wherein the method further comprises:

The method according to claim 1, wherein the method for establishing the association relationship is: the MTC UE carries an request to be associated with the R-MD in an attach request, a routing area update request, or a tracking area update request message. Identifying to the mobility management unit, the mobility management unit locally associates the R-MD with the MTC UE.

4. The method according to claim 3, wherein

The association is embodied in the form of an association table;

Synchronizing the R-MD with the routing area update timer or the tracking area update timer of the MTC UE by the mobility management unit;

The mobility management unit notifies the network in the network access request response message of the MTC UE The MTC UE does not initiate a subsequent routing area update request or tracking area update request.

The method according to claim 1, wherein, when the R-MD performs the periodic routing area update or the tracking area update process, the mobility management unit simultaneously updates the context of all MTC UEs in the association relationship table, And synchronizing the R-MD and the routing area update timer or the tracking area update timer of the MTC UE.

6. The method according to claim 1, wherein, when the R-MD performs a non-periodic routing area update or tracking area update procedure, the new mobility management unit updates the request/response message by serving the GPRS support node SGSN, or The context request/response message acquires the association table of the R-MD and the MTC UE and the context of the MTC UE from the original mobility management unit, and saves it locally.

7. The method according to claim 6, wherein, when the R-MD performs the aperiodic routing area update or tracking area update process, simultaneously updating the R-MD and the new mobility management unit and the R-MD on the gateway unit The control plane bearer information of all the MTC UEs includes:

8. The method according to claim 6, wherein, when the R-MD performs the aperiodic routing area or the update or tracking area or the update process, the R-MD and the The new identity that is allocated by the MTC UE is compression-encoded and sent to the R-MD. The delivery method includes:

The method according to claim 8, wherein, after receiving the new identity identifier delivered by the mobility management unit, the R-MD further includes:

And sending, by the R-MD, the new identity to the MTC UE by using a local connection.

The method according to any one of claims 1 to 9, wherein the method further comprises: The R-MD notifies the MTC UE whether the periodic or aperiodic routing area update or the tracking area or the update procedure is successful through a local connection.

The method according to any one of claims 1 to 9, wherein the method further comprises: the MTC UE determining that the local connection is disconnected, notifying the network to delete the association relationship with the R-MD, and independently performing normal mobility management. Process;

12. A signaling optimization system for jointly setting an MTC device, comprising a common set-direction unit, a co-located unit, and a total mobility management unit; wherein

13. The system according to claim 12, wherein

The R-MD is further configured to establish a local connection with the MTC UE and exchange identifiers for subsequent associations, and notify the mobility management unit of the opening of the related function by using a network access request message;

The system according to claim 12, wherein, when the association unit establishes the association relationship, it is used to: The control MTC UE carries an identifier that is required to be associated with the R-MD to the mobility management unit in an attach request, a routing area update request, or a tracking area update request message, and triggers the mobility management unit to locally perform the R- The MD is associated with the MTC UE.

15. The system according to claim 14, wherein

The association is embodied in the form of an association table;

The mobility management unit is further configured to locally synchronize the routing area update timer or the tracking area update timer of the R-MD with the MTC UE, and notify the network access request response message of the MTC UE The MTC UE does not initiate a subsequent routing area update request or a tracking area update request.

The system according to claim 12, wherein, when the R-MD performs the periodic routing area update or tracking area update process, the R-MD is further configured to trigger the mobility management unit to simultaneously update all MTCs in the association relationship table. The context of the UE, and synchronizing the R-MD and the routing area update timer or the tracking area update timer of the MTC UE.

17. The system according to claim 12, wherein when the R-MD performs an aperiodic routing area update or tracking area update procedure, the new mobility management unit is configured to update the request/response message or the context request by using the SGSN context. The response message is obtained from the original mobility management unit, and the context of the association between the R-MD and the MTC UE and the context of the MTC UE are saved locally.

The system according to claim 17, wherein, when the R-MD performs the aperiodic routing area update or tracking area update process, the R-MD is further configured to simultaneously update the new mobility management unit and the gateway unit. Control plane bearer information of the R-MD and all the MTC UEs; when the R-MD performs the update, it is used to:

The system according to claim 17, wherein when the R-MD performs the aperiodic routing area update or tracking area update process, the mobility management unit is further configured to The code mode compresses and encodes the new identity identifier allocated by the R-MD and the MTC UE to the R-MD; when the mobility management unit performs the update, the method is used to:

The system according to claim 19, wherein the R-MD is further configured to: send the identity identifier newly allocated by the mobility management unit to the MTC UE to the MTC UE by using a local connection.

The system according to any one of claims 12 to 20, wherein the R-MD is further configured to:

The system according to any one of claims 12 to 20, wherein the MTC UE is further configured to: