WO2017193348A1 - 访问资源的方法、装置和系统 - Google Patents

访问资源的方法、装置和系统 Download PDF

Info

Publication number
WO2017193348A1
WO2017193348A1 PCT/CN2016/081921 CN2016081921W WO2017193348A1 WO 2017193348 A1 WO2017193348 A1 WO 2017193348A1 CN 2016081921 W CN2016081921 W CN 2016081921W WO 2017193348 A1 WO2017193348 A1 WO 2017193348A1
Authority
WO
WIPO (PCT)
Prior art keywords
gateway
bearer
packet
dedicated bearer
request
Prior art date
Application number
PCT/CN2016/081921
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 CN201680085637.2A priority Critical patent/CN109076625A/zh
Priority to EP16901303.4A priority patent/EP3451785A4/en
Priority to PCT/CN2016/081921 priority patent/WO2017193348A1/zh
Publication of WO2017193348A1 publication Critical patent/WO2017193348A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/22—Manipulation of transport tunnels
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1095—Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/56—Provisioning of proxy services
    • H04L67/563—Data redirection of data network streams
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/56—Provisioning of proxy services
    • H04L67/568—Storing data temporarily at an intermediate stage, e.g. caching
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/12—Reselecting a serving backbone network switching or routing node
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/16—Gateway arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/16—Interfaces between hierarchically similar devices
    • H04W92/24—Interfaces between hierarchically similar devices between backbone network devices

