WO2018120223A1 - 一种通信方法、移动性管理实体、基站及系统 - Google Patents

一种通信方法、移动性管理实体、基站及系统 Download PDF

Info

Publication number
WO2018120223A1
WO2018120223A1 PCT/CN2016/113956 CN2016113956W WO2018120223A1 WO 2018120223 A1 WO2018120223 A1 WO 2018120223A1 CN 2016113956 W CN2016113956 W CN 2016113956W WO 2018120223 A1 WO2018120223 A1 WO 2018120223A1
Authority
WO
WIPO (PCT)
Prior art keywords
base station
path
mobility management
management entity
serving gateway
Prior art date
Application number
PCT/CN2016/113956
Other languages
English (en)
French (fr)
Inventor
钟瑜
戚彩霞
刘雁
Original Assignee
华为技术有限公司
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 华为技术有限公司 filed Critical 华为技术有限公司
Priority to PCT/CN2016/113956 priority Critical patent/WO2018120223A1/zh
Publication of WO2018120223A1 publication Critical patent/WO2018120223A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/24—Connectivity information management, e.g. connectivity discovery or connectivity update

Definitions

  • the present invention relates to the field of wireless communication technologies, and in particular, to a communication method, a mobility management entity, a base station, and a system.
  • LTE long term evolution
  • SAE system architecture evolution
  • EPC Evolved Packet Core
  • the EPC implements the control plane function through the mobility management entity (English: mobility management entity, abbreviation: MME), and the user equipment (English: user equipment, abbreviation: UE) is used by the service gateway (English: serving gateway, abbreviation: SGW)
  • MME mobility management entity
  • SGW serving gateway
  • PGW packet data network gateway
  • the MME In the process of UE attachment, the MME needs to first select an appropriate SGW for the UE. In the prior art, the MME selects the SGW according to a tracking area list (English: tracking area list, abbreviation: TA list). However, since the user plane data of the UE is directly connected to the SGW by the evolved base station (English: evolved NodeB; abbreviation: eNB), it is transmitted through the S1-U path of the MME. When the S1-U path between the SGW and the eNodeB fails, the MME cannot detect the link failure, and may still select the SGW on the faulty path, so that the UE cannot perform services normally even if the UE repeatedly goes online.
  • TA list tracking area list
  • eNB evolved NodeB
  • the embodiments of the present invention provide a communication method, a mobility management entity, a base station, and a system, which can ensure normal operation of the UE service and improve the user experience of the UE when the link is faulty.
  • the present invention provides a communication method, where the method includes:
  • the mobility management entity acquires indication information that is sent by the base station to indicate that the first path between the base station and the first serving gateway is in a fault state; the mobility management entity acquires a service gateway list corresponding to the base station, where the service gateway list includes a second connected to the base station a serving gateway, wherein the second path between the second serving gateway and the base station is in a normal state; the mobility management entity acquires the identification information of the user equipment on the first path or the identification information of the user equipment to be attached on the base station; The sex management entity selects the second service gateway to provide services for the user equipment according to the service gateway list.
  • the indication information includes: identification information of the base station and identification information of the first serving gateway, or identification information of the base station, identification information of the first serving gateway, and path status information.
  • the mobility management entity acquires the identifier information of the user equipment on the first path, including: the mobility management entity searches for the local context according to the identifier information of the base station and the identifier information of the first serving gateway, and obtains the first The ID of the user device on the path.
  • the mobility management entity acquires the identifier information of the UE to be attached to the base station, where the mobility management entity receives the attach request sent by the base station, and the attach request carries the identifier information of the base station and the user equipment to be attached. Identification information.
  • the mobility management entity acquires the indication information sent by the base station, where the mobility management entity receives the attachment request sent by the base station, and the attach request carries the indication information; or the mobility management entity receives the new information sent by the base station.
  • the signaling message carries the indication information in the newly added signaling message, where the newly added signaling message may be a path failure notification message.
  • the mobility management entity acquires the service gateway list corresponding to the base station, including: the mobility management entity acquires the service gateway list corresponding to the base station from the domain name server DNS; or the mobility management entity obtains the local configuration information.
  • the method further includes: the mobility management entity adds the first path to the path blacklist according to the indication information, and the path blacklist includes the service in the path in the fault state. Identification information of the service gateway and identification information of the base station.
  • the mobility management entity selects the second service gateway to provide the user equipment according to the service gateway list, including: the mobility management entity excludes the service gateway in the path blacklist, and selects from the service gateway list.
  • a second serving gateway connected to the base station.
  • the embodiment of the present invention provides another communication method, where the method includes: the base station acquires a service gateway list, where the service gateway list includes identifier information of the serving gateway connected to the base station; and the base station detects the service gateway in the base station and the service gateway list. If the base station determines that the first path between the first serving gateway and the base station in the serving gateway list fails, the base station sends indication information indicating that the first path is in a fault state to the mobility management entity.
  • the indication information includes: identification information of the base station and identification information of the first serving gateway, or identification information of the base station, identification information of the first serving gateway, and path status information.
  • the base station obtains the service gateway list, including: the base station receives the identifier information of the serving gateway connected to the base station and sent by the mobility management entity, and the base station generates a service gateway list; or the base station obtains the locally configured service gateway list.
  • the receiving, by the base station, the identifier information of the serving gateway that is connected to the base station and sent by the mobility management entity includes: receiving, by the base station, an initial context setup request message sent by the mobility management entity, where the initial context setup request message is connected to the base station Identification information of the service gateway.
  • the base station sends the indication information indicating that the first path is in a fault state to the mobility management entity, including: the base station receives the attach request sent by the user equipment, and the base station sends an attach request to the mobility management entity, and the attach request carries Instructing the information; or, the base station sends a new signaling message to the mobility management entity, where the newly added signaling message carries the indication information, where the newly added signaling message may be a path failure notification message.
  • an embodiment of the present invention provides a mobility management entity having a function of implementing the behavior of the mobility management entity in the foregoing method.
  • the function can Through hardware implementation, the corresponding software implementation can also be performed by hardware.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • the structure of the mobility management entity includes a controller/processor and a transmitter/receiver configured to support the mobility management entity to perform the corresponding functions in the above methods.
  • the transmitter/receiver is configured to support communication between the mobility management entity and the eNodeB or SGW, and to transmit information or instructions related to the foregoing method to the eNodeB or the SGW.
  • the mobility management entity may also include a memory for coupling with a controller/processor that holds program instructions and data necessary for the mobility management entity.
  • the structure of the mobility management entity includes a processing module and a communication module, the processing module being configured to support the mobility management entity to perform corresponding functions in the above methods.
  • the communication module is configured to support communication between the mobility management entity and the eNodeB or the SGW, and send and receive information or instructions related to the foregoing method to the eNodeB or the SGW.
  • the mobility management entity may also include a storage module for coupling with the processing module that stores program instructions and data necessary for the mobility management entity.
  • an embodiment of the present invention provides a base station, which has a function of realizing the behavior of a base station in the actual method.
  • the functions may be implemented by hardware or by corresponding software implemented by hardware.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • the structure of the base station includes a controller/processor and a transmitter/receiver configured to support the base station to perform the corresponding functions in the above methods.
  • the transmitter/receiver is configured to support communication between the base station and the MME, the SGW or the UE, and send and receive information or instructions related to the foregoing method to the MME, the SGW or the UE.
  • the base station can also include a memory for coupling with a controller/processor that stores the necessary program instructions and data for the base station.
  • the structure of the base station includes a processing module and a communication module,
  • the processing module is configured to support the base station to perform the corresponding functions in the above methods.
  • the communication module is configured to support communication between the base station and the MME, the SGW, or the UE, and send and receive information or instructions related to the foregoing method to the MME, the SGW, or the UE.
  • the base station may further include a storage module for coupling with the processing module, which stores necessary program instructions and data of the base station.
  • an embodiment of the present invention provides a communication system, including the mobility management entity and the base station in the foregoing aspect.
  • an embodiment of the present invention provides a computer storage medium for storing computer software instructions for use by the mobility management entity, including a program designed to perform the above aspects.
  • an embodiment of the present invention provides a computer storage medium for storing computer software instructions for use by the base station, including a program designed to perform the above aspects.
  • embodiments of the present invention also provide a computer program product comprising instructions that, when run on a computer, cause the computer to perform the methods described in the various aspects above.
  • the solution provided by the present invention can select a suitable SGW for the UE to ensure that the data packets of the UE can be forwarded or routed normally, and the service can be performed normally, and the user experience of the UE is improved.
  • 1 is a schematic diagram of a network architecture of an EPC defined in 3GPP;
  • FIG. 1A is a schematic diagram of a user attachment process
  • FIG. 2 is a schematic diagram of a communication method according to an embodiment of the present invention.
  • 3A and 3B are respectively a signaling interaction diagram of a communication method according to an embodiment of the present invention.
  • FIG. 4 is a schematic structural diagram of a communication device (eg, an MME) according to an embodiment of the present invention.
  • a communication device eg, an MME
  • FIG. 5 is a schematic structural diagram of a communication device (eg, an eNodeB) according to an embodiment of the present invention
  • FIG. 6 is another schematic structural diagram of a communication device (eg, MME) according to an embodiment of the present invention.
  • FIG. 7 is another schematic structural diagram of a communication device (eg, an eNodeB) according to an embodiment of the present invention.
  • a communication device eg, an eNodeB
  • FIG 1 shows the network architecture diagram of the EPC defined in the 3rd generation partnership project (English: 3rd generation partnership project, abbreviation: 3GPP).
  • the EPC includes subcomponents such as an MME, an SGW, a PGW, and a home subscriber server (English: home subscriber server, abbreviation: HSS).
  • the MME is a control node in the LTE access network, and is connected to a base station in an evolved universal terrestrial radio access network (E-UTRAN) through an S1-MME path.
  • the MME is responsible for tracking and paging control of the UE in idle mode. In the process of tracking and paging control of the UE, the MME needs to select different SGWs for the UE to complete the handover of the core network node in the LTE system.
  • the MME exchanges information with the HSS through the S6a path.
  • the function of the HSS is a central database containing information related to the UE and information related to the subscription.
  • the HSS features include: mobility management, support for call and session establishment, user authentication and access authorization.
  • the base station is connected to the SGW through an S1-U path.
  • the SGW is responsible for routing and forwarding of data packets of the UE, and is also responsible for the exchange of user plane data when the UE moves between eNodeBs or between LTE and other 3GPP technologies.
  • the PGW is connected to the SGW through the s5 path to implement interface transmission between the UE and the external service PDN connection point.
  • One UE can access multiple service PDNs through multiple PGWs at the same time.
  • the MME selects the SGW according to the tracking area list.
  • the evolved base station English: evolved NodeB; abbreviated: eNodeB
  • the MME may still select the SGW on the faulty path, causing the UE to fail to perform services.
  • the MME can sense the state of the data plane path between the SGW and the eNodeB, and eliminate the SGW of the link failure, and select an SGW with a normal data plane to ensure that the UE can perform services normally and improve the UE. user experience.
  • FIG. 2 is a schematic diagram of a communication method in accordance with one embodiment of the present invention.
  • the network element involved in the communication method includes an MME and an eNodeB. as shown in picture 2:
  • Step S202 the eNodeB acquires a list of SGWs connected to the eNodeB.
  • the SGW list includes the identifier information of the SGW connected to the eNodeB, where the identifier information of the SGW is information for identifying the SGW, and specifically, may include an SGW network protocol (English: internet protocol, abbreviation: IP) address, SGW One or more of the number or SGW's identification (English: identification, abbreviation: ID) or other identifying information that identifies the SGW.
  • SGW network protocol English: internet protocol, abbreviation: IP
  • SGW One or more of the number or SGW's identification (English: identification, abbreviation: ID) or other identifying information that identifies the SGW.
  • the specific acquisition process can be achieved in the following ways:
  • the network maintenance personnel manually configure the SGW list on the eNodeB;
  • the eNodeB obtains the identification information of the SGW to which it is connected through the attach procedure, and generates an SGW list. For example, in the process of UE attachment (refer to FIG. 1A), the MME selects an SGW for the UE, and obtains the SGW identification information (for example, the IP address of the SGW) through a DNS query, and the MME notifies the eNodeB in the initial context setup request message.
  • the identifier information of the SGW after receiving the initial context setup request message, the eNodeB obtains the identifier information of the SGW from the initial context setup request message.
  • the eNodeB can learn which SGWs are connected (eg, SGW1, SGW2, SGW3, etc.), and maintain the SGW list by recording the identification information of the SGWs connected thereto.
  • the SGW eg, SGW1, SGW2, or SGW3 maintained in the SGW list does not depend on whether the current eNodeB and the SGW have a bearer. Also That is to say, regardless of whether the bearer currently exists, if the MME notifies the eNodeB of the identification information of the SGW connected thereto in the previous process, the identifier information of the SGW is recorded in the SGW list on the eNodeB.
  • Step S204 The eNodeB detects each SGW in the SGW list to learn the path status between the eNodeB and each SGW.
  • the eNodeB can use echo detection to learn the path status between the eNodeB and the SGW. For example, the eNodeB sends an echo probe request to the SGW1 to determine a path state between the eNodeB and the SGW1 according to whether an echo probe response is received within a predetermined time. If the echo probe response sent by the SGW1 is received at the predetermined time, it is determined that the path state between the eNodeB and the SGW1 is normal. If the echo detection response sent by the SGW1 is not received within a predetermined time, the path state between the eNodeB and the SGW1 may be directly determined to be a fault.
  • the eNodeB may send the probe request again according to the predetermined time interval, and if the echo detection response sent by the SGW1 is not received after the preset number of probe requests are sent, It is determined that the path state between the eNodeB and the SGW1 is a failure.
  • the predetermined time interval and the preset number of transmissions of the probe request may be determined according to actual conditions. For example, if no probe response is received, the eNodeB may send a probe request every 3 seconds, and if there is no response for 5 times, the path fault is confirmed.
  • the eNodeB periodically detects the SGW in the SGW list. For example, every 1 minute, the eNodeB probes the SGW in the SGW list once. In this way, the eNodeB can perceive the state of the path between the eNodeB and the SGW in time.
  • the eNodeB after detecting, by the eNodeB, the SGW in the SGW list, the eNodeB records the detected path status in the SGW list. For example, if the detected path is in a normal state, it is recorded as normal; if the detected path is in an abnormal state, it is recorded as a failure. Alternatively, the eNodeB can also mark only paths that are in an abnormal state.
  • Step S206 if the eNodeB determines the first SGW in the serving gateway list (eg, SGW1) The first path between the eNodeB and the eNodeB fails, and the eNodeB sends indication information indicating that the first path is in a fault state to the MME.
  • the serving gateway list eg, SGW1
  • the indication information can be in two forms:
  • the first form the identification information of the eNodeB and the identification information of the SGW1;
  • the second form identification information of the eNodeB, identification information of the SGW1, and path status information.
  • the identifier information of the eNodeB is used to identify the eNodeB, and specifically, may include an eNodeB network protocol (English: internet protocol, abbreviation: IP) address, an eNodeB number, or an eNodeB identifier (in English: identification, abbreviation: ID).
  • IP internet protocol
  • ID eNodeB identifier
  • the identification information of the SGW can refer to the description in step S202.
  • the path state information may refer to normal or down in step S204.
  • the eNodeB may send indication information indicating that the first path is in a fault state to the MME by:
  • the first way transmit the indication information on the message of the existing protocol definition as much as possible. For example, when there is a UE attachment, the eNodeB receives the attach request sent by the UE, and the eNodeB sends an attach request to the MME, and the attach request carries the indication information. Of course, other existing messages between the eNodeB and the MME may also be used for transmission.
  • the first mode is to add a signaling message type between the eNodeB and the MME, and the message is used by the eNodeB to notify the path status between the MME eNodeB and the SGW in real time.
  • a signaling message type between the eNodeB and the MME
  • the message is used by the eNodeB to notify the path status between the MME eNodeB and the SGW in real time.
  • path failure notification message of course, other new signaling messages can also be used.
  • the MME obtains the indication information sent by the eNodeB.
  • Step S208 the MME acquires an SGW list connected to the eNodeB, where the SGW list includes at least the SGW2 connected to the eNodeB.
  • the second path between the SGW2 and the eNodeB is in a normal state.
  • the SGW list may include a plurality of SGWs connected to the eNodeB.
  • SGW2 is represented as a representative (referred to generally as an SGW with a normal eNodeB path).
  • the MME can obtain the SGW list connected to the eNodeB in the following manners:
  • the first mode the MME obtains the SGW list corresponding to the eNodeB from the domain name server DNS. For example, the MME queries the domain name server (English: domain name server; abbreviation: DNS) to obtain an SGW list connected to the eNodeB according to the identifier information of the eNodeB.
  • DNS domain name server
  • the second mode the MME obtains the SGW list corresponding to the eNodeB from the local configuration information. For example, the MME obtains the SGW list connected to the eNodeB from the local configuration information query according to the identifier information of the eNodeB.
  • the third mode the MME obtains the SGW list corresponding to the eNodeB from the CACHE cache. Specifically, the MME queries, according to the identifier information of the eNodeB, the SGW list that is connected to the eNodeB from the cache.
  • Step S210 the MME acquires the identifier information of the UE that is in the first path or the identifier information of the UE to be attached to the eNodeB.
  • the process of the MME acquiring the identifier information of the UE in the first path may be: searching the local context according to the identifier information of the eNodeB and the identifier information of the SGW1, and acquiring the identifier of the UE on the first path.
  • the process of the MME acquiring the identifier information of the UE to be attached to the eNodeB may be specifically: when the UE sends an attach request to the eNodeB, the eNodeB sends the attach request to the MME, where the attach request carries the eNodeB identifier information and the identifier information of the UE, and the MME receives
  • the UE is the UE to be attached to the eNodeB according to the eNodeB identification information and the identifier information of the UE.
  • step 208 There is no order between step 208 and step 210, and it can also be performed simultaneously.
  • Step S212 the MME selects, according to the SGW list, the SGW2 that is in a normal state with the eNodeB to provide services for the UE.
  • the MME may add the first path to the path blacklist by obtaining the indication information that the first path is in the fault state by the step S206.
  • the MME selects the SGW for the UE, the MME According to the SGW list of the eNodeB and the path blacklist, the path fault SGW1 is excluded from the eNodeB, and the SGW2 in the SGW list and the eNodeB is selected to provide services for the UE.
  • the eNodeB can obtain the SGW list of the SGW connected to the eNodeB, and obtain the path status between the eNodeB and each SGW by detecting.
  • the eNodeB returns a message carrying the indication information indicating that the path status between the eNodeB and the SGW is faulty to the MME.
  • the MME can sense the path status between the eNodeB and the SGW, and select the SGW2 with the normal path status from the SGW list.
  • the MME can exclude the SGW of the path state fault when selecting the SGW for the UE, and select an appropriate UE for the UE.
  • the SGW ensures that the data packets of the UE can be forwarded or routed normally, and the service can be performed normally to improve the user experience of the UE.
  • FIG. 3A is a signaling interaction diagram of a communication method according to an embodiment of the present invention: if the eNodeB determines that the first path between the SGW1 and the eNodeB in the serving gateway list fails, the eNodeB passes the MME when receiving the attach message of the UE.
  • the sending attachment message carries indication information indicating that the first path is in a fault state. This embodiment uses less changes in the flow because the current attachment procedure is used to transmit the indication information.
  • the network elements involved in the signaling interaction in FIG. 3A include: eNodeB, MME, SGW1, and SGW2. In FIG.
  • the SGW1 is taken as an example for detailed description, that is, the execution of the SGW2 is similar to that of the SGW1, and is not described here for brevity.
  • the existing message carries the path state between the eNodeB and the SGW by extending the existing message.
  • the method includes:
  • Step S302 the eNodeB acquires an SGW list of the SGW connected to the eNodeB.
  • Step S304 the eNodeB detects the SGW in the SGW list to learn the eNodeB.
  • the status of the path with the SGW and the path status is recorded in the SGW list.
  • Steps S302 and S304 can refer to the descriptions of steps S202 and S204 in FIG. 2, respectively, and details are not described herein again.
  • Step S306 the eNodeB receives an attach request from the UE.
  • Step S308 the eNodeB sends an attach message of the UE to the MME, and notifies the path state fault between the MME eNodeB and the SGW1 by using an attach message.
  • the user attach message carries the identifier information of the eNodeB, the identifier information of the SGW1, and the indication information indicating that the path status between the eNodeB and the SGW1 is faulty.
  • the indication information is used to indicate that the first path state between the eNodeB and the SGW1 is a failure.
  • the eNodeB may notify the MME to refresh the information on the MME by sending all the currently maintained SGW lists (including the normal state and the fault state) or the part (the fault state part) to the MME, instead of just sending the indication.
  • the first path status between the eNodeB and the SGW1 is indication of a fault.
  • Step S310 the MME adds the path in the fault state (such as the first path between the eNodeB and the SGW1) to the path blacklist according to the received information.
  • the MME maintains a path blacklist based on the received response message.
  • the path blacklist includes at least an IP address of the eNodeB whose path is in a fault state and an IP address of the corresponding SGW.
  • the MME maintains a path blacklist by maintaining path state information.
  • the path state information includes at least an IP address of the eNodeB, an IP address of the SGW, and a state of a path connecting the eNodeB and the SGW.
  • the state of the path connecting the eNodeB and the SGW may be normal or down.
  • the MME may add the path in the fault state (such as the path between the eNodeB and the SGW1) to the path blacklist by setting the state of the path between the eNodeB and the SGW1 to a fault. That is to say, the path whose path status is set to down is the blacklist of the path.
  • the path status information is stored in the MME in the form of a list, as shown in Table 1:
  • the path status between the eNodeB with the IP address A and the SGW with the IP address C is Normal, which means that the path status is normal; the eNodeB with the IP address A and the SGW with the IP address D
  • the path status is down, that is, the path status is faulty; the path status between the eNodeB with the IP address B and the SGW with the IP address E is Normal; the eNodeB with the IP address B and the SGW with the IP address F
  • the path status is down.
  • the path in the fault state belongs to the path blacklist.
  • the path between the eNodeB with IP address A and the SGW with IP address D in Table 1, and the path between the eNodeB with IP address B and the SGW with IP address F are both faults. Status, so it belongs to the path blacklist.
  • the MME parses the IP address of the eNodeB carried in the user attach message and the IP address of the SGW1.
  • the MME may only record the identifier information of the eNodeB and the IP address of the SGW on the path in the down state to maintain the path blacklist.
  • the MME excludes the SGW1 indicated in the path blacklist, and selects a second SGW (for example, SGW2) whose path state is normal for the user equipment UE on the first path or the UE to be attached to the eNodeB.
  • a second SGW for example, SGW2
  • the MME obtains a list of SGWs to be selected from a domain name server (English: domain name server; DNS) or local configuration information or a cache, and according to various factors. Select SGW.
  • the MME excludes the SGW of the path failure between the SGW and the eNodeB, and selects from the SGWs with other paths normal.
  • the MME that the MME obtains from the DNS query includes at least SGW2. It is assumed that at time t1, the first path between SGW1 and the eNodeB fails, and the second path between SGW2 and the eNodeB remains normal.
  • the eNodeB sends a user attach message carrying indication information indicating that the first path state between the eNodeB and the SGW1 is faulty to the MME.
  • the MME adds the first path to the path blacklist, and then excludes the SGW indicated in the path blacklist (such as SGW1 and/or other SGWs with path faults), and selects the path status for the UE from the SGW list. Normal SGW2.
  • the MME selects an SGW for the UE, and may specifically include S312a or S312b according to different states of the UE. If the UE is the UE to be attached, step S312a is performed; if the UE is an existing UE in the first path of the fault state, step S312b is performed. The details of some steps are also referred to the description in step 210.
  • Step S312 If the MME receives the UE attach message sent by the eNodeB (the UE here, including the UE in step 306, and other UEs that initiate the attach message), the MME selects the second SGW (for example, SGW2) for the UE to be attached. A create session request message is sent to the second SGW.
  • SGW2 for example, SGW2
  • Step S312b The MME searches for the local context according to the identifier information of the eNodeB and the identifier information of the SGW1 to determine that the UE is the UE on the first path. Thereafter, the MME switches the UE to the second SGW (eg, SGW2) according to the indication information. How the MME switches the SGW for the UE is an existing technology, and details are not described herein again.
  • the eNodeB can obtain the SGW list of the SGW connected to the eNodeB by means of manual configuration or autonomous learning, and obtain the path status between the eNodeB and each SGW by detecting.
  • the eNodeB sends a second message to the MME indicating that the path status between the eNodeB and the SGW is faulty.
  • the MME can be perceived after receiving the second message.
  • the path state between the eNodeB and the SGW and accordingly selects the SGW2 whose path state is normal.
  • the MME can exclude the SGW of the path state fault when selecting the SGW for the UE, and select an appropriate UE for the UE.
  • the SGW ensures that the data packets of the UE can be forwarded or routed normally, and the service can be performed normally to improve the user experience of the UE.
  • FIG. 3B is a signaling interaction diagram of a communication method according to another embodiment of the present invention.
  • a signaling interaction diagram of a communication method according to an embodiment of the present invention : if the eNodeB determines SGW1 in the service gateway list and The first path between the eNodeBs is faulty, and the eNodeB sends a path path failure notification message to the MME, and carries indication information indicating that the first path is in a fault state.
  • the implementation manner can notify the status of the MME path in real time.
  • the network elements involved in the signaling interaction in FIG. 3B include: eNodeB, MME, SGW1, and SGW2. Similarly, SGW1 will be described in detail in FIG. 3B as an example.
  • the method includes:
  • Step S322 the eNodeB acquires an SGW list of the SGW connected to the eNodeB.
  • Step S324 the eNodeB detects each SGW in the SGW list to learn the status of the path between the eNodeB and each SGW, and records the path status in the SGW list.
  • Steps S322 and S324 may also refer to steps S202 and S204 in FIG. 2, respectively, and details are not described herein again.
  • Step S326 when the eNodeB detects that the path between the eNodeB and the SGW1 in the SGW list fails, the eNodeB actively sends a path path failure notification message to the MME.
  • the path path failure notification message carries the identifier information of the eNodeB, the identifier information of the SGW1 on the fault path, and the indication information used to indicate that the path status between the eNodeB and the SGW1 is a fault.
  • Step S328 after receiving the path path failure notification message, the MME returns a path failure notification response message to the eNodeB.
  • This step is an optional step.
  • Step S330 the MME will be in a fault according to the received path path failure notification message.
  • the path of the state (such as the first path between the eNodeB and SGW1) is added to the path blacklist.
  • Step S332 the MME excludes the SGW1 indicated in the path blacklist, and selects a second SGW (for example, SGW2) whose path state is normal for the UE.
  • a second SGW for example, SGW2
  • Steps S330 and S332 may refer to the description of steps S310 and S312 in FIG. 3A, respectively, and details are not described herein again.
  • the eNodeB acquires the SGW list of the SGW connected to the eNodeB, and obtains the path status between the eNodeB and each SGW by detecting.
  • the eNodeB reports to the MME to enable the MME to perceive the S1-U path status between the eNodeB and the SGW, and select the SGW2 with the normal path status accordingly.
  • the MME can exclude the SGW of the path state fault when selecting the SGW for the UE, and select the appropriate for the UE.
  • the SGW is used to ensure that the data packets of the UE can be forwarded or routed normally, and the service can be performed normally to improve the user experience of the UE.
  • the MME can sense the S1-U path status between the eNodeB and the SGW in real time, thereby further avoiding service loss and improving the UE user.
  • the MME can sense the S1-U path status between the eNodeB and the SGW in real time, thereby further avoiding service loss and improving the UE user.
  • the size of the sequence numbers of the foregoing processes does not mean the order of execution sequence, and the execution order of each process should be determined by its function and internal logic, and should not be implemented in the embodiment of the present invention. Form any limit.
  • each network element such as the mobility management entity MME, the base station eNodeB, etc.
  • each network element such as the mobility management entity MME, the base station eNodeB, etc.
  • the present invention can be implemented in a combination of hardware or hardware and computer software in combination with the elements and algorithm steps of the various examples described in the embodiments disclosed herein. Whether a function is implemented by hardware or computer software to drive hardware Line, depending on the specific application and design constraints of the technical solution. A person skilled in the art can use different methods for implementing the described functions for each particular application, but such implementation should not be considered to be beyond the scope of the present invention.
  • FIG. 4 shows a possible structural diagram of a mobility management entity (such as an MME) involved in the foregoing embodiment.
  • a mobility management entity such as an MME
  • the mobility management entity MME includes a transmitter/receiver 401, a controller/processor 402, and a memory 403.
  • the transmitter/receiver 401 is configured to support the MME to send and receive information between the eNodeB and the SGW in the foregoing embodiment.
  • the controller/processor 402 performs the processes involved in the MME of Figures 2 through 3B and/or other processes for the techniques described herein.
  • the controller/processor 402 is configured to support the MME to perform processes S206 through S212 in FIG. 2, processes S308 through S312 in FIG. 3A, or processes S326 through S332 in FIG. 3B.
  • the memory 403 is used to store program codes and data of the MME.
  • Figure 4 only shows a simplified design of the mobility management entity.
  • the mobility management entity may include any number of transmitters, receivers, processors, controllers, memories, communication units, etc., and all mobility management entities that can implement the present invention are within the scope of the present invention. within.
  • FIG. 5 shows a possible structural diagram of a base station (such as an eNodeB) involved in the above embodiment.
  • a base station such as an eNodeB
  • the base station eNodeB includes a transmitter/receiver 501, a controller/processor 502, and a memory 503.
  • the transmitter/receiver 501 is configured to support the eNodeB to transmit and receive information with the MME and the SGW in the foregoing embodiment, and to support radio communication between the eNodeB and the UE.
  • the controller/processor 502 performs the processes involved in the eNodeB of Figures 2 through 3B and/or other processes for the techniques described herein.
  • the controller/processor 502 is configured to support the eNodeB to perform processes S202 through S206 in FIG. 2, processes S302 through S308 in FIG. 3A, processes S322 through S328 in FIG. 3B, and/or for the techniques described herein Other processes.
  • Memory 501 Program code and data for storing the base station eNodeB.
  • Figure 5 only shows a simplified design of the base station.
  • the base station may include any number of transmitters, receivers, processors, controllers, memories, communication units, etc., and all base stations that can implement the present invention are within the scope of the present invention.
  • the controller/processor for performing the above mobility management entity or base station of the present invention may be a central processing unit (CPU), a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), and a field programmable gate. Array (FPGA) or other programmable logic device, transistor logic device, hardware component, or any combination thereof. It is possible to implement or carry out the various illustrative logical blocks, modules and circuits described in connection with the present disclosure.
  • the controller/processor may also be a combination of computing functions, such as one or more microprocessor combinations, a combination of a DSP and a microprocessor, and the like.
  • FIG. 6 is a schematic diagram showing another possible structure of a mobility management entity (such as an MME) involved in the foregoing embodiment.
  • a mobility management entity such as an MME
  • the mobility management entity MME includes a communication unit 601, a processing unit 602, and a storage unit 603.
  • the communication unit 601 is configured to support the MME to send and receive information between the eNodeB and the SGW in the foregoing embodiment.
  • Processing unit 602 also performs the processes involved in the MME of Figures 2 through 3B and/or other processes for the techniques described herein.
  • processing unit 602 is configured to support MME to perform processes S206 through S212 in FIG. 2, processes S308 through S312 in FIG. 3A, or processes S326 through S332 in FIG. 3B.
  • the storage unit 603 is configured to store program codes and data of the MME.
  • each functional unit in the embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the first obtaining unit and the second obtaining unit may be the same unit and different units.
  • the above integrated unit can be implemented in the form of hardware or in the form of a software functional unit.
  • FIG. 7 shows another possible structural diagram of a base station (such as an eNodeB) involved in the above embodiment.
  • a base station such as an eNodeB
  • the base station eNodeB includes a communication unit 701, a processing unit 702, a storage unit 703, and a communication unit 704.
  • the communication unit 701 is configured to support the eNodeB to transmit and receive information between the MME and the SGW in the foregoing embodiment, and to support radio communication between the eNodeB and the UE.
  • Processing unit 702 performs the processes involved in the eNodeB of Figures 2 through 3B and/or other processes for the techniques described herein.
  • processing unit 702 is configured to support eNodeB to perform processes S202 through S206 in FIG. 2, processes S302 through S308 in FIG. 3A, processes S322 through S328 in FIG. 3B, and/or other processes for the techniques described herein.
  • the storage unit 701 is configured to store program codes and data of the base station eNodeB.
  • each functional unit in the embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the first obtaining unit and the second obtaining unit may be the same unit and different units.
  • the above integrated unit can be implemented in the form of hardware or in the form of a software functional unit.
  • the steps of a method or algorithm described in connection with the present disclosure may be implemented in a hardware, or may be implemented by a controller/processor executing software instructions.
  • the software instructions can be composed of corresponding software modules, which can be stored in random access memory (RAM), flash memory, read only memory (ROM), and erasable programmable read only memory (Erasable).
  • RAM random access memory
  • ROM read only memory
  • Erasable erasable programmable read only memory
  • EPROM electrically erasable programmable read only memory
  • registers hard disk, removable hard disk, compact disk read only (CD-ROM) or any other form of storage medium known in the art.
  • An exemplary storage medium is coupled to the controller/processor such that the controller/processor can read information from, and can write information to, the storage medium.
  • the storage medium can also be part of the controller/processor.
  • the controller/processor and storage medium can be located in the ASIC.
  • the ASIC can be located in a core network interface device.
  • the controller/processor and storage medium can also exist as discrete components in the core network interface device.
  • the functions described herein can be implemented in hardware, software, firmware, or any combination thereof.
  • the functions may be stored in a computer readable medium or transmitted as one or more instructions or code on a computer readable medium.
  • Computer readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one location to another.
  • a storage medium may be any available media that can be accessed by a general purpose or special purpose computer.

