WO2017161568A1

WO2017161568A1 - Paging method, mme, and enodeb

Info

Publication number: WO2017161568A1
Application number: PCT/CN2016/077364
Authority: WO
Inventors: 武绍芸; 姜志健
Original assignee: 华为技术有限公司
Priority date: 2016-03-25
Filing date: 2016-03-25
Publication date: 2017-09-28

Abstract

Disclosed in the present application are a paging method, an MME, and an eNodeB; the MME does not need to send a paging message to all the eNodeB in an eNodeB set, and can instead make full use of forwarding between the eNodeB, achieving the objective of the eNodeB in the eNodeB set all receiving the paging message, and thereby reducing the overhead of the MME.

Description

Paging method and MME, eNodeB

Technical field

The present application relates to the field of communications, and in particular, to a paging method, a Mobility Management Entity (MME), and an E-UTRAN NodeB (eNodeB).

Background technique

In the current communication system, a user equipment (User Equipment, UE) that does not establish a data transmission channel with the network is called an idle state UE. When the network has data sent to the idle state UE or the idle state UE is called by other UEs, the UE is first found, and the UE is notified to establish a data transmission channel with the network. The process by which the MME) looks for an idle state UE is called paging Paging.

The existing paging process is: after obtaining the downlink data notification (DDN) or creating, updating, or deleting a bearer (Create/Update/Delete Bearer) signaling message, the MME sends a list to the tracking area where the UE is located ( All eNodeBs in the Tracking Area List (TA List) deliver paging messages. Generally, a TA List usually includes tens to hundreds of eNodeBs. Therefore, the MME needs to issue dozens to hundreds of paging messages for paging of an idle UE. This will cause the overhead of the MME to be too large.

Summary of the invention

The present application provides a paging method, an MME, and an eNodeB, and aims to solve the problem that the MME overhead caused by paging is excessive.

In order to achieve the above object, the present application provides the following technical solutions:

A first aspect of the present application provides a paging method, where a mobility management entity MME determines an eNodeB packet corresponding to a paged user equipment UE, and sends a paging message to at least one eNodeB in the eNodeB packet, ie, An eNodeB, the first eNodeB forwarding the paging message to a second eNodeB, wherein the first eNodeB and the second eNodeB are in the same eNodeB packet, and the eNodeB packet is at least covered by the paging UE A collection of eNodeBs composed of NodeBs. It can be seen that the MME may not have to all of the set of eNodeBs. The eNodeB can send the paging message, but can fully utilize the forwarding between the eNodeBs, so that all eNodeBs in the eNodeB set can receive the paging message, thereby reducing the overhead of the MME.

A second aspect of the present application provides a mobility management entity including a memory for storing a program and data generated in a program run, and a processor that implements the following functions by running a program in the memory: determining to be found And the eNodeB packet corresponding to the user equipment UE, where the eNodeB packet corresponding to the paging UE is a set of eNodeBs composed at least by an eNodeB that covers the paging UE, and sends a paging message to the eNodeB packet. At least one eNodeB, the eNodeB receiving the paging message is configured to send the paging message to other eNodeBs in the NodeB packet. It can be seen that the MME only sends a paging message to a part of the eNodeB in the eNodeB packet, and then the partial eNodeB forwards the paging message to other eNodeBs. Therefore, the overhead of the MME can be reduced.

A third aspect of the present application provides an eNodeB including a receiver for receiving a paging message and a transmitter for forwarding the paging message to a target eNodeB. The eNodeB and the target eNodeB are in the same eNodeB group, and the eNodeB group is a set of at least eNodeBs that are composed of eNodeBs that cover the paging UE. Since the eNodeB has a function of forwarding a paging message to an eNodeB within the same packet, the overhead of the MME can be reduced.

In an implementation manner, the MME determines an eNodeB packet corresponding to the paging UE, where the eNodeB packet corresponding to the paging UE is at least a set of eNodeBs that are composed of eNodeBs that cover the paging UE. The MME selects an eNodeB tree corresponding to the paged UE from the preset eNodeB tree, and the eNodeB tree corresponding to the paged UE includes at least an eNodeB tree in which the eNodeB that covers the paged UE is located. In any one eNodeB tree of the preset eNodeB tree, the eNodeB constitutes a node of the eNodeB tree, the node includes a root node, an intermediate node, and a leaf node, and the intermediate node connected to the root node is the root node. The child node, the leaf node connected to the intermediate node is a child node of the intermediate node.

In an implementation manner, the process of establishing the preset eNodeB tree includes: receiving, by the MME, an S1 SETUP REQUEST message sent by an eNodeB, where the S1 SETUP REQUEST The message carries the network attribute of the sender and the network attribute of the eNodeB, and establishes an eNodeB tree.

In an implementation manner, the MME establishes an eNodeB tree according to the network attribute of the eNodeB, where the MME establishes an eNodeB tree according to a category attribute in a network attribute of the eNodeB, where any one eNodeB tree The eNodeBs all belong to the same category, and the category attributes include the supported tracking area TA, or the supported non-open user group CSG, or the supported TA and the CSG; or the MME according to the eNodeB a location attribute in the network attribute, establishing an eNodeB tree, wherein the location attribute comprises: information of other eNodeBs connected to the eNodeB and maximum number of other eNodeBs that the eNodeB can interconnect, in the eNodeB tree, The child node or the parent node of the eNodeB belongs to other eNodeBs connected to the eNodeB, and the number of the child nodes of the eNodeB does not exceed the maximum number; or the MME is according to the category in the network attribute of the eNodeB. An attribute and the location attribute, establishing an eNodeB tree, wherein the eNodeBs in the eNodeB tree all belong to the same category, and the child nodes of the eNodeB or The parent node belongs to other eNodeBs connected to the eNodeB, and the number of child nodes of the eNodeB does not exceed the maximum number.

In an implementation manner, after the MME establishes an eNodeB tree according to the network attribute of the eNodeB, the method further includes: the MME sending an S1 SETUP RESPONSE message to the eNodeB, where the S1 SETUP RESPONSE message includes the eNodeB Information about child nodes in the eNodeB tree.

In an implementation manner, after the MME establishes an eNodeB tree according to the network attribute of the eNodeB, the method further includes: the MME receiving an S1SETUP REQUEST message sent by the newly accessed eNodeB, where the S1 SETUP REQUEST message carries Derefering the network attribute of the newly accessed eNodeB, and adding the newly accessed eNodeB to the established eNodeB tree according to the network attribute of the newly accessed eNodeB, and sending the S1 to the newly accessed eNodeB SETUP RESPONSE message, the S1 SETUP RESPONSE message includes information of the child nodes of the newly accessed eNodeB in the joined eNodeB tree.

In an implementation manner, the MME adds the newly accessed eNodeB to the established eNodeB tree according to the network attribute of the newly accessed eNodeB, including: the MME Determining, according to the category attribute of the newly accessed eNodeB, the category of the newly accessed eNodeB, and adding the newly accessed eNodeB to the eNodeB tree corresponding to the category, and according to the newly accessed The category attribute of the eNodeB determines the location of the newly accessed eNodeB in the eNodeB tree corresponding to the category, and the eNodeB tree corresponding to the category is jointly established by the eNodeB in the category.

In an implementation manner, after the MME establishes an eNodeB tree according to the network attribute of the eNodeB, the method further includes: after the MME detects disconnection from an eNodeB in an established eNodeB tree, the MME is The disconnected eNodeB is deleted from the eNodeB tree in which the disconnected eNodeB is located.

In an implementation manner, the method further includes: sending, by the MME, an MME CONFIGURATION UPDATE message to an eNodeB that changes in a child node in the eNodeB tree, where the MME CONFIGURATION UPDATE message includes information of the updated child node.

In an implementation manner, the MME selects an eNodeB tree corresponding to the paged UE from the preset eNodeB tree, where the MME searches for an eNodeB that has the same category attribute as the paged UE, and the category attribute Include the supported tracking area TA, or the supported non-open user group CSG, or the supported TA and the supported CSG, and use the eNodeB tree in which the eNodeB with the same category attribute of the paged UE is located. The eNodeB tree corresponding to the paged UE.

In an implementation manner, the preset eNodeB tree corresponds to a category, and an eNodeB tree corresponding to a category is jointly established by an eNodeB supporting the category, where the category attribute includes a supported tracking area TA, or a supported non- Open the user group CSG, or the supported TA and the CSG. The MME selects an eNodeB tree corresponding to the paged UE from the preset eNodeB tree, and the MME determines the category supported by the paged UE according to the category attribute of the paged UE. The category attribute includes the supported tracking area TA, or the supported non-open user group CSG, or the supported TA and the supported CSG, and the eNodeB tree corresponding to the category supported by the paging UE is used as The eNodeB packet corresponding to the paged device.

In an implementation manner, the sending, by the MME, the paging message to the at least one eNodeB in the eNodeB packet includes: sending, by the MME, a paging message to the paged UE The root node in the corresponding eNodeB tree.

In an implementation, the first eNodeB and the second eNodeB are in the same group, and the first eNodeB and the second eNodeB are in the same eNodeB tree, and the eNodeB tree includes a root node and a middle node. a node and a leaf node, the intermediate node connected to the root node is a child node of the root node, and the leaf node connected to the intermediate node is a child node of the intermediate node; the first eNodeB is a root node, The second eNodeB is a child node of the first eNodeB.

In an implementation manner, before the receiving, by the first eNodeB, the paging message, the first eNodeB sends an S1 SETUP REQUEST message to the MME, where the S1 SETUP REQUEST message carries the network attribute of the first eNodeB. And the network attribute of the first eNodeB is used together with the network attribute of the second eNodeB to establish the eNodeB tree by the MME; the first eNodeB receives an S1 SETUP RESPONSE message sent by the MME, where the S1 SETUP The RESPONSE message includes information of the child nodes of the first eNodeB in the eNodeB tree.

In one implementation, the network attributes include: a category attribute, a location attribute, or a category attribute and a location attribute. The location attribute includes: information of other eNodeBs connected to the first eNodeB and maximum number of other eNodeBs that the first eNodeB can interconnect; the category attribute includes a supported tracking area TA, or a supported non- Open user group CSG, or supported TA and supported CSG.

In an implementation manner, after the first eNodeB receives the S1SETUP RESPONSE message sent by the MME, the method further includes: the first eNodeB receiving an MME CONFIGURATION UPDATE message, where the MME CONFIGURATION UPDATE message includes the first eNodeB Information about the updated child node.

In an implementation manner, the first eNodeB forwarding the paging message to the second eNodeB includes: the first eNodeB classifying the category carried in the paging message with a category currently supported by the first eNodeB The intersection is the target class and the paging message is forwarded to the child node of the first eNodeB having the target class.

In an implementation manner, the first eNodeB is in an eNodeB tree corresponding to a category supported by the first eNodeB, where the category corresponding to the category supported by the first eNodeB is The other eNodeBs in the eNodeB tree are the same as the classes supported by the first eNodeB. Forwarding, by the first eNodeB, the paging message to the second eNodeB includes: the first eNodeB forwarding the paging message to the eNodeB tree corresponding to the category supported by the first eNodeB A child node of the first eNodeB.

DRAWINGS

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the embodiments or the description of the prior art will be briefly described below. Obviously, the drawings in the following description are only It is a certain embodiment of the present invention, and other drawings can be obtained from those skilled in the art without any creative work.

1 is a schematic diagram of communication of an LTE network;

2 is a flowchart of a paging method according to an embodiment of the present invention;

FIG. 3 is a flowchart of a process for establishing an eNodeB tree according to an embodiment of the present invention;

4 is a schematic diagram of an eNodeB tree according to an embodiment of the present invention;

FIG. 5 is a flowchart of an update process of an eNodeB tree according to an embodiment of the present invention;

FIG. 6 is a schematic diagram of updating an eNodeB tree according to an embodiment of the present invention;

FIG. 7 is a flowchart of still another paging method according to an embodiment of the present invention;

FIG. 8 is a schematic structural diagram of an MME according to an embodiment of the present disclosure;

FIG. 9 is a schematic structural diagram of an eNodeB according to an embodiment of the present invention.

detailed description

As shown in FIG. 1 , in a Long Term Evolution (LTE) network, an MME and a Serving Gateway (S-GW) are directly connected to an eNodeB, where an interface between the MME and the eNodeB is an S1-MME, which is responsible for signaling. The interface between the S-GW and the eNodeB is S1-U, which is responsible for user plane communication data transmission. The S11 interface between the MME and the S-GW is used for transmission of control signaling such as path management and tunnel management.

At present, the LTE network is divided into a plurality of location intervals called Tracking Areas (TAs), and tens to hundreds of eNodeBs are deployed under each TA, and there are several cells under each eNodeB. The MME combines the current TA of the UE and several TAs around it to form a tracking area list TA List (depending on the network planning of the operator, the current common network planning) Is to divide a TA into a TA List). When the idle UE moves outside the current TA List, the UE will trigger a Tracking Area Update (TAU) procedure, in which the UE informs the MME of its latest location, and the MME reassigns the UE to the UE. TA List; or, if the UE in the idle state continues to be sent to the UE for a period of time in a certain TA list (for example, 54 minutes, the value is sent by the MME to the UE), the TAU process is also triggered, that is, the UE that is in a TA List for a long time. A periodic TAU is performed.

