WO2017076087A1 - 服务网关的管理方法、装置及系统 - Google Patents

服务网关的管理方法、装置及系统 Download PDF

Info

Publication number
WO2017076087A1
WO2017076087A1 PCT/CN2016/093252 CN2016093252W WO2017076087A1 WO 2017076087 A1 WO2017076087 A1 WO 2017076087A1 CN 2016093252 W CN2016093252 W CN 2016093252W WO 2017076087 A1 WO2017076087 A1 WO 2017076087A1
Authority
WO
WIPO (PCT)
Prior art keywords
sgw
mme
service
message
identifier
Prior art date
Application number
PCT/CN2016/093252
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 中兴通讯股份有限公司
Publication of WO2017076087A1 publication Critical patent/WO2017076087A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/08—Mobility data transfer
    • H04W8/16—Mobility data transfer selectively restricting mobility data tracking
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/12—Setup of transport tunnels

Definitions

  • the present application relates to, but is not limited to, the field of communications, and in particular, to a method, device and system for managing a service gateway.
  • FIG. 1 is a schematic diagram of a network architecture of a 4G EPS in the related art. As shown in FIG. 1 , the functions of the evolved packet system (EPS) are as follows:
  • UE UE Equipment
  • the terminal accesses the core network through the air interface and the 4G base station, and accesses the service network through an Evolved Packet Core (EPC) network.
  • EPC Evolved Packet Core
  • the terminal may be in an idle state and a connected state.
  • RRC radio resource connection
  • eNodeB A 4G base station that provides radio access to the UE. Its main function is to perform radio resource control and scheduling, and provide mobility management within the base station.
  • Mobility Management Element The core network control plane network element, which mainly authenticates and signs the UE.
  • the MME selects a Serving Gateway (Serving Gateway) and a Packet Data Network Gateway (PDN GW) for the user at the same time.
  • PDN GW Packet Data Network Gateway
  • the MME may initiate paging to the user according to the saved user context.
  • the MME also provides mobility management across base stations.
  • Serving GW User plane network element, the anchor point when the user moves across the base station, and provides the roaming interface with the PDN GW in the roaming situation.
  • the Serving GW caches the user data and triggers the MME to page the user.
  • PDN GW User plane network element, which allocates an IP (Internet Protocol) address to the UE and accesses the service network.
  • IP Internet Protocol
  • S1-MME, S11, and S5/S8-C are control plane interfaces, and transmit signaling plane data based on GPRS Tunneling Protocol-C (GTP-C);
  • S1-U, S5 /S8-U is the user interface, based on the GPRS tunneling protocol user plane (GPRS Tunnelling Protocol-U, GTP-U), transmitting user plane data.
  • GTP-C GPRS Tunneling Protocol-C
  • the data traffic carried by the carrier network is rapidly increasing, and operators are under pressure to upgrade the network.
  • the gateway because the control plane and the forwarding plane are unified, Need to upgrade together, the cost is greater.
  • FIG. 2 is a schematic structural diagram of separation of a control plane and a forwarding plane of a Serving GW in the related art.
  • the SGW is divided into a serving gateway (SGW-C) of the control plane and a serving gateway (SGW-U) of the forwarding plane. Interact through a new interface in the middle.
  • SGW-C serving gateway
  • SGW-U serving gateway
  • the main function of the SGW-C is to provide a control plane interface with the MME and the PDN GW, and control the SGW-U at the same time.
  • One SGW-C is generally deployed in a centralized manner, and the location of the SGW-U can be flexible.
  • One SGW-C can control one or more SGW-Us.
  • the main function of the SGW-U is to provide a user plane interface with the base station and the PDN GW, and to accept the control of the SGW-C.
  • the control of the SGW-U by the SGW-C mainly includes requesting the SGW-U to allocate or release the GTP-U tunnel resources of the S1-U and S5/S8-U.
  • Each SGW-U has a service area, and the base station in the area can access the SGW-U. When the service area is generally across, the SGW-U reselection occurs.
  • the MME needs to ensure that all the tracking areas in the TAI list do not exceed the selected SGW-U service area when assigning a Tracking Area Identity (TAI) list to the user. Therefore, when the UE moves in all the tracking areas in the TAI list, it is not necessary to re-select the SGW-U, and how the MME knows that the service area of the SGW-U has not been solved. In addition, after the separation of SGW-U and SGW-C, there is no solution for how SGW-C manages SGW-U.
  • TAI Tracking Area Identity
  • the application provides a management method, device and system for a service gateway.
  • a method for managing a service gateway including:
  • SGW-C receives a registration message of SGW-U, wherein the registration message carries the Service area information of the SGW-U; and/or,
  • the registration message further includes at least one of the following:
  • the identifier of the SGW-U The identifier of the SGW-U, the capacity weight of the SGW-U, the user type of the SGW-U service, and the service information of the SGW-U service.
  • the service area information includes:
  • the method further includes:
  • the SGW-C does not receive the keep-alive response of the SGW-U, confirm that the SGW-U is invalid, and delete the user data of the SGW-U locally in the SGW-C, and Sending, to the MME, a message for updating the SGW-U, where the message carries an identifier of the SGW-U and a failure indication.
  • the method further includes:
  • the SGW-C after receiving the de-registration request of the SGW-U, the SGW-C includes:
  • the SGW-C reselects the SGW-U
  • the information of the SGW-C failure is sent to the MME.
  • the method further includes:
  • a method for managing a service gateway including:
  • the MME receives the update message of the SGW-U sent by the SGW-C, where the update message carries the identifier of the SGW-U and/or the IP address of the SGW-U and the service area information of the SGW-U;
  • the MME allocates a TAI list allocated by the terminal according to the service area information, where the TAI list does not exceed an area served by the SGW-U.
  • the method further includes:
  • the MME receives a message that is sent by the SGW-C to update the SGW-U, where the message carries an identifier of the SGW-U and service area information of the SGW-U.
  • a management device for the service gateway is provided, which is located in the SGW-C, and includes:
  • a first receiving module configured to receive a registration message of the SGW-U, where the registration message carries service area information of the SGW-U;
  • a sending module configured to send an update message for updating the SGW-U to an MME to which the SGW-U belongs, where the update message carries an identifier of the SGW-U and/or an IP address of the SGW-U And the service area information, where the service area information is used to indicate that the TAI list allocated by the MME for the terminal does not exceed the area served by the SGW-U.
  • the registration message further includes at least one of the following:
  • the identifier of the SGW-U The identifier of the SGW-U, the capacity weight of the SGW-U, the user type of the SGW-U service, and the service information of the SGW-U service.
  • the service area information includes:
  • the method further includes:
  • a keep-alive module configured to send a keep-alive request to the SGW-U after sending an update message to update the SGW-U to an MME to which the SGW-U belongs; and receive the SGW at the SGW-C -
  • the keep-alive response of -U confirm that the SGW-U is valid; if the keep-alive response of the SGW-U is not received, confirm that the SGW-U is invalid, and in the SGW-C
  • the user data of the SGW-U is deleted locally, and a message for updating the SGW-U is sent to the MME, where the message carries the identifier of the SGW-U and a failure indication.
  • the method further includes:
  • a registration module configured to receive a deregistration request of the SGW-U; and send a deregistration response to the SGW-U, and send a message to the MME to update the SGW-U, the message carrying the message SGW-U identification and failure indication.
  • the method further includes:
  • a selecting module configured to: after receiving the de-registration request of the SGW-U, reselect the SGW-U; and if the re-selection fails, send the SGW-C invalidation information to the MME.
  • the method further includes:
  • Deleting a module configured to send a request to the SGW-U to delete the SGW-U, and send a message to the MME to update the SGW-U, where the message carries the identifier and the invalidation indication of the SGW-U .
  • a management device for the service gateway is further provided, which is located in the MME, and includes:
  • the second receiving module is configured to receive an update message of the updated SGW-U sent by the SGW-C, where the update message carries the identifier of the SGW-U and/or the IP address of the SGW-U and the service area information. ;
  • an allocation module configured to allocate a TAI list for the terminal according to the service service area information, where the TAI list does not exceed an area served by the SGW-U.
  • the method further includes:
  • an update module configured to receive a message that is sent by the SGW-C to update the SGW-U, where the message carries an identifier of the SGW-U and service area information of the SGW-U.
  • a management system for a service gateway including: SGW-C, SGW-U, and MME:
  • the SGW-C is configured to receive a registration message of the SGW-U, where the registration message carries service area information of the SGW-U; and sends an update to the MME to which the SGW-U belongs.
  • the MME is configured to allocate a TAI list to the terminal according to the service area information, where the TAI list does not exceed an area served by the SGW-U.
  • a computer readable storage medium storing computer executable instructions that, when executed by a processor, implement a management method of any of the service gateways described above.
  • the SGW-C is configured to receive a registration message of the SGW-U, where the registration message carries the service area information of the SGW-U, and/or the SGW-C sends to the MME to update the SGW.
  • An update message of the U where the update message carries the identifier of the SGW-U and/or the IP address of the SGW-U and the service area information of the SGW-U, where the service area information is used to indicate the TAI allocated by the MME to the terminal.
  • the list does not exceed the area of the SGW-U service, and the problem of how the MME learns the service area of the SGW-U is solved, and the TAI list allocated by the MME to the user does not exceed the SGW-U service area.
  • FIG. 1 is a schematic diagram of a network architecture of a 4G EPS in the related art
  • FIG. 2 is a schematic structural diagram of separation of a control plane and a forwarding plane of a Serving GW in the related art
  • FIG. 3 is a flowchart 1 of a method for managing a service gateway according to an embodiment of the present invention
  • FIG. 4 is a second flowchart of a method for managing a service gateway according to an embodiment of the present invention.
  • FIG. 5 is a structural block diagram 1 of a management apparatus of a service gateway according to an embodiment of the present invention.
  • FIG. 6 is a structural block diagram 2 of a management apparatus of a service gateway according to an embodiment of the present invention.
  • FIG. 7 is a structural block diagram 3 of a management apparatus of a service gateway according to an embodiment of the present invention.
  • FIG. 8 is a structural block diagram 4 of a management apparatus of a service gateway according to an embodiment of the present invention.
  • FIG. 9 is a structural block diagram 5 of a management apparatus of a service gateway according to an embodiment of the present invention.
  • FIG. 10 is a structural block diagram 6 of a management apparatus of a service gateway according to an embodiment of the present invention.
  • FIG. 11 is a structural block diagram 7 of a management apparatus of a service gateway according to an embodiment of the present invention.
  • FIG. 12 is a flowchart 1 of interaction between a serving gateway and an MME according to an embodiment of the present invention.
  • FIG. 13 is a second flowchart of interaction between a serving gateway and an MME according to an embodiment of the present invention.
  • FIG. 14 is a third flowchart of interaction between a serving gateway and an MME according to an embodiment of the present invention.
  • FIG. 3 is a flowchart 1 of a method for managing a service gateway according to an embodiment of the present invention. As shown in FIG. 3, the process includes the following steps:
  • Step S302 the SGW-C receives the registration message of the SGW-U, where the registration message carries the service area information of the SGW-U; and/or,
  • Step S304 according to the service area information of the SGW-U, the SGW-C determines a mobility management unit related to the service area, and then sends an update message for updating the SGW-U information to the MME, where the update message And carrying the identifier of the SGW-U and/or the IP address of the SGW-U and the service area information, where the service area information is used to indicate that the TAI list allocated by the MME for the terminal does not exceed the area served by the SGW-U.
  • the SGW-C receives the registration message of the SGW-U, where the registration message carries the service area information of the SGW-U, and/or the SGW-C sends the MME to the MME for updating the SGW-U.
  • An update message wherein the update message carries the identity of the SGW-U and/or SGW-U
  • the IP address and the service area information the service area information is used to indicate that the TAI list allocated by the MME for the terminal does not exceed the area served by the SGW-U, and the problem of how the MME learns the service area of the SGW-U is solved.
  • the TAI list allocated by the MME to the user does not exceed the SGW-U service area.
  • the registration message further includes at least one of the following:
  • the SGW-U identifier the capacity weight of the SGW-U, the user type of the SGW-U service, and the service information of the SGW-U service.
  • the service area information may include:
  • the SGW-C after the SGW-C sends an update message for updating the SGW-U to the MME, the SGW-C sends a keep-alive request to the SGW-U.
  • the SGW-C does not receive the keep-alive response of the SGW-U, confirm that the SGW-U is invalid, delete the user data of the SGW-U locally in the SGW-C, and send an update to the MME.
  • the message of the SGW-U the message carries the identifier of the SGW-U and a failure indication.
  • the SGW-C receives the de-registration request of the SGW-U;
  • the SGW-C sends a registration de-registration response to the SGW-U, and sends a message to the MME to update the SGW-U, the message carrying the SGW-U identifier and the invalidation indication.
  • the SGW-C after the SGW-C receives the de-registration request of the SGW-U, the SGW-C reselects the SGW-U;
  • the information of the SGW-C failure is sent to the MME.
  • the SGW-C sends a request for deleting the SGW-U to the SGW-U, and sends a message for updating the SGW-U to the MME, where the message carries the identifier of the SGW-U and a failure indication.
  • FIG. 4 is a second flowchart of a method for managing a service gateway according to an embodiment of the present invention. As shown in FIG. 4, the process includes the following steps. step:
  • Step S402 the MME receives an update message of the SGW-U sent by the SGW-C, where the update message carries the identifier of the SGW-U and/or the IP address of the SGW-U and the service area information of the SGW-U.
  • Step S404 the MME allocates a TAI list to the terminal according to the service area information, where the TAI list does not exceed the area served by the SGW-U.
  • the MME receives the update message of the SGW-U sent by the SGW-C, where the update message carries the identifier of the SGW-U and/or the IP address of the SGW-U and the service area information of the SGW-U.
  • the MME allocates a TAI list to the terminal according to the service area information, where the TAI does not exceed the area served by the SGW-U, and solves the problem that the MME learns the service area of the SGW-U, and implements the TAI allocated by the MME to the user.
  • the list will not exceed the SGW-U service area.
  • the MME receives the message that is sent by the SGW-C to update the SGW-U, where the message carries the identifier of the SGW-U and the service area information of the SGW-U.
  • a management device for the service gateway is further provided, and the device is used to implement the foregoing embodiments and preferred embodiments, and details are not described herein.
  • the term "module” may implement a combination of software and/or hardware of a predetermined function.
  • the apparatus described in the following embodiments is preferably implemented in software, hardware, or a combination of software and hardware, is also possible and contemplated.
  • FIG. 5 is a structural block diagram 1 of a management apparatus of a service gateway according to an embodiment of the present invention. As shown in FIG. 5, the apparatus is located in the SGW-C, including
  • the first receiving module 52 is configured to receive a registration message of the SGW-U, where the registration message carries service area information of the SGW-U; and/or,
  • the sending module 54 is configured to send an update message for updating the SGW-U to the selected MME, where the update message carries the identifier of the SGW-U and/or the IP address of the SGW-U and the service of the SGW-U
  • the area information is used to indicate that the MME allocates an area in which the TAI list does not exceed the SGW-U service.
  • the first receiving module 52 receives the registration message of the SGW-U, and the sending module 54 An update message for updating the SGW-U is sent to the MME, which solves the problem of how the MME learns the service area of the SGW-U, and realizes that the TAI list allocated by the MME to the user does not exceed the SGW-U service area.
  • the registration message further includes at least one of the following:
  • the SGW-U identifier the capacity weight of the SGW-U, the user type of the SGW-U service, and the service information of the SGW-U service.
  • the service area information includes: a TAI list of the SGW-U.
  • FIG. 6 is a structural block diagram 2 of a management apparatus of a service gateway according to an embodiment of the present invention. As shown in FIG. 6, the apparatus may further include:
  • the keep-alive module 62 is configured to send a keep-alive request to the SGW-U after sending an update message for updating the SGW-U to the MME;
  • the keep-alive module 62 is further configured to confirm that the SGW-U is valid when the SGW-C receives the keep-alive response of the SGW-U;
  • the keep-alive module 62 is further configured to confirm that the SGW-U fails after receiving the keep-alive response of the SGW-U, and delete the user data of the SGW-U locally in the SGW-C, and And sending, by the MME, a message for updating the SGW-U, where the message carries an identifier of the SGW-U and a failure indication.
  • FIG. 7 is a structural block diagram 3 of a management apparatus of a service gateway according to an embodiment of the present invention. As shown in FIG. 7, in addition to the module including FIG. 5, the apparatus further includes:
  • the registration module 72 is configured to receive a deregistration request of the SGW-U;
  • the registration module 72 is further configured to send a deregistration response to the SGW-U, and send a message to the MME to update the SGW-U, the message carrying the identifier of the SGW-U and a failure indication.
  • FIG. 8 is a structural block diagram of a management apparatus of a service gateway according to an embodiment of the present invention. As shown in FIG. 8, in addition to the module including FIG. 5, the apparatus further includes:
  • the selecting module 82 is configured to: after receiving the deregistration request of the SGW-U, reselect the SGW-U;
  • the selection module 82 is further configured to send the information of the SGW-C failure to the MME if the reselection fails.
  • FIG. 9 is a structural block diagram 5 of a management apparatus of a service gateway according to an embodiment of the present invention. As shown in FIG. 9, in addition to the module including FIG. 5, the apparatus further includes:
  • the deleting module 92 is configured to send a request for deleting the SGW-U to the SGW-U, and send a message for updating the SGW-U to the MME, where the message carries the identifier of the SGW-U and a failure indication.
  • FIG. 10 is a structural block diagram of a management apparatus of a service gateway according to an embodiment of the present invention.
  • the device is located in the MME.
  • the apparatus further includes:
  • the second receiving module 1002 is configured to receive an update message of the updated SGW-U sent by the SGW-C, where the update message carries the identifier of the SGW-U and/or the IP address of the SGW-U and the service of the SGW-U Regional information;
  • the allocating module 1004 is configured to allocate a TAI list to the terminal according to the service area information, where the TAI list does not exceed the area served by the SGW-U.
  • the second receiving module 1002 receives an update message of the updated SGW-U sent by the SGW-C, where the update message carries the identifier of the SGW-U and/or the IP address of the SGW-U and the SGW-U
  • the service area information the distribution module 1004 allocates a TAI list to the terminal according to the service area information, where the TAI list does not exceed the area served by the SGW-U, and solves the problem of how the MME learns the service area of the SGW-U, and implements the MME.
  • the list of TAIs assigned to the user does not exceed the SGW-U service area.
  • FIG. 11 is a structural block diagram of a management apparatus of a service gateway according to an embodiment of the present invention.
  • the apparatus further includes:
  • the update module 1102 is configured to receive a message sent by the SGW-C to update the SGW-U, where the message carries the identifier of the SGW-U and the service area information of the SGW-U.
  • a management system for a service gateway including: SGW-C, SGW-U, and MME:
  • the SGW-C receives the registration message of the SGW-U, where the registration message carries the service area information of the SGW-U;
  • the SGW-C selects an MME according to the service area information of the SGW-U, and then sends an update message for updating the SGW-U to the MME, where the update message carries the identifier of the SGW-U and the SGW-U Service area information;
  • the MME allocates a TAI list to the terminal according to the service area information, and the TAI list does not exceed the area served by the SGW-U.
  • FIG. 12 is a flowchart of interaction between a serving gateway and an MME according to an embodiment of the present invention.
  • SGW-U After the SGW-U is started, a registration request process is performed to the SGW-C, and the SGW-C and the SGW-U are associated through the process.
  • the MME can learn the service area of the SGW-U, and the process includes:
  • Step S1201 after the SGW-U is powered on, find the IP address of the SGW-C according to the pre-configuration information, and then initiate a registration process to the SGW-C, where the registration request message carries the identifier of the SGW-U, and the SGW-U The service area (such as the TAI list) and the capacity weight of the SGW-U.
  • the capacity weight of the SGW-U is used to implement load balancing of the SGW-U when the subsequent SGW-U is selected.
  • the SGW-U is only responsible for one type of user or one type of service, and the registration request message may also carry the user type or service information of the SGW-U service.
  • Step S1202 after saving the SGW-U related information, the SGW-C returns a registration response to the SGW-U.
  • Step S1203 The SGW-C finds the corresponding MME according to the TAI list of the SGW-U service, and then performs SGW-U information update to the MME, where the update message carries the identifier of the SGW-U and the area of the SGW-U service.
  • Information such as a list of TAIs.
  • the MME saves the identifier of the SGW-U and the area information of the service.
  • the information is set to the subsequent MME to allocate the TAI list to the terminal. It is necessary to ensure that the TAI list allocated to the terminal cannot exceed the area served by the SGW-U.
  • step S1204 and step S1205 the keep-alive request and the keep-alive response may also be sent between the SGW-U and the SGW-C, so that each other can be known whether the other party exists.
  • Step S1206 After the SGW-C finds that the SGW-U is invalid, the SGW-U related user data is locally deleted and the updated SGW-U information is sent to the MME, carrying the SGW-U identifier and the invalidation indication.
  • Step S1207 after the SGW-U finds that the SGW-C is invalid, the user data is deleted locally. It may be possible to look for a new SGW-C to register, and if it does not find a suitable SGW-C, it will initiate an alarm and wait for the administrator to proceed further.
  • FIG. 13 is a flow chart 2 of the interaction between the serving gateway and the MME according to the embodiment of the present invention.
  • the SGW-U initiates a deregistration process. Through this process, the SGW-U and the SGW-C cancel the association relationship.
  • the process can include:
  • the SGW-U may initiate a deregistration request to the SGW-C, carrying the SGW-U identifier.
  • Step S1302 after receiving the SGW-C, the SGW-C initiates a deregistration response to the SGW-U.
  • step S1303 the SGW-C reselects the new SGW-U for all the current users, and may initiate the SGW-U reselection process. If the SGW-C successfully selects the SGW-U, the subsequent process will use the new SGW-U.
  • Step S1304 If the reselection of the new SGW-U fails, the SGW is sent to the MME to notify the MME that the SGW has expired, and then the MME may reselect the new SGW-C. If the selection fails, the MME deactivates the user.
  • Step S1303 and step S1304 need to perform separate processing for each user of the SGW-U.
  • the SGW-C may send a separate update SGW-U information to the MME, carrying the SGW-U identifier and the invalidation indication.
  • the saved SGW-U service area information is deleted.
  • FIG 14 is a flowchart 3 of the interaction between the serving gateway and the MME according to the embodiment of the present invention.
  • the SGW-C initiates the process of deleting the SGW-U, and the process may include:
  • Step 1401 the SGW-C may also initiate a delete SGW-U request at any time;
  • Step 1402 after the SGW-U receives, the user data is deleted locally.
  • Step 1403 The SGW-C needs to initiate an update SGW-U information process to the MME. After receiving the MME, the saved SGW-U service area information is deleted.
  • the method according to the above embodiment can be implemented by means of software plus a necessary general hardware platform, and of course, by hardware, but in many cases, the former is A better implementation.
  • the technical solution of the present invention may contribute to the prior art in part or in the software product.
  • the computer software product is stored in a storage medium (such as ROM/RAM, disk, optical disk), and includes a plurality of instructions for making a terminal device (which may be a mobile phone, a computer, a server, or a network device, etc.) The methods described in various embodiments of the invention are performed.
  • each of the above modules may be implemented by software or hardware.
  • the foregoing may be implemented by, but not limited to, the foregoing modules are all located in the same processor; or, the modules are located in multiple In the processor.
  • a computer readable storage medium storing computer executable instructions that, when executed by a processor, implement a management method of any of the service gateways described above.
  • the storage medium includes, but is not limited to, an optical disk, a floppy disk, a hard disk, a rewritable memory, and the like.
  • Embodiments of the present invention also provide a storage medium.
  • the above storage medium may be arranged to store program code for performing the method steps of the above-described embodiments.
  • the storage medium is further arranged to store program code for performing the method steps of the above-described embodiments.
  • the foregoing storage medium may include, but not limited to, a USB flash drive, a Read-Only Memory (ROM), a Random Access Memory (RAM), a mobile hard disk, and a magnetic memory.
  • ROM Read-Only Memory
  • RAM Random Access Memory
  • a mobile hard disk e.g., a hard disk
  • magnetic memory e.g., a hard disk
  • the processor performs the method steps of the foregoing embodiments according to the stored program code in the storage medium.
  • modules or steps of the present application can be implemented by a general computing device, which can be concentrated on a single computing device or distributed in a network composed of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein. Perform the steps shown or described, or make them into individual integrated circuit modules, or make multiple modules or steps in them. Implemented as a single integrated circuit module. Thus, the application is not limited to any particular combination of hardware and software.
  • the embodiment of the present invention provides a method, a device, and a system for managing a service gateway, where the method may include: the SGW-C receives a registration message of the SGW-U, where the registration message carries the service of the SGW-U The area information; and/or the SGW-C sends an update message for updating the SGW-U to the MME, where the update message carries the identifier of the SGW-U and/or the IP address of the SGW-U And the service area information, where the service area information is used to indicate that the MME allocates, to the terminal, an area where the TAI list does not exceed the SGW-U service.
  • the SGW-C is configured to receive a registration message of the SGW-U, where the registration message carries the service area information of the SGW-U, and/or the SGW-C sends to the MME to update the SGW.
  • An update message of the U where the update message carries the identifier of the SGW-U and/or the IP address of the SGW-U and the service area information of the SGW-U, where the service area information is used to indicate the TAI allocated by the MME to the terminal.
  • the list does not exceed the area of the SGW-U service, and the problem of how the MME learns the service area of the SGW-U is solved, and the TAI list allocated by the MME to the user does not exceed the SGW-U service area.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Databases & Information Systems (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本文公布了一种服务网关的管理方法、装置及系统，其中，该方法包括：SGW-C接收SGW-U的注册消息，其中，该注册消息携带有该SGW-U的服务区域信息，和/或，该SGW-C向MME发送设置为更新该SGW-U的更新消息，其中，该更新消息携带该SGW-U的标识和/或SGW-U的IP地址以及该SGW-U的服务区域信息，该服务区域信息设置为指示该MME为终端分配TAI列表不超过该SGW-U服务的区域，解决了MME如何获知SGW-U的服务区域的问题，实现了MME在给用户分配的TAI列表不会超过SGW-U服务区域。

Description

服务网关的管理方法、装置及系统 技术领域
本申请涉及但不限于通信领域，具体而言，涉及一种服务网关的管理方法、装置及系统。
背景技术
图1是相关技术中4G EPS的网络架构的示意图，如图1所示，演进的分组系统(Evolved Packet System，EPS)各网元功能如下：
UE(UE Equipment)：终端，通过空口和4G基站接入核心网，并通过演进分组网络(Evolved Packet Core，EPC)网络接入业务网络。终端可以处于空闲态和连接态，当和基站建立无线资源连接(Radio Resource Connection，RRC)连接时，进入连接态，释放RRC连接时，进入空闲态。
eNodeB：4G基站，为UE提供无线接入，主要功能是进行无线资源控制和调度，并提供基站内的移动性管理。
移动性管理单元(Mobility Management Element，MME)：核心网控制面网元，主要对UE进行鉴权并签约检查。MME同时为用户选择服务网关(Serving Gateway，Serving GW)和分组域网关(Packet Data Network Gateway，PDN GW)。当用户处于空闲态时，MME可以根据保存的用户上下文，向基站发起对该用户的寻呼。MME还提供跨基站的移动性管理。
Serving GW：用户面网元，用户跨基站移动时候的锚点，并在漫游情况提供和PDN GW的漫游接口。当用户处于空闲态下时，Serving GW缓存用户数据并触发MME对用户进行寻呼。
PDN GW：用户面网元，为UE分配IP(Internet Protocol)地址，并接入业务网络。当用户移动的时候PDN GW是IP层锚点，不会发生变化，从而保证业务连续性。
在图1中，S1-MME、S11、S5/S8-C为控制面接口，基于GPRS隧道协议控制面(GPRS Tunnelling Protocol-C，GTP-C)，传输信令面数据；S1-U、S5/S8-U为用户面接口，基于GPRS隧道协议用户面(GPRS Tunnelling  Protocol-U，GTP-U)，传输用户面数据。
随着4G网络的部署，以及智能终端的的普及，运营商网络承载的数据流量急速增长，运营商面临着升级网络的压力，对于网关来说，因为控制面和转发面是合一的，因此需要一起升级，成本较大。
在相关技术中，Serving GW的控制面和转发面分离。图2是相关技术中Serving GW的控制面和转发面分离的架构示意图，如图2所示，SGW分为控制面的服务网关(SGW-C)和转发面的服务网关(SGW-U)，中间通过一个新接口交互。
SGW-C的主要功能是提供和MME以及PDN GW的控制面接口，同时控制SGW-U，一个SGW-C一般集中式部署，而SGW-U的位置可以比较灵活。一个SGW-C可以控制1个或者多个SGW-U。
SGW-U的主要功能是提供和基站以及PDN GW的用户面接口，并接受SGW-C的控制。SGW-C对SGW-U的控制主要包括请求SGW-U分配或者释放S1-U、S5/S8-U的GTP-U隧道资源。每个SGW-U都有一个服务区域，在该区域内的基站能够接入该SGW-U，一般跨服务区域的时候，会发生SGW-U重选。
SGW-U和SGW-C分离之后，MME在给用户分配跟踪区标识(Tracking Area Identity，TAI)列表的时候，需要保证TAI列表中所有的跟踪区不会超出所选的SGW-U服务区域，从而保证UE在TAI列表中的所有跟踪区内移动的时候，不需要重新选择SGW-U，MME如何获知SGW-U的服务区域尚未有解决方案。另外SGW-U和SGW-C分离之后，SGW-C如何管理SGW-U也尚未有解决方案。
发明内容
以下是对本文详细描述的主题的概述。本概述并非是为了限制权利要求的保围。
本申请提供了一种服务网关的管理方法、装置及系统。
一个方面，提供了一种服务网关的管理方法，包括：
SGW-C接收SGW-U的注册消息，其中，所述注册消息携带有所述 SGW-U的服务区域信息；和/或，
所述SGW-C向所述SGW-U所属的MME发送用于更新所述SGW-U的更新消息，其中，所述更新消息携带所述SGW-U的标识和/或SGW-U的IP地址以及所述服务区域信息，所述服务区域信息用于指示所述MME为终端分配TAI列表不超过所述SGW-U服务的区域。
优选的，所述注册消息还包括以下至少之一：
所述SGW-U的标识，所述SGW-U的容量权重，所述SGW-U服务的用户类型，所述SGW-U服务的业务信息。
优选的，所述服务区域信息包括：
所述SGW-U的TAI列表。
优选的，所述SGW-C向所述SGW-U所属的MME发送更新所述SGW-U的更新消息之后，还包括：
所述SGW-C向所述SGW-U发送保活请求；
在所述SGW-C收到所述SGW-U的保活响应的情况下，确认所述SGW-U有效；
在所述SGW-C没有收到所述SGW-U的保活响应的情况下，确认所述SGW-U失效，并在所述SGW-C的本地删除所述SGW-U的用户数据，以及向所述MME发送更新所述SGW-U的消息，所述消息携带所述SGW-U的标识和失效指示。
优选的，还包括：
所述SGW-C接收所述SGW-U的去注册请求；
所述SGW-C向所述SGW-U的发送去注册响应，以及向所述MME发送更新所述SGW-U的消息，所述消息携带所述SGW-U的标识和失效指示。
优选的，所述SGW-C接收所述SGW-U的去注册请求之后，包括：
所述SGW-C重新选择SGW-U；
在所述重新选择失败的情况下，向所述MME发送所述SGW-C失效的信息。
优选的，还包括：
所述SGW-C向所述SGW-U发送删除所述SGW-U的请求，以及向所述MME发送更新所述SGW-U的消息，所述消息携带所述SGW-U的标识和失效指示。
另一个方面，还提供了一种服务网关的管理方法，包括：
MME接收SGW-C发送的更新SGW-U的更新消息，其中，所述更新消息携带所述SGW-U的标识和/或SGW-U的IP地址以及所述SGW-U的服务区域信息；
所述MME依据所述服务区域信息为终端分配的TAI列表，其中，所述TAI列表不超过所述SGW-U服务的区域。
优选的，还包括：
所述MME接收所述SGW-C发送的更新所述SGW-U的消息，其中，所述消息携带所述SGW-U的标识和和所述SGW-U的服务区域信息。
另一个方面，还提供了一种服务网关的管理装置，位于SGW-C中，包括：
第一接收模块，设置为接收SGW-U的注册消息，其中，所述注册消息携带有所述SGW-U的服务区域信息；和/或，
发送模块，设置为向所述SGW-U所属的MME发送用于更新所述SGW-U的更新消息，其中，所述更新消息携带所述SGW-U的标识和/或SGW-U的IP地址以及所述服务区域信息，所述服务区域信息用于指示所述MME为终端分配的TAI列表不超过所述SGW-U服务的区域。
优选的，所述注册消息还包括以下至少之一：
所述SGW-U的标识，所述SGW-U的容量权重，所述SGW-U服务的用户类型，所述SGW-U服务的业务信息。
优选的，所述服务区域信息包括：
所述SGW-U的TAI列表。
优选的，还包括：
保活模块，设置为向所述SGW-U所属的MME发送更新所述SGW-U的更新消息之后，向所述SGW-U发送保活请求；以及在所述SGW-C收到所述SGW-U的保活响应的情况下，确认所述SGW-U有效；在没有收到所述SGW-U的保活响应的情况下，确认所述SGW-U失效，并在所述SGW-C的本地删除所述SGW-U的用户数据，以及向所述MME发送更新所述SGW-U的消息，所述消息携带所述SGW-U的标识和失效指示。
优选的，还包括：
注册模块，设置为接收所述SGW-U的去注册请求；以及向所述SGW-U的发送去注册响应，以及向所述MME发送更新所述SGW-U的消息，所述消息携带所述SGW-U的标识和失效指示。
优选的，还包括：
选择模块，设置为接收所述SGW-U的去注册请求之后，重新选择SGW-U；以及在所述重新选择失败的情况下，向所述MME发送所述SGW-C失效的信息。
优选的，还包括：
删除模块，设置为向所述SGW-U发送删除所述SGW-U的请求，以及向所述MME发送更新所述SGW-U的消息，所述消息携带所述SGW-U的标识和失效指示。
另一个方面，还提供了一种服务网关的管理装置，位于MME中，包括：
第二接收模块，设置为接收SGW-C发送的更新SGW-U的更新消息，其中，所述更新消息携带所述SGW-U的标识和/或SGW-U的IP地址以及所述服务区域信息；
分配模块，设置为依据所述服服务区域信息为终端分配的TAI列表，其中，所述TAI列表不超过所述SGW-U服务的区域。
优选的，还包括：
更新模块，设置为接收所述SGW-C发送的更新所述SGW-U的消息，其中，所述消息携带所述SGW-U的标识和所述SGW-U的服务区域信息。
另一个方面，还提供了一种服务网关的管理系统，包括：SGW-C，SGW-U以及MME：
所述SGW-C，设置为接收所述SGW-U的注册消息，其中，所述注册消息携带有所述SGW-U的服务区域信息；以及向所述SGW-U所属的MME发送用于更新所述SGW-U的更新消息，其中，所述更新消息携带所述SGW-U的标识以及所述服务区域信息；
所述MME，设置为依据所述服务区域信息为终端分配TAI列表，所述TAI列表不超过所述SGW-U服务的区域。
依另一个方面，还提供了一种计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令被处理器执行时实现上述任意一种服务网关的管理方法。
通过本申请，SGW-C设置为接收SGW-U的注册消息，其中，该注册消息携带有该SGW-U的服务区域信息，和/或，该SGW-C向MME发送用于更新该SGW-U的更新消息，其中，该更新消息携带该SGW-U的标识和/或SGW-U的IP地址以及该SGW-U的服务区域信息，该服务区域信息用于指示该MME为终端分配的TAI列表不超过该SGW-U服务的区域，解决了MME如何获知SGW-U的服务区域的问题，实现了MME在给用户分配的TAI列表不会超过SGW-U服务区域。
在阅读并理解了附图和详细描述后，可以明白其他方面。
附图概述
在附图中：
图1是相关技术中4G EPS的网络架构的示意图；
图2是相关技术中Serving GW的控制面和转发面分离的架构示意图；
图3是根据本发明实施例的一种服务网关的管理方法的流程图一；
图4是根据本发明实施例的一种服务网关的管理方法的流程图二；
图5是根据本发明实施例的一种服务网关的管理装置的结构框图一；
图6是根据本发明实施例的一种服务网关的管理装置的结构框图二；
图7是根据本发明实施例的一种服务网关的管理装置的结构框图三；
图8是根据本发明实施例的一种服务网关的管理装置的结构框图四；
图9是根据本发明实施例的一种服务网关的管理装置的结构框图五；
图10是根据本发明实施例的一种服务网关的管理装置的结构框图六；
图11是根据本发明实施例的一种服务网关的管理装置的结构框图七；
图12是根据本发明实施例的服务网关与MME的交互流程图一；
图13是根据本发明实施例的服务网关与MME的交互流程图二；
图14是根据本发明实施例的服务网关与MME的交互流程图三。
本发明的实施方式
下文中将参考附图并结合实施例来详细说明本发明。需要说明的是，在不冲突的情况下，本申请中的实施例及实施例中的特征可以相互组合。
需要说明的是，本发明的说明书和权利要求书及上述附图中的术语“第一”、“第二”等是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。
在本实施例中提供了一种服务网关的管理方法，图3是根据本发明实施例的一种服务网关的管理方法的流程图一，如图3所示，该流程包括如下步骤：
步骤S302，SGW-C接收SGW-U的注册消息，其中，该注册消息携带有该SGW-U的服务区域信息；和/或，
步骤S304，根据SGW-U的服务区域信息，该SGW-C确定和所述服务区域相关的移动管理单元，然后向该MME发送用于更新该SGW-U信息的更新消息，其中，该更新消息携带该SGW-U的标识和/或SGW-U的IP地址以及该服务区域信息，该服务区域信息用于指示该MME为终端分配的TAI列表不超过该SGW-U服务的区域。
通过上述步骤，SGW-C接收SGW-U的注册消息，其中，该注册消息携带有该SGW-U的服务区域信息，和/或，该SGW-C向MME发送用于更新该SGW-U的更新消息，其中，该更新消息携带该SGW-U的标识和/或SGW-U 的IP地址以及该服务区域信息，该服务区域信息用于指示该MME为终端分配的TAI列表不超出该SGW-U服务的区域，解决了MME如何获知SGW-U的服务区域的问题，实现了MME在给用户分配的TAI列表不会超出SGW-U服务区域。
在本实施例中，该注册消息还包括以下至少之一：
该SGW-U的标识，该SGW-U的容量权重，该SGW-U服务的用户类型，该SGW-U服务的业务信息。
在本实施例中，该服务区域信息可包括：
该SGW-U的TAI列表。
在本实施例中，该SGW-C向MME发送更新该SGW-U的更新消息之后，该SGW-C向该SGW-U发送保活请求；
在该SGW-C收到该SGW-U的保活响应的情况下，确认该SGW-U有效；
在该SGW-C没有收到该SGW-U的保活响应的情况下，确认该SGW-U失效，并在该SGW-C的本地删除该SGW-U的用户数据，以及向该MME发送更新该SGW-U的消息，该消息携带该SGW-U的标识和失效指示。
在本实施例中，该SGW-C接收该SGW-U的去注册请求；
该SGW-C向该SGW-U的发送去注册响应，以及向该MME发送更新该SGW-U的消息，该消息携带该SGW-U的标识和失效指示。
在本实施例中，该SGW-C接收该SGW-U的去注册请求之后，该SGW-C重新选择SGW-U；
在该重新选择失败的情况下，向该MME发送该SGW-C失效的信息。
在本实施例中，该SGW-C向该SGW-U发送删除该SGW-U的请求，以及向该MME发送更新该SGW-U的消息，该消息携带该SGW-U的标识和失效指示。
在本实施例中还提供了一种服务网关的管理方法，图4是根据本发明实施例的一种服务网关的管理方法的流程图二，如图4所示，该流程包括如下 步骤：
步骤S402，MME接收SGW-C发送的更新SGW-U的更新消息，其中，该更新消息携带该SGW-U的标识和/或SGW-U的IP地址以及该SGW-U的服务区域信息；
步骤S404，该MME依据该服务区域信息给终端分配TAI列表，其中，该TAI列表不超过该SGW-U服务的区域。
通过上述步骤，MME接收SGW-C发送的更新SGW-U的更新消息，其中，该更新消息携带该SGW-U的标识和/或SGW-U的IP地址以及该SGW-U的服务区域信息，该MME依据该服务区域信息给终端分配TAI列表，其中，该TAI不超出该SGW-U服务的区域，解决了MME如何获知SGW-U的服务区域的问题，实现了MME在给用户分配的TAI列表不会超过SGW-U服务区域。
在本实施例中，该MME接收该SGW-C发送的更新该SGW-U的消息，其中，该消息携带该SGW-U的标识和该SGW-U的服务区域信息。
在本实施例中还提供了一种服务网关的管理装置，该装置用于实现上述实施例及优选实施方式，已经进行过说明的不再赘述。如以下所使用的，术语“模块”可以实现预定功能的软件和/或硬件的组合。尽管以下实施例所描述的装置较佳地以软件来实现，但是硬件，或者软件和硬件的组合的实现也是可能并被构想的。
图5是根据本发明实施例的一种服务网关的管理装置的结构框图一，如图5所示，该装置位于SGW-C中，包括
第一接收模块52，设置为接收SGW-U的注册消息，其中，该注册消息携带有该SGW-U的服务区域信息；和/或，
发送模块54，设置为向选择的MME发送用于更新该SGW-U的更新消息，其中，该更新消息携带该SGW-U的标识和/或SGW-U的IP地址以及该SGW-U的服务区域信息，该服务区域信息用于指示该MME为终端分配TAI列表不超过该SGW-U服务的区域。
通过上述装置，第一接收模块52接收SGW-U的注册消息，发送模块54 向MME发送用于更新该SGW-U的更新消息，解决了MME如何获知SGW-U的服务区域的问题，实现了MME在给用户分配的TAI列表不会超过SGW-U服务区域。
在本实施例中，该注册消息还包括以下至少之一：
该SGW-U的标识，该SGW-U的容量权重，该SGW-U服务的用户类型，该SGW-U服务的业务信息。
在本实施例中，该服务区域信息包括：该SGW-U的TAI列表。
图6是根据本发明实施例的一种服务网关的管理装置的结构框图二，如图6所示，除了包括图5的模块，该装置还可以包括：
保活模块62，设置为向MME发送更新该SGW-U的更新消息之后，向该SGW-U发送保活请求；
该保活模块62，还设置为在该SGW-C收到该SGW-U的保活响应的情况下，确认该SGW-U有效；
该保活模块62，还设置为在没有收到该SGW-U的保活响应的情况下，确认该SGW-U失效，并在该SGW-C的本地删除该SGW-U的用户数据，以及向该MME发送更新该SGW-U的消息，该消息携带该SGW-U的标识和失效指示。
图7是根据本发明实施例的一种服务网关的管理装置的结构框图三，如图7所示，除了包括图5的模块，该装置还包括：
注册模块72，设置为接收该SGW-U的去注册请求；
该注册模块72，还设置为向该SGW-U的发送去注册响应，以及向该MME发送更新该SGW-U的消息，该消息携带该SGW-U的标识和失效指示。
图8是根据本发明实施例的一种服务网关的管理装置的结构框图四，如图8所示，除了包括图5的模块，该装置还包括：
选择模块82，设置为接收该SGW-U的去注册请求之后，重新选择SGW-U；
该选择模块82，还设置为在该重新选择失败的情况下，向该MME发送该SGW-C失效的信息。
图9是根据本发明实施例的一种服务网关的管理装置的结构框图五，如图9所示，除了包括图5的模块，该装置还包括：
删除模块92，设置为向该SGW-U发送删除该SGW-U的请求，以及向该MME发送更新该SGW-U的消息，该消息携带该SGW-U的标识和失效指示。
图10是根据本发明实施例的一种服务网关的管理装置的结构框图六，位于MME中，如图10所示，该装置还包括：
第二接收模块1002，设置为接收SGW-C发送的更新SGW-U的更新消息，其中，该更新消息携带该SGW-U的标识和/或SGW-U的IP地址以及该SGW-U的服务区域信息；
分配模块1004，设置为依据该服务区域信息给终端分配TAI列表，其中，该TAI列表不超过该SGW-U服务的区域。
通过上述装置，第二接收模块1002接收SGW-C发送的更新SGW-U的更新消息，其中，该更新消息携带该SGW-U的标识和/或SGW-U的IP地址以及该SGW-U的服务区域信息，分配模块1004依据该服务区域信息给终端分配TAI列表，其中，该TAI列表不超过该SGW-U服务的区域，解决了MME如何获知SGW-U的服务区域的问题，实现了MME在给用户分配的TAI列表不会超过SGW-U服务区域。
图11是根据本发明实施例的一种服务网关的管理装置的结构框图七，除了包括图10的模块外，该装置还包括：
更新模块1102，设置为接收该SGW-C发送的更新该SGW-U的消息，其中，该消息携带该SGW-U的标识和所述SGW-U的服务区域信息。
在本发明的另一个实施例中，还提供了一种服务网关的管理系统，包括：SGW-C，SGW-U以及MME：
该SGW-C接收该SGW-U的注册消息，其中，该注册消息携带有该SGW-U的服务区域信息；
该SGW-C根据该SGW-U的服务区域信息，选择MME，然后向该MME发送用于更新该SGW-U的更新消息，其中，该更新消息携带该SGW-U的标识以及该SGW-U的服务区域信息；
该MME依据该服务区域信息为终端分配TAI列表，该TAI列表不超过该SGW-U服务的区域。
下面结合优选实施例和实施方式对本发明进行详细说明。
图12是根据本发明实施例的服务网关与MME的交互流程图一，SGW-U启动之后，向SGW-C进行注册请求过程，通过该过程，实现了SGW-C和SGW-U相关联，并且MME可以获知SGW-U的服务区域，该流程包括：
步骤S1201，SGW-U上电之后，根据预配置信息，找到SGW-C的IP地址，然后向SGW-C发起注册过程，该注册请求消息中带有SGW-U的标识、该SGW-U的服务区域(比如TAI列表)、SGW-U的容量权重。SGW-U的容量权重用于后续SGW-U选择的时候实现SGW-U的负荷均衡。在一些时候，该SGW-U只负责一种类型的用户或者一种类型的业务，那么该注册请求消息中还可能带有该SGW-U服务的用户类型或者业务信息。
步骤S1202，SGW-C保存该SGW-U的相关信息之后，向SGW-U返回注册响应。
步骤S1203，SGW-C根据该SGW-U服务的TAI列表，找到对应MME，然后向该MME进行SGW-U信息更新，该更新消息里面带有SGW-U的标识以及该SGW-U服务的区域信息，比如TAI列表。MME保存SGW-U的标识和服务的区域信息，该信息设置为后续MME为终端分配TAI列表，需要保证给终端所分配的TAI列表不能超过SGW-U服务的区域。
步骤S1204和步骤S1205，SGW-U和SGW-C之间还可以相互发送保活请求和保活响应，这样可以相互知道对方是否存在。
步骤S1206，当SGW-C发现SGW-U失效之后，将本地删除该SGW-U相关的用户数据并向MME发送更新SGW-U信息，携带有SGW-U标识和失效指示。
步骤S1207，当SGW-U发现SGW-C失效之后，将本地删除用户数据然 后可能寻找新的SGW-C进行注册，如果找不到合适的SGW-C则发起告警并等待管理员进一步操作。
图13是根据本发明实施例的服务网关与MME的交互流程图二，如图13所示，SGW-U发起的去注册过程示意图，通过该过程，SGW-U和SGW-C取消关联关系，该流程可包括：
步骤S1301，SGW-U可以向SGW-C发起去注册请求，携带有SGW-U标识。
步骤S1302，SGW-C收到之后向SGW-U发起去注册响应。
步骤S1303，SGW-C为当前所有用户重新选择新的SGW-U，可能发起SGW-U重选过程，如果SGW-C成功选到SGW-U，则后续过程将使用新的SGW-U。
步骤S1304，如果重新选择新的SGW-U失败，则向MME发送SGW通知请求，通知MME该SGW已经失效，然后MME可能重新选择新的SGW-C，如果选择失败，则MME去活该用户。
步骤S1303和步骤S1304需要针对每个该SGW-U的用户进行分别处理。另外在步骤402之后，SGW-C可能向MME发送单独的更新SGW-U信息，携带有SGW-U标识和失效指示。MME收到之后，删除保存的该SGW-U服务区域信息。
图14是根据本发明实施例的服务网关与MME的交互流程图三，如图14所示，SGW-C发起删除SGW-U过程，该流程可包括：
步骤1401，SGW-C在任何时候也可以发起删除SGW-U请求；
步骤1402，SGW-U收到之后，将本地删除用户数据。
步骤1403，SGW-C需要向MME发起更新SGW-U信息过程，MME收到之后，删除保存的该SGW-U服务区域信息。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到根据上述实施例的方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本发明的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的 形式体现出来，该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台终端设备(可以是手机，计算机，服务器，或者网络设备等)执行本发明各个实施例所述的方法。
需要说明的是，上述各个模块是可以通过软件或硬件来实现的，对于后者，可以通过以下方式实现，但不限于此：上述模块均位于同一处理器中；或者，上述模块分别位于多个处理器中。
在另外一个实施例中，还提供了一种计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令被处理器执行时实现上述任意一种服务网关的管理方法。该存储介质包括但不限于：光盘、软盘、硬盘、可擦写存储器等。
本发明的实施例还提供了一种存储介质。可选地，在本实施例中，上述存储介质可以被设置为存储用于执行上述实施例的方法步骤的程序代码。
可选地，存储介质还被设置为存储用于执行上述实施例的方法步骤的程序代码。
可选地，在本实施例中，上述存储介质可以包括但不限于：U盘、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、移动硬盘、磁碟或者光盘等各种可以存储程序代码的介质。
可选地，在本实施例中，处理器根据存储介质中已存储的程序代码执行上述实施例的方法步骤。
可选地，本实施例中的具体示例可以参考上述实施例及可选实施方式中所描述的示例，本实施例在此不再赘述。
显然，本领域的技术人员应该明白，上述的本申请的各模块或各步骤可以用通用的计算装置来实现，它们可以集中在单个的计算装置上，或者分布在多个计算装置所组成的网络上，可选地，它们可以用计算装置可执行的程序代码来实现，从而，可以将它们存储在存储装置中由计算装置来执行，并且在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤，或者将它们分别制作成各个集成电路模块，或者将它们中的多个模块或步骤制作 成单个集成电路模块来实现。这样，本申请不限制于任何特定的硬件和软件结合。
以上所述仅为本申请的优选实施例而已，并不用于限制本申请，对于本领域的技术人员来说，本申请可以有各种更改和变化。凡在本申请的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本申请的保护范围之内。
工业实用性
本发明实施例提供了一种服务网关的管理方法及装置、系统，其中，方法可包括：SGW-C接收SGW-U的注册消息，其中，所述注册消息携带有所述SGW-U的服务区域信息；和/或，所述SGW-C向MME发送用于更新所述SGW-U的更新消息，其中，所述更新消息携带所述SGW-U的标识和/或SGW-U的IP地址以及所述服务区域信息，所述服务区域信息用于指示所述MME为终端分配TAI列表不超过所述SGW-U服务的区域。
本申请中，SGW-C设置为接收SGW-U的注册消息，其中，该注册消息携带有该SGW-U的服务区域信息，和/或，该SGW-C向MME发送用于更新该SGW-U的更新消息，其中，该更新消息携带该SGW-U的标识和/或SGW-U的IP地址以及该SGW-U的服务区域信息，该服务区域信息用于指示该MME为终端分配的TAI列表不超过该SGW-U服务的区域，解决了MME如何获知SGW-U的服务区域的问题，实现了MME在给用户分配的TAI列表不会超过SGW-U服务区域。

Claims (20)

  1. 一种服务网关的管理方法，包括：
    控制面的服务网关SGW-C接收转发面的服务网关SGW-U的注册消息，其中，所述注册消息携带有所述SGW-U的服务区域信息；和/或，
    所述SGW-C向移动性管理单元MME发送用于更新所述SGW-U的更新消息，其中，所述更新消息携带所述SGW-U的标识和/或SGW-U的IP地址以及所述服务区域信息，所述服务区域信息用于指示所述MME为终端分配跟踪区标识TAI列表不超过所述SGW-U服务的区域。
  2. 根据权利要求1所述的方法，其中，所述注册消息还包括以下至少之一：
    所述SGW-U的标识，所述SGW-U的容量权重，所述SGW-U服务的用户类型，所述SGW-U服务的业务信息。
  3. 根据权利要求1所述的方法，其中，所述服务区域信息包括：
    所述SGW-U的TAI列表。
  4. 根据权利要求1所述的方法，所述SGW-C向所述SGW-U所属的MME发送更新所述SGW-U的更新消息之后，还包括：
    所述SGW-C向所述SGW-U发送保活请求；
    在所述SGW-C收到所述SGW-U的保活响应的情况下，确认所述SGW-U有效；
    在所述SGW-C没有收到所述SGW-U的保活响应的情况下，确认所述SGW-U失效，并在所述SGW-C的本地删除所述SGW-U的用户数据，以及向所述MME发送更新所述SGW-U的消息，所述消息携带所述SGW-U的标识和失效指示。
  5. 根据权利要求1所述的方法，还包括：
    所述SGW-C接收所述SGW-U的去注册请求；
    所述SGW-C向所述SGW-U的发送去注册响应，以及向所述MME发送更新所述SGW-U的消息，所述消息携带所述SGW-U的标识和失效指示。
  6. 根据权利要求5所述的方法，所述SGW-C接收所述SGW-U的去注册请求之后，包括：
    所述SGW-C重新选择SGW-U；
    在所述重新选择失败的情况下，向所述MME发送所述SGW-C失效的信息。
  7. 根据权利要求1所述的方法，还包括：
    所述SGW-C向所述SGW-U发送删除所述SGW-U的请求，以及向所述MME发送更新所述SGW-U的消息，所述消息携带所述SGW-U的标识和失效指示。
  8. 一种服务网关的管理方法，包括：
    移动性管理单元MME接收控制面的服务网关SGW-C发送的更新转发面的服务网关SGW-U的更新消息，其中，所述更新消息携带所述SGW-U的标识和/或SGW-U的IP地址以及所述服务区域信息；
    所述MME依据所述服务区域信息为终端分配跟踪区标识TAI列表，其中，所述TAI列表不超过所述SGW-U服务的区域。
  9. 根据权利要求8所述的方法，还包括：
    所述MME接收所述SGW-C发送的更新所述SGW-U的消息，其中，所述消息携带所述SGW-U的标识和所述SGW-U的服务区域信息。
  10. 一种服务网关的管理装置，位于控制面的服务网关SGW-C中，包括：
    第一接收模块，设置为接收转发面的服务网关SGW-U的注册消息，其中，所述注册消息携带有所述SGW-U的服务区域信息；和/或，
    发送模块，设置为向所述SGW-U所属的移动性管理单元MME发送用于更新所述SGW-U的更新消息，其中，所述更新消息携带所述SGW-U的标识和/或SGW-U的IP地址以及所述服务区域信息，所述服务区域信息用于指示所述MME为终端分配的跟踪区标识TAI列表不超过所述SGW-U服务的区域。
  11. 根据权利要求10所述的装置，其中，所述注册消息还包括以下至少之一：
    所述SGW-U的标识，所述SGW-U的容量权重，所述SGW-U服务的用户类型，所述SGW-U服务的业务信息。
  12. 根据权利要求10所述的装置，其中，所述服务区域信息包括：
    所述SGW-U的TAI列表。
  13. 根据权利要求10所述的装置，还包括：
    保活模块，设置为向所述SGW-U所属的MME发送更新所述SGW-U的更新消息之后，向所述SGW-U发送保活请求；以及在所述SGW-C收到所述SGW-U的保活响应的情况下，确认所述SGW-U有效；在没有收到所述SGW-U的保活响应的情况下，确认所述SGW-U失效，并在所述SGW-C的本地删除所述SGW-U的用户数据，以及向所述MME发送更新所述SGW-U的消息，所述消息携带所述SGW-U的标识和失效指示。
  14. 根据权利要求10所述的装置，还包括：
    注册模块，设置为接收所述SGW-U的去注册请求；以及向所述SGW-U的发送去注册响应，以及向所述MME发送更新所述SGW-U的消息，所述消息携带所述SGW-U的标识和失效指示。
  15. 根据权利要求10所述的装置，还包括：
    选择模块，设置为接收所述SGW-U的去注册请求之后，重新选择SGW-U；以及在所述重新选择失败的情况下，向所述MME发送所述SGW-C失效的信息。
  16. 根据权利要求10所述的装置，还包括：
    删除模块，设置为向所述SGW-U发送删除所述SGW-U的请求，以及向所述MME发送更新所述SGW-U的消息，所述消息携带所述SGW-U的标识和失效指示。
  17. 一种服务网关的管理装置，位于移动性管理单元MME中，包括：
    第二接收模块，设置为接收控制面的服务网关SGW-C发送的更新转发 面的服务网关SGW-U的更新消息，其中，所述更新消息携带所述SGW-U的标识和/或SGW-U的IP地址以及所述服务区域信息；
    分配模块，设置为依据所述服务区域信息为终端分配跟踪区标识TAI列表，其中，所述TAI列表不超过所述SGW-U服务的区域。
  18. 根据权利要求17所述的装置，还包括：
    更新模块，设置为接收所述SGW-C发送的更新所述SGW-U的消息，其中，所述消息携带所述SGW-U的标识和所述SGW-U的服务区域信息。
  19. 一种服务网关的管理系统，包括：控制面的服务网关SGW-C，转发面的服务网关SGW-U以及移动性管理单元MME：
    所述SGW-C，设置为接收所述SGW-U的注册消息，其中，所述注册消息携带有所述SGW-U的服务区域信息；以及向所述SGW-U所属的MME发送用于更新所述SGW-U的更新消息；
    所述MME，设置为依据所述服务区域信息为终端分配跟踪区标识TAI列表，所述TAI列表不超过所述SGW-U服务的区域。
  20. 一种计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令被处理器执行时实现权利要求1至7任一项所述服务网关的管理方法方法或权利要求8所述服务网关的管理方法。
PCT/CN2016/093252 2015-11-06 2016-08-04 服务网关的管理方法、装置及系统 WO2017076087A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201510752879.XA CN106686569A (zh) 2015-11-06 2015-11-06 服务网关的管理方法、装置及系统
CN201510752879.X 2015-11-06

Publications (1)

Publication Number Publication Date
WO2017076087A1 true WO2017076087A1 (zh) 2017-05-11

Family

ID=58661539

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/093252 WO2017076087A1 (zh) 2015-11-06 2016-08-04 服务网关的管理方法、装置及系统

Country Status (2)

Country Link
CN (1) CN106686569A (zh)
WO (1) WO2017076087A1 (zh)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109246778B (zh) * 2017-06-16 2020-12-04 华为技术有限公司 功能网元的选择方法及相关设备
WO2022036626A1 (en) * 2020-08-20 2022-02-24 Telefonaktiebolaget Lm Ericsson (Publ) Methods, nodes and computer readable media for sgw-u selection

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101360331A (zh) * 2007-08-02 2009-02-04 华为技术有限公司 一种服务网关信息更新方法、系统及装置
CN102523570A (zh) * 2006-06-15 2012-06-27 华为技术有限公司 一种网络侧用户面实体选择方法
WO2014000266A1 (zh) * 2012-06-29 2014-01-03 华为技术有限公司 信息处理方法、转发面设备和控制面设备
CN104995878A (zh) * 2013-12-31 2015-10-21 华为技术有限公司 一种报文传输方法、设备及通信系统

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102523570A (zh) * 2006-06-15 2012-06-27 华为技术有限公司 一种网络侧用户面实体选择方法
CN101360331A (zh) * 2007-08-02 2009-02-04 华为技术有限公司 一种服务网关信息更新方法、系统及装置
WO2014000266A1 (zh) * 2012-06-29 2014-01-03 华为技术有限公司 信息处理方法、转发面设备和控制面设备
CN104995878A (zh) * 2013-12-31 2015-10-21 华为技术有限公司 一种报文传输方法、设备及通信系统

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
ZTE ET AL.: "Solution to maintain existing TAI list allocation support", 3GPP SA WG2 MEETING #112 S2-153902, 20 November 2015 (2015-11-20), XP051013986 *

Also Published As

Publication number Publication date
CN106686569A (zh) 2017-05-17

Similar Documents

Publication Publication Date Title
JP6855575B2 (ja) ネットワーク間変更方法および装置、ならびに関連デバイス
US10911990B2 (en) Network handover method and related device
WO2018177277A1 (zh) 网络系统中状态信息的处理方法、装置及存储介质
US10455489B2 (en) Method for supporting PDN GW selection
CN107318176B (zh) 恢复标识的获取、发送方法及装置、ue、接入网设备
WO2017076088A1 (zh) 服务网关的管理方法及装置
KR101519547B1 (ko) 사용자 장비의 위치 정보를 갱신하기 위한 방법 및 장치
US8913588B2 (en) Handover method, communication device and communication system
JP6727341B2 (ja) 通信制御方法および関連するネットワーク要素
JP2020504566A (ja) 移動通信システムでアクセス及び移動性管理機能を選択するための方法及び装置
JP6637418B2 (ja) 第１のコアネットワーク装置、基地局装置及び通信制御方法
JP2019520765A (ja) 無線通信システムにおけるネットワークスライスベースのｎｒのためのセル特定手順を実行する方法及び装置
US20110019644A1 (en) Method for switching session of user equipment in wireless communication system and system employing the same
CN107888498A (zh) 实现用户面功能管理的方法及装置和网元及装置
CN106028471A (zh) 用于在lte系统中的小数据传输的永久在线的承载
WO2018145670A1 (zh) 基站的切换方法、系统和存储介质
US20170318613A1 (en) Base station device, position management device, terminal device, and control method
US20220166703A1 (en) Apparatus, method, and computer program
CN101677470A (zh) 服务请求的处理方法、装置及系统
EP2497287A1 (en) Node selection in a communication network
WO2018059401A1 (zh) 网络切换方法、装置及系统，网络接入方法及装置
WO2016180018A1 (zh) 一种接入方法及相应的接入节点、终端和通信网络
JPWO2015105183A1 (ja) 通信制御方法、位置管理装置、基地局装置、端末装置および通信システム
CN114731723A (zh) 一种通信方法及装置
JP6751717B2 (ja) 無線通信システム、ゲートウェイ装置、移動管理エンティティ及び通信制御方法

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: 16861356

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: 16861356

Country of ref document: EP

Kind code of ref document: A1