WO2013002566A2

WO2013002566A2 - Paging optimization method

Info

Publication number: WO2013002566A2
Application number: PCT/KR2012/005109
Authority: WO
Inventors: Huarui Liang; Hong Wang
Original assignee: Samsung Electronics Co Ltd
Current assignee: Samsung Electronics Co Ltd
Priority date: 2011-06-29
Filing date: 2012-06-28
Publication date: 2013-01-03
Anticipated expiration: 2013-12-29
Also published as: WO2013002566A3; CN102858013A; CN102858013B

Abstract

The present invention provides paging optimization methods. One of the methods is applied to a network including a HeNB GW and includes that: if LIPA paging optimization is configured in the network, transmitting, by a MME, to the HeNB GW a paging message including a HeNB ID corresponding to a LIPA bearer. By the present invention, LIPA paging optimization can be realized in the scenario in which the HeNB GW is configured or in network architecture supported by R-11.

Description

PAGING OPTIMIZATION METHOD

The present invention relates to radio communication technologies, and more particularly to a paging optimization method.

Figure 1 is a schematic diagram illustrating the structure of a conventional System Architecture Evolution (SAE). In Figure 1, a User Equipment (UE) 101 is a terminal device for receiving data. An Evolved Universal Terrestrial Radio Access Network (E-UTRAN) 102 is a radio access network which includes an eNodeB/NodeB for providing a radio network interface for the UE. A Mobile Management Entity (MME) 103 is adapted to manage mobility contexts, session contexts and security information of the UE. A Serving Gateway (SGW) 104 is adapted to provide functions of a subscriber plane. The MME 103 and the SGW 104 may be in the same physical entity. A Packet Gateway (PGW) 105 is adapted to implement charging and legal monitoring functions. The PGW 105 and the SGW 104 may be in the same physical entity. A Policy and Charging Rules Function (PCRF) 106 is adapted to provide QoS policies and charging rules. A Service GPRS Supporting Node (SGSN) 108 is a network node device for providing routing for data transmission in a Universal Mobile Telecommunications System (UMTS). A Home Subscriber Server (HSS) 109 is a home sub-system of the UE and is adapted to protect user information including the current location of the UE, the address of a serving node, user security information and packet data contexts of the UE.

In 3GPP Release 9, a Home (evolved) Node B (H(e)NB) supports a Closed Subscriber Group (CSG), that is to say, the H(e)NB only provides network access services for a specific subscriber or a subscriber group. In order to decrease signaling traffic of air interfaces, a paging optimization method is introduced in Release 9, which specifically includes that: when a network initiates paging to the UE, if in the network there are a part of CSG cells which the UE is not allowed accessing, these CSG cells are excluded preferentially when the network initiates paging.

In 3GPP Release-10 (which is called R-10 for short), the network needs to support Local IP Access (LIPA). The LIPA refers to that the UE accesses a home network or an enterprise network through a HeNB or a Home Node B (HNB). When LIPA is performed, a subscriber plane node adjacent to the HNB may be selected or reselected for the UE or a subscriber plane node in a HeNB/HNB access network may be selected for the UE. The subscriber plane node is a core network device or a gateway. In the SAE, the subscriber plane node may be a SGW, PGW or a Local Gateway (LGW), and in the UMTS system, the subscriber plane node may be a SGSN or a Gateway GPRS Supporting Node (GGSN).

But, the LIPA in R-10 does not support mobility. When the UE moves outside the HeNB/HNB supporting LIPA, LIPA related services of the UE are interrupted. When paging optimization is performed for the LIPA in R-10, the network may sends a paging signaling to a H(e)NB at which the UE activated the LIPA service last time. If paging is successful, the LIPA service is recovered. If the UE does not respond, paging is initiated again in a larger area. Figure 2 is a flowchart illustrating a procedure of performing paging optimization for the LIPA in R-10. As shown in Figure 2, the paging optimization procedure includes the following steps.

Step 201, a LGW receives downlink data; if a LIPA connection exists, the LGW sends the first downlink data to a SGW, and caches other downlink data for the moment.

Step 202, the SGW sends a downlink data notification message to a MME to trigger paging, where the downlink data notification message carries a bearer ID (ID).

Step 203, the MME sends a downlink data recovering ACK message to the SGW.

Step 204, the MME send a paging message to a HeNB according to the bearer ID carried in the downlink data notification message. During a procedure that the UE sets up the LIPA connection, the MME stores a corresponding relation between an ECGI (which corresponds to a HeNB ID) and the bearer ID. Therefore, when step 204 is performed, the MME determines a HeNB corresponding to the bearer ID carried in the downlink data notification message according to the stored corresponding relation and the bearer ID carried in the downlink data notification message, and sends the paging message to the determined HeNB.

Step 205, the HeNB sends the paging message to the UE.

Thus, the procedure of performing paging optimization the LIPA in R-10 shown in Figure 2 is completed.

However, the paging optimization performed for the LIPA in R-10 is optional, and can not be used when a HeNB GW is configured in the network. The reasons are as follows: when the HeNB GW is configured in the network, the MME knows the corresponding relation between the bearer ID and the HeNB ID (ECGI), but the MME can not find the correct HeNB through paging because the HeNB GW releases all contexts of the UE when being in an idle state, and thus paging optimization can not be realized.