When the MME pages the UE, it searches for all eNodeBs under the TA List according to the TA List where the UE is located, and sends a paging message to the eNodeBs through the S1-MME interface. Based on the above paging mechanism, the paging message is spread N times in the MME network element (N is the number of eNodeBs in the TA List), so the overhead of the MME is very large. In some extreme cases, such as S-GW network element operation triggering batch bearer deactivation, network server pushes a large number of advertisements, etc., all of which will cause bursts of paging source messages, which will easily cause MME to be overloaded and congested due to paging users. Even downtime.

The purpose of the technical solution provided in this application is to reduce the overhead of the MME in the paging process.

The user equipment UE involved in the present application may include a handheld device having a wireless communication function, an in-vehicle device, a wearable device, a computing device, or other processing device connected to the wireless modem, and various forms of mobile stations (Mobile stations, MS), terminal, terminal equipment, etc. For convenience of description, in the present application, it is simply referred to as a user equipment or a UE.

FIG. 2 is a flowchart of a paging method according to an embodiment of the present application, including the following steps:

S201: After the MME is triggered to perform the paging process, determine an eNodeB packet corresponding to the paged user equipment UE.

In this embodiment, the eNodeB group corresponding to the paged UE is a set of eNodeBs that are preset, and at least includes a NodeB that covers the paged UE.