Landscapes

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

Abstract

本发明公开了一种通信方法和通信装置，用于为用户设备选择合适的SGW。方法包括：移动性管理实体获取基站发送的指示所述基站与第一服务网关之间的第一路径处于故障状态的指示信息.移动性管理实体获取基站对应的服务网关列表，服务网关列表包括与所述基站相连的第二服务网关，其中，所述第二服务网关与所述基站之间的第二路径处于正常状态.所述移动性管理实体获取处于所述第一路径上的用户设备的标识信息或者所述基站上待附着的用户设备的标识信息,所述移动性管理实体根据服务网关列表选择第二服务网关为所述用户设备提供服务.

Description

一种通信方法、移动性管理实体、基站及系统 技术领域
本发明涉及无线通信技术领域，具体涉及一种通信方法、移动性管理实体、基站及系统。
背景技术
长期系统演进(英文：long term evolution，缩写：LTE)网络中系统架构演进(英文：system architecture evolution，缩写：SAE)体系结构的主要组成部分是核心分组网(英文：Evolved Packet Core，缩写：EPC)。EPC通过移动性管理实体(英文：mobility management entity，缩写：MME)实现控制面功能，通过服务网关(英文：serving gateway，缩写：SGW)将用户设备(英文：user equipment，缩写：UE)的用户面数据路由或转发至分组数据网网关(英文：PDN Gateway，缩写：PGW)，以实现UE与外部分组数据网络(英文，packet data network，缩写：PDN)连接点的接口传输。
在UE附着的过程中，MME需要先为UE选择合适的SGW。现有技术中，MME会根据跟踪区列表(英文：tracking area list，缩写：TA list)来选择SGW。然而，由于UE的用户面数据通过由演进型基站(英文：evolvedNodeB；缩写：eNB)与SGW直接相连而不经过MME的S1-U路径来传输。当SGW和eNodeB之间的S1-U路径发生故障时，MME无法感知该链路故障，仍可能会选择该故障路径上的SGW，导致UE即使反复上线，也无法正常进行业务。
发明内容
本发明实施例提供了一种通信方法、移动性管理实体、基站及系统，在链路故障时，也能保证UE业务的正常进行，提升UE的用户体验。
一方面，本发明是实施例提供一种通信方法，该方法包括：
移动性管理实体获取基站发送的指示基站与第一服务网关之间的第一路径处于故障状态的指示信息；移动性管理实体获取基站对应的服务网关列表，服务网关列表包括与基站相连的第二服务网关，其中，第二服务网关与基站之间的第二路径处于正常状态；移动性管理实体获取处于第一路径上的用户设备的标识信息或者基站上待附着的用户设备的标识信息；移动性管理实体根据服务网关列表选择第二服务网关为用户设备提供服务。
在一种可能的设计中，指示信息包括：基站的标识信息和第一服务网关的标识信息，或者，基站的标识信息，第一服务网关的标识信息，以及路径状态信息。
在一种可能的设计中，移动性管理实体获取处于第一路径上的用户设备的标识信息包括：移动性管理实体根据基站的标识信息和第一服务网关的标识信息查找本地上下文，获取第一路径上的用户设备的标识。
在一种可能的设计中，则移动性管理实体获取基站上待附着的UE的标识信息包括：移动性管理实体接收基站发送的附着请求，附着请求携带基站的标识信息和待附着的用户设备的标识信息。
在一种可能的设计中，移动性管理实体获取基站发送的指示信息，包括：移动性管理实体接收基站发送的附着请求，附着请求携带指示信息；或者，移动性管理实体接收基站发送的新增的信令消息，新增的信令消息中携带指示信息，其中，该新增的信令消息可以是路径故障通知消息。
在一种可能的设计中，移动性管理实体获取基站对应的服务网关列表，包括：移动性管理实体从域名服务器DNS获取基站对应的服务网关列表；或者，移动性管理实体从本地配置信息中获取基站对应的服务网关列表；或者，移动性管理实体从缓存中获取基站对应的服务网关列表。
在一种可能的设计中，方法还包括：移动性管理实体根据指示信息，将第一路径添加至路径黑名单，路径黑名单包括处于故障状态的路径上的服 务网关的标识信息和基站的标识信息。
在一种可能的设计中，移动性管理实体根据服务网关列表选择第二服务网关为用户设备提供服务，包括：移动性管理实体排除掉路径黑名单中的服务网关，从服务网关列表中选出与基站相连的第二服务网关。
再一方面，本发明实施例提供另一种通信方法，该方法包括：基站获取服务网关列表，服务网关列表包括与基站相连的服务网关的标识信息；基站检测基站与服务网关列表中的服务网关之间的路径状态；若基站确定服务网关列表中的第一服务网关与基站之间的第一路径发生故障，基站向移动性管理实体发送指示第一路径处于故障状态的指示信息。
在一种可能的设计中，指示信息包括：基站的标识信息和第一服务网关的标识信息，或者基站的标识信息，第一服务网关的标识信息，以及路径状态信息。
在一种可能的设计中，基站获取服务网关列表，包括：基站接收移动性管理实体发送的与基站相连的服务网关的标识信息，基站生成服务网关列表；或者，基站获取本地配置的服务网关列表。
在一种可能的设计中，基站接收移动性管理实体发送的与基站相连的服务网关的标识信息包括：基站接收移动性管理实体发送的初始上下文建立请求消息，初始上下文建立请求消息携带与基站相连的服务网关的标识信息。
在一种可能的设计中，基站向移动性管理实体发送指示第一路径处于故障状态的指示信息，包括：基站接收用户设备发送的附着请求，基站向移动性管理实体发送附着请求，附着请求携带指示信息；或者，基站向移动性管理实体发送新增的信令消息，新增的信令消息中携带指示信息，其中，该新增的信令消息可以是路径故障通知消息。
另一方面，本发明实施例提供了一种移动性管理实体，该移动性管理实体具有实现上述方法实际中移动性管理实体行为的功能。所述功能可以 通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。
在一个可能的设计中，移动性管理实体的结构中包括控制器/处理器和发射器/接收器，所述控制器/处理器被配置为支持移动性管理实体执行上述方法中相应的功能。所述发射器/接收器用于支持移动性管理实体与eNodeB或SGW之间的通信，向与eNodeB或SGW发送接收上述方法中所涉及的信息或者指令。所述移动性管理实体还可以包括存储器，所述存储器用于与控制器/处理器耦合，其保存移动性管理实体必要的程序指令和数据。
在一个可能的设计中，移动性管理实体的结构中包括处理模块和通信模块，所述处理模块被配置为支持移动性管理实体执行上述方法中相应的功能。所述通信模块用于支持移动性管理实体与eNodeB或SGW之间的通信，向与eNodeB或SGW发送接收上述方法中所涉及的信息或者指令。所述移动性管理实体还可以包括存储模块，所述存储模块用于与处理模块耦合，其保存移动性管理实体必要的程序指令和数据。
另一方面，本发明实施例提供了一种基站，该基站具有实现上述方法实际中基站行为的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。
在一个可能的设计中，基站的结构中包括控制器/处理器和发射器/接收器，所述控制器/处理器被配置为支持基站执行上述方法中相应的功能。所述发射器/接收器用于支持基站与MME，SGW或UE之间的通信，向MME，SGW或UE发送接收上述方法中所涉及的信息或者指令。所述基站还可以包括存储器，所述存储器用于与控制器/处理器耦合，其保存基站必要的程序指令和数据。
在一个可能的设计中，基站的结构中包括处理模块和通信模块，所述 处理模块被配置为支持基站执行上述方法中相应的功能。所述通信模块用于支持基站与MME，SGW或UE之间的通信，向MME，SGW或UE发送接收上述方法中所涉及的信息或者指令。所述基站还可以包括存储模块，所述存储模块用于与处理模块耦合，其保存基站必要的程序指令和数据。
又一方面，本发明实施例提供了一种通信系统，该系统包括上述方面所述的移动性管理实体和基站。
再一方面，本发明实施例提供了一种计算机存储介质，用于储存为上述移动性管理实体所用的计算机软件指令，其包含用于执行上述方面所设计的程序。
再一方面，本发明实施例提供了一种计算机存储介质，用于储存为上述基站所用的计算机软件指令，其包含用于执行上述方面所设计的程序。
再一方面，本发明实施例还提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行上述各方面所述的方法。
相较于现有技术，本发明提供的方案可为UE选择合适的SGW，以保证UE的数据包能够正常转发或路由，业务能够正常进行，提升UE的用户体验。
附图说明
图1为3GPP中定义的EPC的网络架构示意图；
图1A为用户附着流程的示意图；
图2为根据本发明一个实施例的通信方法的示意图；
图3A和图3B分别为根据本发明一个实施例的通信方法的信令交互图；
图4为根据本发明实施例的通信装置(如，MME)的结构示意图；
图5为根据本发明实施例的通信装置(如，eNodeB)的结构示意图；
图6为根据本发明实施例的通信装置(如，MME)的另一结构示意图；及
图7为根据本发明实施例的通信装置(如，eNodeB)的另一结构示意图。
具体实施方式
为使本发明的目的、技术方案、及优点更加清楚明白，下面结合附图并举实施例，对本发明提供的技术方案进一步详细描述。
图1所示为第三代合作伙伴计划(英文：3rd generation partnership project，缩写：3GPP)中定义的EPC的网络架构图。EPC包括MME、SGW、PGW和归属用户服务器(英文：home subscriber server，缩写：HSS)等子组件。
MME是LTE接入网络中的控制节点，通过S1-MME路径与演进型通用陆地无线接入网(英文：evolved universal terrestrial radio access network，缩写：E-UTRAN)中的基站相连。MME负责对空闲模式下的UE进行跟踪和寻呼控制。在对UE跟踪和寻呼控制的过程中，MME需要为UE选择不同的SGW，以完成LTE系统内核心网节点的切换。MME通过S6a路径与HSS交流信息。
HSS的功能为一个中央数据库，包含与UE相关的信息以及与订阅相关的信息。HSS的功能包括：移动性管理，呼叫和会话建立的支持，用户认证和访问授权。
基站通过S1-U路径与SGW相连。SGW负责UE的数据包的路由和转发，同时也负责UE在eNodeB之间或LTE与其他3GPP技术之间移动时的用户面数据的交换。PGW通过s5路径与SGW相连，实现UE与外部的业务PDN连接点的接口传输。一个UE可以同时通过多个PGW访问多个业务PDN。
现有技术中，当UE附着时，MME会根据跟踪区列表来选择SGW。 然而，由于UE的用户面数据通过由演进型基站(英文：evolved NodeB；缩写：eNodeB)与SGW直接相连而不经过MME的S1-U路径来传输，当SGW和eNodeB之间的数据面路径发生故障时，而用户附着时，MME仍可能会选择该故障路径上的SGW，导致UE无法正常进行业务。通过本发明的通信方法，MME可感知SGW和eNodeB之间的数据面路径的状态，排除链路故障的SGW,而选择一个数据面路径正常的SGW，从而保证UE能够正常进行业务，提升UE的用户体验。
图2所示为根据本发明一个实施例的通信方法的示意图。该通信方法涉及的网元包括MME和eNodeB。如图2所示：
步骤S202，eNodeB获取与eNodeB相连的SGW的列表。
SGW的列表包括与eNodeB相连的SGW的标识信息，其中，SGW的标识信息为用于标识SGW的信息，具体的，可以包括SGW的网络协议(英文：internet protocol，缩写：IP)地址、SGW的编号或SGW的标识(英文：identification,缩写：ID)或者其他其他能够识别该SGW的标识信息中的一项或多项。
具体的获取过程可以通过以下方式实现：
第一种，网络维护人员在eNodeB上人工配置该SGW列表；
第二种，eNodeB通过附着流程获得到其对接的SGW的标识信息，并生成SGW列表。举例来说，在UE附着的过程(参考图1A)，MME为UE选择SGW，并通过DNS查询获得SGW的标识信息(例如：SGW的IP地址)，MME在初始上下文建立请求消息中通知eNodeB该SGW的标识信息，eNodeB接收到初始上下文建立请求消息后，从该初始上下文建立请求消息中获取SGW的标识信息。大量UE附着后，eNodeB可获知与哪些SGW相连(如：SGW1、SGW2、SGW3等)，通过记录这些与其相连的SGW的标识信息来维护SGW列表。其中，SGW列表中维护的SGW(如：SGW1、SGW2、或SGW3)不依赖于当前eNodeB与该SGW是否存在承载。也就 是说，无论承载当前是否存在，如果MME在之前的流程中通知eNodeB与之相连的SGW的标识信息，该SGW的标识信息就被记录在eNodeB上的SGW列表中。
步骤S204，eNodeB对SGW列表中的各SGW进行探测，以获知eNodeB与各SGW间路径状态。
具体的可以通过以下方式实现：
eNodeB可采用回波(echo)探测的方式来获知eNodeB与SGW间的路径状态。举例来说，eNodeB向该SGW1发送echo探测请求，根据预定时间内是否收到echo探测响应，确定eNodeB与SGW1之间的路径状态。如果在预定时间收到SGW1发送的echo探测响应，则确定eNodeB与SGW1之间的路径状态为正常。如果在预定时间内未收到SGW1发送的echo探测响应，可直接确定eNodeB与SGW1之间的路径状态为故障。或者，如果在预定时间内未收到SGW1发送的echo探测响应，eNodeB可按照预定时间间隔再次发送探测请求，如果发送预设次数的探测请求后，仍未收到SGW1发送的echo探测响应，则确定eNodeB与SGW1之间的路径状态为故障。该预定时间间隔和探测请求的发送预设次数可根据实际情况而定。例如，在没有收到探测响应的情况下，eNodeB可每3s再发送一次探测请求，若发送5次都无响应则确认路径故障。
可选的，eNodeB周期性地对SGW列表中的SGW进行探测。例如，每隔1分钟，eNodeB对SGW列表中的SGW测探测一次。这样，eNodeB能够及时地感知到eNodeB与SGW之间路径的状态。
可选的，eNodeB对SGW列表中的SGW进行探测后，在SGW列表中记录检测到的路径状态。例如，若检测到的路径处于正常状态，则记录为正常(normal)；若检测到的路径处于异常状态，则记录为故障(down)。或者，eNodeB也可以只对处于异常状态的路径进行标记。
步骤S206，若eNodeB确定服务网关列表中的第一SGW(如，SGW1) 与eNodeB之间的第一路径发生故障，eNodeB向MME发送指示该第一路径处于故障状态的指示信息。
该指示信息可以采用以下两种形式：
第一种形式：eNodeB的标识信息和SGW1的标识信息；
第二种形式：eNodeB的标识信息，SGW1的标识信息，以及路径状态信息。
其中，eNodeB的标识信息用于标识eNodeB,具体的，可以包括eNodeB的网络协议(英文：internet protocol，缩写：IP)地址、eNodeB的编号或eNodeB的标识(英文：identification,缩写：ID)中的一项或多项。SGW的标识信息可以参考步骤S202中的描述。路径状态信息可以参考步骤S204中的正常(normal)或者故障(down)。
eNodeB可以通过以下方式向MME发送指示该第一路径处于故障状态的指示信息：
第一种方式：尽量复用现有的协议定义的消息上传输该指示信息。例如：当有UE附着时，eNodeB接收用UE发送的附着请求，eNodeB向MME发送附着请求，附着请求携带该指示信息。当然，也可以采用其他的eNodeB与MME之间的现有消息进行传输
第一种方式：在eNodeB和MME之间新增信令消息类型，该消息用于eNodeB实时通知MME eNodeB和SGW之间的路径状态。例如：路径故障通知消息，当然，也可以采用其他的新增信令消息。
相应的，MME获取eNodeB发送的该指示信息。
步骤S208，MME获取与eNodeB相连的SGW列表，该SGW列表至少包括与eNodeB相连的SGW2。其中，SGW2与eNodeB之间的第二路径处于正常状态。
该SGW列表可以包括多个与eNodeB相连的SGW，在此，仅以SGW2为代表进行说明(泛指与eNodeB路径正常的SGW)。
MME可以采用以下几种方式获取与eNodeB相连的SGW列表：
第一种方式：MME从域名服务器DNS获取eNodeB对应的SGW列表。例如，MME根据eNodeB的标识信息，从域名服务器(英文：domain nameserver；简称：DNS)查询获取与eNodeB相连的SGW列表。
第二种方式：MME从本地配置信息中获取eNodeB对应的SGW列表；例如，MME根据eNodeB的标识信息，从本地配置信息查询获取与eNodeB相连的SGW列表。
第三种方式：MME从CACHE缓存中获取eNodeB对应的SGW列表。具体的，MME根据eNodeB的标识信息，从缓存中查询获取与eNodeB相连的SGW列表。
步骤S210，MME获取处于第一路径上的UE的标识信息或者eNodeB上待附着的UE的标识信息；
MME获取处于第一路径上的UE的标识信息的过程具体可以为：根据eNodeB的标识信息和SGW1的标识信息查找本地上下文，获取该第一路径上的UE的标识。
MME获取eNodeB上待附着的UE的标识信息的过程具体可以为：当UE向eNodeB发送附着请求时，eNodeB向MME发送该附着请求，该附着请求中携带eNodeB标识信息和UE的标识信息，MME收到该附着请求，根据eNodeB标识信息和UE的标识信息获知该UE为eNodeB上待附着的UE。
步骤208和步骤210之间没有先后顺序，也可以同时进行。
步骤S212，MME根据SGW列表选择与eNodeB之间路径处于正常状态的SGW2，为上述UE提供服务；
具体的，可以通过以下方式实现：
通过步骤S206MME获得第一路径处于故障状态的指示信息，则MME可以将第一路径添加至路径黑名单。当MME为上述UE选择SGW时，MME 根据eNodeB的SGW列表以及路径黑名单，排除与eNodeB之间路径故障SGW1，而选择SGW列表中与eNodeB之间路径正常的SGW2为UE提供服务。
因此，根据本发明一个实施例的通信方法，eNodeB可获取与该eNodeB相连的SGW的SGW列表，并通过探测获知该eNodeB与各SGW之间的路径状态。当eNodeB与SGW之间的路径状态为故障，eNodeB向MME返回携带用于指示eNodeB与SGW之间的路径状态为故障的指示信息的消息。MME接收到消息后可感知到eNodeB与SGW之间的路径状态，并据此从SGW列表中选择路径状态正常的SGW2。
相比现有技术中MME根据TA list来选择SGW的方案，由于MME可感知到SGW与eNodeB之间的路径状态，MME为UE选择SGW时可排除掉路径状态故障的SGW，为UE选择合适的SGW，以保证UE的数据包能够正常转发或路由，业务能够正常进行，提升UE的用户体验。
图3A和图3B将分别结合本发明具体实施例来详细描述图2所描述的方法。图3A为本发明一个实施例的通信方法的信令交互图：若eNodeB确定服务网关列表中的SGW1与eNodeB之间的第一路径发生故障，当eNodeB收到UE的附着消息时，通过向MME发送附着消息中携带指示该第一路径处于故障状态的指示信息，该实施方式由于利用了现在的附着流程传输指示信息，对流程的改动较少。图3A中的信令交互涉及的网元包括：eNodeB、MME、SGW1和SGW2。图3A中以SGW1为例进行详细说明，即SGW2的执行动作与SGW1类似，为了简洁，在此不再赘述。在图3A的例子中，通过对现有消息进行扩展，使得现有的消息携带了eNodeB与SGW之间的路径状态。
如图3A所示，该方法包括：
步骤S302，eNodeB获取与eNodeB相连的SGW的SGW列表。
步骤S304，eNodeB对SGW列表中的SGW进行探测，以获知eNodeB 与SGW之间路径的状态，并在SGW列表中记录路径状态。
步骤S302和S304可分别参考图2中步骤S202和S204的描述，在此不再赘述。
步骤S306，eNodeB接收来自UE的附着请求。
步骤S308，eNodeB向MME发送UE的附着消息，并通过附着消息通知MME eNodeB与SGW1之间的路径状态故障。
若eNodeB与SGW1之间的路径状态为故障，则用户附着消息中携带eNodeB的标识信息、SGW1的标识信息，以及用于指示eNodeB与SGW1之间的路径状态为故障的指示信息。例如，指示信息用于指示eNodeB与SGW1之间的第一路径状态为故障。
可选的，eNodeB可以通过将当前维护的SGW列表全部(包括正常状态和故障状态)或者部分(故障状态部分)发送给MME的方式通知MME用于刷新MME上的信息，而不仅仅只发送指示eNodeB与SGW1之间的第一路径状态为故障的指示信息。
步骤S310，MME根据接收到的信息将处于故障状态的路径(如eNodeB与SGW1之间的第一路径)添加至路径黑名单。换句话说，MME根据接收到的响应消息维护路径黑名单。其中，路径黑名单至少包括路径处于故障状态的eNodeB的IP地址和对应SGW的IP地址。
例如，在一种实现方式中，MME通过维护路径状态信息来维护路径黑名单。路径状态信息至少包括eNodeB的IP地址、SGW的IP地址，还可以包括连接该eNodeB和该SGW的路径的状态。连接eNodeB和SGW的路径的状态可以为正常(normal)或故障(down)。其中，MME可通过将处于故障状态的路径(如eNodeB与SGW1之间的路径)的状态置为故障(down)，来将其添加至路径黑名单。也就是说，路径状态被置为故障(down)的路径即属于路径黑名单。
例如，路径状态信息以列表的形式存储在MME中，如表1所示：
表1
Figure PCTCN2016113956-appb-000001
举例来说，表1中IP地址为A的eNodeB与IP地址为C的SGW之间的路径状态为Normal，即表示路径状态为正常；IP地址为A的eNodeB与IP地址为D的SGW之间的路径状态为down，即表示路径状态为故障；IP地址为B的eNodeB与IP地址为E的SGW之间的路径状态为Normal；IP地址为B的eNodeB与IP地址为F的SGW之间的路径状态为down。其中，处于故障状态的路径即属于路径黑名单。例如，表1中IP地址为A的eNodeB与IP地址为D的SGW之间的路径，和IP地址为B的eNodeB与IP地址为F的SGW之间的路径，由于这两条路径都处于故障状态，所以属于路径黑名单。
具体地，MME接收到eNodeB发送的用户附着消息后，解析用户附着消息中携带的eNodeB的IP地址与SGW1的IP地址。
作为另一种实现方式，MME可以只记录状态为down的路径上的eNodeB的标识信息与SGW的IP地址，以维护路径黑名单。
步骤S312，MME排除掉路径黑名单中指示的SGW1，为处于该第一路径上的用户设备UE或者该eNodeB上待附着的UE选择路径状态正常的第二SGW(如，SGW2)。
例如，MME从域名服务器(英文：domain name server；简称：DNS)或本地配置信息中或者缓存中获取待选择的SGW列表，并根据各种因素来 选择SGW。根据本发明的实施例，MME排除掉SGW和eNodeB之间的路径故障的SGW，从其他路径正常的SGW进行选择。
在图3A的例子中，MME向DNS查询得到的SGW列表中至少包括SGW2。假设在时刻t1，SGW1与eNodeB之间的第一路径发生故障，而SGW2与eNodeB之间的第二路径保持正常。eNodeB向MME发送携带用于指示eNodeB与SGW1之间的第一路径状态为故障的指示信息的用户附着消息。MME收到用户附着消息后，将第一路径加入路径黑名单，然后排除掉路径黑名单中指示的SGW(如SGW1和/或其他路径状态故障的SGW)，从SGW列表中为UE选择路径状态正常的SGW2。
步骤S312中，MME为UE选择SGW，根据UE的不同状态，具体可包括S312a或S312b。若UE为待附着的UE，则执行步骤S312a；若UE为故障状态的第一路径下已有的UE，则执行步骤S312b。某些步骤细节也参考步骤210中的描述。
步骤S312a：若MME收到eNodeB发送的UE附着消息(这里的UE，包括步骤306中UE，以及后续发起附着消息的其他UE)，MME为待附着的UE选择第二SGW(如，SGW2)，向第二SGW发送创建会话请求消息。为UE选择SGW2后创建会话的过程为现有技术，此处不再赘述。
步骤S312b:MME根据eNodeB的标识信息和SGW1的标识信息查找本地上下文，以确定UE为该第一路径上的UE。之后，MME根据指示信息将该UE切换至第二SGW(如，SGW2)。MME如何为UE切换SGW为现有技术，此处不再赘述。
因此，根据本发明一个实施例的通信方法，eNodeB可通过人工配置或自主学习的方式获取与该eNodeB相连的SGW的SGW列表，并通过探测获知该eNodeB与各SGW之间的路径状态。当eNodeB与SGW之间的路径状态为故障，eNodeB向MME发送指示eNodeB与SGW之间的路径状态为故障的指示信息的第二消息。MME接收到第二消息后可感知到 eNodeB与SGW之间的路径状态，并据此选择路径状态正常的SGW2。相比现有技术中MME根据TA list来选择SGW的方案，由于MME可感知到SGW与eNodeB之间的路径状态，MME为UE选择SGW时可排除掉路径状态故障的SGW，为UE选择合适的SGW，以保证UE的数据包能够正常转发或路由，业务能够正常进行，提升UE的用户体验。
图3B为根据本发明另一个实施例的通信方法的信令交互图，在此实施例中，为本发明一个实施例的通信方法的信令交互图：若eNodeB确定服务网关列表中的SGW1与eNodeB之间的第一路径发生故障，eNodeB主动向MME发送路径路径故障通知消息，并携带指示该第一路径处于故障状态的指示信息，该实施方式可以实时通知MME路径的状态。图3B中的信令交互涉及的网元包括：eNodeB、MME、SGW1和SGW2。同样地，图3B中也以SGW1为例进行详细说明。
如图3B所示，该方法包括：
步骤S322，eNodeB获取与eNodeB相连的SGW的SGW列表。
步骤S324，eNodeB对SGW列表中的各SGW进行探测，以获知eNodeB与各SGW之间路径的状态，并在SGW列表中记录路径状态。
步骤S322和S324也可分别参考图2中步骤S202和S204，在此不再赘述。
步骤S326，当eNodeB检测到eNodeB与SGW列表中的SGW1之间的路径发生故障时，eNodeB主动向MME发送路径路径故障通知消息。该路径路径故障通知消息携带eNodeB的标识信息、该故障路径上的SGW1的标识信息，以及用于指示eNodeB与该SGW1之间的路径状态为故障的指示信息。
步骤S328，MME收到路径路径故障通知消息后，向eNodeB返回一个路径故障通知响应消息。该步骤为可选步骤。
步骤S330，MME根据接收到的路径路径故障通知消息将处于故障状 态的路径(如eNodeB与SGW1之间的第一路径)添加至路径黑名单。
步骤S332，MME排除掉路径黑名单中指示的SGW1，为UE选择路径状态正常的第二SGW(如，SGW2)。
步骤S330和S332可分别参考图3A中步骤S310和S312的描述，在此不再赘述。
因此，根据本发明一个实施例的通信方法，eNodeB获取与该eNodeB相连的SGW的SGW列表，并通过探测获知该eNodeB与各SGW之间的路径状态。当eNodeB与SGW之间的路径状态为故障，eNodeB向MME上报以使MME能感知到eNodeB与SGW之间的S1-U路径状态，并据此选择路径状态正常的SGW2。相比现有技术中MME根据TA list来选择eNodeB的方案，由于MME可感知到eNodeB与SGW之间的路径状态，MME为UE选择SGW时都可排除掉路径状态故障的SGW，为UE选择合适的SGW，以保证UE的数据包能够正常转发或路由，业务能够正常进行，提升UE的用户体验。此外，由于eNodeB在检测到eNodeB与SGW之间的路径状态为故障就主动向MME上报，MME能实时感知到eNodeB与SGW之间的S1-U路径状态，可进一步避免业务损失，提高UE的用户体验。
应理解，在本发明实施例中，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本发明实施例的实施过程构成任何限定。
上述主要从各个网元之间交互的角度对本发明实施例提供的方案进行了介绍。可以理解的是，各个网元，例如移动性管理实体MME、基站eNodeB等为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，本发明能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执 行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本发明的范围。
图4示出了上述实施例中所涉及的移动性管理实体(如MME)的一种可能的结构示意图。
移动性管理实体MME包括发射器/接收器401,控制器/处理器402，存储器403。该发射器/接收器401用于支持MME与上述实施例中的该的eNodeB，SGW之间收发信息。控制器/处理器402执行图2至图3B中涉及MME的处理过程和/或用于本申请所描述的技术的其他过程。作为示例，控制器/处理器402用于支持MME执行图2中的过程S206至S212、图3A中的过程S308至S312、或图3B中的过程S326至S332。存储器403用于存储MME的程序代码和数据。
可以理解的是，图4仅仅示出了移动性管理实体的简化设计。在实际应用中，移动性管理实体可以包含任意数量的发射器，接收器，处理器，控制器，存储器，通信单元等，而所有可以实现本发明的移动性管理实体都在本发明的保护范围之内。
图5示出了上述实施例中涉及到的基站(如eNodeB)的一种可能的结构示意图。
基站eNodeB包括发射器/接收器501,控制器/处理器502，存储器503。该发射器/接收器501用于支持eNodeB与上述实施例中的该的MME以及SGW之间收发信息，以及支持eNodeB与UE之间进行无线电通信。控制器/处理器502执行图2至图3B中涉及eNodeB的处理过程和/或用于本申请所描述的技术的其他过程。例如，控制器/处理器502用于支持eNodeB执行图2中的过程S202至S206，图3A中的过程S302至S308，图3B中的过程S322至S328，和/或用于本文所描述的技术的其他过程。存储器501 用于存储基站eNodeB的程序代码和数据。
可以理解的是，图5仅仅示出了基站的简化设计。在实际应用中，基站可以包含任意数量的发射器，接收器，处理器，控制器，存储器，通信单元等，而所有可以实现本发明的基站都在本发明的保护范围之内。
用于执行本发明上述移动性管理实体或基站的控制器/处理器可以是中央处理器(CPU)，通用处理器、数字信号处理器(DSP)、专用集成电路(ASIC)，现场可编程门阵列(FPGA)或者其他可编程逻辑器件、晶体管逻辑器件，硬件部件或者其任意组合。其可以实现或执行结合本发明公开内容所描述的各种示例性的逻辑方框，模块和电路。该控制器/处理器也可以是实现计算功能的组合，例如包含一个或多个微处理器组合，DSP和微处理器的组合等等。
图6示出了上述实施例中所涉及的移动性管理实体(如MME)的另一种可能的结构示意图。
移动性管理实体MME包括通信单元601,处理单元602，存储单元603。该通信单元601用于支持MME与上述实施例中的该的eNodeB，SGW之间收发信息。处理单元602还执行图2至图3B中涉及MME的处理过程和/或用于本申请所描述的技术的其他过程。作为示例，处理单元602用于支持MME执行图2中的过程S206至S212、图3A中的过程S308至S312、或图3B中的过程S326至S332。存储单元603用于存储MME的程序代码和数据。
需要说明的是，本发明实施例中对单元的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。本发明实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。例如，上述实施例中，第一获取单元和第二获取单元可以是同一个单元，也不同的单元。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
图7示出了上述实施例中涉及到的基站(如eNodeB)的另一种可能的结构示意图。
基站eNodeB包括通信单元701,处理单元702，存储单元703以及通信单元704。该通信单元701用于支持eNodeB与上述实施例中的该的MME以及SGW之间收发信息，以及支持eNodeB与UE之间进行无线电通信。处理单元702执行图2至图3B中涉及eNodeB的处理过程和/或用于本申请所描述的技术的其他过程。例如，处理单元702用于支持eNodeB执行图2中的过程S202至S206，图3A中的过程S302至S308，图3B中的过程S322至S328，和/或用于本文所描述的技术的其他过程。存储单元701用于存储基站eNodeB的程序代码和数据。
需要说明的是，本发明实施例中对单元的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。本发明实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。例如，上述实施例中，第一获取单元和第二获取单元可以是同一个单元，也不同的单元。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
结合本发明公开内容所描述的方法或者算法的步骤可以硬件的方式来实现，也可以是由控制器/处理器执行软件指令的方式来实现。软件指令可以由相应的软件模块组成，软件模块可以被存放于随机存取存储器(RandomAccess Memory，RAM)、闪存、只读存储器(Read Only Memory，ROM)、可擦除可编程只读存储器(Erasable Programmable ROM，EPROM)、电可擦可编程只读存储器(Electrically EPROM，EEPROM)、寄存器、硬盘、移动硬盘、只读光盘(CD-ROM)或者本领域熟知的任何其它形式的存储介质中。一种示例性的存储介质耦合至控制器/处理器，从而使控制器/处理器能够从该存储介质读取信息，且可向该存储介质写入信息。当然，存储介质也可以是控制器/处理器的组成部分。控制器/处理器和存储介质可以位于ASIC中。另外，该ASIC可以位于核心网接口设备中。当然，控制器/处理器和存储介质也可以作为分立组件存在于核心网接口设备中。
本领域技术人员应该可以意识到，在上述一个或多个示例中，本发明所描述的功能可以用硬件、软件、固件或它们的任意组合来实现。当使用软件实现时，可以将这些功能存储在计算机可读介质中或者作为计算机可读介质上的一个或多个指令或代码进行传输。计算机可读介质包括计算机存储介质和通信介质，其中通信介质包括便于从一个地方向另一个地方传送计算机程序的任何介质。存储介质可以是通用或专用计算机能够存取的任何可用介质。
以上所述的具体实施方式，对本发明的目的、技术方案和有益效果进行了进一步详细说明，所应理解的是，以上所述仅为本发明的具体实施方式而已，并不用于限定本发明的保护范围，凡在本发明的技术方案的基础之上，所做的任何修改、等同替换、改进等，均应包括在本发明的保护范围之内。