In addition, when the HeNB GW is configured in the network, the paging optimization performed for LIPA in R-10 can not be used, but in the UMTS system, the HNB GW is an essential node, and thus, the paging optimization performed for the LIPA in R-10 is inapplicable to the UMTS system.

In 3GPP Release-11 (which is called R-11 for short), LIPA supports mobility, that is to say, when the UE moves in a local network, the continuity of UE services should be guaranteed. Compared with the network architecture of LIPA in R-10, the network architecture of LIPA in R-11 is changed. Specifically, only one kind of network architecture of LIPA is supported in R-10, and the H(e)NB and the LGW are in the same physical entity; three kinds of network architecture of LIPA are supported in R-11. Herein, two kinds of network architecture are similar, as shown in Figures 3a to 3c, and the difference lies in that the Sxx interface between the HeNB/HNB and the LGW supports different protocol stacks. In one kind of network architecture, the Sxx interface supports both GTP-C and GTP-U protocols, and the other kind of network architecture, the Sxx interface only supports the GTP-U protocol. In the third network architecture, as shown in Figures 3d to 3f, a S1 protocol is supported between the HeNB and the LGW, and an Iuh interface is supported between the HNB and the LGW. But, no paging optimization performed for LIPA can be applicable to the three kinds of network architecture in R-11 at present.

The present invention provides paging optimization methods, so as to realize paging optimization performed for LIPA in a scenario in which a HeNB GW is configured or in network architecture supported by R-11.

The technical solution provided by the present invention is as follows:

A paging optimization method in a network including a HeNB GW, includes:

if LIPA paging optimization is configured in the network, transmitting, by a MME, to the HeNB GW a paging message including a HeNB ID corresponding to a LIPA bearer.

A paging optimization method in a network including a HeNB GW , includes:

if LIPA paging optimization is configured in the network, transmitting, by a MME, a paging message to the HeNB GW,

wherein the paging message includes a parameter used for determining a HeNB corresponding to a LIPA bearer.

A paging optimization method in a network, includes:

if LIPA paging optimization is configured in the network, transmitting, by a MME, to a HeNB a paging message including a HeNB ID corresponding to a LIPA bearer.

As can be seen from the above technical solution, in the present invention, regardless the paging optimization method is applied to the scenario in which the HeNB GW is configured, to the scenario in which no HeNB GW is configured, or to the network architecture supported by R-11, the paging optimization performed for LIPA can be realized.

Figure 1 is a schematic diagram illustrating the structure of a conventional SAE.

Figure 2 is a flowchart illustrating a procedure of performing paging optimization for the LIPA in R-10.

Figures 3a to 3f are schematic diagrams illustrating network architecture supported by R-11.

Figure 4a is a flowchart illustrating a first embodiment of the present invention.

Figure 4b is a flowchart illustrating a procedure of setting up a S1 connection between a HeNB GW and a HeNB according to the first embodiment of the present invention.

Figure 5a is a flowchart illustrating a second embodiment of the present invention.

Figure 5b is a flowchart illustrating a procedure that a UE sets up a LIPA connection.

Figure 6a is a flowchart illustrating a third embodiment of the present invention.

Figure 6b is a flowchart illustrating a procedure that a MME sets up a S1 connection according to the third embodiment of the present invention.

Figure 7 is a flowchart illustrating a procedure that a UE initiates a LIPA connection.

Figure 8 is a flowchart illustrating a fourth embodiment of the present invention.

Figures 9a to 9b are flowcharts illustrating a S1 setup procedure according to the fourth embodiment of the present invention.

Figures 10a to 10c are schematic diagrams illustrating a UE access procedure according to an embodiment of the present invention.

Figure 11 is a flowchart illustrating a fifth embodiment of the present invention.

Figures 12a to 12b are flowcharts illustrating a S1 setup procedure according to the fifth embodiment of the present invention.

Figure 13 is a flowchart illustrating a sixth embodiment of the present invention.

Figures 14a to 14c are flowcharts illustrating a procedure that a H-GW obtains an APN ID according to the sixth embodiment of the present invention.

Figure 15 is a flowchart illustrating a seventh embodiment of the present invention.

In order to make the object, technical solution and merits of the present invention clearer, the present invention will be illustrated in detail hereinafter with reference to the accompanying drawings and specific embodiments.

The paging optimization methods provided by the present invention may be applied to a scenario in which a HeNB GW is configured or to a scenario in which no HeNB GW is configured, and will be illustrated hereinafter with reference to embodiments.

The first embodiment

The first embodiment is applied to the scenario in which the HeNB GW is configured and includes that: if LIPA paging optimization is configured in a network, a paging message sent to the HeNB GW by a MME carries a HeNB identity (ID) corresponding to a LIPA bearer. The first embodiment will be described in detail hereinafter with reference to Figure 4a.

Figure 4a is a flowchart illustrating the first embodiment of the present invention. As shown in Figure 4a, the flowchart includes the following steps.

Step 401a, a LGW receives downlink data; if the downlink data is used for LIPA, the LGW sends the downlink data to a SGW.

In step 401a, if the method is applied to network architecture of R-10, the LGW sends the first downlink data to the SGW, and caches other downlink data in the LGW. If the method is applied to other network architecture, the downlink data is sent according to the requirements of other network architecture.

Step 402a, the SGW sends a downlink data notification message to the MME, where the downlink data notification message carries a bearer ID.