There are many reasons why the MME is triggered to page. The following examples illustrate:

1. The P-GW/S-GW receives the data packet sent by the network to the UE (VoLTE voice is also part of it). Specifically, the MME receives the Downlink Data Notification (DDN) of the S-GW on the S11 interface. Or bear the operation related signaling.

2. In the scenario of Circuit Switched FallBack (CSFB), the Mobile Switching Center (MSC) notifies the MME to page the UE.

3. In other service scenarios, such as location services, the location server requests the latest location of the UE.

S202: The MME sends a paging message to at least one eNodeB in the eNodeB packet.

S203: The eNodeB that receives the paging message forwards the paging message to other eNodeBs in the eNodeB packet.

In this embodiment, the paging message sent by the MME to the at least one eNodeB is the same as that in the prior art, and details are not described herein again. For the paging message forwarded between the eNodeBs, refer to the paging message sent by the MME to the at least one eNodeB.

In this embodiment, the MME sends a paging message to at least one eNodeB in the eNodeB packet during the paging of the idle state UE, and then the eNodeB that receives the paging message forwards the paging message to other eNodeBs, based on this mechanism, Taking a TA List as an example, the MME may not need to send a paging message to all eNodeBs in the TA List, but may fully utilize the forwarding between the eNodeBs, so that all eNodeBs in the TA List receive the paging message, thereby , can reduce the overhead of the MME.

In order to make the eNodeB packet more conform to the design and communication mechanism of the existing communication network, in the embodiment shown in FIG. 2, the eNodeB packet is specifically an eNodeB tree established according to the network attribute of the eNodeB.

FIG. 3 is a process for establishing an eNodeB tree according to an embodiment of the present application, including the following steps:

S301: After the eNodeB accesses the MME, the S1 SETUP REQUEST message is sent to the MME, where the S1 SETUP REQUEST message carries the network attribute of the sender.

In this embodiment, the network attribute includes a category attribute and a location attribute of the eNodeB, where the category attribute of the eNodeB includes a TA supported by the eNodeB, or a Closed Subscriber Group (CSG) supported by the eNodeB, or an eNodeB Supported TA and CSG. The location attribute includes information of other eNodeBs connected to the eNodeB and the maximum number of other eNodeBs that the eNodeB can interconnect.

It should be noted that, in this embodiment, the S1 SETUP REQUEST message is improved by using the existing The S1 SETUP REQUEST message of (3GPP 36413) is obtained. As shown in Table 1, the cells are added in the existing SETUP REQUEST message: the connected eNodeB list Connected eNodeB List, and the cell: the sub-cell of the Connected eNodeB List: global The eNodeB identifies the Global eNodeB Id for indicating other eNodeBs connected to the eNodeB, and the Forwarding Paging Ability field, which is used to indicate the maximum number of other eNodeBs that the eNodeB can interconnect. See Table 1 for additional attributes of the added cells.

In addition to the newly added fields, the cells in Table 1: Supported TAs and their sub-cells are used to indicate the TA supported by the eNodeB. The signal: CSG Id List and its sub-cells are used to indicate the CSG supported by the eNodeB.