Claims (27)

  1. 一种通信方法，其特征在于，包括：
    移动性管理实体获取基站发送的指示所述基站与第一服务网关之间的第一路径处于故障状态的指示信息；
    所述移动性管理实体获取所述基站对应的服务网关列表，所述服务网关列表包括与所述基站相连的第二服务网关，其中，所述第二服务网关与所述基站之间的第二路径处于正常状态；
    所述移动性管理实体获取处于所述第一路径上的用户设备的标识信息或者所述基站上待附着的用户设备的标识信息；
    所述移动性管理实体根据所述服务网关列表选择所述第二服务网关为所述用户设备提供服务。
  2. 根据权利要求1所述的方法，其特征在于，所述指示信息包括：
    所述基站的标识信息和所述第一服务网关的标识信息，或者
    所述基站的标识信息，所述第一服务网关的标识信息，以及路径状态信息。
  3. 根据权利要求2所述的方法，其特征在于，所述移动性管理实体获取处于所述第一路径上的用户设备的标识信息包括：
    所述移动性管理实体根据所述基站的标识信息和所述第一服务网关的标识信息查找本地上下文，获取所述第一路径上的用户设备的标识。
  4. 根据权利要求1或2所述的方法，其特征在于，则所述移动性管理实体获取所述基站上待附着的UE的标识信息包括：
    所述移动性管理实体接收所述基站发送的附着请求，所述附着请求携带所述基站的标识信息和所述待附着的用户设备的标识信息。
  5. 根据权利要求1至4任一所述的方法，其特征在于，所述移动性管理实体获取所述基站发送的所述指示信息，包括：
    所述移动性管理实体接收所述基站发送的附着请求，所述附着请求携带 所述指示信息；或者
    所述移动性管理实体接收所述基站发送的路径故障通知消息，所述路径故障通知消息中携带所述指示信息。
  6. 根据权利要求1至5任一所述的方法，其特征在于，所述移动性管理实体获取所述基站对应的服务网关列表，包括：
    所述移动性管理实体从域名服务器DNS获取所述基站对应的所述服务网关列表；或
    所述移动性管理实体从本地配置信息中获取所述基站对应的所述服务网关列表；或者
    所述移动性管理实体从缓存中获取所述基站对应的所述服务网关列表。
  7. 根据权利要求1-6任一所述的方法，其特征在于，所述方法还包括：
    所述移动性管理实体根据所述指示信息，将所述第一路径添加至路径黑名单，所述路径黑名单包括处于故障状态的路径上的服务网关的标识信息和基站的标识信息。
  8. 根据权利要求7任一所述的方法，其特征在于，其特征在于，所述移动性管理实体根据服务网关列表选择第二服务网关为所述用户设备提供服务，包括：
    所述移动性管理实体排除掉所述路径黑名单中的服务网关，从所述服务网关列表中选出与所述基站相连的所述第二服务网关。
  9. 一种通信方法，其特征在于，包括：
    基站获取服务网关列表，所述服务网关列表包括与所述基站相连的服务网关的标识信息；
    所述基站检测所述基站与所述服务网关列表中的服务网关之间的路径状态；
    若所述基站确定所述服务网关列表中的第一服务网关与所述基站之间的第一路径发生故障，所述基站向移动性管理实体发送指示所述第一路径 处于故障状态的指示信息。
  10. 根据权利要求9所述的方法，其特征在于，所述指示信息包括：
    所述基站的标识信息和所述第一服务网关的标识信息，或者
    所述基站的标识信息，所述第一服务网关的标识信息，以及路径状态信息。
  11. 根据权利要求9或10所述的方法，其特征在于，所述基站获取服务网关列表，包括：
    所述基站接收所述移动性管理实体发送的与所述基站相连的服务网关的标识信息，所述基站生成所述服务网关列表；
    或者
    所述基站获取本地配置的服务网关列表。
  12. 根据权利要求11所述的方法，其特征在于，所述基站接收所述移动性管理实体发送的与所述基站相连的服务网关的标识信息包括：
    所述基站接收所述移动性管理实体发送的初始上下文建立请求消息，所述初始上下文建立请求消息携带与所述基站相连的服务网关的标识信息。
  13. 根据权利要求9至12任一所述的方法，其特征在于，所述基站向移动性管理实体发送指示所述第一路径处于故障状态的指示信息，包括：
    所述基站接收用户设备发送的附着请求，基站向所述移动性管理实体发送所述附着请求，所述附着请求携带所述指示信息；或者
    所述基站向所述移动性管理实体发送路径故障通知消息，所述路径故障通知消息携带所述指示信息。
  14. 一种移动性管理实体，其特征在于，包括：
    通信单元，用于获取基站发送的指示所述基站与第一服务网关之间的第一路径处于故障状态的指示信息；
    处理单元，用于获取所述基站对应的服务网关列表，所述服务网关列表包括与所述基站相连的第二服务网关，其中，所述第二服务网关与所述基 站之间的第二路径处于正常状态；获取处于所述第一路径上的用户设备的标识信息或者所述基站上待附着的用户设备的标识信息；根据服务网关列表选择第二服务网关为所述用户设备提供服务。
  15. 根据权利要求14所述的移动性管理实体，其特征在于，所述指示信息包括：
    所述基站的标识信息和所述第一服务网关的标识信息，或者
    所述基站的标识信息，所述第一服务网关的标识信息，以及路径状态信息。
  16. 根据权利要求15所述的移动性管理实体，其特征在于，
    处理单元具体用于根据所述基站的标识信息和所述第一服务网关的标识信息查找本地上下文，获取所述第一路径上的用户设备的标识。
  17. 根据权利要求14或15所述的移动性管理实体，其特征在于，
    所述通信单元还用于接收所述基站发送的附着请求，所述处理单元具体用于从所述附着请求获取所述基站的标识信息和所述待附着的用户设备的标识信息。
  18. 根据权利要求14至17任一所述的移动性管理实体，其特征在于，
    所述通信单元具体用于接收所述基站发送的附着请求，所述附着请求携带所述指示信息；或者
    所述通信单元具体用于接收所述基站发送的路径故障通知消息，所述路径故障通知消息中携带所述指示信息。
  19. 根据权利要求14至18任一所述的移动性管理实体，其特征在于，
    所述处理单元具体用于从域名服务器DNS获取所述基站对应的所述服务网关列表；或
    所述处理单元具体用于从本地配置信息中获取所述基站对应的所述服务网关列表；或者
    所述处理单元具体用于从缓存中获取所述基站对应的所述服务网关列 表。
  20. 根据权利要求14-19任一所述的移动性管理实体，其特征在于，
    所述处理单元还用于根据所述指示信息，将所述第一路径添加至路径黑名单，所述路径黑名单包括处于故障状态的路径上的服务网关的标识信息和基站的标识信息。
  21. 根据权利要求20任一所述的移动性管理实体，其特征在于，其特征在于，
    所述处理单元具体用于排除掉所述路径黑名单中的服务网关，从所述服务网关列表中选出与所述基站相连的所述第二服务网关
  22. 一种基站，其特征在于，包括：
    处理单元，用于获取服务网关列表，所述服务网关列表包括与所述基站相连的服务网关的标识信息；检测所述基站与所述服务网关列表中的服务网关之间的路径状态；
    通信单元，用于若所述处理单元确定所述服务网关列表中的第一服务网关与所述基站之间的第一路径发生故障，向移动性管理实体发送指示所述第一路径处于故障状态的指示信息。
  23. 根据权利要求22所述的基站，其特征在于，所述指示信息包括：
    所述基站的标识信息和所述第一服务网关的标识信息，或者
    所述基站的标识信息，所述第一服务网关的标识信息，以及路径状态信息。
  24. 根据权利要求22或23所述的基站，其特征在于，：
    所述通信单元还用于接收所述移动性管理实体发送的与所述基站相连的服务网关的标识信息，所述处理单元具体用于根据收到的服务网关的标识信息生成所述服务网关列表；
    或者
    所述处理单元获取本地配置的服务网关列表。
  25. 根据权利要求24所述的基站，其特征在于，
    所述通信单元具体用于接收所述移动性管理实体发送的初始上下文建立请求消息，所述初始上下文建立请求消息携带与所述基站相连的服务网关的标识信息。
  26. 根据权利要求22至25任一所述的基站，其特征在于，
    所述通信单元还用于接收用户设备发送的附着请求，并向所述移动性管理实体发送所述附着请求，所述附着请求携带所述指示信息；或者
    所述通信单元还用于向所述移动性管理实体发送路径故障通知消息，所述路径故障通知消息携带所述指示信息。
  27. 一种数据传输系统，包括：
    如权利要求14至21任一所述的移动性管理实体，以及如权利要求22至26任一所述的基站。