Definitions

  • the present invention relates to the field of communications, and in particular, to a method, device and system for accessing resources.
  • a Content Delivery Network has a cache server deployed at a gateway at various edges, wherein the cache server can cache the remote server. resource of.
  • the user equipment User Equipment, UE
  • SGW Serving Gateway
  • PGW Packet Data Network Gateway
  • the UE In the case of a single packet data network (PDN) connection, the UE is connected to the external network through a certain PGW (for example, PGW1), and the resources that the UE needs to access are stored in another PGW deployed outside the PGW1 (for example, When the server at the PGW2) needs to establish a connection with the PGW2, the PGW1 acquires the resource through the PGW2, and then the PGW1 sends the resource to the UE.
  • PGW packet data network
  • the invention provides a method for accessing resources, a service gateway, a packet gateway, a mobility management network element and a system, so as to avoid route detour of the access path and improve the efficiency of the UE accessing resources.
  • the embodiment of the present invention provides a method for accessing a resource, including: the serving gateway receives an IP packet of the UE, where the IP packet carries an IP address of the target server, where the target server stores the resource to be accessed by the UE.
  • the service gateway and the first packet gateway have a first bearer corresponding to the UE; the serving gateway determines a second packet gateway corresponding to the target server according to the IP address; and determines a correspondence between the serving gateway and the second packet gateway.
  • the second bearer of the UE; the access request of the UE is transmitted by the second bearer, and the access request is used to request access to the resource stored in the target server.
  • the second gateway gateway corresponding to the target server may further determine the second The bearer is transmitted and the access request of the UE is transmitted through the second bearer to access the resource stored in the target server. Therefore, the solution provided by the embodiment of the present invention can avoid route detour of the access path, so as to improve the efficiency of the UE accessing resources.
  • the serving gateway and the second grouping can be determined in one of the following ways:
  • the serving gateway determines the second bearer from the at least two existing bearers, where the at least two existing bearers are respectively the serving gateway and the at least two groups The bearer corresponding to the UE between the gateways.
  • the serving gateway sends a bearer setup request to the second packet gateway, where the bearer setup request is used to establish a second bearer.
  • the second packet gateway establishes the second bearer.
  • the second packet gateway may also send a bearer setup response message to the serving gateway.
  • the serving gateway may send a bearer setup request to the second packet gateway according to the indication of the mobility management network element or the first packet gateway.
  • the service gateway receives an indication message sent by the mobility management network element or the first packet gateway, where the indication message carries an IP address of the second packet gateway, where the indication message is used to indicate that the service gateway and the second packet gateway are established.
  • Second bearer Therefore, the serving gateway may determine the IP address of the second packet gateway by using the mobility management network element or the indication message sent by the first packet gateway, and establish the second bearer in advance under the indication of the indication message, thereby saving the time for the UE to access the resource.
  • the access request of the UE may be transmitted through the second bearer by: the serving gateway sending the access request through the second packet gateway; and the second packet gateway receiving the access of the UE sent by the serving gateway through the second bearer
  • the response message can also be replied to the service gateway to complete the response process.
  • the resources stored in the target server may be transmitted between the serving gateway and the second packet gateway through the second bearer.
  • a dedicated bearer corresponding to the UE between the serving gateway and the second packet gateway may also be established.
  • the second packet gateway may send a dedicated bearer setup request to the serving gateway, where the dedicated bearer setup request is used to establish a first dedicated bearer corresponding to the UE between the serving gateway and the second packet gateway; the serving gateway receives the dedicated bearer setup After the request, the first dedicated bearer is established according to the dedicated bearer setup request; and the serving gateway determines the second dedicated bearer between the serving gateway and the UE.
  • the serving gateway may determine the second dedicated bearer between the serving gateway and the UE by: the serving gateway determines that there is a dedicated bearer between the serving gateway and the UE, and determines the dedicated bearer as the second dedicated bearer; or, the service The gateway determines that there is no dedicated bearer between the serving gateway and the UE, and establishes the second dedicated bearer.
  • the first dedicated bearer and the second dedicated bearer transmission resource can be utilized to meet the transmission requirements of services having different Quality of Service (QoS) requirements.
  • QoS Quality of Service
  • the dedicated bearer can be used as the second dedicated bearer, and no other bearers need to be established, so that the utilization of the bearer resources can be improved to save network resources.
  • the first dedicated bearer between the serving gateway and the second packet gateway can also be modified.
  • the second packet gateway may send a dedicated bearer modification request to the serving gateway, the dedicated bearer modification request is used to request to modify the first dedicated bearer; the serving gateway receives the dedicated bearer repair After the request is changed, the first dedicated bearer is modified according to the dedicated bearer modification request; and the serving gateway determines that there is a dedicated bearer corresponding to the UE between the serving gateway and other packet gateways other than the second packet gateway, and modifies the serving gateway and the second A dedicated bearer between other packet gateways other than the packet gateway. Therefore, the serving gateway can modify the dedicated bearer between the serving gateway and other packet gateways other than the second packet gateway to modify the UE and the first dedicated bearer between the second packet gateway. Communication of dedicated bearers between other packet gateways.
  • the first dedicated bearer between the serving gateway and the second packet gateway may also be deleted.
  • the second packet gateway may send a dedicated bearer deletion request to the serving gateway, where the dedicated bearer deletion request is used to request to delete the first dedicated bearer; after receiving the dedicated bearer deletion request, the serving gateway deletes the first dedicated bearer according to the dedicated bearer deletion request. And, the serving gateway determines that there is no dedicated bearer corresponding to the UE between the serving gateway and other packet gateways other than the second packet gateway, and deletes the second dedicated bearer.
  • the serving gateway deletes the first dedicated bearer between the serving gateway and the second packet gateway, it may determine whether there is a dedicated bearer corresponding to the UE between the serving gateway and the other packet gateway, and if there is a dedicated bearer, the service The gateway does not delete the second dedicated bearer between the serving gateway and the UE to ensure normal communication of the dedicated bearer between the UE and other packet gateways; if there is no dedicated bearer, the second dedicated bearer may be deleted to release the bearer resources. .
  • the target server may be a service server or a cache server.
  • the second packet gateway and the target server may be located at the same node.
  • the serving gateway may be an SGW or a Serving General Packet Radio Service Support Node (SGSN), and the first packet gateway and the second packet gateway may be a PGW or a (Gateway General Packet Radio Service Support). Node, GGSN).
  • SGSN Serving General Packet Radio Service Support Node
  • GGSN Gateway General Packet Radio Service Support Node
  • an embodiment of the present invention provides a service gateway, which has a function of implementing a service gateway behavior in the above method design.
  • 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 serving gateway includes a processing unit and a communication unit, the processing unit being configured to support the serving gateway to perform the corresponding functions in the above methods.
  • the communication unit is configured to support communication between the serving gateway and other devices.
  • the serving gateway may also include a storage unit for coupling with the processing unit that holds program instructions and data necessary for the service gateway.
  • the processing unit can be a processor
  • the communication unit can be a communication interface
  • the storage unit can be a memory.
  • an embodiment of the present invention provides a packet gateway, which may be referred to as a second packet gateway, and the second packet gateway has a function of implementing a second packet gateway behavior in the foregoing method design.
  • 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 second packet gateway includes a processing unit and a communication unit, the processing unit being configured to support the second packet gateway to perform the corresponding function in the above method.
  • the communication unit is configured to support communication between the second packet gateway and other devices.
  • the second packet gateway may further comprise a storage unit for coupling with the processing unit, which stores program instructions and data necessary for the second packet gateway.
  • the processing unit can be a processor
  • the communication unit can be a communication interface
  • the storage unit can be a memory.
  • an embodiment of the present invention provides a mobility management network element, where the mobility management network element has a function of implementing mobility management network element behavior in the foregoing method design.
  • 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 serving gateway includes a processing unit and a communication unit, the processing unit being configured to support the serving gateway to perform the corresponding functions in the above methods.
  • the communication unit is configured to support communication between the mobility management network element and other devices.
  • the mobility management network element may further include a storage unit for coupling with the processing unit, which stores program instructions and data necessary for the mobility management network element.
  • the processing unit can be a processor
  • the communication unit can be a communication interface
  • the storage unit can be a memory.
  • an embodiment of the present invention provides a communication system, where the system includes the serving gateway and the second packet gateway according to the foregoing aspect; or the system includes the service gateway, the second packet gateway, and mobility management according to the foregoing aspect.
  • Network element the system includes the serving gateway and the second packet gateway according to the foregoing aspect; or the system includes the service gateway, the second packet gateway, and mobility management according to the foregoing aspect.
  • an embodiment of the present invention provides a computer storage medium for storing computer software instructions for use by the service gateway, 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 in the second packet gateway, which includes 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 in the mobility management network element, including a program designed to perform the above aspects.
  • the serving gateway may receive the IP packet of the UE. Determining, by the IP address of the target server carried in the IP packet, a second packet gateway corresponding to the target server, determining a second bearer corresponding to the UE between the serving gateway and the second packet gateway, and transmitting the UE by using the second bearer Request, the access request is used to request access to resources stored in the target server. Therefore, the solution provided by the embodiment of the present invention can avoid the path of accessing the path. It is backed up to improve the efficiency of UE access to resources.
  • FIG. 1 is a schematic diagram of a possible application scenario of an embodiment of the present invention
  • FIG. 2 is a schematic diagram of a possible system architecture of an application according to an embodiment of the present invention.
  • FIG. 3 is a schematic flowchart of a method for accessing resources according to an embodiment of the present invention.
  • FIG. 4 is a schematic diagram of communication of another method for accessing resources according to an embodiment of the present invention.
  • FIG. 5 is a schematic diagram of communication of another method for accessing resources according to an embodiment of the present invention.
  • FIG. 6 is a schematic diagram of communication of another method for accessing resources according to an embodiment of the present invention.
  • FIG. 7 is a schematic diagram of communication of a method for establishing a dedicated bearer according to an embodiment of the present invention.
  • FIG. 8 is a schematic diagram of communication of a method for modifying a dedicated bearer according to an embodiment of the present invention.
  • FIG. 9 is a schematic diagram of communication of a method for deleting a dedicated bearer according to an embodiment of the present invention.
  • FIG. 10A is a schematic structural diagram of a service gateway according to an embodiment of the present disclosure.
  • FIG. 10B is a schematic structural diagram of another service gateway according to an embodiment of the present disclosure.
  • 11A is a schematic structural diagram of a packet gateway according to an embodiment of the present invention.
  • FIG. 11B is a schematic structural diagram of another packet gateway according to an embodiment of the present disclosure.
  • FIG. 12A is a schematic structural diagram of a mobility management network element provided by an implementation of the present invention.
  • FIG. 12B is a schematic structural diagram of another mobility management network element according to an embodiment of the present invention.
  • the network architecture and the service scenario described in the embodiments of the present invention are for the purpose of more clearly illustrating the technical solutions of the embodiments of the present invention, and are not limited to the technical solutions provided by the embodiments of the present invention.
  • the technical solutions provided by the embodiments of the present invention are equally applicable to similar technical problems.
  • the UE accesses an operator's Internet Protocol (IP) service network through a Radio Access Network (RAN) and a Core Network (CN), such as a multimedia subsystem (IP Multimedia).
  • IP Internet Protocol
  • RAN Radio Access Network
  • CN Core Network
  • IP Multimedia multimedia subsystem
  • IMS IP Multimedia System
  • PSS Packet Switched Streaming Service
  • LTE Long Term Evolution
  • FDMA Frequency Division Multiple Access
  • TDMA Time Division Multiple Access
  • OFDMA Orthogonal Frequency Division Multiple Access
  • SC-FDMA Single Carrier Frequency Division Multiple Access
  • LTE system Long Term Evolution
  • 5G 5th Generation
  • E-UTRAN Evolved Universal Terrestrial Radio Access Network
  • EPC Evolved Packet Core
  • the user equipment UE related to the embodiments of the present invention may include various handheld devices, in-vehicle devices, wearable devices, computing devices, or other processing devices connected to the wireless modem, and various forms of user equipment ( User Equipment, UE), mobile station (MS), terminal, terminal device, and the like.
  • User Equipment User Equipment
  • MS mobile station
  • terminal terminal device
  • a base station BS according to an embodiment of the present invention is a device deployed in a radio access network to provide a wireless communication function for a UE.
  • the base station may include various forms of macro base stations, micro base stations, relay stations, access points, and the like.
  • the names of devices with base station functionality may vary.
  • an evolved NodeB eNB or eNodeB
  • Node B or the like in a 3rd Generation (3G) network.
  • 3G 3rd Generation
  • the foregoing apparatus for providing a wireless communication function to the UE is collectively referred to as a base station or a BS.
  • FIG. 2 shows a schematic diagram of a possible system architecture of an embodiment of the present invention.
  • the UE accesses the SGW through the base station, and accesses the PGW1 through the SGW.
  • the Mobility Management Entity MME
  • MME Mobility Management Entity
  • the MME is used as the control plane network element, and is connected to the base station and the SGW through the port.
  • the MME is used to transmit signaling of the control plane to the base station and the SGW.
  • other PGWs are also included in the system architecture shown in FIG. 2, such as PGW2, PGW3, and the like. Wherein, at PGW1, PGW2, PGW3, etc., there is usually a local server.
  • the local server may be a cache server or a service server deployed on the same node as the corresponding PGW.
  • FIG. 2 is only an example.
  • the function of the SGW may be completed by the SGSN, and the PGW is used.
  • the function can be done by the GGSN.
  • a bearer corresponding to the UE has been established between the SGW and the PGW1.
  • the UE accesses the network resource, it may first find whether the resource is stored in the local server corresponding to the PGW1.
  • the UE may obtain the resource from the local server, thereby avoiding network congestion and improving the network congestion. The response speed of the user accessing the resource.
  • PGW1 may query whether the resource is stored in other local servers.
  • the other local server for example, the local server corresponding to PGW2 stores the resource
  • PGW1 may The PGW2 corresponding to the other local server establishes a bearer to acquire the resource.
  • the path of the obtained resource is detoured, affecting the access speed of the UE, and is not conducive to saving network resources.
  • the embodiment of the present invention provides a method for accessing resources, and the main idea is that, under a single PDN link, the service gateway can establish a bearer with at least one other packet gateway in addition to establishing a bearer with the default packet gateway. The bearer of the same UE, thereby facilitating the UE to acquire resources.
  • the method may include: the serving gateway receives an IP packet of the UE, where the IP packet carries an IP address of the target server, where the target server stores the resource to be accessed by the UE, where the serving gateway and the first packet gateway Having a first bearer corresponding to the UE; the serving gateway determines a second packet gateway corresponding to the target server according to the foregoing IP address; and determining a second bearer corresponding to the UE between the serving gateway and the second packet gateway, for example,
  • the second bearer may be established or selected from the existing bearers; and the access request of the UE is transmitted through the second bearer, and the access request is used to request access to the foregoing resources stored in the target server.
  • the serving gateway may send an access request of the UE to the second packet gateway by using the second bearer to access the target server corresponding to the second packet gateway. Resources, so as to avoid route detours of the access path, which is beneficial to improve the speed and efficiency of UE access and save network resources.
  • FIG. 3 shows a method 300 for accessing resources provided by an embodiment of the present invention. As shown in FIG. 3, the method 300 includes:
  • the serving gateway receives the IP packet of the UE, where the IP packet carries the IP address of the target server, where the target server stores the resource to be accessed by the UE, where the service gateway has a correspondence with the first packet gateway.
  • the first bearer of the UE may be a Transmission Control Protocol (TCP) setup request packet, or the IP packet may be an IP packet in other formats.
  • TCP Transmission Control Protocol
  • the IP address of the target server may also be obtained.
  • the UE may receive the IP address of the target server sent by the first packet gateway.
  • the first packet gateway may send a redirect message to the UE (for example, an HTTP redirect Message), the redirect message contains the IP address of the target server.
  • the first bearer between the serving gateway and the first packet gateway may be a default bearer established between the UE and the first packet gateway when the UE establishes a PDN link with the core network, and the default bearer along with the PDN The establishment of the establishment, the default bearer always exists in the case of continuous PDN links.
  • the serving gateway determines the second packet gateway corresponding to the target server according to the IP address.
  • the serving gateway determines the target server based on the IP address and determines a second packet gateway corresponding to the target server.
  • the second packet gateway may be a packet gateway that is deployed on the same node as the target server.
  • the second packet gateway may be a packet gateway that is located on the same local area network (LAN) as the target server.
  • LAN local area network
  • a second bearer corresponding to the UE between the serving gateway and the second packet gateway is determined.
  • the serving gateway may determine a second bearer corresponding to the UE between the serving gateway and the second packet gateway. For example, the serving gateway may determine the second bearer from the at least two existing bearers, where the at least two existing bearers are bearers corresponding to the UE between the serving gateway and the at least two packet gateways respectively.
  • the second bearer may be determined by the serving gateway sending a bearer setup request to the second packet gateway, the bearer setup request for establishing the second bearer; and the second packet gateway receiving the bearer setup request After that, the second bearer is established.
  • the bearer request message may include parameter information of the second bearer, and the second packet gateway may establish the second bearer according to the parameter information.
  • the second packet gateway may further send a bearer setup response message to the serving gateway.
  • the bearer setup request may be an S5 connection setup request message
  • the bearer setup response message may be an S5 connection setup response message.
  • the serving gateway may further receive an indication message sent by the mobility management network element or the first packet gateway, where the indication message carries the IP of the second packet gateway.
  • An indication the indication message is used to indicate that a second bearer is established between the serving gateway and the second packet gateway.
  • the mobility management network element may be an MME.
  • the indication message may be an S5 connection setup request message.
  • the IP address of the target server sent by the cache controller may also be received.
  • an access request of the UE is transmitted through the second bearer, and the access request is used to request access to resources stored in the target server.
  • the access request of the UE may be an HTTP request.
  • the access request of the UE may be transmitted through the second bearer by: the serving gateway sending an access request to the second packet gateway by using the second bearer; and the second packet gateway receiving the UE sent by the serving gateway by using the second bearer
  • the response message can also be replied to the service gateway to complete the response process.
  • the resources stored in the target server may be transmitted between the serving gateway and the second packet gateway through the second bearer.
  • the access request may include an IP address of the target server, and the serving gateway may determine or select an access request for transmitting the UE through the second bearer according to the IP address in the access request.
  • the first bearer may be part of a bearer corresponding to the UE established by the UE through the base station, the serving gateway, and the first packet gateway, for example, the first bearer may be between the serving gateway and the first packet gateway.
  • the S5 bearer It can be understood that, in the case that the UE sends a request message to the first packet gateway through the first bearer via the serving gateway, or sends a request message to the second packet gateway through the second bearer via the serving gateway, the UE and the serving gateway
  • the inter-bearing can be reused, thereby improving the utilization efficiency of the bearer.
  • first bearer and the second bearer correspond to the same PDN link, or it can be understood that the solution provided by the embodiment of the present invention can implement the service gateway and multiple packet gateway anchors under the same PDN link condition.
  • Point connection for example, in an LTE system, the connection of the SGW to multiple PGW anchors can be implemented.
  • the serving gateway has a first bearer corresponding to the UE between the first packet gateway and the first bearer
  • the second bearer is determined between the serving gateway and the second packet gateway, so that the UE can pass the second
  • the bearer accesses the resources in the target server corresponding to the second packet gateway, thereby reducing the route bypass of the access path, and improving the efficiency of accessing resources.
  • the serving gateway may further receive a dedicated bearer setup request sent by the second packet gateway, where the dedicated bearer setup request is used to request to establish a first dedicated bearer corresponding to the UE between the serving gateway and the second packet gateway; Establishing a first dedicated bearer according to the dedicated bearer setup request; and the serving gateway determines a second dedicated bearer between the serving gateway and the UE.
  • the first dedicated bearer is established between the serving gateway and the second packet gateway, and the second dedicated bearer between the serving gateway and the UE is determined, so that the resource is transmitted through the first dedicated bearer and the second dedicated bearer.
  • the default bearer refers to the bearer of data and signaling that meets the default QoS.
  • the default bearer is established when a PDN link is established.
  • a dedicated bearer is a bearer established on the basis of a PDN link to provide a specific QoS transmission requirement. That is to say, the dedicated bearer is established on the basis of the default bearer establishment.
  • the QoS of a dedicated bearer is higher than the QoS requirement of a default bearer.
  • the first dedicated bearer may be after the default bearer is established between the serving gateway and the packet gateway.
  • the second dedicated bearer between the serving gateway and the UE refers to a dedicated bearer between the serving gateway and the UE, and the UE and the PGW 2 transmit resources through the first dedicated bearer and the second dedicated bearer.
  • the second dedicated bearer may include a dedicated bearer between the serving gateway and the base station, and a wireless dedicated bearer between the base station and the UE.
  • the serving gateway determines the second dedicated bearer between the serving gateway and the UE, including: the serving gateway determines that there is a dedicated bearer between the serving gateway and the UE, and determines the dedicated bearer as the second dedicated bearer; or, the service The gateway determines that there is no dedicated bearer between the serving gateway and the UE, and establishes a second dedicated bearer.
  • the serving gateway determines that there is a dedicated bearer between the serving gateway and the UE
  • the second dedicated bearer is not required to be established, and the dedicated bearer is determined as the second dedicated bearer, and the second dedicated bearer can be reused. To save network resources.
  • the SGW may only establish a first dedicated bearer corresponding to the UE with one packet gateway. For example, in the prior art, after the SGW establishes the first dedicated bearer with the PGW1, the SGW needs to establish a second dedicated bearer with the UE to establish a dedicated bearer between the UE and the PGW1. In the embodiment of the present invention, when the SGW receives the first dedicated bearer request of the PGW2, the SGW may establish a first dedicated bearer with other PGWs, which indicates that a dedicated bearer has been established between the SGW and the UE, and the SGW does not need to be configured at this time.
  • a second dedicated bearer is established, and only the dedicated bearer existing between the SGW and the UE is confirmed as the second dedicated bearer. And transmitting the resources accessed by the UE by using the first dedicated bearer and the second dedicated bearer.
  • the serving gateway establishes the second dedicated bearer, which can save network resources and improve the efficiency of the UE accessing resources.
  • the second packet gateway in the method for establishing the dedicated bearer may be replaced by the first packet gateway. I will not repeat them here.
  • the method provided by the embodiment of the present invention may further include: the serving gateway receiving a dedicated bearer modification request sent by the second packet gateway, where the dedicated bearer modification request is used to request to modify the first dedicated bearer.
  • the serving gateway modifies the first dedicated bearer according to the dedicated bearer modification request; and the serving gateway determines that there is a corresponding to the UE between the serving gateway and other packet gateways other than the second packet gateway Dedicated bearer and modify the dedicated bearer between the serving gateway and other packet gateways other than the second packet gateway.
  • the serving gateway modifies the first dedicated bearer between the second packet gateway, and simultaneously modifies the serving gateway and other packet gateways other than the second packet gateway Dedicated bearer to ensure communication between the UE and other packet gateways, and improve the efficiency of accessing resources.
  • the serving gateway after receiving the dedicated bearer modification request of the second packet gateway, the serving gateway needs to modify the first dedicated bearer between the serving gateway and the second packet gateway, and modify the service gateway and the UE.
  • the second dedicated bearer At this time, the serving gateway further needs to determine whether another packet gateway shares the second dedicated bearer with the second packet gateway, or the service gateway needs to determine whether the service gateway exists with other gateways other than the second packet gateway.
  • the serving gateway Corresponding to the dedicated bearer of the UE, when there is a dedicated bearer, the serving gateway also needs to modify the dedicated bearer between the serving gateway and other gateways to ensure normal communication of the dedicated bearer between the UE and other packet gateways.
  • the second packet gateway in the method for modifying the dedicated bearer may be replaced by the first packet gateway, and details are not described herein again.
  • the method provided by the embodiment of the present invention further includes: the serving gateway receiving a dedicated bearer deletion request sent by the second packet gateway, where the dedicated bearer deletion request is used to request to delete the first dedicated bearer; Deleting, by the serving gateway, the first dedicated bearer according to the dedicated bearer request; and the serving gateway determines that there is no corresponding to the UE between the serving gateway and other packet gateways other than the second packet gateway Dedicated bearer and delete the second dedicated bearer to improve the efficiency of accessing resources.
  • the serving gateway when the serving gateway deletes the first dedicated bearer between the second packet gateway and the second packet gateway, the serving gateway determines whether there is a dedicated bearer corresponding to the UE between the other packet gateways of the serving gateway, when there is a dedicated bearer.
  • the serving gateway does not delete the dedicated bearer between the serving gateway and the UE to ensure normal communication of the dedicated bearer between the UE and other packet gateways.
  • the serving gateway after receiving the dedicated bearer deletion request of the second packet gateway, the serving gateway needs to delete the first dedicated bearer between the serving gateway and the second packet gateway, and determine whether to delete the serving gateway and the UE.
  • the serving gateway also needs to determine whether another packet gateway shares the second dedicated bearer with the second packet gateway, or the service gateway needs to determine whether the service gateway exists with other gateways other than the second packet gateway.
  • the serving gateway when there is a dedicated bearer, the serving gateway does not delete the second dedicated bearer.
  • the serving gateway deletes the second dedicated bearer, Ensure proper communication of dedicated bearers between the UE and other packet gateways.
  • the second packet gateway in the method for deleting the dedicated bearer may be replaced by the first packet gateway, where I won't go into details here.
  • the UE can only work with a single packet under a single PDN link condition.
  • the gateway establishes a connection corresponding to the UE.
  • the serving gateway does not support establishing a bearer corresponding to the UE with other packet gateways while maintaining the same PDN link. , thereby affecting the efficiency of the UE to obtain resources.
  • the second between the at least one other packet gateway may also be determined.
  • the solution of the embodiment of the present invention can reduce the route bypass of the access path, and is beneficial to improving the efficiency of accessing resources.
  • FIG. 4 shows another method for accessing resources provided by an embodiment of the present invention.
  • the serving gateway may be an SGW
  • the first packet gateway may be PGW1
  • the first cache server may be a cache server corresponding to PGW1
  • the second cache server may be stored for the target server, that is, the second cache server.
  • the PGW2 may be the second packet gateway, that is, the PGW2 is a packet gateway corresponding to the second cache server.
  • the cache controller can be used to schedule and control each cache server in the distributed cache system
  • the second bearer can be an S5 bearer.
  • the method of accessing resources can be as follows:
  • a PDN link is established between the UE and the PGW1.
  • the S5 bearer is established between the SGW and the PGW1.
  • the UE establishes a first TCP connection with the first cache server through the PGW1.
  • the UE sends a first HTTP request message to the first cache server through the PGW1, where the first HTTP request message is used to request access to the resource.
  • the first cache server performs a local cache query, and if the local cache does not hit, sends a query message to the cache controller.
  • the cache controller after receiving the query message, performs a cache hit query in the distributed cache. After determining that the resource is stored in the second cache server, the IP address of the second cache server is fed back to the first cache. server.
  • the first cache server notifies the second cache server IP address to the UE by using the HTTP redirect message, so that the UE re-initiates the second HTTP request message to the second cache server according to the IP address of the second cache server. And sending a notification message to the cache controller, the notification message is used to notify the first cache server that an HTTP redirect message is about to be sent.
  • the cache controller after receiving the notification message sent by the first cache server, the cache controller notifies the MME of the IP address of the second cache server; or the cache controller determines the IP address of the PGW2 according to the IP address of the second buffer. The IP address of the second packet gateway is notified to the MME.
  • the MME obtains the IP address of the PGW2, or the MME determines the IP address of the PGW2 according to the IP address of the second cache server, and sends an establishment S5 connection establishment indication message to the SGW, where the establishment of the S5 connection establishment indication message includes the PGW2. IP address.
  • the serving gateway determines the IP address of the second packet gateway by using the indication message sent by the MME, and the serving gateway establishes the second bearer in advance according to the indication of the MME, thereby saving the time for the UE to access the resource.
  • the SGW determines the IP address of the PGW2, and sends an S5 bearer connection establishment request message to the PGW2, where the S5 bearer setup request message includes the parameter information carried by the S5.
  • the PGW2 after receiving the S5 bearer connection establishment request message, the PGW2 establishes an S5 bearer and returns an S5 connection setup response message to the SGW.
  • the SGW receives the second TCP setup request message sent by the UE, where the second TCP setup request message includes the IP address of the second cache server, and the SGW determines the IP address of the PGW2 according to the IP address of the second cache server. Address and find whether there is a corresponding S5 bearer in the local area. If yes, the S5 bearer establishes a TCP connection with the second cache server. If not, the corresponding S5 bearer is established, and a TCP connection is established with the second cache server. .
  • the SGW receives the second HTTP request message sent by the UE, where the second HTTP request message is used to request to access the resource from the second cache server, and the SGW uses the S5 bearer between the PGW2 to transmit the resource to the UE.
  • FIG. 5 shows still another method for accessing resources provided by an embodiment of the present invention.
  • the same or similar content as the method shown in FIG. 4 can be referred to the detailed description related to FIG. 4, and details are not described herein again.
  • the method of accessing resources can be as follows:
  • the parts S501 to S506 in FIG. 5 are the same as or similar to the parts in S401 to S406 in FIG. 4, and the detailed description in the corresponding part in FIG. 4 can be referred to, and details are not described herein again.
  • the cache controller after receiving the notification message sent by the first cache server, the cache controller notifies the PGW1 of the IP address of the second cache server; or the cache controller determines the IP address of the PGW2 according to the IP address of the second buffer, The PGW1 is notified of the IP address of the second packet gateway.
  • the PGW1 determines the IP address of the PGW2 according to the IP address of the second cache server, and sends an establishment S5 connection establishment indication message to the SGW, where the establishment S5 connection establishment indication message includes the IP address of the PGW2.
  • the serving gateway determines the IP address of the second packet gateway by receiving the indication message sent by the first packet gateway, and further establishes the second bearer in advance with the indication of the first packet gateway. It saves time for UE to access resources.
  • the SGW After receiving the setup S5 connection establishment indication message of the PGW 1, the SGW determines the IP address of the PGW 2 and transmits an S5 bearer connection establishment request message to the PGW 2 .
  • the PGW2 after receiving the S5 bearer connection setup request message, the PGW2 establishes an S5 bearer and returns an S5 connection setup response message to the SGW.
  • the SGW receives the second TCP setup request message sent by the UE, where the second TCP setup request message includes the IP address of the second cache server, and the SGW searches for the local address according to the IP address of the second cache server.
  • the corresponding S5 bearer if present, establishes a TCP connection with the second cache server by using the S5 bearer, and if not, establishes a corresponding S5 bearer, and establishes a TCP connection with the second cache server.
  • the SGW receives the second HTTP request message sent by the UE, where the second HTTP request message is used to request to access the resource from the second cache server, and the SGW transmits the resource to the UE by using the S5 bearer between the PGW2 and the PGW2.
  • FIG. 6 shows another method for accessing resources provided by the embodiment of the present invention.
  • the same or similar content as the method shown in FIG. 4 or 5 can be referred to the detailed description related to FIG. 4 or 5, and details are not described herein again.
  • the method of accessing resources can be as follows:
  • the S601 part to the S606 in FIG. 6 are the same as or similar to the S401 part to the S406 part in FIG. 4, and the detailed description in the corresponding part in FIG. 4 can be referred to, and details are not described herein again.
  • the SGW receives the second TCP setup request message sent by the UE, where the second TCP setup request message includes an IP address of the second cache server, and the SGW determines the IP address of the PGW2 according to the IP address of the second cache server. The address is used to find whether there is an S5 bearer corresponding to the PGW2 in the local area. If yes, the S5 bearer establishes a TCP connection with the second cache server, and if not, sends an S5 bearer connection establishment request message to the PGW2.
  • the serving gateway determines the IP address of the second packet gateway by parsing the IP packet sent by the UE, and directly establishes the second bearer without signaling of the control plane, thereby saving network resources.
  • the PGW2 after receiving the S5 bearer connection setup request message, the PGW2 establishes an S5 bearer and returns an S5 bearer connection setup response message to the SGW.
  • the SGW establishes a TCP connection using the S5 bearer between the PGW2.
  • the SGW receives the second HTTP request message sent by the UE, where the second HTTP request message is used to request to access the resource from the second cache server, and the SGW uses the S5 bearer between the PGW2 to transmit the resource to the UE.
  • the UE may also establish a dedicated bearer with the second packet gateway according to the service quality level requirement of the service, and access the resource by using the dedicated bearer.
  • a method of establishing, modifying, and deleting a dedicated bearer will be described below with reference to FIGS. 7 through 9.
  • a default bearer for example, an S5 bearer
  • a default bearer for example, an S5 bearer
  • FIG. 7 is a schematic diagram of communication of a method for establishing a dedicated bearer according to an embodiment of the present invention. As shown in FIG. 7, the method for establishing a dedicated bearer includes:
  • the SGW receives a dedicated bearer setup request sent by the PGW2, and the dedicated bearer setup request is used to request to establish a first dedicated bearer between the SGW and the PGW2.
  • the SGW determines whether there is a dedicated bearer between the SGW and the UE.
  • the SGW determines the dedicated bearer as a second dedicated bearer between the SGW and the UE, and establishes a first dedicated bearer between the SGW and the PGW2. After the SGW establishes the first dedicated bearer, the SGW sends a dedicated bearer setup response message to the PGW2, where the dedicated bearer setup response message includes parameter information of the first dedicated bearer and the second dedicated bearer (for example, the bearer ID identifier).
  • the SGW when there is no dedicated bearer between the SGW and the UE, the SGW establishes a first dedicated bearer between the SGW and the PGW2, and establishes a second dedicated bearer between the SGW and the UE. After establishing the first dedicated bearer, the SGW sends a dedicated bearer setup response message to the PGW2.
  • the serving gateway determines whether there is a dedicated bearer between the serving gateway and the UE.
  • the dedicated bearer is determined as the serving gateway and the UE.
  • the second dedicated bearer only the first dedicated bearer between the serving gateway and the second packet gateway is established, and the resources accessed by the UE are transmitted through the first dedicated bearer and the second resource, thereby saving network resources and improving UE access resources. s efficiency.
  • FIG. 8 is a schematic diagram of communication of a modification method of a dedicated bearer. As shown in FIG. 8, the method for modifying a dedicated bearer includes:
  • the SGW receives the dedicated bearer modification request sent by the PGW2, and the dedicated bearer modification request is used to request to modify the dedicated bearer between the SGW and the PGW2.
  • the SGW determines whether there is a dedicated bearer corresponding to the UE between the SGW and other PGWs other than PGW2.
  • the SGW when there is a dedicated bearer between the SGW and the other PGW, the SGW modifies the dedicated bearer between the SGW and the PGW2, and modifies the dedicated bearer between the SGW and other packet gateways, and the dedicated bearer between the SGW and the UE.
  • the SGW modifies the dedicated bearer between the SGW and the PGW2, and the dedicated bearer between the SGW and the UE.
  • the serving gateway determines whether there is a dedicated bearer between the serving gateway and the other packet gateway, and when there is a dedicated bearer between the serving gateway and the other packet gateway, Modifying the dedicated bearer between the second packet gateway and the serving gateway, and modifying the dedicated bearer between the other packet gateway and the serving gateway to ensure communication between the serving gateway and other packet gateways, thereby improving the efficiency of accessing resources.
  • FIG. 9 is a schematic diagram of communication of a method for deleting a dedicated bearer. As shown in FIG. 9, the method for deleting a dedicated bearer includes:
  • the SGW receives the dedicated bearer deletion request sent by the PGW2.
  • the SGW determines whether there is a first dedicated bearer corresponding to the UE between the SGW and other PGWs other than PGW2.
  • the SGW when the SGW has a dedicated bearer with other PGWs, the SGW deletes the dedicated bearer between the SGW and the PGW2, and does not delete the second dedicated bearer between the SGW and the UE.
  • the SGW when the SGW does not have a dedicated bearer with other PGWs, the SGW deletes the dedicated bearer between the SGW and the PGW2, and deletes the second dedicated bearer between the SGW and the UE.
  • the serving gateway determines whether there is a dedicated bearer corresponding to the UE between the serving gateway and the other packet gateway, and there is a dedicated bearer between the serving gateway and other packet gateways.
  • the dedicated bearer between the serving gateway and the second packet gateway is deleted, the second dedicated bearer between the serving gateway and the UE, and the dedicated bearer between the serving gateway and other packet gateways are reserved, thereby ensuring the service gateway and other Communication between packet gateways improves the efficiency of accessing resources.
  • the serving gateway may be an SGW or an SGSN
  • the packet gateway may be a PGW or a GGSN.
  • the serving gateway is an SGW and the packet gateway is a PGW.
  • each network element such as a service gateway, a second packet gateway, a mobility management network element, etc.
  • each network element such as a service gateway, a second packet gateway, a mobility management network element, etc.
  • each network element includes hardware structures and/or software modules corresponding to each function.
  • 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 in hardware or computer software to drive hardware depends on the specific application and design constraints of the 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.
  • the embodiments of the present invention may perform functional unit division on a serving gateway, a packet gateway (for example, a second packet gateway), and the like according to the foregoing method example.
  • each function may be divided according to each function.
  • Units can also integrate two or more functions into one processing unit.
  • the above integrated unit can be implemented in the form of hardware or in the form of a software functional unit. It should be noted that the division of the unit in the embodiment of the present invention is schematic, and is only a logical function division, and the actual implementation may have another division manner.
  • FIG. 10A shows a possible structural diagram of the service gateway involved in the above embodiment.
  • the service gateway 1000 includes a processing unit 1002 and a communication unit 1003.
  • the processing unit 1002 is configured to perform control management on the action of the serving gateway.
  • the processing unit 1002 is configured to support the service gateway to perform the processes 310-340 in FIG. 3, the processes 401, 409, 411, and 412 in FIG. Processes 501, 509, 511, and 512, processes 601, 607, 608, 609, and 610 in FIG. 6, processes 702-704 in FIG. 7, processes 802-804 in FIG. 8, and process 902 in FIG. 904, and/or other processes for the techniques described herein.
  • the communication unit 1003 is configured to support communication between the serving gateway and other network entities, such as communication with the base station, MME, PGW, etc. shown in FIG. 2.
  • the service gateway may further include a storage unit 1001 for storing program codes and data of the service gateway.
  • the processing unit 1002 may be a processor or a controller, such as a central processing unit (CPU), a general-purpose processor, a digital signal processor (DSP), and an application-specific integrated circuit (Application-Specific). Integrated Circuit (ASIC), 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 processor may also be a combination of computing functions, for example, including one or more microprocessor combinations, a combination of a DSP and a microprocessor, and the like.
  • the communication unit 1003 may be a communication interface, a transceiver or a transceiver circuit, etc., wherein the communication interface is a collective name.
  • the communication interface may include multiple interfaces, for example, may include: an interface between the service gateway and the packet gateway. The interface and/or other interface between the service gateway and the mobility management network element.
  • the storage unit 1001 may be a memory.
  • the service gateway according to the embodiment of the present invention may be the service gateway shown in FIG. 10B.
  • the service gateway 1010 includes a processor 1012, a communication interface 1013, and a memory 1011.
  • the service gateway 1010 may further include a bus 1014.
  • the communication interface 1013, the processor 1012, and the memory 1011 may be connected to each other through a bus 1014.
  • the bus 1014 may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (abbreviated). EISA) bus and so on.
  • the bus 1014 can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is shown in Figure 10B, but it does not mean that there is only one bus or one type. Bus.
  • FIG. 11A shows a possible structural diagram of the packet gateway involved in the above embodiment.
  • the packet gateway 1100 includes a processing unit 1102 and a communication unit 1103.
  • the processing unit 1102 is configured to control and manage the actions of the packet gateway.
  • the processing unit 1102 is configured to support the packet gateway to perform the processes 330, 340 in FIG. 3, the processes 410 and 412 in FIG. 4, the process 510 in FIG. 512, processes 608, 610 in FIG. 6, process 701 in FIG. 7, process 801 in FIG. 8, process 901 in FIG. 9, and/or other processes for the techniques described herein.
  • the communication unit 1103 is for supporting communication between the packet gateway and other network entities, such as communication with the base station, MME, PGW, etc. shown in FIG. 2.
  • the packet gateway may further include a storage unit 1101 for storing program codes and data of the packet gateway.
  • the processing unit 1102 may be a processor or a controller, and may be, for example, a central processing unit (CPU), a general-purpose processor, a digital signal processor (DSP), and an application-specific integrated circuit (Application-Specific). Integrated Circuit (ASIC), 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 processor may also be a combination of computing functions, for example, including one or more microprocessor combinations, a combination of a DSP and a microprocessor, and the like.
  • the communication unit 1103 can be a communication interface, a transceiver or a transceiver circuit, etc., wherein the communication interface is a collective name.
  • the communication interface can include multiple interfaces, for example, the interface between the packet gateway and the service gateway can be included. And / or other interfaces.
  • the storage unit 1101 may be a memory.
  • the packet gateway involved in the embodiment of the present invention may be the packet gateway shown in FIG. 11B.
  • the packet gateway 1110 includes a processor 1112, a communication interface 1113, and a memory 1111.
  • the packet gateway 1110 may further include a bus 1114.
  • the communication interface 1113, the processor 1112, and the memory 1111 may be connected to each other through a bus 1114.
  • the bus 1114 may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (abbreviated). EISA) bus and so on.
  • the bus 1114 can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is shown in FIG. 11B, but it does not mean that there is only one bus or one type of bus.
  • FIG. 12A shows a possible structural diagram of the mobility management network element involved in the above embodiment.
  • the mobility management network element 1200 includes a processing unit 1202 and a communication unit 1203.
  • the mobility management network element 1200 may further include: storing Storage unit 1201.
  • the storage unit 1201 is configured to store a program
  • the communication unit 1203 is configured to communicate with other devices
  • the processing unit 1202 is configured to execute a program in the storage unit 1201.
  • the processing unit is configured to execute FIG. 1
  • FIG. 1 The steps performed by the mobility management network element in FIG.
  • repeated descriptions are omitted as appropriate.
  • the mobility management network element in the embodiment of the present invention may be the mobility management network element shown in FIG. 12B, when the processing unit 1202 is a processor, the communication unit 1203 is a communication interface, and the storage unit 1201 is a memory.
  • the mobility management network element 1210 includes a processor 1212, a communication interface 1213, a memory 1211, and a bus 1214. For the sake of brevity, repeated descriptions are omitted as appropriate.
  • the processor for performing the functions of the foregoing service gateway, packet gateway or mobility management network element in the embodiment of the present invention may be a central processing unit (CPU), a general-purpose processor, and a digital signal processor (Digital Signal Processor, DSP), Application-Specific Integrated Circuit (ASIC), 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 various exemplary logical blocks, modules and circuits described in connection with the disclosure of the embodiments of the invention.
  • the processor may also be a combination of computing functions, for example, including one or more microprocessor combinations, a combination of a DSP and a microprocessor, and the like.
  • the steps of the method or algorithm described in connection with the disclosure of the embodiments of the present invention may be implemented in a hardware manner, or may be implemented by a processor executing software instructions.
  • the software instructions may be composed of corresponding software modules, which may be stored in a random access memory (RAM), a flash memory, a read only memory (ROM), an erasable programmable read only memory ( Erasable Programmable ROM (EPROM), electrically erasable programmable read only memory (EEPROM), 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 processor to enable the processor to read information from, and write information to, the storage medium.
  • the storage medium can also be an integral part of the processor.
  • the processor and the storage medium can be located in an ASIC.
  • the ASIC can be located in a gateway device or mobility management network element.
  • the processor and the storage medium may also exist as discrete components in the gateway device or the mobility management network element.
  • the functions described in the embodiments of the present invention may 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 medium including computer storage Storage medium and communication medium, wherein the communication medium includes 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.

Abstract

本发明实施例提供一种访问资源的方法、装置和系统。该方法包括：服务网关接收UE的IP报文，IP报文中携带目标服务器的IP地址，目标服务器中存储有UE待访问的资源，其中，服务网关与第一分组网关之间具有对应于UE的第一承载；服务网关根据IP地址确定目标服务器对应的第二分组网关；服务网关确定服务网关与第二分组网关之间的对应于UE的第二承载；服务网关通过第二承载向第二分组网关发送UE的访问请求，访问请求用于请求访问目标服务器中存储的资源。本发明实施例提供的方案能够避免访问路径的路由迂回，以提高UE访问资源的效率。

Description

访问资源的方法、装置和系统 技术领域
本发明涉及通信领域，尤其涉及一种访问资源的方法，装置和系统。
背景技术
现有技术中，随着长期演进(Long Term Evolution，LTE)系统的发展，内容分发网络(Content Delivery Network，CDN)在各地边缘的网关处部署有缓存服务器，其中，缓存服务器可以缓存远程服务器中的资源。通过中心平台的调度，用户设备(User Equipment，UE)可以从各地边缘的缓存服务器中就近获取资源。通常情况下，UE通过基站、服务网关(Serving Gateway，SGW)以及分组数据网络网关(Packet Data Network Gateway，PGW)连入外网。在单一分组数据网络(Packet Data Network，PDN)连接的情况下，UE通过某个PGW(例如PGW1)与外网连接，当UE需要访问的资源存储于部署在该PGW1以外的另一个PGW(例如PGW2)处的服务器时，PGW1需要与PGW2建立连接后，通过PGW2获取该资源，然后PGW1再将该资源发送给UE。这种访问资源的路径造成了路由的迂回，不利于UE获取资源。
发明内容
本发明提供了一种访问资源的方法、服务网关、分组网关、移动性管理网元和系统，用以避免访问路径的路由迂回，提高UE访问资源的效率。
一方面，本发明实施例提供了一种访问资源的方法，包括：服务网关接收UE的IP报文，该IP报文中携带目标服务器的IP地址，该目标服务器中存储有UE待访问的资源，其中，服务网关与第一分组网关之间具有对应于UE的第一承载；服务网关根据该IP地址，确定目标服务器对应的第二分组网关；确定服务网关与第二分组网关之间的对应于UE的第二承载；通过第二承载传输UE的访问请求，该访问请求用于请求访问目标服务器中存储的资源。通过本发明实施例提供的方案，在服务网关与第一分组网关之间存在对应于UE的第一承载的情况下，服务网关与对应于目标服务器的第二分组网关之间还可以确定第二承载，并通过第二承载传输UE的访问请求，以访问目标服务器中存储的资源。因此，本发明实施例提供的方案能够避免访问路径的路由迂回，以提高UE访问资源的效率。
在一个可能的设计中，可以通过以下方式之一确定服务网关与第二分组 网关之间的对应于UE的第二承载：第一种方式，服务网关从至少两个已有的承载中确定第二承载，该至少两个已有的承载为服务网关分别与至少两个分组网关之间的对应于UE的承载。第二种方式，服务网关向第二分组网关发送承载建立请求，该承载建立请求用于建立第二承载；第二分组网关在接收该承载建立请求后，建立该第二承载。在第二种方式中，第二分组网关还可以向服务网关发送承载建立响应消息。
在上述第二种方式中，服务网关可以根据移动性管理网元或第一分组网关的指示向第二分组网关发送承载建立请求。例如，服务网关接收移动性管理网元或第一分组网关发送的指示消息，该指示消息中携带第二分组网关的IP地址，该指示消息用于指示在服务网关和第二分组网关之间建立第二承载。因此，服务网关可以通过移动性管理网元或第一分组网关发送的指示消息确定第二分组网关的IP地址，并在指示消息的指示下提前建立第二承载，节约了UE访问资源的时间。
在一个可能的设计中，可以通过以下方式通过第二承载传输UE的访问请求：服务网关通过第二分组网关发送访问请求；第二分组网关在接收到服务网关通过第二承载发送的UE的访问请求之后，还可以向服务网关回复响应消息，以完成响应流程。在完成响应流程后，服务网关和第二分组网关之间可以通过第二承载传输目标服务器中存储的资源。
在一个可能的设计中，还可以建立服务网关与第二分组网关之间的对应于UE的专用承载。例如，第二分组网关可以向服务网关发送专用承载建立请求，该专用承载建立请求用于建立服务网关与第二分组网关之间的对应于UE的第一专用承载；服务网关接收该专用承载建立请求后，根据专用承载建立请求，建立第一专用承载；以及，服务网关确定服务网关与UE之间的第二专用承载。进一步的，服务网关可以通过以下方式确定服务网关与UE之间的第二专用承载：服务网关确定服务网关与UE之间存在专用承载，并将该专用承载确定为第二专用承载；或者，服务网关确定服务网关与UE之间不存在专用承载，并建立该第二专用承载。从而可以利用第一专用承载和第二专用承载传输资源，以满足具有不同服务质量(Quality of Service，QoS)要求的业务的传输需求。进一步的，在服务网关与UE之间已存在专用承载的情况下，可以将该专用承载作为第二专用承载，而无需再建立其他承载，从而可以提高承载资源的利用率，以节约网络资源。
在一个可能的设计中，还可以修改服务网关与第二分组网关之间的第一专用承载。例如，第二分组网关可以向服务网关发送专用承载修改请求，该专用承载修改请求用于请求修改第一专用承载；服务网关接收该专用承载修 改请求后，根据该专用承载修改请求修改第一专用承载；以及，服务网关确定服务网关与第二分组网关以外的其他分组网关之间存在对应于UE的专用承载，并修改服务网关与第二分组网关以外的其他分组网关之间的专用承载。因此，服务网关可以在修改与第二分组网关之间的第一专用承载的情况下，一并修改服务网关与除第二分组网关之外的其他分组网关之间的专用承载，以确保UE与其他分组网关之间的专用承载的通信。
在一个可能的设计中，还可以删除服务网关与第二分组网关之间的第一专用承载。例如，第二分组网关可以向服务网关发送专用承载删除请求，该专用承载删除请求用于请求删除第一专用承载；服务网关接收该专用承载删除请求后，根据专用承载删除请求删除第一专用承载；以及，服务网关确定服务网关与第二分组网关以外的其他分组网关之间不存在对应于UE的专用承载，并删除第二专用承载。因此，服务网关在删除与第二分组网关之间的第一专用承载的情况下，可以一并确定服务网关与其他分组网关之间是否存在对应于UE的专用承载，若存在专用承载时，服务网关不删除服务网关与UE之间的第二专用承载，以确保UE与其他分组网关之间的专用承载的正常通信；若不存在专用承载时，可以删除该第二专用承载，以释放承载资源。
上述方法示例中，目标服务器可以是业务服务器，也可以是缓存服务器。其中，第二分组网关与目标服务器可以位于同一节点。
上述方法示例中，服务网关可以是SGW或服务通用分组无线技术支持节点(Serving General Packet Radio Service Support Node，SGSN)，第一分组网关、第二分组网关可以是PGW或(Gateway General Packet Radio Service Support Node,GGSN)。
另一方面，本发明实施例提供一种服务网关，该服务网关具有实现上述方法设计中服务网关行为的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。
在一个可能的设计中，服务网关的结构中包括处理单元和通信单元，所述处理单元被配置为支持服务网关执行上述方法中相应的功能。所述通信单元用于支持服务网关与其他设备之间的通信。所述服务网关还可以包括存储单元，所述存储单元用于与处理单元耦合，其保存服务网关必要的程序指令和数据。作为示例，处理单元可以为处理器，通信单元可以为通信接口，存储单元可以为存储器。
又一方面，本发明实施例提供一种分组网关，该分组网关可以称为第二分组网关，第二分组网关具有实现上述方法设计中第二分组网关行为的功能。 所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。
在一个可能的设计中，第二分组网关的结构中包括处理单元和通信单元，所述处理单元被配置为支持第二分组网关执行上述方法中相应的功能。所述通信单元用于支持第二分组网关与其他设备之间的通信。所述第二分组网关还可以包括存储单元，所述存储单元用于与处理单元耦合，其保存第二分组网关必要的程序指令和数据。作为示例，处理单元可以为处理器，通信单元可以为通信接口，存储单元可以为存储器。
又一方面，本发明实施例提供一种移动性管理网元，该移动性管理网元具有实现上述方法设计中移动性管理网元行为的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。
在一个可能的设计中，服务网关的结构中包括处理单元和通信单元，所述处理单元被配置为支持服务网关执行上述方法中相应的功能。所述通信单元用于支持移动性管理网元与其他设备之间的通信。所述移动性管理网元还可以包括存储单元，所述存储单元用于与处理单元耦合，其保存移动性管理网元必要的程序指令和数据。作为示例，处理单元可以为处理器，通信单元可以为通信接口，存储单元可以为存储器。
又一方面，本发明实施例提供一种通信系统，该系统包括上述方面所述的服务网关和第二分组网关；或者该系统包括上述方面所述的服务网关、第二分组网关和移动性管理网元。
再一方面，本发明实施例提供一种计算机存储介质，用于储存为上述服务网关所用的计算机软件指令，其包含用于执行上述方面所设计的程序。
再一方面，本发明实施例提供一种计算机存储介质，用于储存为上述第二分组网关所用的计算机软件指令，其包含用于执行上述方面所设计的程序。
再一方面，本发明实施例提供一种计算机存储介质，用于储存为上述移动性管理网元所用的计算机软件指令，其包含用于执行上述方面所设计的程序。
相较于现有技术，本发明实施例提供的方案中，在服务网关与第一分组网关之间具有对应于UE的第一承载的情况下，服务网关在接收UE的IP报文后，可以根据IP报文中携带的目标服务器的IP地址确定目标服务器对应的第二分组网关，确定服务网关与第二分组网关之间的对应于UE的第二承载，并通过第二承载传输UE的访问请求，该访问请求用于请求访问目标服务器中存储的资源。因此，本发明实施例提供的方案能够避免访问路径的路 由迂回，以提高UE访问资源的效率。
附图说明
为了更清楚地说明本发明实施例的技术方案，下面将对本发明实施例中所需要使用的附图作简单地介绍，显而易见地，下面所描述的附图仅仅是本发明的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1是本发明实施例的一种可能的应用场景示意图；
图2是本发明实施例应用的一种可能的系统架构示意图；
图3是本发明实施例提供的一种访问资源的方法的流程示意图；
图4是本发明实施例提供的另一种访问资源的方法的通信示意图；
图5是本发明实施例提供的又一种访问资源的方法的通信示意图；
图6是本发明实施例提供的再一种访问资源的方法的通信示意图；
图7是本发明实施例提供的一种专用承载的建立方法的通信示意图；
图8是本发明实施例提供的一种专用承载的修改方法的通信示意图；
图9是本发明实施例提供的一种专用承载的删除方法的通信示意图；
图10A是本发明实施例提供的一种服务网关的结构示意图；
图10B是本发明实施例提供的另一种服务网关的结构示意图；
图11A是本发明实施例提供的一种分组网关的结构示意图；
图11B是本发明实施例提供的另一种分组网关的结构示意图；
图12A是本发明实施提供的一种移动性管理网元的结构示意图；
图12B是本发明实施例提供的另一种移动性管理网元的结构示意图。
具体实施方式
为使本发明实施例的目的、技术方案和优点更加清楚，下面将结合本发明实施例中的附图，对本发明实施例中的技术方案进行描述。
本发明实施例描述的网络架构以及业务场景是为了更加清楚的说明本发明实施例的技术方案，并不构成对本发明实施例提供的技术方案的限定，本领域普通技术人员可知，随着网络架构的演变和新业务场景的出现，本发明实施例提供的技术方案对于类似的技术问题，同样适用。
如图1所示，UE通过无线接入网(Radio Access Network，RAN)及核心网(Core Network，CN)接入运营商互联网协议(Internet Protocol，IP)业务网络，例如多媒体子系统(IP Multimedia System，IMS)网络、包交换流业务(Packet Switched Streaming Service，简PSS)网络等。本发明描述的 技术方案可以适用于长期演进(Long Term Evolution，LTE)系统，或其他采用各种无线接入技术的无线通信系统，例如采用码分多址(Code Division Multiple Access，CDMA)、频分多址(Frequency Division Multiple Access，FDMA)、时分多址(Time Division Multiple Access，TDMA)、正交频分多址(Orthogonal Frequency Division Multiple Access，OFDMA)、单载波频分多址(Single Carrier Frequency Division Multiple Access，SC-FDMA)等接入技术的系统。此外，还可以适用于LTE系统后续的演进系统，如第五代(5th Generation，5G)系统等。为清楚起见，这里仅以LTE系统为例进行说明。在LTE系统中，演进的通用陆地无线接入网(Evolved Universal Terrestrial Radio Access Network，E-UTRAN)作为无线接入网，演进分组核心网(Evolved Packet Core，EPC)作为核心网。UE通过E-UTRAN及EPC接入IMS网络。
本发明实施例中，名词“网络”和“系统”经常交替使用，但本领域技术人员可以理解其含义。本发明实施例所涉及到的用户设备UE可以包括各种具有无线通信功能的手持设备、车载设备、可穿戴设备、计算设备或连接到无线调制解调器的其他处理设备，以及各种形式的用户设备(User Equipment，UE)，移动台(Mobile Station，MS)，终端(terminal)，终端设备(terminal device)等等。为方便描述，本发明实施例中，上面提到的设备统称为用户设备或UE。本发明实施例所涉及到的基站(Base Station，BS)是一种部署在无线接入网中用以为UE提供无线通信功能的装置。所述基站可以包括各种形式的宏基站，微基站，中继站，接入点等。在采用不同的无线接入技术的系统中，具有基站功能的设备的名称可能会有所不同。例如在LTE网络中，称为演进的节点B(evolved NodeB，eNB或eNodeB)，在第三代(3rd Generation，3G)网络中，称为节点B(Node B)等等。为方便描述，本发明实施例中，上述为UE提供无线通信功能的装置统称为基站或BS。
图2示出了本发明实施例的一种可能的系统架构示意图。如图2所示，UE通过基站接入到SGW，并通过SGW接入到PGW1，其中移动性管理实体(Mobility Management Entity，MME)作为控制面网元，通过端口与分别与基站以及SGW连接，MME用于向基站和SGW传输控制面的信令。此外，图2所示的系统架构中还包括其他PGW，例如PGW2、PGW3等。其中，在PGW1、PGW2、PGW3等处通常部属有本地服务器，例如，本地服务器可以为与相应PGW部署在相同节点的缓存服务器(cache server)或业务服务器。需要说明的是，图2仅作为一种示例，当本发明实施例的方案应用于2G或3G的网络架构时，上述SGW的功能可以由SGSN完成，上述PGW 的功能可以由GGSN完成。
图2中，SGW与PGW1之间已建立对应于UE的承载。当UE访问网络资源时，可以首先查找PGW1对应的本地服务器中是否存储有该资源，当本地服务器存储有该资源时，UE可以就近从本地服务器中获取资源，从而能够避免网络拥堵的状况，提高用户访问资源的响应速度。当PGW1对应的本地服务器中未存储该资源时，PGW1可以查询其他本地服务器中是否存储有该资源，当其他本地服务器(例如，与PGW2对应的本地服务器)中存储有该资源时，PGW1可以与其他本地服务器对应的PGW2建立承载，以获取该资源。然而，在PGW1通过与PGW2建立承载以获取资源的情况中，获取资源的路径迂回，影响UE的访问速度，且不利于节约网络资源。
基于此，本发明实施例提出了一种访问资源的方法，其主要思想是，在单一PDN链接下，服务网关除了与默认的分组网关建立承载之外，还可以与至少一个其他分组网关建立对应于同一UE的承载，从而有利于UE获取资源。例如，该方法可以包括：服务网关接收UE的IP报文，该IP报文中携带目标服务器的IP地址，该目标服务器中存储有该UE待访问的资源，其中，服务网关与第一分组网关之间具有对应于该UE的第一承载；服务网关根据上述IP地址确定目标服务器对应的第二分组网关；确定服务网关与第二分组网关之间的对应于该UE的第二承载，例如，可以建立该第二承载或从已存在的承载中选择该第二承载；以及，通过该第二承载传输UE的访问请求，该访问请求用于请求访问目标服务器中存储的上述资源。通过本发明实施例提供的方案，服务网关在接收到UE的访问请求之后，可以通过上述第二承载向第二分组网关发送UE的访问请求，以访问第二分组网关对应的目标服务器中存储的资源，从而能够避免访问路径的路由迂回，有利于提高UE访问的速度和效率，以及节约网络资源。
下面结合附图3，对本发明实施例提供的方案进行说明。图3示出了本发明实施例提供的一种访问资源的方法300。如图3所示，该方法300包括：
在S310部分，服务网关接收UE的IP报文，该IP报文中携带目标服务器的IP地址，该目标服务器中存储有UE待访问的资源，其中，服务网关与第一分组网关之间具有对应于UE的第一承载。例如，该IP报文可以是传输控制协议(Transmission Control Protocol，TCP)建立请求报文，或者该IP报文也可以是其他格式的IP报文。
在一个示例中，UE向服务网关发送该IP报文之前，还可以获取目标服务器的IP地址。例如，UE可以接收第一分组网关发送的目标服务器的IP地址。其中，第一分组网关可以向UE发送重定向消息(例如HTTP重定向 消息)，该重定向消息中包含目标服务器的IP地址。
在一个示例中，服务网关与第一分组网关之间的第一承载，可以是UE在与核心网建立PDN链接时，UE与第一分组网关之间建立的默认承载，该默认承载随着PDN的建立而建立，在PDN链接持续的情况下该默认承载始终存在。
在S320部分，服务网关根据该IP地址，确定目标服务器对应的第二分组网关。
在一个示例中服务网关根据该IP地址，确定目标服务器，以及确定目标服务器对应的第二分组网关。其中，第二分组网关可以是与目标服务器部署在同一节点的分组网关；或者，第二分组网关也可以是与目标服务器位于同一局域网(Local Area Network，LAN)的分组网关。
在S330部分，确定服务网关与第二分组网关之间的对应于UE的第二承载。
在一个示例中，服务网关可以确定服务网关与第二分组网关之间的对应于UE的第二承载。例如，服务网关可以从至少两个已有的承载中确定第二承载，该至少两个已有的承载为服务网关分别与至少两个分组网关之间的对应于UE的承载。
在另一个示例中，可以通过以下方式确定该第二承载：服务网关向第二分组网关发送承载建立请求，该承载建立请求用于建立第二承载；第二分组网关在接收到该承载建立请求后，建立该第二承载。其中，该承载请求消息中可以包含第二承载的参数信息，第二分组网关可以根据该参数信息建立该第二承载。进一步的，第二分组网关还可以向服务网关发送承载建立响应消息。例如，该承载建立请求可以是S5连接建立请求消息，该承载建立响应消息可以是S5连接建立响应消息。
在一个示例中，在服务网关向第二分组网关发送承载建立请求之前，服务网关还可以接收移动性管理网元或第一分组网关发送的指示消息，该指示消息中携带第二分组网关的IP地址，该指示消息用于指示在服务网关与第二分组网关之间建立第二承载。其中，移动性管理网元可以是MME。该指示消息可以是S5连接建立请求消息。在该示例中，移动性管理网元或第一分组网关发送指示消息之前，还可以接收缓存控制器发送的目标服务器的IP地址。
在S340部分，通过第二承载传输UE的访问请求，该访问请求用于请求访问目标服务器中存储的资源。例如，该UE的访问请求可以是HTTP请求。
在一个示例中，可以通过以下方式通过第二承载传输UE的访问请求：服务网关通过第二承载向第二分组网关发送访问请求；第二分组网关在接收到服务网关通过第二承载发送的UE的访问请求之后，还可以向服务网关回复响应消息，以完成响应流程。在完成响应流程后，服务网关和第二分组网关之间可以通过第二承载传输目标服务器中存储的资源。
在一个示例中，访问请求中可以包括目标服务器的IP地址，服务网关可以根据访问请求中的IP地址确定或选择通过第二承载传输UE的访问请求。
需要说明的是，该第一承载可以是UE通过基站、服务网关以及第一分组网关建立的对应于该UE的承载的一部分，例如所述第一承载可以是服务网关与第一分组网关之间的S5承载。可以理解的是，在UE经由服务网关通过第一承载向第一分组网关发送请求消息，或经由服务网关通过第二承载向第二分组网关发送请求消息的两种情况中，UE与服务网关之间的承载可以重用，从而提高了承载的利用效率。
可以理解的是，该第一承载和该第二承载对应于同一PDN链接，或者，可以理解为，本发明实施例提供的方案可以在同一PDN链接的条件下实现服务网关与多个分组网关锚点的连接，例如，在LTE系统中，可以实现SGW与多个PGW锚点的连接。
在本发明实施例中，服务网关在与第一分组网关之间存在对应于UE的第一承载的情况下，在服务网关与第二分组网关之间确定第二承载，使得UE能够通过第二承载访问第二分组网关对应的目标服务器中的资源，从而减少访问路径的路由迂回，提高了访问资源的效率。
在一个示例中，服务网关还可以接收第二分组网关发送的专用承载建立请求，专用承载建立请求用于请求建立服务网关与第二分组网关之间的对应于UE的第一专用承载；服务网关根据专用承载建立请求，建立第一专用承载；以及服务网关确定服务网关与UE之间的第二专用承载。
在本发明实施例中，服务网关与第二分组网关之间建立第一专用承载，并确定服务网关与UE之间的第二专用承载，以便通过第一专用承载和第二专用承载传输资源，以满足传输不同QoS的业务的需求。
应理解，在一个PDN链接中，可以存在一个默认承载和多个专用承载。其中默认承载是指满足默认的QoS的数据和信令的承载。默认承载在建立PDN链接时建立。而专用承载是指在PDN链接的基础上，为了提供某种特定的QoS传输需求而建立的承载。也就是说，专用承载是在默认承载建立的基础上建立的。通常情况下，专用承载的QoS比默认承载的QoS要求高。
上述第一专用承载可以指服务网关与分组网关之间建立默认承载之后， 为了传输对QoS要求更高的数据，在服务网关与分组网关之间建立的专用承载。例如，当服务网关与分组网关之间需要传输视频数据等对QoS要求较高的资源时，服务网关与分组网关可以建立用于传输视频数据的专用承载。
应理解，上述服务网关与UE之间的第二专用承载，是指服务网关与UE之间的专用承载，UE和PGW2之间通过第一专用承载和第二专用承载传输资源。其中，第二专用承载可以包括服务网关与基站之间的专用承载，以及基站与UE之间的无线专用承载。
在一个示例中，上述服务网关确定服务网关与UE之间的第二专用承载，包括：服务网关确定服务网关与UE之间存在专用承载，并将专用承载确定为第二专用承载；或者，服务网关确定服务网关与UE之间不存在专用承载，并建立第二专用承载。
在本发明实施例中，服务网关在确定服务网关与UE之间存在专用承载的情况下，无需再建立第二专用承载，将该专用承载确定为第二专用承载，该第二专用承载可以重用，以节约网络资源。
现有技术中SGW只可能与一个分组网关建立对应UE的第一专用承载。例如，现有技术中，SGW在与PGW1建立第一专用承载后，SGW需要与UE之间建立第二专用承载，以建立UE到PGW1之间的专用承载。而在本发明实施例中，SGW在接收到PGW2的第一专用承载请求时，SGW可能与其他PGW已建立第一专用承载，这说明SGW和UE之间已经建立专用承载，此时SGW无需再建立第二专用承载，只需将SGW和UE之间已存在的专用承载确认为第二专用承载。并通过第一专用承载和第二专用承载传输UE访问的资源。当服务网关与UE之间不存在专用承载时，服务网关建立该第二专用承载，能够节约网络资源，提高UE访问资源的效率。
在一个示例中，在本发明实施例中，在服务网关接收第一分组网关发送的专用承载建立请求的情况下，上述专用承载建立的方法中的第二分组网关可以置换为第一分组网关，此处不再赘述。
在一个示例中，本发明实施例提供的方法还可以包括：所述服务网关接收所述第二分组网关发送的专用承载修改请求，所述专用承载修改请求用于请求修改所述第一专用承载；所述服务网关根据所述专用承载修改请求修改所述第一专用承载；以及所述服务网关确定所述服务网关与所述第二分组网关以外的其他分组网关之间存在对应于所述UE的专用承载，并修改所述服务网关与所述第二分组网关以外的其他分组网关之间的专用承载。
在本发明实施例中，服务网关在修改与第二分组网关之间的第一专用承载的情况下，同时修改服务网关与除第二分组网关之外的其他分组网关之间 的专用承载，以确保UE与其他分组网关之间的专用承载的通信，提高访问资源的效率。
应理解，在本发明实施例中，服务网关接收到第二分组网关的专用承载修改请求后，需要修改服务网关与第二分组网关之间的第一专用承载，并且修改服务网关与UE之间的第二专用承载。此时，服务网关还需确定是否存在其他分组网关与第二分组网关共用该第二专用承载，或者说，服务网关还需要确定服务网关与除第二分组网关之外的其他网关之间是否存在对应于UE的专用承载，当存在专用承载时，服务网关还需修改服务网关与其他网关之间的专用承载，以确保UE与其他分组网关之间的专用承载的正常通信。
在本发明实施例中，在服务网关接收第一分组网关发送的专用承载修改请求的情况下，上述修改专用承载的方法中的第二分组网关可以置换为第一分组网关，此处不再赘述。
在一个示例中，本发明实施例提供的方法还包括：所述服务网关接收所述第二分组网关发送的专用承载删除请求，所述专用承载删除请求用于请求删除所述第一专用承载；所述服务网关根据所述专用承载请求删除所述第一专用承载；以及所述服务网关确定所述服务网关与所述第二分组网关以外的其他分组网关之间不存在对应于所述UE的专用承载，并删除所述第二专用承载，提高访问资源的效率。
在本发明实施例中，服务网关在删除与第二分组网关之间的第一专用承载的情况下，同时确定服务网关其他分组网关之间是否存在对应于UE的专用承载，当存在专用承载时，服务网关不删除服务网关与UE之间的专用承载，以确保UE与其他分组网关之间的专用承载的正常通信。
应理解，在本发明实施例中，服务网关接收到第二分组网关的专用承载删除请求后，需要删除服务网关与第二分组网关之间的第一专用承载，并且确定是否删除服务网关与UE之间的第二专用承载。此时，服务网关还需确定是否有其他分组网关与第二分组网关共用该第二专用承载，或者说，服务网关还需要确定服务网关与除第二分组网关之外的其他网关之间是否存在对应于UE的专用承载，当存在专用承载时，服务网关不删除第二专用承载，当服务网关与其他分组网关之间不存在对应于UE的专用承载时，服务网关删除第二专用承载，以确保UE与其他分组网关之间的专用承载的正常通信。
可选地，在本发明实施例中，在服务网关接收第一分组网关发送的专用承载删除请求的情况下，上述删除专用承载的方法中的第二分组网关可以置换为第一分组网关，此处不再赘述。
在现有技术中，UE在单一PDN链接条件下，服务网关只能与单个分组 网关建立对应于该UE的连接，当UE访问的资源位于本地其他分组网关对应的本地服务器中时，服务网关不支持在保持同一PDN链接的前提下，与其他分组网关建立对应于该UE的承载，从而影响UE获取资源的效率。而本发明实施例中，在服务网关与第一分组网关之间存在对应于UE的第一承载的情况下，还可以确定与至少一个其他分组网关(例如第二分组网关)之间的第二承载，从而可以通过第二承载传输UE的访问请求，以获取对应于第二分组网关的目标服务器中存储的资源。因此，本发明实施例的方案能够减少访问路径的路由迂回，有利于提高访问资源的效率。
下面将结合更多的附图，对本发明实施例的方案做进一步说明。
图4示出了本发明实施例提供的另一种访问资源的方法。如图4所示，服务网关可以为SGW，第一分组网关可以为PGW1，第一缓存服务器可以为PGW1对应的缓存服务器，第二缓存服务器可以为所述目标服务器，即第二缓存服务器存储有UE待访问的资源。PGW2可以为所述第二分组网关，即PGW2为第二缓存服务器对应的分组网关。缓存控制器可以用于调度和控制分布式缓存系统内的各缓存服务器，该第二承载可以为S5承载。
如图4所示，访问资源的方法可以如下所述：
在S401部分，UE与PGW1之间建立PDN链接。其中，SGW与PGW1之间建立S5承载。
在S402部分，UE通过PGW1与第一缓存服务器之间建立第一TCP连接。
在S403部分，UE通过PGW1向第一缓存服务器发送第一HTTP请求报文，该第一HTTP请求报文用于请求访问资源。
在S404部分，第一缓存服务器进行本地缓存查询，如果本地缓存没有命中，则向缓存控制器发送查询消息。
在S405部分，缓存控制器接收查询消息之后，在分布式缓存范围内进行缓存命中查询，在确定所述资源存储于第二缓存服务器中后，将第二缓存服务器的IP地址反馈给第一缓存服务器。
在S406部分，第一缓存服务器通过HTTP重定向消息将第二缓存服务器IP地址通知至UE，以便于UE根据该第二缓存服务器的IP地址，重新向第二缓存服务器发起第二HTTP请求报文；并向缓存控制器发送通知消息，该通知消息用于通知第一缓存服务器即将发送HTTP重定向消息。
在S407部分，在接收到第一缓存服务器发送的通知消息后，缓存控制器通知MME第二缓存服务器的IP地址；或者，缓存控制器根据第二缓存器的IP地址，确定PGW2的IP地址，向MME通知第二分组网关的IP地址。
在S408部分，MME获取PGW2的IP地址，或者，MME根据第二缓存服务器的IP地址，确定PGW2的IP地址，并向SGW发送建立S5连接建立指示消息，该建立S5连接建立指示消息中包括PGW2的IP地址。
在本部分中，服务网关通过MME发送的指示消息确定第二分组网关的IP地址，服务网关在MME的指示下提前建立第二承载，节约了UE访问资源的时间。
在S409部分，SGW在接收到MME的建立S5连接建立指示消息之后，确定PGW2的IP地址，并向PGW2发送S5承载连接建立请求消息，S5承载建立请求消息中包括S5承载的参数信息。
在S410部分，PGW2收到S5承载连接建立请求消息后，建立S5承载，并向SGW回复S5连接建立响应消息。
在S411部分，SGW接收UE发送的第二TCP建立请求报文，该第二TCP建立请求报文中包括第二缓存服务器的IP地址，SGW根据该第二缓存服务器的IP地址，确定PGW2的IP地址，并查找本地是否有对应的S5承载，若存在，则利用S5承载与第二缓存服务器之间建立TCP连接，若不存在，则建立对应的S5承载，再与第二缓存服务器建立TCP连接。
在S412部分，SGW接收UE发送的第二HTTP请求报文，该第二HTTP请求报文用于请求从第二缓存服务器中访问资源，SGW利用与PGW2之间的S5承载向UE传输资源。
图5示出了本发明实施例提供的又一种访问资源的方法。图5所示方法中，与图4所示方法相同或相似的内容可以参考与图4有关的详细描述，此处不再赘述。
如图5所示，访问资源的方法可以如下所述：
图5中的S501部分至S506与图4中的S401部分至S406部分相同或类似，可以参考图4中相应部分中的详细描述，此处不再赘述。
在S507部分，在接收到第一缓存服务器发送的通知消息后，缓存控制器通知PGW1第二缓存服务器的IP地址；或者，缓存控制器根据第二缓存器的IP地址，确定PGW2的IP地址，向PGW1通知第二分组网关的IP地址。
在S508部分，PGW1根据所述第二缓存服务器的IP地址，确定PGW2的IP地址，并向SGW发送建立S5连接建立指示消息，该建立S5连接建立指示消息中包括PGW2的IP地址。
本部分中，服务网关通过接收第一分组网关发送的指示消息，确定第二分组网关的IP地址，进而与在第一分组网关的指示下提前建立第二承载， 节约了UE访问资源的时间。
在S509部分，SGW在接收到PGW1的建立S5连接建立指示消息之后，确定PGW2的IP地址，并向PGW2发送S5承载连接建立请求消息。
在S510部分，PGW2收到S5承载连接建立请求消息后，建立S5承载，并向SGW回复S5连接建立响应消息。
在S511部分，SGW接收UE发送的第二TCP建立请求报文，该第二TCP建立请求报文中包括第二缓存服务器的IP地址，SGW根据该第二缓存服务器的IP地址，查找本地是否有对应的S5承载，若存在，则利用S5承载与第二缓存服务器之间建立TCP连接，若不存在，则建立对应的S5承载，再与第二缓存服务器建立TCP连接。
在S512部分，SGW接收UE发送的第二HTTP请求报文，该第二HTTP请求报文用于请求从第二缓存服务器中访问资源，SGW利用与PGW2之间的S5承载向UE传输资源。
为更清楚的说明上述方法中确定服务网关与第二分组网关之间的第二承载的方式，图6示出了本发明实施例提供的又一种访问资源的方法。图6所示方法中，与图4或5所示方法相同或相似的内容可以参考与图4或5有关的详细描述，此处不再赘述。
如图6所示，访问资源的方法可以如下所述：
图6中的S601部分至S606与图4中的S401部分至S406部分相同或类似，可以参考图4中相应部分中的详细描述，此处不再赘述。
在S607部分，SGW接收UE发送的第二TCP建立请求报文，该第二TCP建立请求报文中包括第二缓存服务器的IP地址，SGW根据该第二缓存服务器的IP地址，确定PGW2的IP地址，查找本地是否有对应PGW2的S5承载，若存在，则利用S5承载与第二缓存服务器之间建立TCP连接，若不存在，则向PGW2发送S5承载连接建立请求消息。
本发明实施例中，服务网关通过解析UE发送的IP报文，确定第二分组网关的IP地址，无需控制面的信令，直接建立第二承载，节约了网络资源。
在S608部分，PGW2收到S5承载连接建立请求消息后，建立S5承载，并向SGW回复S5承载连接建立响应消息。
在S609部分，SGW利用与PGW2之间的S5承载建立TCP连接。
在S610部分，SGW接收UE发送的第二HTTP请求报文，该第二HTTP请求报文用于请求从第二缓存服务器中访问资源，SGW利用与PGW2之间的S5承载向UE传输资源。
上文结合图1至图6详细的阐述了本发明实施例提供的方案。在此基础 上，根据业务的服务质量等级需求不同，UE还可以和第二分组网关建立专用承载，并利用专用承载访问资源。下文将结合图7至图9说明建立、修改以及删除专用承载的方法。其中，图7至图9所示的方法中，SGW与PGW1之间已存在默认承载(例如S5承载)，SGW与PGW2之间也已存在默认承载(例如S5承载)。
图7示出了本发明实施例提供的一种专用承载的建立方法的通信示意图。如图7所示，建立专用承载的方法包括：
在S701部分，SGW接收PGW2发送的专用承载建立请求，该专用承载建立请求用于请求建立SGW与PGW2之间的第一专用承载。
在S702部分，SGW确定SGW与UE之间是否存在专用承载。
在S703部分，当SGW与UE之间存在专用承载时，SGW将该专用承载确定为SGW与UE之间的第二专用承载，以及建立SGW与PGW2之间的第一专用承载。SGW在建立第一专用承载后，向PGW2发送专用承载建立响应消息，专用承载建立响应消息中包括该第一专用承载和第二专用承载的参数信息(例如，承载的ID标识)。
在S704部分，当SGW和UE之间不存在专用承载时，SGW建立SGW与PGW2之间的第一专用承载，以及建立SGW与UE之间的第二专用承载。SGW在建立第一专用承载之后，向PGW2发送专用承载建立响应消息。
本发明实施例中，在第二分组网关请求服务网关建立专用承载时，服务网关确定服务网关与UE之间是否存在专用承载，当存在专用承载时，将该专用承载确定为服务网关与UE之间的第二专用承载，只建立服务网关与第二分组网关之间的第一专用承载，并通过第一专用承载和第二资源传输UE访问的资源，节约了网络资源，提高了UE访问资源的效率。
图8示出了一种专用承载的修改方法的通信示意图，如图8所示，修改专用承载的方法包括：
在S801部分，SGW接收PGW2发送的专用承载修改请求，该专用承载修改请求用于请求修改SGW与PGW2之间的专用承载。
在S802部分，SGW确定SGW与除PGW2之外的其他PGW之间是否存在对应于UE的专用承载。
在S803部分，当SGW与其他PGW之间存在专用承载时，SGW修改SGW与PGW2之间的专用承载，并且修改SGW与其他分组网关之间的专用承载，以及SGW与UE之间的专用承载。
在S804部分，当SGW与其他PGW之间不存在专用承载时，SGW修改SGW与PGW2之间的专用承载，以及SGW与UE之间的专用承载。
本发明实施例中，在第二分组网关请求服务网关修改专用承载时，服务网关确定服务网关与其他分组网关之间是否存在专用承载，当服务网关与其他分组网关之间存在专用承载时，除了修改第二分组网关与服务网关之间的专用承载外，同时修改其他分组网关与服务网关之间的专用承载，保证服务网关与其他分组网关之间的通信，从而提高了访问资源的效率。
图9示出了一种专用承载的删除方法的通信示意图，如图9所示，删除专用承载的方法包括：
在S901部分，SGW接收PGW2发送的专用承载删除请求。
在S902部分，SGW确定SGW与除PGW2之外的其他PGW之间是否存在对应于UE的第一专用承载。
在S903部分，当SGW与其他PGW存在专用承载时，SGW删除SGW与PGW2之间的专用承载，不删除SGW与UE之间的第二专用承载。
在S904部分，当SGW与其他PGW不存在专用承载时，SGW删除SGW与PGW2之间的专用承载，以及删除SGW与UE之间的第二专用承载。
本发明实施例中，在第二分组网关请求服务网关删除专用承载时，服务网关确定服务网关与其他分组网关之间是否存在对应UE的专用承载，当服务网关与其他分组网关之间存在专用承载时，只删除服务网关与第二分组网关之间的专用承载，保留服务网关与UE之间的第二专用承载，以及服务网关与其他分组网关之间的专用承载，从而保证了服务网关与其他分组网关之间的通信，提高访问资源的效率。
需要说明的是，本发明实施例提供的方案在应用于不同的系统架构时，服务网关可以为SGW或SGSN，分组网关可以为PGW或GGSN。例如，当应用于图1所示的系统架构时，服务网关为SGW，分组网关为PGW。
上述主要从各个网元之间交互的角度对本发明实施例的方案进行了介绍。可以理解的是，各个网元，例如服务网关，第二分组网关，移动性管理网元等为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，本发明能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本发明的范围。
本发明实施例可以根据上述方法示例对服务网关、分组网关(例如第二分组网关)等进行功能单元的划分，例如，可以对应各个功能划分各个功能 单元，也可以将两个或两个以上的功能集成在一个处理单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。需要说明的是，本发明实施例中对单元的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。
在采用集成的单元的情况下，图10A示出了上述实施例中所涉及的服务网关的一种可能的结构示意图。服务网关1000包括：处理单元1002和通信单元1003。处理单元1002用于对服务网关的动作进行控制管理，例如，处理单元1002用于支持服务网关执行图3中的过程310～340，图4中的过程401、409、411和412，图5中的过程501、509、511和512，图6中的过程601、607、608、609和610，图7中的过程702～704，图8中的过程802～804，图9中的过程902～904，和/或用于本文所描述的技术的其它过程。通信单元1003用于支持服务网关与其他网络实体的通信，例如与图2中示出的基站、MME、PGW等之间的通信。服务网关还可以包括存储单元1001，用于存储服务网关的程序代码和数据。
其中，处理单元1002可以是处理器或控制器，例如可以是中央处理器(Central Processing Unit，CPU)，通用处理器，数字信号处理器(Digital Signal Processor，DSP)，专用集成电路(Application-Specific Integrated Circuit，ASIC)，现场可编程门阵列(Field Programmable Gate Array，FPGA)或者其他可编程逻辑器件、晶体管逻辑器件、硬件部件或者其任意组合。其可以实现或执行结合本发明公开内容所描述的各种示例性的逻辑方框，模块和电路。所述处理器也可以是实现计算功能的组合，例如包含一个或多个微处理器组合，DSP和微处理器的组合等等。通信单元1003可以是通信接口、收发器或收发电路等，其中，该通信接口是统称，在具体实现中，该通信接口可以包括多个接口，例如可以包括：服务网关和分组网关之间的接口，服务网关和移动性管理网元之间的接口和/或其他接口。存储单元1001可以是存储器。
当处理单元1002为处理器，通信单元1003为通信接口，存储单元1001为存储器时，本发明实施例所涉及的服务网关可以为图10B所示的服务网关。
参阅图10B所示，该服务网关1010包括：处理器1012、通信接口1013、存储器1011。可选的，服务网关1010还可以包括总线1014。其中，通信接口1013、处理器1012以及存储器1011可以通过总线1014相互连接；总线1014可以是外设部件互连标准(Peripheral Component Interconnect，简称PCI)总线或扩展工业标准结构(Extended Industry Standard Architecture，简称EISA)总线等。所述总线1014可以分为地址总线、数据总线、控制总线等。为便于表示，图10B中仅用一条粗线表示，但并不表示仅有一根总线或一种类型 的总线。
在采用集成的单元的情况下，图11A示出了上述实施例中所涉及的分组网关的一种可能的结构示意图。分组网关1100包括：处理单元1102和通信单元1103。处理单元1102用于对分组网关的动作进行控制管理，例如，处理单元1102用于支持分组网关执行图3中的过程330、340，图4中的过程410和412，图5中的过程510和512，图6中的过程608、610，图7中的过程701，图8中的过程801，图9中的过程901，和/或用于本文所描述的技术的其它过程。通信单元1103用于支持分组网关与其他网络实体的通信，例如与图2中示出的基站、MME、PGW等之间的通信。分组网关还可以包括存储单元1101，用于存储分组网关的程序代码和数据。
其中，处理单元1102可以是处理器或控制器，例如可以是中央处理器(Central Processing Unit，CPU)，通用处理器，数字信号处理器(Digital Signal Processor，DSP)，专用集成电路(Application-Specific Integrated Circuit，ASIC)，现场可编程门阵列(Field Programmable Gate Array，FPGA)或者其他可编程逻辑器件、晶体管逻辑器件、硬件部件或者其任意组合。其可以实现或执行结合本发明公开内容所描述的各种示例性的逻辑方框，模块和电路。所述处理器也可以是实现计算功能的组合，例如包含一个或多个微处理器组合，DSP和微处理器的组合等等。通信单元1103可以是通信接口、收发器或收发电路等，其中，该通信接口是统称，在具体实现中，该通信接口可以包括多个接口，例如可以包括：分组网关和服务网关之间的接口和/或其他接口。存储单元1101可以是存储器。
当处理单元1102为处理器，通信单元1103为通信接口，存储单元1101为存储器时，本发明实施例所涉及的分组网关可以为图11B所示的分组网关。
参阅图11B所示，该分组网关1110包括：处理器1112、通信接口1113、存储器1111。可选的，分组网关1110还可以包括总线1114。其中，通信接口1113、处理器1112以及存储器1111可以通过总线1114相互连接；总线1114可以是外设部件互连标准(Peripheral Component Interconnect，简称PCI)总线或扩展工业标准结构(Extended Industry Standard Architecture，简称EISA)总线等。所述总线1114可以分为地址总线、数据总线、控制总线等。为便于表示，图11B中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
在采用集成的单元的情况下，图12A示出了上述实施例中所涉及的移动性管理网元的一种可能的结构示意图。移动性管理网元1200包括：处理单元1202和通信单元1203。可选的，该移动性管理网元1200还可以包括：存 储单元1201。其中，存储单元1201用于存储程序，通信单元1203用于和其他设备通信，处理单元1202用于执行存储单元1201中的程序，当所述程序被执行时，所述处理单元用于执行图1至图9中的移动性管理网元所执行的步骤。为了简洁，适当省略重复的描述。
其中，当处理单元1202为处理器，通信单元1203为通信接口，存储单元1201为存储器时，本发明实施例所涉及的移动性管理网元可以为图12B所示的移动性管理网元。参阅图12B所示，该移动性管理网元1210包括：处理器1212、通信接口1213、存储器1211，总线1214。为了简洁，适当省略重复的描述。
用于执行本发明实施例上述服务网关、分组网关或移动性管理网元的功能的处理器可以是中央处理器(Central Processing Unit，CPU)，通用处理器、数字信号处理器(Digital Signal Processor，DSP)、专用集成电路(Application-Specific Integrated Circuit，ASIC)，现场可编程门阵列(Field Programmable Gate Array，FPGA)或者其他可编程逻辑器件、晶体管逻辑器件，硬件部件或者其任意组合。其可以实现或执行结合本发明实施例公开内容所描述的各种示例性的逻辑方框，模块和电路。所述处理器也可以是实现计算功能的组合，例如包含一个或多个微处理器组合，DSP和微处理器的组合等等。
结合本发明实施例公开内容所描述的方法或者算法的步骤可以硬件的方式来实现，也可以是由处理器执行软件指令的方式来实现。软件指令可以由相应的软件模块组成，软件模块可以被存放于随机存取存储器(Random Access Memory，RAM)、闪存、只读存储器(Read Only Memory，ROM)、可擦除可编程只读存储器(Erasable Programmable ROM，EPROM)、电可擦可编程只读存储器(Electrically EPROM，EEPROM)、寄存器、硬盘、移动硬盘、只读光盘(CD-ROM)或者本领域熟知的任何其它形式的存储介质中。一种示例性的存储介质耦合至处理器，从而使处理器能够从该存储介质读取信息，且可向该存储介质写入信息。当然，存储介质也可以是处理器的组成部分。处理器和存储介质可以位于ASIC中。另外，该ASIC可以位于网关设备或移动性管理网元中。当然，处理器和存储介质也可以作为分立组件存在于网关设备或移动性管理网元中。
本领域技术人员应该可以意识到，在上述一个或多个示例中，本发明实施例所描述的功能可以用硬件、软件、固件或它们的任意组合来实现。当使用软件实现时，可以将这些功能存储在计算机可读介质中或者作为计算机可读介质上的一个或多个指令或代码进行传输。计算机可读介质包括计算机存 储介质和通信介质，其中通信介质包括便于从一个地方向另一个地方传送计算机程序的任何介质。存储介质可以是通用或专用计算机能够存取的任何可用介质。
以上所述的具体实施方式，对本发明实施例的目的、技术方案和有益效果进行了进一步详细说明，所应理解的是，以上所述仅为本发明实施例的具体实施方式而已，并不用于限定本发明实施例的保护范围，凡在本发明实施例的技术方案的基础之上，所做的任何修改、等同替换、改进等，均应包括在本发明实施例的保护范围之内。

Claims (25)

  1. 一种访问资源的方法，其特征在于，包括：
    服务网关接收用户设备UE的互联网协议IP报文，所述IP报文中携带目标服务器的IP地址，所述目标服务器中存储有所述UE待访问的资源，其中，所述服务网关与第一分组网关之间具有对应于所述UE的第一承载；
    所述服务网关根据所述IP地址确定所述目标服务器对应的第二分组网关；
    所述服务网关确定所述服务网关与所述第二分组网关之间的对应于所述UE的第二承载；
    所述服务网关通过所述第二承载向所述第二分组网关发送所述UE的访问请求，所述访问请求用于请求访问所述目标服务器中存储的所述资源。
  2. 如权利要求1所述的方法，其特征在于，所述服务网关确定所述服务网关与所述第二分组网关之间的第二承载，包括：
    所述服务网关向所述第二分组网关发送承载建立请求，所述承载建立请求用于建立所述第二承载；或，
    所述服务网关从至少两个已有的承载中确定所述第二承载，所述至少两个已有的承载为所述服务网关分别与至少两个分组网关之间的对应于所述UE的承载。
  3. 如权利要求2所述的方法，其特征在于，所述方法还包括：
    所述服务网关接收移动性管理网元或所述第一分组网关发送的指示消息，所述指示消息中携带所述第二分组网关的IP地址，所述指示消息用于指示在所述服务网关与所述第二分组网关之间建立所述第二承载。
  4. 如权利要求1至3中任一项所述的方法，其特征在于，所述方法还包括：
    所述服务网关接收所述第二分组网关发送的专用承载建立请求，所述专用承载建立请求用于请求建立所述服务网关与所述第二分组网关之间的对应于所述UE的第一专用承载；
    所述服务网关根据所述专用承载建立请求，建立所述第一专用承载；以及
    所述服务网关确定所述服务网关与所述UE之间的第二专用承载。
  5. 如权利要求4所述的方法，其特征在于，所述服务网关确定所述服务网关与所述UE之间的第二专用承载，包括：
    所述服务网关确定所述服务网关与所述UE之间存在专用承载，并将所述专用承载确定为所述第二专用承载；或者，
    所述服务网关确定所述服务网关与所述UE之间不存在专用承载，并建立所述第二专用承载。
  6. 如权利要求4或5所述的方法，其特征在于，所述方法还包括：
    所述服务网关接收所述第二分组网关发送的专用承载修改请求，所述专用承载修改请求用于请求修改所述第一专用承载；
    所述服务网关根据所述专用承载修改请求修改所述第一专用承载；以及
    所述服务网关确定所述服务网关与所述第二分组网关以外的其他分组网关之间存在对应于所述UE的专用承载，并修改所述服务网关与所述第二分组网关以外的其他分组网关之间的专用承载。
  7. 如权利要求4至6中任一项所述的方法，其特征在于，所述方法还包括：
    所述服务网关接收所述第二分组网关发送的专用承载删除请求，所述专用承载删除请求用于请求删除所述第一专用承载；
    所述服务网关根据所述专用承载请求删除所述第一专用承载；以及
    所述服务网关确定所述服务网关与所述第二分组网关以外的其他分组网关之间不存在对应于所述UE的专用承载，并删除所述第二专用承载。
  8. 一种访问资源的方法，其特征在于，包括：
    第二分组网关确定所述第二分组网关与服务网关之间的对应于用户设备UE的第二承载，其中，所述服务网关与第一分组网关之间具有对应于所述UE的第一承载；
    所述第二分组网关接收所述服务网关通过所述第二承载发送的所述UE的访问请求，所述访问请求用于请求访问所述第二分组网关对应的目标服务器中存储的资源。
  9. 如权利要求8所述的方法，其特征在于，所述第二分组网关确定所述第二分组网关与所述服务网关之间的第二承载，包括：
    所述第二分组网关接收所述服务网关发送的承载建立请求，所述承载建立请求用于请求建立所述第二承载；
    所述第二分组网关根据所述承载建立请求，建立所述第二承载。
  10. 如权利要求8或9所述的方法，其特征在于，所述方法还包括：
    所述第二分组网关向所述服务网关发送专用承载建立请求，所述专用承载建立请求用于建立所述服务网关与所述第二分组网关之间的对应于所述UE的第一专用承载。
  11. 如权利要求10所述的方法，其特征在于，所述方法还包括：
    所述第二分组网关向所述服务网关发送专用承载修改请求，所述专用承 载修改请求用于请求修改所述第一专用承载。
  12. 如权利要求10或11所述的方法，其特征在于，所述方法还包括：
    所述第二分组网关向所述服务网关发送专用承载删除请求，所述专用承载删除请求用于请求删除所述第一专用承载。
  13. 一种服务网关，其特征在于，包括：处理单元和通信单元，
    所述处理单元用于通过所述通信单元接收用户设备UE的互联网协议IP报文，所述IP报文中携带目标服务器的IP地址，所述目标服务器中存储有所述UE待访问的资源，其中，所述服务网关与第一分组网关之间具有对应于所述UE的第一承载；以及用于根据所述IP地址确定所述目标服务器对应的第二分组网关；以及用于确定所述服务网关与所述第二分组网关之间的对应于所述UE的第二承载；以及用于通过所述通信单元通过所述第二承载向所述第二分组网关发送所述UE的访问请求，所述访问请求用于请求访问所述目标服务器中存储的所述资源。
  14. 如权利要求13所述的服务网关，其特征在于，所述处理单元具体用于通过所述通信单元向所述第二分组网关发送承载建立请求，所述承载建立请求用于建立所述第二承载；或，所述处理单元具体用于从至少两个已有的承载中确定所述第二承载，所述至少两个已有的承载为所述服务网关分别与至少两个分组网关之间的对应于所述UE的承载。
  15. 如权利要求14所述的服务网关，其特征在于，所述处理单元还用于通过所述通信单元接收移动性管理网元或所述第一分组网关发送的指示消息，所述指示消息中携带所述第二分组网关的IP地址，所述指示消息用于指示在所述服务网关与所述第二分组网关之间建立所述第二承载。
  16. 如权利要求13至15中任一项所述的服务网关，其特征在于，所述处理单元还用于通过所述通信单元接收所述第二分组网关发送的专用承载建立请求，所述专用承载建立请求用于请求建立所述服务网关与所述第二分组网关之间的对应于所述UE的第一专用承载；以及用于根据所述专用承载建立请求，建立所述第一专用承载；以及用于确定所述服务网关与所述UE之间的第二专用承载。
  17. 如权利要求16所述的服务网关，其特征在于，所述处理单元具体用于确定所述服务网关与所述UE之间存在专用承载，并将所述专用承载确定为所述第二专用承载；或者，所述处理单元具体用于确定所述服务网关与所述UE之间不存在专用承载，并建立所述第二专用承载。
  18. 如权利要求16或17所述的服务网关，其特征在于，所述处理单元还用于通过所述通信单元接收所述第二分组网关发送的专用承载修改请求， 所述专用承载修改请求用于请求修改所述第一专用承载；以及用于根据所述专用承载修改请求修改所述第一专用承载；以及用于确定所述服务网关与所述第二分组网关以外的其他分组网关之间存在对应于所述UE的专用承载，并修改所述服务网关与所述第二分组网关以外的其他分组网关之间的专用承载。
  19. 如权利要求16至18中任一项所述的服务网关，其特征在于，所述处理单元还用于通过所述通信单元接收所述第二分组网关发送的专用承载删除请求，所述专用承载删除请求用于请求删除所述第一专用承载；以及用于根据所述专用承载请求删除所述第一专用承载；以及用于确定所述服务网关与所述第二分组网关以外的其他分组网关之间不存在对应于所述UE的专用承载，并删除所述第二专用承载。
  20. 一种分组网关，其特征在于，所述分组网关为第二分组网关，包括：处理单元和通信单元，
    所述处理单元用于确定所述第二分组网关与服务网关之间的对应于用户设备UE的第二承载，其中，所述服务网关与第一分组网关之间具有对应于所述UE的第一承载；以及用于通过所述通信单元接收所述服务网关通过所述第二承载发送的所述UE的访问请求，所述访问请求用于请求访问所述第二分组网关对应的目标服务器中存储的资源。
  21. 如权利要求20所述的分组网关，其特征在于，所述通信单元具体用于通过所述通信单元接收所述服务网关发送的承载建立请求，所述承载建立请求用于请求建立所述第二承载；以及用于根据所述承载建立请求，建立所述第二承载。
  22. 如权利要求20或21所述的分组网关，其特征在于，所述处理单元还用于通过所述通信单元向所述服务网关发送专用承载建立请求，所述专用承载建立请求用于建立所述服务网关与所述第二分组网关之间的对应于所述UE的第一专用承载。
  23. 如权利要求22所述分组网关，其特征在于，所述处理单元还用于通过所述通信单元向所述服务网关发送专用承载修改请求，所述专用承载修改请求用于请求修改所述第一专用承载。
  24. 如权利要求22或23所述的分组网关，其特征在于，所述处理单元还用于通过所述通信单元向所述服务网关发送专用承载删除请求，所述专用承载删除请求用于请求删除所述第一专用承载。
  25. 一种通信系统，其特征在于，包括如权利要求13至19中任一项所述的服务网关和如权利要求20至24中任一项所述的分组网关。
PCT/CN2016/081921 2016-05-12 2016-05-12 访问资源的方法、装置和系统 WO2017193348A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
CN201680085637.2A CN109076625A (zh) 2016-05-12 2016-05-12 访问资源的方法、装置和系统
EP16901303.4A EP3451785A4 (en) 2016-05-12 2016-05-12 METHOD, DEVICE AND SYSTEM FOR ACCESSING A RESOURCE
PCT/CN2016/081921 WO2017193348A1 (zh) 2016-05-12 2016-05-12 访问资源的方法、装置和系统

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2016/081921 WO2017193348A1 (zh) 2016-05-12 2016-05-12 访问资源的方法、装置和系统

Publications (1)

Publication Number Publication Date
WO2017193348A1 true WO2017193348A1 (zh) 2017-11-16

Family

ID=60266863

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/081921 WO2017193348A1 (zh) 2016-05-12 2016-05-12 访问资源的方法、装置和系统

Country Status (3)

Country Link
EP (1) EP3451785A4 (zh)
CN (1) CN109076625A (zh)
WO (1) WO2017193348A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112312426B (zh) * 2019-07-31 2023-07-21 中国移动通信集团吉林有限公司 核心网网关的选择方法、移动性管理实体和网关设备

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101232724A (zh) * 2008-01-15 2008-07-30 中兴通讯股份有限公司 一种ip多媒体子系统中终呼的实现方法
CN101552978A (zh) * 2008-03-31 2009-10-07 华为技术有限公司 实现路由优化的方法、系统及装置
CN102036325A (zh) * 2009-09-28 2011-04-27 华为终端有限公司 一种建立或修改本地ip接入承载的方法和设备
US20120188983A1 (en) * 2009-08-25 2012-07-26 Telefonaktiebolaget L M Ericsson (Publ) Mobility Anchor Relocation

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20130041943A1 (en) * 2010-04-20 2013-02-14 Nec Corporation Distribution system, distribution control device, and distribution control method
US8848516B2 (en) * 2010-09-15 2014-09-30 Telefonaktiebolaget L M Ericsson (Publ) Methods and apparatus for relocating and restoring connections through a failed serving gateway and traffic offloading
CN103841607A (zh) * 2012-11-21 2014-06-04 中兴通讯股份有限公司 一种网关重定位的方法、移动管理实体及宿主基站
EP2919528B1 (en) * 2012-11-28 2018-01-10 Huawei Technologies Co., Ltd. Mobile network communication method, communication device and communication system
WO2015100553A1 (zh) * 2013-12-30 2015-07-09 华为技术有限公司 业务连续性判断方法和设备

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101232724A (zh) * 2008-01-15 2008-07-30 中兴通讯股份有限公司 一种ip多媒体子系统中终呼的实现方法
CN101552978A (zh) * 2008-03-31 2009-10-07 华为技术有限公司 实现路由优化的方法、系统及装置
US20120188983A1 (en) * 2009-08-25 2012-07-26 Telefonaktiebolaget L M Ericsson (Publ) Mobility Anchor Relocation
CN102036325A (zh) * 2009-09-28 2011-04-27 华为终端有限公司 一种建立或修改本地ip接入承载的方法和设备

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3451785A4 *

Also Published As

Publication number Publication date
CN109076625A (zh) 2018-12-21
EP3451785A1 (en) 2019-03-06
EP3451785A4 (en) 2019-05-15

Similar Documents

Publication Publication Date Title
USRE49729E1 (en) Session information management method and apparatus
WO2019196608A1 (zh) 传输数据的方法和装置
WO2014127515A1 (zh) 业务提供系统、方法、移动边缘应用服务器及支持节点
EP3457748B1 (en) Communication method and apparatus during switching
JP7209105B2 (ja) 拡張されたｕｐ機能要求ｐｆｃｐアソシエーション解放
US20180242188A1 (en) Quality of service control method, device, and system
US10827348B2 (en) Data transmission method and apparatus
EP3606005B1 (en) Redirection method, control plane network element, aggregation user plane network element, content server and terminal device
WO2019007226A1 (zh) 建立会话的方法和装置
WO2019128666A1 (zh) 一种会话建立的方法及装置
WO2020233249A1 (zh) 一种报文传输方法以及相关装置
WO2017177753A1 (zh) 一种基于流的承载管理方法、数据传输方法及装置
WO2018112759A1 (zh) 访问资源的方法、装置和系统
WO2019223702A1 (zh) 管理pdu会话的方法、装置和系统
WO2019091307A1 (zh) 通信方法和装置
WO2019076308A1 (zh) 终端设备的状态的确定方法、装置及设备
WO2018141278A1 (zh) 无线通信方法、用户设备、接入网设备和网络系统
WO2018018469A1 (zh) 用户设备上下文管理方法、装置和设备
WO2017101076A1 (zh) 一种发送下行数据通知消息的方法和装置
WO2017193348A1 (zh) 访问资源的方法、装置和系统
WO2017193344A1 (zh) 访问资源的方法、装置和系统
CN109155923B (zh) 用于传输报文的方法、装置和系统
CN109150752B (zh) 缓存控制方法、网元及控制器
CN113039835A (zh) 以信息为中心的联网中的移动性管理
WO2017193346A1 (zh) 访问资源的方法、装置和系统

Legal Events

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

Ref country code: DE

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

Ref document number: 16901303

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2016901303

Country of ref document: EP

Effective date: 20181130