Step 403, the MME determines, according to the bearer ID carried in the downlink data notification message, that the paging supports LIPA, determines a HeNB ID corresponding to the bearer ID according to a corresponding relation between the bearer ID and the HeNB ID which is stored when the UE sets up a LIPA connection, and sends the HeNB ID to the HeNB GW through carrying the HeNB ID in the paging message.

In step 403a, the HeNB ID may be the name of the HeNB, serial numbers of the ECGI and HeNB, or an ID through which the HeNB can be found.

In addition, the HeNB ID is carried in the paging message in step 403a, so as to help the HeNB GW to send the paging message to the HeNB at which the UE sets up the LIPA connection.

Step 404a, after receiving the paging message, the HeNB GW sends the paging message to the HeNB corresponding to the HeNB ID carried in the paging message.

In step 404a, the HeNB GW sending the paging message to the HeNB corresponding to the HeNB ID carried in the paging message includes that: the HeNB GW determines the HeNB corresponding to the determined HeNB ID according to a corresponding relation between HeNB identities and all HeNBs connected with the HeNB GW which is stored when the HeNB GW sets up a S1 connection to the HeNB, and sends the paging message to the determined HeNB. The procedure of setting up the S1 connection between the HeNB GW and the HeNB may refer to Figure 4b, and includes the following procedure.

The HeNB sends a S1 setup request to the HeNB GW, where the S1 setup request carries the HeNB ID and CSG information. The HeNB GW may store the HeNB identities corresponding to the all HeNBs connected with the HeNB GW according to the S1 setup request.

Step 405a, the HeNB sends the paging message to the UE.

Thus, the paging procedure shown in Figure 4a is completed.

In the paging procedure, paging success or paging failure usually occurs, which will be illustrated hereinafter.

It should be described that, the flowchart shown in Figure 4a is illustrated by taking the LTE architecture as an example, which is also applicable to the UMTS system. But, in the UMTS syste, the HeNB should be replaced with a HNB, the HeNB GW should be replaced with a HNB GW, the MME should be replaced with a SGSN, and the LGW should be replaced with a GGSN.

In the first embodiment, the MME directly determines to send the paging message to which HeNB. Preferably, as an extended example of this embodiment, the MME may determine a parameter for helping the HeNB GW to determine to send the paging message to which HeNB, and then the HeNB GW determines, according to the parameter, to send the paging message to which HeNB, referring to the second embodiment.

The second embodiment

The second embodiment is also applied to the scenario in which the HeNB GW is configured and includes that: if LIPA paging optimization is configured in the network, the paging message sent to the HeNB GW by the MME carries a parameter for helping the HeNB GW to determine a HeNB corresponding to the LIPA bearer. And thus, the HeNB GW may determine the HeNB according to the parameter carried in the paging message. The second embodiment will be illustrated hereinafter in detail.

Figure 5a is a flowchart illustrating the second embodiment of the present invention. As shown in Figure 5a, the flowchart includes the following steps.

Steps 501a to 502a are similar to steps 401a to 402a, and will not be described in detail.

Step 503a, the MME determines, according to the bearer ID carried in the paging message, that this paging supports LIPA, and determines a LGW IP address corresponding to the bearer ID carried in the paging message according to a corresponding relation between the bearer ID and the LGW IP address which is stored when the UE sets up the LIPA connection, and sends the determined LGW IP address to the HeNB GW through carrying the LGW IP address in the paging message.

In step 503a, the LGW IP address is carried in the paging message, so as to help the HeNB GW to send the paging message to the HeNB GW at which the UE sets up the LIPA connection.

The procedure that the UE sets up the LIPA connection may refers to the flowchart shown in Figure 5b and will be illustrated hereinafter.

Step 504a, the HeNB GW determines, according to the corresponding relation between the LGW IP address and the HeNB ID which is stored when the UE sets up the LIPA connection, that the HeNB corresponding to the LGW IP address carried in the paging message is a HeNB receiving the paging message.

Preferably, as an extended example of the embodiment of the present invention, step 504a may be replaced with that the HeNB GW preferentially excludes, according to the corresponding relation between the LGW IP address and the HeNB ID which is stored when the UE sets up the LIPA connection, HeNBs corresponding to other LGW IP addresses expect the LGW IP address carried in the paging message, and determines that the remained HeNB is the HeNB receiving the paging message.

Step 505a is similar to step 405a.

Thus, the flowchart shown in Figure 5a is completed.

It should be described that, the flowchart shown in Figure 5a is illustrated by taking the LTE architecture as an example, which is also applicable to the UMTS system. But in the UMTS system, the HeNB should be replaced with a HNB, the HeNB GW should be replaced with a HNB GW, the MME should be replaced with a SGSN, and the LGW should be replaced with a GGSN.

Figure 5b is a flowchart illustrating a procedure that the UE sets up the LIPA connection. As shown in Figure 5b, the flowchart includes the following steps.

Step 501b, Radio Resource Control (RRC) is set up between the UE and the HeNB.

Step 502b, the HeNB sends an initial UE message to the H-GW, where the initial UE message carries such information as the LGW IP address, the HeNB ID (ECGI), the CSG ID and TAI.

