[go: up one dir, main page]

WO2013002566A2 - Procédé d'optimisation d'appel - Google Patents

Procédé d'optimisation d'appel Download PDF

Info

Publication number
WO2013002566A2
WO2013002566A2 PCT/KR2012/005109 KR2012005109W WO2013002566A2 WO 2013002566 A2 WO2013002566 A2 WO 2013002566A2 KR 2012005109 W KR2012005109 W KR 2012005109W WO 2013002566 A2 WO2013002566 A2 WO 2013002566A2
Authority
WO
WIPO (PCT)
Prior art keywords
henb
lhn
lgw
paging message
mme
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/KR2012/005109
Other languages
English (en)
Other versions
WO2013002566A3 (fr
Inventor
Huarui Liang
Hong Wang
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Samsung Electronics Co Ltd
Original Assignee
Samsung Electronics Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Samsung Electronics Co Ltd filed Critical Samsung Electronics Co Ltd
Publication of WO2013002566A2 publication Critical patent/WO2013002566A2/fr
Publication of WO2013002566A3 publication Critical patent/WO2013002566A3/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W68/00—User notification, e.g. alerting and paging, for incoming communication, change of service or the like
    • H04W68/02—Arrangements for increasing efficiency of notification or paging channel

Definitions

  • the present invention relates to radio communication technologies, and more particularly to a paging optimization method.
  • FIG. 1 is a schematic diagram illustrating the structure of a conventional System Architecture Evolution (SAE).
  • SAE System Architecture Evolution
  • UE User Equipment
  • E-UTRAN Evolved Universal Terrestrial Radio Access Network
  • a Mobile Management Entity (MME) 103 is adapted to manage mobility contexts, session contexts and security information of the UE.
  • MME Mobile Management Entity
  • SGW Serving Gateway
  • 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.
  • 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.
  • CSG Closed Subscriber Group
  • 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.
  • LIPA Local IP Access
  • HNB Home Node B
  • 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.
  • 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).
  • LGW Local Gateway
  • GGSN Gateway GPRS Supporting Node
  • FIG. 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).
  • ID bearer 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.
  • 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.
  • an ECGI which corresponds to a HeNB ID
  • Step 205 the HeNB sends the paging message to the UE.
  • 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.
  • 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.
  • LIPA supports mobility, that is to say, when the UE moves in a local network, the continuity of UE services should be guaranteed.
  • 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.
  • 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.
  • 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.
  • 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.
  • a paging optimization method in a network including a HeNB GW includes:
  • LIPA paging optimization 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:
  • the paging message includes a parameter used for determining a HeNB corresponding to a LIPA bearer.
  • a paging optimization method in a network includes:
  • LIPA paging optimization 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.
  • the paging optimization performed for LIPA can be realized.
  • 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.
  • 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.
  • 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 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.
  • ID HeNB identity
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the MME directly determines to send the paging message to which HeNB.
  • 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 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.
  • 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.
  • the HeNB GW may determine the HeNB according to the parameter carried in the paging message.
  • 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.
  • 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.
  • 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.
  • 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.
  • RRC Radio Resource Control
  • 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.
  • the initial UE message carries such information as the LGW IP address, the HeNB ID (ECGI), the CSG ID and TAI.
  • the H-GW 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.
  • ECGI HeNB ID
  • 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.
  • 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.
  • step 505b the MME stores the corresponding relation between the LGW IP address and the bearer ID.
  • 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.
  • the SGSN can find the H-GW ID corresponding to the bearer ID.
  • 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 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.
  • ACK downlink data notification
  • 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.
  • 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.
  • Step 601b the HeNB sends a S1 setup request to the MME, where the S1 setup request contains a Local Home Network (LHN) ID.
  • 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.
  • 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.
  • FIG. 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.
  • 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.
  • This embodiment is similar to the first and second embodiments, and is applied to the scenario in which the HeNB GW is configured.
  • FIG 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.
  • 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.
  • 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.
  • 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.
  • the procedure of setting up the S1 connection between the HeNB and the H-GW after the HeNB is powered on is completed.
  • 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.
  • 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.
  • 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.
  • 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).
  • 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.
  • 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.
  • 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.
  • the LIPA paging may be further optimized, referring to 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.
  • FIG 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the S1 setup request may carry one or more LGW IP addresses.
  • the LHN ID is optional.
  • 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.
  • 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.
  • FIG. 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • DNS Domain Name Server
  • 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.
  • the APN ID of the APN which the HeNB can access is carried in the S1 setup request.
  • 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.
  • 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.
  • the HeNB sends the above information to the H-GW through an eNB configuration information update message, as shown in Figure 14c.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the initial UE message also called the service request
  • 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.
  • 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.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

La présente invention concerne des procédés d'optimisation d'appel. L'un des procédés est appliqué à un réseau comprenant une GW HeNB et consiste à : si une optimisation d'appel LIPA est configurée dans le réseau, transmettre, par une MME, à la GW HeNB un message d'appel comprenant un ID d'HeNB correspondant à un support LIPA. Selon la présente invention, une optimisation d'appel LIPA peut être réalisée dans le scénario dans lequel la GW HeNB est configurée ou dans une architecture de réseau prise en charge par R-11.
PCT/KR2012/005109 2011-06-29 2012-06-28 Procédé d'optimisation d'appel Ceased WO2013002566A2 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201110189335.9 2011-06-29
CN201110189335.9A CN102858013B (zh) 2011-06-29 2011-06-29 寻呼优化的方法