PCT/CN2016/113956 2016-12-30 2016-12-30 一种通信方法、移动性管理实体、基站及系统 WO2018120223A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2016/113956 WO2018120223A1 (zh) 2016-12-30 2016-12-30 一种通信方法、移动性管理实体、基站及系统

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2016/113956 WO2018120223A1 (zh) 2016-12-30 2016-12-30 一种通信方法、移动性管理实体、基站及系统

Publications (1)

Publication Number Publication Date
WO2018120223A1 true WO2018120223A1 (zh) 2018-07-05

Family

ID=62706683

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/113956 WO2018120223A1 (zh) 2016-12-30 2016-12-30 一种通信方法、移动性管理实体、基站及系统

Country Status (1)

Country Link
WO (1) WO2018120223A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101459928A (zh) * 2008-04-16 2009-06-17 中兴通讯股份有限公司 网元间的过载通知方法
CN102137487A (zh) * 2010-12-31 2011-07-27 华为技术有限公司 一种选择服务网关实体的方法及设备
WO2015142078A1 (en) * 2014-03-19 2015-09-24 Lg Electronics Inc. Method and apparatus for transmitting information on serving gateway for supporting small cell mobility in wireless communication system
WO2015194890A1 (en) * 2014-06-19 2015-12-23 Samsung Electronics Co., Ltd. Method and apparatus for establishing user plane bearer

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101459928A (zh) * 2008-04-16 2009-06-17 中兴通讯股份有限公司 网元间的过载通知方法
CN102137487A (zh) * 2010-12-31 2011-07-27 华为技术有限公司 一种选择服务网关实体的方法及设备
WO2015142078A1 (en) * 2014-03-19 2015-09-24 Lg Electronics Inc. Method and apparatus for transmitting information on serving gateway for supporting small cell mobility in wireless communication system
WO2015194890A1 (en) * 2014-06-19 2015-12-23 Samsung Electronics Co., Ltd. Method and apparatus for establishing user plane bearer