After receiving the initial UE message, the H-GW stores the corresponding relation between the HeNB ID (ECGI) and the LGW IP address, and does not release the corresponding relation when the UE is in an idle state. Preferably, in this embodiment, the H-GW may also obtain and store the corresponding relation between the HeNB ID and the LGW IP address through the S1 setup procedure.

Step 503b, the HeNB GW sends the initial UE message to the MME, where the initial UE message carries such information as the LGW IP address, the HeNB ID (ECGI), the CSG ID and TAI.

Step 504b, the UE sends an attach message to the MME, or sends a connection request initiated by the UE to the MME.

Step 505b, the MME sends a create session request to the SGW, to set up the LIPA connection. The subsequent procedure is the same as the conventional procedure and will not be illustrated in detail.

In step 505b, the MME stores the corresponding relation between the LGW IP address and the bearer ID.

Thus, the LIPA connection procedure initiated by the UE is completed.

It should be described that, if the method is applied to the UMTS system, in step 503b, when the H-GW replacing the HeNB GW sends the initial UE message to the SGSN, the initial UE message carries the LGW IP address and the H-GW ID, so as to guarantee that in the subsequent procedure the SGSN can obtain the corresponding relation between the bearer ID and the H-GW ID. In this way, during the paging procedure, after receiving the downlink data notification message, the SGSN can find the H-GW ID corresponding to the bearer ID.

Thus, the second embodiment is completed. The second embodiment and the first embodiment may be replaced with each other to support LIPA paging optimization, and the method provided by the first and second embodiments is more applicable to the R-10 LIPA architecture.

The third embodiment

The third embodiment is applied to the scenario in which no HeNB GW is configured and includes that: if LIPA paging optimization is configured in the network, the paging message sent to the HeNB by the MME carries the HeNB ID corresponding to the LIPA bearer. The third embodiment will be described hereinafter in detail.

Figure 6a is a flowchart illustrating the third embodiment of the present invention. As shown in Figure 6a, the flowchart includes the following steps.

Steps 601a to 602a are similar to steps 401a to 402a, and will not be described herein.

Step 603a, the MME sends a downlink data notification (ACK) to the SGW.

Step 604, the MME determines, according to the bearer ID carried in the downlink data notification message sent by the SGW, that this paging supports LIPA, obtains the LHN ID corresponding to the bearer ID carried in the paging message according to the stored corresponding relation between the bearer ID and the LHN ID, determines, according to the obtained LHN ID, the corresponding relation between the LHN ID and the HeNB ID which is stored when the S1 connection is set up, and the current location information of the UE (TA list), to send the paging message to which NeNB. Specifically, the MME sends the paging message to all HeNBs in the LHN corresponding to the obtained LHN ID.

Preferably, as an extended example of the embodiment of the present invention, step 604a may be replaced with that the MME determines, according to the bearer ID carried in the downlink data notification message sent by the SGW, that this paging supports LIPA, obtains the LHN ID corresponding to the bearer ID carried in the paging message according to the stored corresponding relation between the bearer ID and the LHN ID, preferentially excludes NeNBs corresponding to other LHN identities according to the obtained LHN ID, the corresponding relation between the LHN ID and the HeNB ID which is stored when the S1 connection is set up and the current location information of the UE, and determines the remained HeNB as the HeNB which the paging message is to be sent to.

Step 605a is similar to step 405a and will not be described in detail.

The procedure that the MME sets up the S1 connection is shown in Figure 6b and includes the following steps.

Step 601b, the HeNB sends a S1 setup request to the MME, where the S1 setup request contains a Local Home Network (LHN) ID. The LHN ID may be a network ID, or an IP address, or a name uniquely identifying the LHN. One HeNB only belongs to one LHN. The S1 setup request also contains the HeNB ID, the location information of the HeNB (Tracking area code), PLMN ID information and CSG ID information. In this way, the MME may obtain the corresponding relation between the LHN ID and HeNB identities of all connected HeNBs through the S1 setup request.

Step 602, the MME sends a S1 setup response to the HeNB.

Thus, the procedure of setting up the S1 connection between the MME and the HeNB is completed.

In addition, the MME stores the corresponding relation between the bearer ID and the LHN ID through the following mode (called a deducing mode): the MME deduces and stores the corresponding relation between the bearer ID and the LHN ID according to the corresponding relation between the bearer ID and the HeNB ID which is stored when the UE sets up the LIPA connection and the corresponding relation between the HeNB ID and the LHN ID which is stored when the UE sets up the S1 connection, referring to Figure 7. The corresponding relation between the bearer ID and the LHN ID may be obtained when the UE sets up the LIPA connection.

Figure 7 is a flowchart illustrating a procedure that the UE initiates the LIPA connection. As shown in Figure 7, the flowchart includes the following steps.

Step 701 is similar to step 501b.

Step 702, the HeNB sends an initial UE message to the MME, where the initial UE message carries the LHN ID, the HeNB ID, the CSG ID and the TAI. The LHN ID is optional.

Preferably, as an extended example of the embodiment of the present invention, if the method is applied to the scenario in which the HeNB GW is configured, the initial UE message is forwarded to the MME by the HeNB through the HeNB GW.

Step 703, the UE sends an attach message to the MME, or sends a connection request initiated by the UE to the MME.