Table 1

IE/Group NameIE/Group Name	PresencePresence	RangeRange
Message TypeMessage Type	MM
Global eNB IDGlobal eNB ID	MM
eNB NameeNB Name	OO
Supported TAsSupported TAs		1..<maxnoofTACs>1..<maxnoofTACs>
>TAC>TAC	MM
>Broadcast PLMNs>Broadcast PLMNs		1..<maxnoofBPLMNs>1..<maxnoofBPLMNs>
>>PLMN Identity>>PLMN Identity	MM
Default paging DRXDefault paging DRX	MM
CSG Id ListCSG Id List		0..10..1
>CSG Id>CSG Id	CC	1 to<maxnoofCSGIds>1 to<maxnoofCSGIds>
Connected eNodeB ListConnected eNodeB List		0..10..1
>Global eNodeB Id>Global eNodeB Id	CC	1 to<maxnoofConnectedeNodeBs>1 to<maxnoofConnectedeNodeBs>
Forward Paging AbilityForward Paging Ability	CC	0..160..16

S302: The MME establishes an eNodeB tree according to the network attribute of the eNodeB.

Specifically, when establishing an eNodeB tree, the MME sets the eNodeBs belonging to the same category on an eNodeB tree to form an eNodeB tree corresponding to the category, and according to the connection relationship between each eNodeB and other eNodeBs and the largest child node that the eNodeB can bear. The number of each eNodeB is set on the eNodeB tree corresponding to the category. Specifically, the child node or the parent node of the eNodeB on the eNodeB tree belongs to other eNodeBs connected to the eNodeB carried in the S1 SETUP REQUEST message sent by the eNodeB, and the child node cannot exceed the maximum child node that it can bear. Quantity.

For example, the values of Supported TAs, Connected eNodeB List, and Forward Paging Ability in the S1 SETUP REQUEST message sent by eNodeB1, eNodeB2, eNodeB3, eNodeB4, and eNodeB5 are as follows:

As can be seen from Table 2, eNodeB1, eNodeB2, eNodeB3, eNodeB4, and eNodeB5 are in the same TA. Therefore, the MME sets it on an eNodeB tree, and since eNodeB1 is connected to eNodeB2 and eNodeB3, eNodeB1 is the root. The node, the eNodeB2 and the eNodeB3 are the child nodes of the eNodeB1, and the eNodeB2 is connected to the eNodeB4 and the eNodeB5. Therefore, the eNodeB4 and the eNodeB5 are the child nodes of the eNodeB2. Taking the binary tree as an example, the eNodeB tree is established as shown in FIG. FIG. 4 is only an example of an eNodeB tree established according to the network attributes of the eNodeB1, the eNodeB2, the eNodeB3, the eNodeB4, and the eNodeB5. Of course, the established eNodeB tree may also be in other forms as long as the above-mentioned principle according to the network attribute setting is satisfied.

S303: The MME sends an S1 SETUP RESPONSE message to the eNodeB, where the S1SETUP RESPONSE message includes information of the eNodeB's child nodes in the eNodeB tree.

In this embodiment, the S1 SETUP RESPONSE message is obtained by modifying the existing S1 SETUP RESPONSE (3GPP 36413) message. As shown in Table 4, the cell is added to the existing S1 SETUP RESPONSE message: the leaf eNodeB list Leaf eNodeB List and Its child cell: The global eNodeB identifies the Global eNodeB Id, which is used to represent the information of the child nodes of the eNodeB.

Table 4

IE/Group NameIE/Group Name	PresencePresence	RangeRange
Message TypeMessage Type	MM
MME NameMME Name	OO
Served GUMMEIsServed GUMMEIs		1..<maxnoofRATs>1..<maxnoofRATs>
>Served PLMNs>Served PLMNs		1..<maxnoofPLMNsPer MME>1..<maxnoofPLMNsPer MME>
>>PLMN Identity>>PLMN Identity	MM
>Served GroupIDs>Served GroupIDs		1..<maxnoofGroupIDs>1..<maxnoofGroupIDs>
>>MME Group ID>>MME Group ID	MM
>Served MMECs>Served MMECs		1..<maxnoofMMECs>1..<maxnoofMMECs>
>>MME Code>>MME Code	MM
Relative MME CapacityRelative MME Capacity	MM
MME Relay Support IndicatorMME Relay Support Indicator	OO
Criticality DiagnosticsCriticality Diagnostics	OO
Leaf eNodeB ListLeaf eNodeB List	CC	0..10..1
>Global eNodeB Id>Global eNodeB Id	CC	1..161..16

It should be noted that, in particular, the MME may send an S1 SETUP RESPONSE message carrying information of the child node to the eNodeB if the eNodeB is not a leaf node. In the case where the eNodeB is a leaf node, an existing S1 SETUP RESPONSE message, that is, an S1 SETUP RESPONSE message that does not carry a Leaf eNodeB List cell, is transmitted to the eNodeB.

S304: After receiving the information of the child node, the eNodeB stores the information of the child node locally.

It should be noted that, in addition to the method shown in FIG. 3, the following method may be used to establish an eNodeB tree: the MME establishes an eNodeB tree only according to the category attribute of the eNodeB, that is, the MMEs have the same category (for example, belong to the same TA). The eNodeB is set in an eNodeB tree regardless of the location attribute of the eNodeB. In this case, the S1 SETUP REQUEST message sent by the eNodeB to the MME may use the existing (3GPP 36413) S1 SETUP REQUEST message.

Or: the MME does not consider the class of the eNodeB, but only considers the location attribute of the eNodeB, so that the child node or the parent node of each eNodeB in the eNodeB tree belongs to its S1 SETUP. The other eNodeBs connected to the REQUEST message are connected, and the child nodes do not exceed the value indicated by the Forward Paging Ability in the S1SETUP REQUEST message.