Publications (2)

Publication Number Publication Date
WO2013002566A2 true WO2013002566A2 (fr) 2013-01-03
WO2013002566A3 WO2013002566A3 (fr) 2013-03-28

Family

ID=47404114

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2012/005109 Ceased WO2013002566A2 (fr) 2011-06-29 2012-06-28 Procédé d'optimisation d'appel

Country Status (2)

Country Link
CN (1) CN102858013B (fr)
WO (1) WO2013002566A2 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11006385B2 (en) 2013-02-27 2021-05-11 Huawei Technologies Co., Ltd. Paging optimization method, apparatus, and system

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104159300B (zh) * 2014-07-25 2018-07-06 京信通信系统（中国）有限公司 一种寻呼方法及设备
CN105517105A (zh) * 2014-09-23 2016-04-20 中兴通讯股份有限公司 网络的接入方法及装置
CN105681267B (zh) * 2014-11-21 2019-11-29 南京中兴新软件有限责任公司 数据传送方法及装置
WO2018053691A1 (fr) * 2016-09-20 2018-03-29 Nokia Technologies Oy Procédé et appareil de rétablissement d'un service dans un système de communication sans fil

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10893556B2 (en) * 2009-04-30 2021-01-12 Samsung Electronics Co., Ltd Method and apparatus for supporting local IP access in a femto cell of a wireless communication system
CN101938736A (zh) * 2009-06-30 2011-01-05 中兴通讯股份有限公司 家庭基站本地网际协议网络访问能力的上报方法及系统
KR101091300B1 (ko) * 2009-08-21 2011-12-07 엘지전자 주식회사 이동통신 네트워크 내에서 제어 평면（Ｃｏｎｔｒｏｌ　Ｐｌａｎｅ） 을 담당하는 서버 및 ＬＩＰＡ（Ｌｏｃａｌ　ＩＰ　Ａｃｃｅｓｓ） 서비스를 제어하는 방법
EP2471226B1 (fr) * 2009-11-02 2018-09-19 LG Electronics Inc. Identification de corrélation pour accès ip local
CN102056347B (zh) * 2009-11-09 2014-07-09 华为终端有限公司 一种转移核心网ip业务的方法、设备及系统
CN102158961A (zh) * 2010-02-11 2011-08-17 中兴通讯股份有限公司 一种本地访问寻呼优化方法及装置

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11006385B2 (en) 2013-02-27 2021-05-11 Huawei Technologies Co., Ltd. Paging optimization method, apparatus, and system

Also Published As

Publication number Publication date
WO2013002566A3 (fr) 2013-03-28
CN102858013A (zh) 2013-01-02
CN102858013B (zh) 2017-09-01

Similar Documents

Publication Publication Date Title
WO2011142567A2 (fr) Procédé de transfert intercellulaire prenant en charge une mobilité de terminal
WO2010021475A2 (fr) Procédé et appareil pour effectuer une commutation dans un système de communication mobile
WO2014104705A1 (fr) Procédé et système pour assister une reprise rapide d'un équipement utilisateur
WO2014148859A1 (fr) Méthode et équipement utilisateur permettant de mettre en œuvre des communications dispositif à dispositif entre ue
WO2014046431A2 (fr) Procédé pour établir correctement un service d'accès ip local
WO2011021875A2 (fr) Serveur pour plan de commande au niveau d'un réseau de communication mobile et procédé de commande de service d'accès ip local
WO2010090451A2 (fr) Procédé et appareil de transfert
WO2014003455A1 (fr) Procédé de détermination de contrôle d'accès
WO2010126326A2 (fr) Procédé et appareil destinés à assister un accès à un protocole internet (ip) local dans une femtocellule d'un système de communication sans fil
WO2013005992A2 (fr) Procédé permettant d'éviter l'échec du transfert intercellulaire
WO2010128773A2 (fr) Serveur pour plan de commande destiné à un réseau de communication mobile et procédé de commande d'établissement de connexion apparenté
WO2015037947A1 (fr) Procédé et dispositif pour paramétrer des supports de dérivation locaux
WO2015115814A1 (fr) Procédé et appareil de gestion efficace de session, garantissant la mobilité d'un terminal
WO2015012631A1 (fr) Procédé permettant de résoudre des problèmes de sécurité au moyen de paires nh et ncc dans un système de communication mobile
WO2011056046A2 (fr) Procédé et système de support de continuité d'appel radio vidéo unique pendant un transfert
WO2013129832A1 (fr) Procédé pour établir un rapport d'informations d'échec de liaison radio
WO2018174383A1 (fr) Procédé de gestion de session et nœud smf
WO2011019159A2 (fr) Procédé et système d'accès distant
WO2013133663A1 (fr) Procédé de commande de service dans un système de radiocommunication
WO2013051845A2 (fr) Procédé et appareil pour commander l'accès d'un équipement d'utilisateur dans un système de communication mobile
WO2015065062A1 (fr) Procédé et système de transfert intercellulaire
WO2015126160A1 (fr) Appareil et procédé d'amélioration de la qualité de service de visiotéléphonie
WO2012138110A2 (fr) Procédé pour garantir l'établissement d'accès ip local correctement
WO2013002566A2 (fr) Procédé d'optimisation d'appel
WO2021235889A1 (fr) Procédés de gestion d'interfonctionnement de session pdu sur eps et 5 gs pour nb-iot

Legal Events

Date Code Title Description
NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 12804949

Country of ref document: EP

Kind code of ref document: A2