Step 704, the MME sends a create session request to the SGW. If the initial UE message carries the LHN ID, the MME may obtain the corresponding relation between the LHN ID and the bearer ID according to the procedure. If the initial UE message does not carry the LHN ID, the MME may obtain the corresponding relation between the HeNB ID and the bearer ID through the procedure, and deduces the corresponding relation between the LHN ID and the bearer ID according to the corresponding relation between the HeNB ID and the LHN ID which is obtained during the S1 setup procedure.

The fourth embodiment

This embodiment is similar to the first and second embodiments, and is applied to the scenario in which the HeNB GW is configured.

Figure 8 is a flowchart illustrating the fourth embodiment of the present invention. As shown in Figure 8, the flowchart includes the following steps.

Steps 801 to 803 are similar to steps 601a to 603a, and will not be described herein.

Step 804, the MME determines, according to the bearer ID carried in the downlink data notification message sent by the SGW, that this paging supports LIPA, determines the LHN ID according to the bearer ID carried in the downlink data notification message, the corresponding relation between the bearer ID and the LHN ID which is obtained when the UE sets up the LIPA connection (as shown in Figure 7), and the current location information of the UE, and sends the determined LHN ID to the H-GW by carrying the LHN ID in the paging message.

In step 804, the paging message carries the LHN ID, to make the H-GW send the paging message to HeNBs in the LHN corresponding to the carried LHN ID.

It should be described that, the LHN ID carried in the paging message is the LHN ID used when the UE sets up the LIPA bearer , or may be multiple LHN ID lists.

Step 805, the H-GW determines the HeNB corresponding to the LHN ID carried in the paging message according to the corresponding relation between the LHN ID and the connected HeNBs which is stored during the S1 setup procedure, and sends the paging message to the determined HeNB.

The S1 setup procedure in step 805 is shown in Figure 9a, which is a S1 setup procedure between the HeNB and the H-GW after the HeNB is powered on and includes the following steps.

Step 901a, the HeNB sends a S1 setup request to the H-GW, where the S1 setup request carries the LHN ID, the HeNB ID, the location information of the HeNB (Tracking area code), the PLMN ID information and the CSG ID information. In this way, the H-GW stores the corresponding relation between the LHN ID and all connected HeNBs according to the S1 setup request.

Step 902a, the H-GW sends a S1 setup response to the HeNB. Thus, the procedure of setting up the S1 connection between the HeNB and the H-GW after the HeNB is powered on is completed.

It should be described that, the present invention also discloses the procedure of setting up S1 between the H-GW and the MME, as shown in Figure 9b, which includes the following steps.