After the eNodeB tree is established, the MME needs to update the eNodeB tree after a new eNodeB accesses the MME or after the connected eNodeB disconnects from the MME. Figure 5 shows the update process of the eNodeB tree, including the following steps:

S501: The MME receives the S1 SETUP REQUEST message sent by the newly accessed eNodeB, where the S1 SETUP REQUEST message carries the network attribute of the newly accessed eNodeB. Specifically, the network attribute includes a location attribute and/or a category attribute. S1 SETUP REQUEST is as described above and will not be described here.

S502: The MME adds the newly accessed eNodeB to the established eNodeB tree according to the network attribute of the newly accessed eNodeB.

Specifically, the method for the MME to add the newly accessed eNodeB to the established eNodeB tree may refer to the process of establishing an eNodeB tree according to FIG. 3, that is, scheduling new access according to the category attribute and/or location attribute of the newly accessed eNodeB. The location of the eNodeB in the eNodeB tree. For example, if the newly accessed eNodeB supports TA1, the MME adds the newly accessed eNodeB to the eNodeB tree corresponding to TA1.

S503: After the MME detects that the eNodeB in the established eNodeB tree is disconnected (for example, the eNodeB is faulty or is removed), the MME deletes the disconnected eNodeB in the eNodeB tree where the disconnected eNodeB is located.

S504: The MME sends an MME CONFIGURATION UPDATE message to the eNodeB that changes the child node in the eNodeB tree, where the MME CONFIGURATION UPDATE message includes information of the updated child node.

It should be noted that there are two cases in which a new eNodeB accesses the MME and the connected eNodeB is disconnected from the MME, which may occur at the same time or separately, so that both S502 and S503 may be executed separately or separately. Execution, in either case, S504 is performed. It should be emphasized that, in S504, the MME sends an MME CONFIGURATION UPDATE message to the eNodeB whose sub-node changes, which is an eNodeB transmission that changes to all the child nodes, instead of only the eNodeB involved in S502 or S503. For example, as shown in Figure 6, in A new intermediate node New eNodeB is inserted in the established eNodeB tree, and the node in the eNodeB tree is changed to eNodeB_root. Therefore, the MME not only sends the MME CONFIGURATION UPDATE message carrying the information of the eNodeBx and the eNodeBy to the New eNodeB, but also The eNodeB_root sends an MME CONFIGURATION UPDATE message carrying the information of the New eNodeB and the eNodeBz.

S505: The eNodeB that receives the MME CONFIGURATION UPDATE message updates the information of the stored child node.

Based on the establishment process of the eNodeB tree described above, a more specific implementation process of the process shown in FIG. 2 is as shown in FIG. 7, and includes the following steps:

S701: After the MME is triggered to perform the paging process, select an eNodeB tree corresponding to the paged UE from the preset eNodeB tree.

Specifically, if one of the basis of the eNodeB tree establishment is the category attribute of the eNodeB, the MME selects an eNodeB tree corresponding to the paging UE from the preset eNodeB tree, and implements according to the category attribute of the paged UE. The category supported by the paged UE is determined, and the eNodeB tree corresponding to the category supported by the paging UE is used as the selected eNodeB tree.

For example, if the paged UE is in TA1, the MME selects the eNodeB tree corresponding to TA1.

Specifically, another implementation manner of the MME selecting an eNodeB tree corresponding to the paging UE from the preset eNodeB tree is: the MME searches for an eNodeB that is the same as the category attribute of the paged UE, and searches for the eNodeB that is found. The eNodeB tree is located as the eNodeB tree corresponding to the paged UE.

For example, if the MME allocated to the paged UE includes TA1 and TA2, the eNodeB1 and the eNodeB2 support TA1, and the eNodeB3 supports the TA2, the MME uses the eNodeB tree where the eNodeB1, the eNodeB2, and the eNodeB3 are located as the eNodeB tree corresponding to the paged UE. .

S702: The MME sends the paging message to the root node in the eNodeB tree corresponding to the paged UE.

Specifically, the MME sends the paging request to the first layer (ie, the root node) of the eNodeB tree by using the root node of the paging tree as the destination address of the multicast. The multicast mentioned in this embodiment refers only to one type. According to the distribution method, including but not limited to the existing IP multicast technology.

S703: The root node in the eNodeB tree sends a paging message to its child node, and each child node sends a paging message to the respective child node, and so on, and the paging message is finally sent to the leaf node.

In this embodiment, the paging PAGING message is defined by the existing (3GPP 36413) message, as shown in Table 5.

The two cells of the List of TAIs and the CSG Id List are different according to the UE. The List of TAIs is a TA List allocated by the MME to the UE.

After an eNodeB receives the paging message, an implementation manner of sending a paging message to the child node is: by associating the List of TAIs with the list of supported TAs, the TA in the intersection is the target category, and the paging message is sent. Forwarded to the child nodes of this eNodeB with child nodes of the target class.

For example, the List of TAIs in the paging message received by an eNodeB includes TA1 and TA2. The eNodeB supports TA1, and the target TA obtained after the intersection is TA1. If the eNodeB has two sub-nodes, one of the eNodeBs supports TA1. The other supports TA2, which forwards the paging message to the child node supporting TA1.

If one of the basis of the eNodeB tree establishment is the category attribute of the eNodeB, after the eNodeB receives the paging message, another implementation manner of sending the paging message to the child node is: the eNodeB directly sends the paging message to the child node. .

The paging method in this embodiment can reduce the number of paging messages sent by the MME, thereby reducing the overhead of the MME. Taking a binary tree as an example, if there are 5 TAs in the TA List and 30 eNodeBs in each TA, the comparison of paging messages sent by the MME before and after the improvement is 150:1.

table 5

The structure of the MME described in FIG. 2, FIG. 3, FIG. 5 and FIG. 7 is as shown in FIG. 8, and includes a memory and a processor. The memory is used to store the program and the data generated during the running of the program, and the processor is configured to implement the functions implemented by the MME described in FIG. 2, FIG. 3, FIG. 5 and FIG. 7 by running the program in the memory.