Similar Documents

Publication Publication Date Title
JP5687358B2 (ja) サービング・ゲートウェイ・エンティティを選択する方法および装置
US8249020B2 (en) Synchronization method, communication handover method, radio network and node
JP5664988B2 (ja) ページング処理方法およびシステム、サービングゲートウェイ
US11178000B2 (en) Method and system for processing NF component exception, and device
WO2016101575A1 (zh) 一种语音业务切换方法及设备
JP5947982B2 (ja) サービングゲートウェイ、移動管理ノード、データゲートウェイを取得するための方法、及びシステム
US9667481B2 (en) Correlation identifier for user plane congestion and other use cases
JP5101734B2 (ja) トンネル管理方法、トンネル管理装置および通信システム
KR101922577B1 (ko) 서비스 처리 방법 및 장치
WO2012126362A1 (zh) 一种信令跟踪方法、装置和系统
CN104081808A (zh) Mme恢复
US20160119830A1 (en) Radio terminal, network apparatus, and method therefor
WO2013163945A1 (zh) 一种机器类通信事件的上报方法及相应装置
CN107613023B (zh) 设备连接方法及装置
JP6561995B2 (ja) 制御装置及びその方法
JP6340076B2 (ja) 移動性管理方法、装置及びシステム
WO2017101120A1 (zh) 通信方法、装置及系统
WO2011134370A1 (zh) 机器类通信事件上报方法及系统
WO2018120223A1 (zh) 一种通信方法、移动性管理实体、基站及系统
JP6212344B2 (ja) ネットワーク監視装置、ネットワーク監視システム、ネットワーク監視方法およびネットワーク監視プログラム
JP6028268B2 (ja) ショートメッセージシグナリングを最適化するための方法、デバイス、及びシステム
WO2018132966A1 (zh) 探测老化时延的方法、装置、数据中心和系统
US9350604B1 (en) Packet gateway assignment based on network connectivity
JP7261759B2 (ja) 移動通信ネットワークにおけるプレーン間の死活監視方法、ｐｇｗ－ｃ及びプログラム
CN106973415B (zh) 一种获取pgw fqdn的方法及装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 16925689

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 16925689

Country of ref document: EP

Kind code of ref document: A1