Step 901b, the H-GW sends a S1 setup request to the MME, where the S1 setup request carries a LHN ID list (an ID list of LHNs supported by the H-GW, a H-GW ID, a CSG list, PLMN ID information and location information.

Step 902b, the MME returns a S1 setup response. Thus, the procedure of setting up S1 between the H-GW and the MME as shown in Figure 9b is completed.

Step 806, the HeNB sends the paging message to the UE.

Thus, the flowchart shown in Figure 8 is completed. It should be described that, as an extended example of the embodiment of the present invention, in step 804, the paging message sent to the H-GW by the MME may carry the LHN ID and the access location information of the UE (TA list). Thus, step 805 is replaced with that the H-GW excludes, according to the LHN ID carried in the paging message and the location information of the UE, HeNBs corresponding to the LHN or LHN list which the UE can not access, and sends the paging message to the remained HeNB.

Thus, the fourth embodiment is completed.

It should be described that, the UE may access the LAN through the following modes.

A first mode includes that: one LAN has one LGW, and the UE may access the LHN through the LGW, as shown in Figure 10a. In this mode, one UE may access more than one connections at the same time, and the one or more connections are LIPA connections for the UE.

A second mode includes that: one LAN may include multiple sub-networks, so that UE with different identities can access different types of services. For example, a user A may access PDN 1 through a sub-network 1 and access PDN 2 through a sub-network 2 at the same time, and a user B only accesses PDN1 through the sub-network 2, as shown in Figure 10b.

A third mode includes that: one LAN may include multiple LGW, and one HeNB may be connected with multiple LGWs. The UE may access multiple PDNs through one LGW, or may access multiple PDNs through multiple LGWs, as shown in Figure 10c.

Based on the above three modes, the LIPA paging may be further optimized, referring to the fifth embodiment.

The fifth embodiment

The fifth embodiment is applied to a scenario in which H-GW is configured, the fifth embodiment and the fourth embodiment may be replaced with each other.

Figure 11 is a flowchart illustrating the fifth embodiment of the present invention. As shown in Figure 11 the flowchart includes the following steps.

Steps 1101 to 1103 are similar to steps 601a to 603a, and will not be described in detail herein.

Step 1104, the MME determines, according to the bearer ID carried in the downlink data notification message sent by the SGW, that this paging supports LIPA, obtains the LGW IP address corresponding to the bearer ID according to the corresponding relation between the bearer ID and the LGW IP address which is stored when the UE sets up the LIPA connection, and sends the obtained LGW IP address to the H-GW by carrying the LGW IP address in the paging message.

The LGW IP address may be a LGW IP address determined through one of the above three modes.

It should be described that, if the initial UE message sent to the MME carries the LHN ID, the MME may store a corresponding relation among the bearer ID, the LGW IP address and the LHN ID. The paging message sent in step 1104 may carry the LHN ID determined according to the bearer ID, or does not carry the LHN ID determined according to the bearer ID, i.e., the LHN ID is optional.

As an extended example of the embodiment of the present invention, if no H-GW is configured, the MME may only send the paging message to the HeNB according to the stored corresponding relation between the LGW IP address and the HeNB ID. Or, if no H-GW is configured, as an extended example of the present invention, the MME preferentially excludes, according to the stored corresponding relation between the LGW IP address and the HeNB ID, other LGW IP address except the LGW IP address carried in the paging message, and sends the paging message to the HeNB corresponding to the remained LGW IP address.

Step 1105, the H-GW determines the HeNB corresponding to the LGW IP address carried in the paging message according to the corresponding relation between the HeNB ID and the LGW IP address or the LGW IP address list which is stored during the S1 setup procedure, and sends the paging message to the determined HeNB.

Preferably, as an extended example of the embodiment of the present invention, step 1105 may be replaced with that the H-GW preferentially excludes, according to the corresponding relation between the HeNB ID and the LGW IP address or the LGW IP address list which is stored during the S1 setup procedure, other LGW IP addresses except the LGW IP address carried in the paging message, and sends the paging message to the HeNB corresponding to the remained LGW IP address.

The S1 setup procedure is shown in Figure 12a, includes the S1 setup procedure between the HeNB and the H-GW, and includes the following steps.

Step 1201a, the HeNB sends a S1 setup request to the H-GW, where the S1 setup request carries the HeNB ID, the PLMN ID, the CSG ID, the location information of the HeNB, the LHN ID and IP addresses of all LGWs connected to the HeNB. It can be seen from the above three modes or Figures 10a to 10c that the HeNB may be connected with multiple LGWs, and thus, the S1 setup request may carry one or more LGW IP addresses.

The LHN ID is optional.

Based on the S1 setup request, the H-GW may store the corresponding relation between the HeNB ID and the LGW IP address or the LGW IP address list. If the LHN ID may also be sent to the H-GW, the H-GW may store the corresponding relation among the LGW IP address or the LGW IP address list, the HeNB ID and the LHN ID.

Step 1202a, the H-GW returns a S1 setup response.

The present invention also discloses the S1 setup procedure between the H-GW and the MME, as shown in Figure 12b.

Step 1201b, the H-GW sends a S1 setup request to the MME, where the S1 setup request carries the H-GW ID. The S1 setup request may further carry the LHN ID list (an ID list of LHNs of all connected HeNBs), where the ID list is optional.

Step 1202b, the MME returns a S1 setup response.

It should be described that, if no H-GW is configured, the HeNB may directly send the S1 setup request to the MME, where the S1 setup request is the same as that in step 1201a. The MME stores the corresponding relation between the connected HeNB ID and the LGW IP address list.

The sixth embodiment

The sixth embodiment is applied to a scenario in which the H-GW is configured. Figure 13 is a flowchart illustrating the sixth embodiment of the present invention. As shown in Figure 13, the flowchart includes the following steps.

Steps 1301 to 1303 are similar to steps 601a to 603a, and will not be described in detail herein.

Step 1304, the MME determines, according to the bearer ID carried in the downlink data notification message sent by the SGW, that this paging supports LIPA, determines the APN ID corresponding to the bearer ID carried in the downlink data notification message according to the corresponding relation between the bearer ID and the APN ID which is obtained when the UE sets up the LIPA connection, and sends the determined APN ID to the H-GW by carrying the APN ID in the paging message.

If the H-GW sends the LHN ID to the MME when the UE sets up the LIPA connection, the MME may obtain the corresponding relation among the bearer ID, the APN ID and the LHN ID. And thus, when step 1304 is performed, the MME may obtain the APN ID and the LHN ID according to the bearer ID carried in the downlink data notification message, and sends the APN ID and the LHN ID to the H-GW through carrying the APN ID and the LHN ID in the paging message.

Step 1305, the H-GW determines, according to the stored corresponding relation between the APN ID and the HeNB ID, the HeNB ID corresponding to the APN ID carried in the paging message, and sends the paging message to the HeNB corresponding to the determined HeNB ID.

If the H-GW stores the corresponding relation among the APN ID, the HeNB ID and the LHN ID, and the paging message only carries the APN ID, the H-GW may determine, according to the stored corresponding relation, the corresponding relation the APN ID carried in the paging message and other identities, preferentially sends the paging message to the HeNB supporting the APN ID and the LHN ID in the corresponding relation. If the paging message carries the APN ID and the LHN ID, the H-GW may determine, according to the stored corresponding relation, to preferentially send the paging message to the HeNB supporting the APN ID and the LHN ID carried in the paging message.

As an extended example of the embodiment of the present invention, step 1305 may be replace with that the H-GW preferentially excludes HeNBs corresponding to other APNs, or preferentially excludes HeNBs corresponding to other APNs and LHN IDs when paging optimization is performed.

It should be described that, if this embodiment is applied to a scenario in which no H-GW is configured, the MME preferentially sends, according to the stored corresponding relation among the APN ID, the HeNB ID and the LHN ID (which is optional), the paging message to the HeNB corresponding to the APN ID and the LHN ID (which is optional) carried in the paging message. Or, the MME preferentially exclude HeNBs corresponding to other APN identities or preferentially excludes HeNBs corresponding to other APN identities and LHN identities when paging optimization is performed.

The present invention provides several modes for obtaining the APN ID by the H-GW.

The LGW may obtain, through pre-configuration or interaction with a Domain Name Server (DNS) server, the APN ID of an APN which the LGW can access. When the HeNB and the LGW are powered on respectively, the LGW may send the APN ID to the HeNB through an interface between the LGW and the HeNB, as shown in Figure 14a. It should be described that, for the network architecture shown in Figures 3d to 3f, since the H-GW and the LGW may be in the same physical entity, the H-GW may obtain APN information from the LGW through an internal interface.

When the S1 connection is set up between the HeNB and the H-GW, the APN ID of the APN which the HeNB can access is carried in the S1 setup request. There may be one or more APN identities because the HeNB may be connected with multiple LGWs. The S1 setup request may also carry the LHN ID, the HeNB ID, the CSG ID and the location information of the HeNB, which is not limited in the present invention. In this way, the H-GW may store the corresponding relation among the APN ID, the HeNB ID and the LHN ID through the S1 setup request. The LHN ID is optional, as shown in Figure 14b. Or, the HeNB sends the above information to the H-GW through an eNB configuration information update message, as shown in Figure 14c.

In a scenario in which no H-GW is configured, similar to the above procedure, the HeNB sends the above information to the MME through the S1 setup request and the eNB configuration information update message. The MEE may obtain the corresponding relation among the APN ID, the HeNB ID and the LHN ID, where the LHN ID is optional.

Thus, the sixth embodiment is competed.

The seventh embodiment

This embodiment provides an instance of paging success or paging failure, and particularly relates to an operation after the HeNB in any one of the above embodiments receives the paging message. Specifically, the HeNB sends the received paging message to the UE; if the UE generates a paging response, the UE returns a service request after receiving the paging message at the current HeNB; after receiving the service request, the MME determines whether the LHN ID and/or the LGW IP address carried in the service request is the same as the LHN ID and/or the LGW IP address carried in the paging message; if yes, the MME determines that paging is successful, and continues to perform the service request procedure for the UE; otherwise, the MME triggers a LIPA deactivation procedure.

Take the sixth embodiment as an example and refer to the flowchart shown in Figure 15.

Steps 1501 to 1505 are similar to steps 601a to 603a.

Step 1506, the HeNB sends the received paging message to the UE.

Step 1507, if the UE generates a paging response, a RRC setup procedure is performed between the UE and the HeNB.

Step 1508, the HeNB sends an initial UE message to the H-GW, wherein the initial UE message carries the LHN ID or the LGW IP address, and the H-GW forwards the initial UE message to the MME.

Of cause, if the method is applied to a scenario in which no H-GW is configured, the HeNB directly sends the initial UE message to the MME.

Step 1509, after receiving the initial UE message (also called the service request) sent by the UE, the MME determines whether the LHN ID or the LGW IP address carried in the service request is the same as the LHN ID or the LGW IP address carried in the paging message; if yes, paging is successful, and the MME continues to perform the service request procedure for the UE; otherwise, the MME triggers a LIPA deactivation procedure.

Thus, the seventh embodiment is completed.

As can be seen from the above seven embodiments, the functions of the MME are changed. Specifically, the MME needs to determine whether to use the method supporting LIPA paging optimization. The functions of the H-GW are also changed. Specifically, the H-GW performs paging optimization according to the paging message sent by the MME. The contexts of the MME and UE are changed. Specifically, the MME needs to store the LHN ID which is the LHN ID of the LHN currently accessed by the UE. A new byte may be added in the contexts of the MME and UE, to identify the LHN ID of the LHN currently accessed by the UE.

The foregoing is only preferred examples of the present invention and is not used to limit the protection scope of the present invention. Any modification, equivalent substitution and improvement without departing from the spirit and principle of the present invention are within the protection scope of the present invention.

Claims

A paging optimization method in a network including a Home evolved Node B Gateway (HeNB GW), comprising:

if Local IP Access (LIPA) paging optimization is configured in the network, transmitting, by a Mobile Management Entity (MME), to the HeNB GW a paging message including a HeNB identity (ID) corresponding to a LIPA bearer.
The method of claim 1, wherein the HeNB ID is determined by the MME, and includes a HeNB ID corresponding to a bearer ID included in a received downlink data notification message.
The method of claim 1, further comprising:

determining, by the HeNB GW, a HeNB corresponding to the HeNB ID among all HeNBs set up a connection with the HeNB GW, and transmitting the paging message including the HeNB ID to the determined HeNB.
A paging optimization method in a network including a Home evolved Node B Gateway (HeNB GW) is configured, comprising:

if Local IP Access (LIPA) paging optimization is configured in the network, transmitting, by a Mobile Management Entity (MME), a paging message to the HeNB GW,

wherein the paging message includes a parameter used for determining a HeNB corresponding to a LIPA bearer.
The method of claim 4, wherein the parameter includes a Local Gateway (LGW) IP address which is determined based on a bearer ID included in a received downlink data notification message, further comprising:

determining, by the HeNB GW, the HeNB corresponding to the LGW IP address, and transmitting the paging message to the determined HeNB,

wherein the HeNB GW stores a corresponding relation between the LGW IP address and the HeNB ID when the UE sets up the LIPA connection, and does not release the corresponding relation when being in an idle state; or the HeNB GW stores the corresponding relation between the LGW IP address and the HeNB ID when the UE sets up a S1 connection.
The method of claim 4, wherein the parameter includes a LHN (Local Home Network) ID which is determined by the MME according to a corresponding relation between the bearer ID and the LHN ID, the bearer ID included in the received downlink data notification message and location information of the UE,

further comprising:

determining, by the HeNB GW, a HeNB corresponding to the LHN ID included in the paging message, and transmitting the paging message to the determined HeNB, or excluding HeNBs corresponding to other LHN IDs except the LHN ID included in the paging message, and transmitting the paging message to a remained HeNB; or

excluding, by the HeNB GW, according to the LHN ID included in the paging message and the location information of the UE, LHN IDs of LHNs which the UE can not access, and determining a HeNB corresponding to a remained LHN ID, and transmitting the paging message to the determined HeNB.
The method of claim 4, wherein the parameter includes an APN (Access Point Name) ID which is determined by the MME based on the bearer ID included in the downlink data notification message,

further comprising:

determining, by the HeNB GW, a HeNB corresponding to the APN ID included in the paging message, and transmitting the paging message to the determined HeNB, or excluding HeNBs corresponding to other APN IDs except the APN ID included in the paging message, and determining that a remained HeNB is a HeNB receiving the paging message.
The method of claim 4, wherein the parameter includes at least one of an APN ID, a LHN ID and a LGW IP address determined by the MME,

further comprising:

determining, by the HeNB GW, a HeNB according to the HeNB ID and the at least one of the APN ID, the LHN ID and the LGW IP address, and transmitting the paging message to the determined HeNB, or excluding HeNBs corresponding to at least one of other APN IDs, LHN IDs and LGW IP addresses except the parameter included in the paging message, and determining that a remained HeNB is a HeNB receiving the paging message,

wherein the APN ID is obtained by the HeNB GW through following modes:

obtaining, by the HeNB, through interaction with a LGW, the APN ID which is pre-configured in the LGW or obtaining, by the LGW, the APN ID through interaction with a Domain Name Server (DNS) server;

obtaining, by the HeNB GW, the APN ID through setting up the S1 connection with the HeNB or obtaining, by the HeNB GW, the APN ID through an eNB configuration information update message sent by the HeNB.
A paging optimization method in a network, comprising:

if Local IP Access (LIPA) paging optimization is configured in the network, transmitting, by a Mobile Management Entity (MME), to a HeNB a paging message including a HeNB identity (ID) corresponding to a LIPA bearer.
The method of claim 9, wherein the HeNB ID is determined by the MME according to a step of:

obtaining, by the MME, a LHN (Local Home Network) ID corresponding to the bearer ID included in a received downlink data notification message;

determining a HeNB ID according to the obtained LHN ID, a corresponding relation between the LHN ID and the HeNB ID which is stored when a S1 connection is set up, current location information of a User Equipment (UE), or excluding HeNB IDs corresponding to other LHN IDs, and determining that a remained HeNB ID is a HeNB ID included in the paging message.
The method of claim 9, wherein the MME stores the corresponding relation between the bearer ID and the LHN ID when the UE sets up a LIPA connection;

or, the MME stores the corresponding relation between the bearer ID and the LHN ID through a following mode:

deducing and storing, by the MME, the corresponding relation between the bearer ID and the LHN ID according to a corresponding relation between the bearer ID and the HeNB ID which is stored when a UE sets up a LIPA connection, and a corresponding relation between the HeNB ID and the LHN ID which is stored when a S1 connection is set up.
The method of claim 9, wherein the HeNB ID is determined by the MME according to a step of:

determining, by the MME, the HeNB ID according to a bearer ID included in a received downlink data notification message, a corresponding relation between the bearer ID and an LGW IP address which is stored when a UE sets up a LIPA connection, and a corresponding relation between the LGW IP address and the HeNB ID which is stored when a S1 connection is set up, or excluding HeNB IDs corresponding other LGW IP addresses corresponding to the bearer ID, and determining that a remained HeNB ID is a HeNB ID included in the paging message; or

determining, by the MME, the HeNB ID according to a bearer ID included in a received downlink data notification message, a corresponding relation between the bearer ID and an APN ID which is stored when a UE sets up a LIPA connection, and a stored corresponding relation between the APN ID and the HeNB ID, or excluding HeNB IDs corresponding other APN IDs corresponding to the bearer ID, and determining that a remained HeNB ID is a HeNB ID carried in the paging message.
The method of claim 9, further comprising:

after receiving the paging message at a current HeNB, transmitting, by the UE, a service request;

after receiving the service request, determining, by the MME, whether an LHN ID and/or an LGW IP address included in the service request is the same as an LHN ID and/or an LGW IP address included in the paging message; if the LHN ID and/or the LGW IP address included in the service request is the same as the LHN ID and/or the LGW IP address included in the paging message, determining that paging is successful and continuing the service request procedure for the UE; if the LHN ID and/or the LGW IP address included in the service request is not the same as the LHN ID and/or the LGW IP address included in the paging message, triggering a LIPA deactivation procedure.
A paging optimization apparatus in a network, comprising a controller adapted to perform the steps comprised in one of a method described in claims 1 to 3.
A paging optimization apparatus in a network, comprising a controller adapted to perform the steps comprised in one of a method described in claims 4 to 8.
A paging optimization apparatus in a network, comprising a controller adapted to perform the steps comprised in one of a method described in claims 9 to 13.