Figure 9 shows the structure of an eNodeB, including: a receiver and a transmitter. The receiver is configured to receive a paging message, and the transmitter is configured to forward the paging message to the target eNodeB. The eNodeB packet is a set of eNodeBs composed at least of eNodeBs that cover the paged UE.

For the specific function implementation of the receiver and the transmitter, reference may be made to the eNodeBs described in FIG. 2, FIG. 3, FIG. 5, and FIG. 7, which are not described herein again.

The various embodiments in the specification are described in a progressive manner, and each embodiment focuses on differences from other embodiments, and the same or similar parts of the respective embodiments may be referred to each other.

The above description of the disclosed embodiments enables those skilled in the art to make or use the invention. Various modifications to these embodiments will be apparent to those skilled in the art, and the general principles defined herein may be practiced in other embodiments without departing from the scope of the invention. Therefore, the present invention is not to be limited to the embodiments shown herein, but the scope of the invention is to be accorded

Claims

A paging method, comprising:

The mobility management entity MME determines an eNodeB packet corresponding to the paged user equipment UE, where the eNodeB packet corresponding to the paged UE is a set of eNodeBs composed at least by an eNodeB that covers the paged UE;

The MME sends a paging message to at least one eNodeB in the eNodeB packet, and the eNodeB that receives the paging message is used to send the paging message to other eNodeBs in the NodeB packet.
The method according to claim 1, wherein the MME determines an eNodeB packet corresponding to the paged UE, and the eNodeB packet corresponding to the paged UE is composed of at least an eNodeB that covers the paged UE. The set of eNodeBs includes:

The MME selects an eNodeB tree corresponding to the paged UE from the preset eNodeB tree, and the eNodeB tree corresponding to the paged UE includes at least an eNodeB tree in which the eNodeB that covers the paged UE is located, In any one of the eNodeB trees of the preset eNodeB tree, the eNodeB constitutes a node of the eNodeB tree, the node includes a root node, an intermediate node, and a leaf node, and the intermediate node connected to the root node is the root node. The child node, the leaf node connected to the intermediate node is a child node of the intermediate node.
The method according to claim 2, wherein the establishing process of the preset eNodeB tree comprises:

Receiving, by the MME, an S1 SETUP REQUEST message sent by the eNodeB, where the S1SETUP REQUEST message carries a network attribute of the sender;

The MME establishes an eNodeB tree according to the network attribute of the eNodeB.
The method according to claim 3, wherein the establishing, by the MME, the eNodeB tree according to the network attribute of the eNodeB comprises:

The MME establishes an eNodeB tree according to the category attribute in the network attribute of the eNodeB, where the eNodeBs in any one of the eNodeB trees belong to the same category, and the category attribute includes the supported tracking area TA or the supported non- Open user group CSG, or supported TA and CSG;

Or the MME is established according to a location attribute in a network attribute of the eNodeB. An eNodeB tree, wherein the location attribute comprises: information of other eNodeBs connected to the eNodeB and maximum number of other eNodeBs that the eNodeB can interconnect, in which the child nodes or parent nodes of the eNodeB belong The other eNodeBs connected to the eNodeB, the number of the child nodes of the eNodeB not exceeding the maximum number;

Or the MME establishes an eNodeB tree according to the category attribute and the location attribute in the network attribute of the eNodeB, where the eNodeBs in the eNodeB tree belong to the same category, and the child nodes of the eNodeB Or the parent node belongs to other eNodeBs connected to the eNodeB, and the number of child nodes of the eNodeB does not exceed the maximum number.
The method according to claim 3 or 4, wherein after the MME establishes an eNodeB tree according to the network attribute of the eNodeB, the method further includes:

The MME sends an S1 SETUP RESPONSE message to the eNodeB, where the S1SETUP RESPONSE message includes information of the eNodeB's child nodes in the eNodeB tree.
The method according to any one of claims 3 to 5, after the MME establishes an eNodeB tree according to the network attribute of the eNodeB, the method further includes:

The MME receives the S1 SETUP REQUEST message sent by the newly accessed eNodeB, where the S1 SETUP REQUEST message carries the network attribute of the newly accessed eNodeB;

Adding, by the MME, the newly accessed eNodeB to the established eNodeB tree according to the network attribute of the newly accessed eNodeB;

The MME sends an S1 SETUP RESPONSE message to the newly accessed eNodeB, where the S1 SETUP RESPONSE message includes information of the child nodes of the newly accessed eNodeB in the joined eNodeB tree.
The method according to any one of claims 3 to 6, wherein after the MME establishes an eNodeB tree according to the network attribute of the eNodeB, the method further includes:

After the MME detects disconnection from the eNodeB in the established eNodeB tree, the MME deletes the disconnected eNodeB in the eNodeB tree in which the disconnected eNodeB is located.
The method according to claim 6 or 7, further comprising:

The MME sends an eNodeB that changes in a child node in the eNodeB tree The MME CONFIGURATION UPDATE message includes information of the updated child node in the MME CONFIGURATION UPDATE message.
The method according to any one of claims 2 to 8, wherein the MME selects an eNodeB tree corresponding to the paged UE from the preset eNodeB tree, including:

The MME searches for an eNodeB that is the same as the category attribute of the paged UE, the category attribute includes a supported tracking area TA, or a supported non-open user group CSG, or a supported TA and supported CSG;

The MME uses the eNodeB tree in which the eNodeB that is the same as the category attribute of the paged UE is the eNodeB tree corresponding to the paged UE.
The method according to any one of claims 2 to 8, wherein the preset eNodeB tree corresponds to a category, and an eNodeB tree corresponding to a category is jointly established by an eNodeB supporting the category, and the category attribute includes Supported tracking area TA, or supported non-open user group CSG, or supported TA and CSG;

The MME selects an eNodeB tree corresponding to the paged UE from the preset eNodeB tree, including:

Determining, by the MME, a category supported by the paged UE according to a category attribute of the paged UE, where the category attribute includes a supported tracking area TA, or a supported non-open user group CSG, or supported TA and supported CSG;

The MME groups the eNodeB tree corresponding to the category supported by the paging UE as the eNodeB corresponding to the paged device.
The method according to any one of claims 1 to 10, wherein the sending, by the MME, a paging message to at least one eNodeB in the eNodeB packet comprises:

The MME sends a paging message to the root node in the eNodeB tree corresponding to the paged UE.
A paging method, comprising:

Receiving, by the first eNodeB, a paging message;

The first eNodeB forwards the paging message to a second eNodeB, where the first eNodeB and the second eNodeB are in the same eNodeB packet, and the eNodeB packet is composed of at least an eNodeB that covers the paged UE. A collection of eNodeBs.
The method according to claim 12, wherein the first eNodeB and the second eNodeB are in the same group:

The first eNodeB and the second eNodeB are in the same eNodeB tree, the eNodeB tree includes a root node, an intermediate node, and a leaf node, and the intermediate node connected to the root node is a child node of the root node, a leaf node connected to the intermediate node is a child node of the intermediate node;

The first eNodeB is a root node, and the second eNodeB is a child node of the first eNodeB.
The method according to claim 13, wherein before the first eNodeB receives the paging message, the method further includes:

The first eNodeB sends an S1 SETUP REQUEST message to the MME, where the S1SETUP REQUEST message carries the network attribute of the first eNodeB, and the network attribute of the first eNodeB is used together with the network attribute of the second eNodeB. The MME establishes the eNodeB tree;

The first eNodeB receives an S1 SETUP RESPONSE message sent by the MME, where the S1 SETUP RESPONSE message includes information of a child node of the first eNodeB in the eNodeB tree.
The method of claim 14 wherein said network attributes comprise:

Category attribute, location attribute or category attribute and location attribute;

The location attribute includes: information of other eNodeBs connected to the first eNodeB and maximum number of other eNodeBs that the first eNodeB can interconnect; the category attribute includes a supported tracking area TA, or a supported non- Open user group CSG, or supported TA and supported CSG.
The method according to claim 14 or 15, wherein after the first eNodeB receives the S1 SETUP RESPONSE message sent by the MME, the method further includes:

The first eNodeB receives an MME CONFIGURATION UPDATE message, where the MME CONFIGURATION UPDATE message includes information of the updated child node of the first eNodeB.
Method according to any one of claims 13 to 16, wherein said Forwarding the paging message to the second eNodeB by an eNodeB includes:

The first eNodeB uses, as the target category, an intersection of a category carried in the paging message and a category currently supported by the first eNodeB;

The first eNodeB forwards the paging message to a child node of the first eNodeB having the target class.
The method according to any one of claims 13 to 16, wherein the first eNodeB is on an eNodeB tree corresponding to a category supported by the first eNodeB, and the category supported by the first eNodeB The other eNodeBs in the corresponding eNodeB tree are the same as the classes supported by the first eNodeB;

Forwarding, by the first eNodeB, the paging message to the second eNodeB includes:

The first eNodeB forwards the paging message to a child node of the first eNodeB in an eNodeB tree corresponding to a category supported by the first eNodeB.
A mobility management entity, comprising:

a memory for storing programs and data generated during program execution;

And a processor, configured to: determine, by running a program in the memory, an eNodeB packet corresponding to the paged user equipment UE, where the eNodeB packet corresponding to the paged UE is at least covered by the paging UE a set of eNodeBs composed of eNodeBs; and transmitting a paging message to at least one eNodeB in the eNodeB packet, the eNodeB receiving the paging message for transmitting the paging message to the NodeB packet Other eNodeBs.
The mobility management entity according to claim 19, wherein the processor is configured to determine an eNodeB packet corresponding to the paged UE, and the eNodeB packet corresponding to the paged UE is at least covered by the paging The set of eNodeBs composed of UE eNodeBs includes:

The processor is specifically configured to: select, from a preset eNodeB tree, an eNodeB tree corresponding to the paged UE, where the eNodeB tree corresponding to the paged UE includes at least an eNodeB that covers the paged UE. An eNodeB tree, in an eNodeB tree of the preset eNodeB tree, the eNodeB constitutes a node of the eNodeB tree, the node includes a root node, an intermediate node, and a leaf node, and the intermediate node connected to the root node is A child node of the root node, and a leaf node connected to the intermediate node is a child node of the intermediate node.
The mobility management entity according to claim 20, wherein the processor is further configured to:

Receiving an S1 SETUP REQUEST message sent by the eNodeB, where the S1 SETUP REQUEST message carries a network attribute of the sender;

An eNodeB tree is established according to the network attributes of the eNodeB.
The mobility management entity according to claim 21, wherein the processor is configured to establish an eNodeB tree according to network attributes of the eNodeB, including:

The processor is specifically configured to establish an eNodeB tree according to the category attribute in the network attribute of the eNodeB, where the eNodeBs in any one of the eNodeB trees belong to the same category, and the category attribute includes the supported tracking area TA, Or a supported non-open user group CSG, or a supported TA and a CSG;

Or establishing an eNodeB tree according to the location attribute in the network attribute of the eNodeB, where the location attribute includes: information about other eNodeBs connected to the eNodeB and maximum number of other eNodeBs that the eNodeB can interconnect, In the eNodeB tree, the child node or the parent node of the eNodeB belongs to other eNodeBs connected to the eNodeB, and the number of child nodes of the eNodeB does not exceed the maximum number;

Or establishing an eNodeB tree according to the category attribute and the location attribute in a network attribute of the eNodeB, where eNodeBs in the eNodeB tree belong to the same category, and a child node or a parent node of the eNodeB It belongs to other eNodeBs connected to the eNodeB, and the number of child nodes of the eNodeB does not exceed the maximum number.
The mobility management entity according to claim 21 or 22, wherein the processor is further configured to:

After the eNodeB tree is established according to the network attribute of the eNodeB, an S1 SETUP RESPONSE message is sent to the eNodeB, where the S1 SETUP RESPONSE message includes information of the eNodeB's child nodes in the eNodeB tree.
The mobility management entity according to any one of claims 21 to 23, wherein the processor is further configured to:

After the eNodeB tree is established according to the network attribute of the eNodeB, receiving an S1 SETUP REQUEST message sent by the newly accessed eNodeB, where the S1 SETUP REQUEST The message carries the network attribute of the newly accessed eNodeB;

Adding the newly accessed eNodeB to the established eNodeB tree according to the network attribute of the newly accessed eNodeB;

Sending an S1 SETUP RESPONSE message to the newly accessed eNodeB, where the S1SETUP RESPONSE message includes information of a child node of the newly accessed eNodeB in the joined eNodeB tree.
The mobility management entity according to any one of claims 21 to 24, wherein the processor is further configured to:

After the eNodeB tree is established according to the network attribute of the eNodeB, after the MME detects disconnection from the eNodeB in the established eNodeB tree, deleting the eNodeB tree in which the disconnected eNodeB is located Disconnected eNodeB.
The mobility management entity according to claim 24 or 25, wherein the processor is further configured to:

Sending an MME CONFIGURATION UPDATE message to the eNodeB that changes in the child node in the eNodeB tree, where the MME CONFIGURATION UPDATE message includes information of the updated child node.
The mobility management entity according to any one of claims 20 to 26, wherein the processor is configured to select, from a preset eNodeB tree, an eNodeB tree corresponding to the paged UE, including:

The processor is specifically configured to: search for an eNodeB that is the same as a category attribute of the paged UE, where the category attribute includes a supported tracking area TA, or a supported non-open user group CSG, or supported The TA and the supported CSG; the eNodeB tree in which the eNodeB having the same category attribute as the paged UE is located as the eNodeB tree corresponding to the paged UE.
The mobility management entity according to any one of claims 20 to 27, wherein the preset eNodeB tree corresponds to a category, and an eNodeB tree corresponding to one category is jointly established by an eNodeB supporting the category, The category attribute includes the supported tracking area TA, or the supported non-open user group CSG, or the supported TA and the CSG;

The processor is configured to select an eNodeB corresponding to the paged UE from a preset eNodeB tree. The tree includes:

The processor is specifically configured to determine, according to a category attribute of the paged UE, a category supported by the paged UE, where the category attribute includes a supported tracking area TA, or a supported non-open user group. The CSG, or the supported TA and the supported CSG; the eNodeB tree corresponding to the category supported by the paging UE is grouped as the eNodeB corresponding to the paged device.
The mobility management entity according to any one of claims 19 to 28, wherein the processor is configured to send a paging message to at least one eNodeB in the eNodeB packet, including:

The processor is specifically configured to send a paging message to a root node in an eNodeB tree corresponding to the paged UE.
An eNodeB, comprising:

a receiver for receiving a paging message;

And a transmitter, configured to forward the paging message to a target eNodeB, where the eNodeB and the target eNodeB are in the same eNodeB group, and the eNodeB packet is a set of eNodeBs composed at least by an eNodeB that covers the paging UE.
The eNodeB according to claim 30, wherein the eNodeB and the target eNodeB are in the same eNodeB group includes:

The eNodeB and the target eNodeB are in the same eNodeB tree, the eNodeB tree includes a root node, an intermediate node, and a leaf node, and the intermediate node connected to the root node is a child node of the root node, and the The leaf node connected by the intermediate node is a child node of the intermediate node;

The eNodeB is a root node, and the target eNodeB is a child node of the eNodeB.
The eNodeB according to claim 31, wherein the transmitter is further configured to:

Before the receiving the paging message, send an S1 SETUP REQUEST message to the MME, where the S1 SETUP REQUEST message carries the network attribute of the eNodeB, and the network attribute of the eNodeB is used together with the network attribute of the target eNodeB. The MME establishes the eNodeB tree;

The receiver is further configured to: receive an S1 SETUP RESPONSE message sent by the MME, where the S1 SETUP RESPONSE message includes information of a child node of the eNodeB in the eNodeB tree.
The eNodeB according to claim 32, wherein the sender is configured to send an S1 SETUP REQUEST message to the MME, where the network attributes of the eNodeB that are carried in the S1 SETUP REQUEST message include:

The transmitter is specifically configured to send an S1 SETUP REQUEST message to the MME, where the S1 SETUP REQUEST message carries the network attribute of the eNodeB, where the network attribute includes:

Category attribute, location attribute or category attribute and location attribute;

The location attribute includes: information of other eNodeBs connected to the eNodeB and maximum number of other eNodeBs that the eNodeB can interconnect; the category attribute includes a supported tracking area TA, or a supported non-open user group CSG, or supported TA and supported CSG.
The eNodeB according to claim 32 or 33, wherein the receiver is further configured to:

And after receiving the S1 SETUP RESPONSE message sent by the MME, receiving an MME CONFIGURATION UPDATE message, where the MME CONFIGURATION UPDATE message includes information of the updated child node of the eNodeB.
The eNodeB according to any one of claims 31 to 34, wherein the transmitter is configured to forward the paging message to the target eNodeB, including:

The transmitter is specifically configured to: use an intersection of a category carried in the paging message and a category currently supported by the eNodeB as a target category; and forward the paging message to a child node of the eNodeB. The child nodes of the target category.
The eNodeB according to any one of claims 31 to 34, wherein the eNodeB is in an eNodeB tree corresponding to a category supported by the eNodeB, and the eNodeB tree corresponding to a category supported by the eNodeB Other eNodeBs are of the same type as the eNodeB supports;

The transmitting, by the transmitter, the forwarding of the paging message to the target eNodeB includes:

The transmitter is specifically configured to forward the paging message to a child node of the eNodeB in an eNodeB tree corresponding to a category supported by the eNodeB.