WO2017193346A1 - Resource access method, device and system - Google Patents

Resource access method, device and system Download PDF

Info

Publication number
WO2017193346A1
WO2017193346A1 PCT/CN2016/081918 CN2016081918W WO2017193346A1 WO 2017193346 A1 WO2017193346 A1 WO 2017193346A1 CN 2016081918 W CN2016081918 W CN 2016081918W WO 2017193346 A1 WO2017193346 A1 WO 2017193346A1
Authority
WO
WIPO (PCT)
Prior art keywords
gateway
bearer
packet gateway
lightweight
packet
Prior art date
Application number
PCT/CN2016/081918
Other languages
French (fr)
Chinese (zh)
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 CN201680085627.9A priority Critical patent/CN109155752A/en
Priority to PCT/CN2016/081918 priority patent/WO2017193346A1/en
Publication of WO2017193346A1 publication Critical patent/WO2017193346A1/en

Links

Images

Definitions

  • the present invention relates to the field of communications technologies, and in particular, to a method, apparatus, 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 lightweight packet gateway, a service gateway, a packet gateway, a mobility management network element and a system, so as to improve the efficiency of accessing resources.
  • the embodiment of the present invention provides a method for accessing a resource, including: the serving gateway receives the IP packet of the first UE, where the IP packet carries the IP address of the target server, and the target server stores the first UE to be accessed. a resource, wherein the serving gateway and the first packet gateway have a first bearer corresponding to the first UE; the serving gateway determines a first lightweight packet gateway corresponding to the target server according to the IP address; the serving gateway determines the serving gateway and the first a second bearer corresponding to the first UE between the lightweight packet gateways; the serving gateway sends an access request of the first UE to the first lightweight packet gateway by using the second bearer, where the access request is used to request access to the target server Stored resources.
  • the lightweight packet gateway sends the charging information generated by the first UE accessing the resource to the first packet gateway, so that the first packet gateway performs charging.
  • the serving gateway may send an access request of the UE to the first lightweight packet gateway by using the second bearer to access the corresponding one of the first lightweight packet gateway.
  • the resource stored in the target server, and the charging information of the UE accessing the resource is sent by the first lightweight packet gateway to the first packet gateway for charging, thereby avoiding routing detour of the access path, which is beneficial to improving UE access. Speed and efficiency, as well as saving network resources.
  • the second bearer between the serving gateway and the first lightweight packet gateway may be determined in one of the following manners:
  • the serving gateway sends a bearer setup request to the first lightweight packet gateway.
  • the bearer setup request is used to request to establish the second bearer;
  • the serving gateway receives the bearer setup response sent by the first lightweight packet gateway, and the bearer setup response is used to indicate that the second bearer has been established;
  • the second manner the service gateway is from at least two
  • the second bearer is determined in the existing bearer, and the at least two existing bearers are bearers corresponding to the first UE between the serving gateway and the at least two gateways.
  • the serving gateway may receive the first information sent by the mobility management network element, where the first information is used to indicate that the third gateway corresponding to the second UE is established between the serving gateway and the second lightweight packet gateway.
  • Bearer when the serving gateway supports establishing a bearer between the serving gateway and the second lightweight packet gateway, the serving gateway establishes a third bearer between the serving gateway and the second lightweight packet gateway; or, when the serving gateway does not support
  • the serving gateway establishes a bearer corresponding to the second UE between the second packet gateway corresponding to the second lightweight packet gateway and the serving gateway, thereby
  • the serving gateway is capable of interacting with the second UE via the second packet gateway and the second lightweight packet gateway.
  • the serving gateway may send the second information to the mobility management network element, where the second information is used to notify the mobility management network element service gateway to support or not support the service gateway and the second lightweight packet gateway. Establish a bearer between.
  • a dedicated bearer corresponding to the UE between the first packet gateway and the lightweight packet gateway may also be established.
  • the lightweight packet gateway sends a dedicated bearer setup request to the first packet gateway for requesting establishment of a first dedicated bearer corresponding to the UE between the lightweight packet gateway and the first packet gateway.
  • the first packet gateway establishes a first dedicated bearer according to the dedicated bearer setup request; the first packet gateway determines a second dedicated bearer between the first packet gateway and the UE; and the first packet gateway instructs the serving gateway to establish a serving gateway and a lightweight packet
  • the third dedicated bearer between the gateways may be established.
  • the first packet gateway may determine, by using the following manner, a second dedicated bearer between the first packet gateway and the UE: the first packet gateway determines that a dedicated bearer exists between the first packet gateway and the UE, and Determining the dedicated bearer as the second dedicated bearer; or, the first packet gateway determines that there is no dedicated bearer between the first packet gateway and the UE, and establishing the second dedicated bearer. There is no need to establish other bearers, so that the utilization of the bearer resources can be improved to save network resources.
  • a dedicated bearer between the first packet gateway and the lightweight packet gateway can also be modified.
  • the lightweight packet gateway sends a dedicated bearer modification request to the first packet gateway, where the dedicated bearer modification request is used to request to modify the first dedicated bearer; after receiving the dedicated bearer modification request, the first packet gateway is configured according to the Dedicating a dedicated bearer modification request to modify the first dedicated Carrying, and instructing the serving gateway to modify the third dedicated bearer; the first packet gateway determines that there is a corresponding to the UE between the first packet gateway and other gateways other than the lightweight packet gateway Dedicated bearer, and newly create a dedicated bearer between the first packet gateway and the UE.
  • the first packet gateway modifies the first dedicated bearer, it is determined that there is a dedicated bearer corresponding to the UE between the first packet gateway and other gateways other than the lightweight packet gateway, that is, the lightweight packet gateway shares the same with other gateways.
  • the two dedicated bearers the first packet gateway establishes a dedicated bearer between the first packet gateway and the UE, to ensure communication of the dedicated bearer between the UE and other gateways, and improve the efficiency of accessing resources.
  • the first dedicated bearer between the first packet gateway and the lightweight packet gateway may also be deleted, and the method further includes: the lightweight packet gateway sends a dedicated bearer deletion request to the first packet gateway, and the dedicated bearer is deleted.
  • the request is for requesting to delete the first dedicated bearer; after receiving the dedicated bearer deletion request, the first packet gateway deletes the first dedicated bearer, and instructs the serving gateway to delete the third dedicated bearer;
  • a packet gateway determines that the first packet gateway and other gateways other than the lightweight packet gateway do not have a dedicated bearer corresponding to the UE, and deletes the second dedicated bearer.
  • the first packet gateway determines whether there is a dedicated bearer corresponding to the UE between the other gateways of the first packet gateway in the case of deleting the first dedicated bearer between the first packet gateway, and when there is a dedicated bearer, the first The packet gateway does not delete the dedicated bearer between the first packet gateway and the UE to ensure normal communication of the dedicated bearer between the UE and other gateways.
  • the target server may be a service server or a cache server.
  • the lightweight packet gateway can be located at the same node as the target server.
  • the serving gateway may be an SGW or a Serving General Packet Radio Service Support Node (SGSN); the first packet gateway may be a packet data network gateway PGW or a gateway general packet radio technical support node. (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 lightweight packet gateway, which may be referred to as a target lightweight packet gateway, and the target lightweight packet gateway has a lightweight target for implementing the foregoing method design.
  • the function of grouping gateway behavior 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 target lightweight packet gateway includes a processing unit and a communication unit, the processing unit being configured to support the target lightweight packet gateway to perform the corresponding function in the above method.
  • the communication unit is configured to support communication between the target lightweight packet gateway and other devices.
  • the target lightweight packet gateway may also include a storage unit for coupling with the processing unit to store program instructions and data necessary for the target lightweight 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 packet gateway, which may be referred to as a first packet gateway, and the first packet gateway has a function of implementing a behavior of a first packet gateway 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 first packet gateway structure includes a processing unit and a communication unit, the processing unit being configured to support the first packet gateway to perform a corresponding function in the above method.
  • the communication unit is configured to support communication between the first packet gateway and other devices.
  • the first packet gateway may further comprise a storage unit for coupling with the processing unit, which stores program instructions and data necessary for the first packet gateway.
  • the processing unit can be a processor
  • the communication unit can be a communication interface
  • the storage unit can be a memory.
  • the embodiment of the present invention provides a mobility management network element, which may be referred to as a first mobility management network element, where the first mobility management network element has the first implementation in the foregoing method design.
  • the function of mobility management network element behavior 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 first mobility management network element includes a processing unit and a communication unit, and the processing unit is configured to support the first mobility management network element to perform a corresponding function in the foregoing method.
  • the communication unit is configured to support communication between the first mobility management network element and other devices.
  • the first mobility management network element may further include a storage unit, where the storage unit is configured to be coupled to the processing unit, where the program instructions and data necessary for the first mobility management network element are saved.
  • 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, including the service gateway and the lightweight packet gateway described in the foregoing aspect; or the system includes the service gateway described in the foregoing aspect, Lightweight packet gateway, first packet gateway, and mobility management network element.
  • 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 lightweight packet 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 first 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 according to the IP address.
  • the IP address of the target server carried in the packet determines the first lightweight packet gateway corresponding to the target server, determines the second bearer corresponding to the UE between the base station and the first lightweight packet gateway, and transmits the second bearer through the second bearer.
  • the charging information of the UE accessing the resource is sent by the first lightweight packet gateway to the first packet gateway for charging, thereby facilitating the function of the first lightweight packet gateway.
  • 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 applied by 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 a method for establishing a dedicated bearer according to an embodiment of the present invention.
  • FIG. 7 is a schematic diagram of communication of a method for modifying a dedicated bearer according to an embodiment of the present invention.
  • FIG. 8 is a schematic diagram of communication of a method for deleting a dedicated bearer according to an embodiment of the present invention.
  • 9A is a schematic structural diagram of a service gateway according to an embodiment of the present invention.
  • FIG. 9B is a schematic structural diagram of another service gateway according to an embodiment of the present disclosure.
  • FIG. 10A is a schematic structural diagram of a lightweight packet gateway according to an embodiment of the present invention.
  • FIG. 10B is a schematic structural diagram of another lightweight packet 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 according to an embodiment of the present disclosure.
  • 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 Subsystem
  • PSS Packet Switched Streaming Service
  • LTE Long Term Evolution
  • CDMA Code Division Multiple Access
  • FDMA Frequency Division Multiple Access
  • TDMA Time Division Multiple Access
  • OFDMA Orthogonal Frequency Division Multiple Access
  • SC-FDMA Single Carrier Frequency Division Multiple Access
  • SC-FDMA Single Carrier Frequency Division Multiple Access
  • SC-FDMA Single Carrier Frequency Division Multiple Access
  • SC-FDMA Single Carrier Frequency Division Multiple Access
  • SC-FDMA Single Carrier Frequency Division Multiple Access
  • SC-FDMA Single Carrier Frequency Division Multiple Access
  • SC-FDMA Single Carrier Frequency Division Multiple Access
  • SC-FDMA Single Carrier Frequency Division Multiple Access
  • SC-FDMA Single Carrier Frequency Division Multiple Access
  • E-UTRAN Evolved Universal Terrestrial Radio Access Network
  • EPC Evolved Packet Core
  • the UE accesses the IMS network through E-UTRAN and EPC.
  • the user equipment UE involved in the embodiment of the present invention may include each Handheld devices with wireless communication capabilities, in-vehicle devices, wearable devices, computing devices or other processing devices connected to wireless modems, and various forms of User Equipment (UE), Mobile Station (MS) , terminal, terminal device, etc.
  • UE User Equipment
  • MS Mobile Station
  • terminal terminal device
  • a base station (BS) 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 PGW through the SGW.
  • the Mobility Management Entity (MME) is used as the control plane network element, and is connected to the base station and the SGW through the port respectively. Signaling for transmitting control planes to base stations and SGWs.
  • other gateways such as lightweight packet gateways, are also included in the system architecture shown in FIG. 2.
  • the lightweight packet gateway may be a gateway with data routing and forwarding functions.
  • the lightweight packet gateway may also be referred to as a lightweight PGW.
  • the lightweight packet gateway may not include a charging function, and the lightweight packet gateway may send charging information generated when the UE accesses the resource through the lightweight packet gateway to the PGW, and the PGW performs charging.
  • a local server is usually deployed at a PGW, a lightweight packet gateway, etc., for example, the local server may be a cache server or a service server deployed on the same node as the corresponding packet gateway.
  • FIG. 2 is only an example.
  • the function of the SGW may be completed by the SGSN
  • the function of the PGW may be completed by the GGSN.
  • a bearer corresponding to the UE has been established between the SGW and the PGW.
  • the UE accesses the network resource, it may first find whether the resource is stored in the local server corresponding to the PGW.
  • 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 When the resource is not stored in the local server corresponding to the PGW, the PGW can query whether the resource is stored in the other local server.
  • the PGW can establish a bearer with the corresponding packet gateway of the other local service. To get the resource.
  • the PGW establishes a bearer with other packet gateways to acquire resources, the path of the obtained resource is bypassed, 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 be combined with at least one lightweight packet gateway in addition to the default packet gateway. A bearer corresponding to the same UE is established, 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 first lightweight packet gateway corresponding to the target server according to the IP address; the serving gateway determines that the serving gateway and the first lightweight packet gateway correspond to the UE a second bearer, for example, the second bearer may be established or selected from an existing bearer; and the serving gateway sends an access request of the UE to the first lightweight packet gateway by using the second bearer, where The access request is used to request access to the above resources stored in the target server.
  • the first lightweight packet gateway may transmit the resource to the UE by using the second bearer; the first lightweight packet gateway may further send, by the first packet gateway, the UE to access the resource. Billing information to enable the first packet gateway to perform charging.
  • the serving gateway may send an access request of the UE to the first lightweight packet gateway by using the second bearer to access the first lightweight packet gateway.
  • the resource stored in the target server does not need to request resources from the first bearer corresponding to the first lightweight packet gateway through the first bearer between the serving gateway and the first packet gateway, thereby avoiding route routing of the access path, It is beneficial to improve the speed and efficiency of UE access and save network resources.
  • the charging information of the UE accessing the resource is sent by the first lightweight packet gateway to the first packet gateway for charging, thereby facilitating the function of the first lightweight packet gateway, and implementing the present invention.
  • the solution of the example has better compatibility with the prior art.
  • FIG. 3 is a schematic flowchart of a method 300 for accessing a resource according to an embodiment of the present invention. As shown in FIG. 3, the method 300 includes:
  • the serving gateway receives the IP packet of the first UE, where the IP packet carries the IP address of the target server, and the target server stores the resource to be accessed by the first UE, where the serving gateway and the first packet gateway have Corresponding to the first bearer of the first UE.
  • the IP packet 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 first 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 first UE (for example 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 first UE and the first packet gateway when the first UE establishes a PDN link with the core network, where The default bearer is established with the establishment of the PDN, and the default bearer always exists if the PDN link continues.
  • the serving gateway determines, according to the IP address, a first lightweight packet gateway corresponding to the target server;
  • the base station determines the target server according to the IP address, and then determines the first lightweight packet gateway corresponding to the target server.
  • the determining the first lightweight packet gateway may be determining an IP address of the first lightweight packet gateway.
  • the first lightweight packet gateway may be a gateway deployed on the same node as the target server; or the first lightweight packet gateway may be a gateway located on the same local area network (LAN) as the target server.
  • the first lightweight packet gateway may not include the charging function, and the first lightweight packet gateway may send the charging information generated by the first UE to the target server to the first packet gateway, and the first packet gateway performs charging.
  • the serving gateway determines a second bearer corresponding to the first UE between the serving gateway and the first lightweight packet gateway;
  • the serving gateway may determine the second bearer from the at least two existing bearers, where the at least two existing bearers are the bearers corresponding to the first UE between the serving gateway and the at least two gateways respectively.
  • the at least two gateways may include a first packet gateway, and may also include at least one lightweight packet gateway.
  • the second bearer can be determined by the serving gateway sending a bearer setup request to the first lightweight packet gateway, the bearer setup request for requesting to establish the second bearer.
  • the bearer request message may include parameter information of the second bearer, where the parameter information may be used to establish the second bearer.
  • the first lightweight packet gateway may further send a bearer setup response to the serving gateway after the second bearer is established, where the bearer setup response is used to indicate that the second bearer has been established.
  • the bearer setup request may be an S5 connection setup request message
  • the bearer setup response may be an S5 connection setup response message.
  • the serving gateway sends an access request of the first UE to the first lightweight packet gateway by using the second bearer, where the access request is used to request access to the resource stored in the target server, where the first UE accesses the resource
  • the generated charging information is sent by the first lightweight packet gateway to the first packet gateway, so that the first packet gateway performs charging.
  • the access request may include an IP address of the target server, and the serving gateway may determine or select a second bearer to transmit an access request of the first UE according to the IP address in the access request.
  • the first bearer may be the first UE through the base station, the serving gateway, and the first A part of the bearer established by the packet gateway corresponding to the first UE, it may be understood that the first UE sends a request message to the first packet gateway through the first bearer via the serving gateway, or through the second bearer via the serving gateway.
  • the bearer between the first UE and the serving gateway can be reused, thereby improving the utilization efficiency of the bearer.
  • the first lightweight packet gateway transmits the foregoing resource to the first UE by using the second bearer.
  • the first lightweight packet gateway may send a dedicated bearer setup request to the first packet gateway, where the dedicated bearer setup request is used to request to establish a correspondence between the lightweight packet gateway and the first packet gateway corresponding to the first UE.
  • Dedicated bearer may be used to request to establish a correspondence between the lightweight packet gateway and the first packet gateway corresponding to the first UE.
  • the first lightweight packet gateway may further send a dedicated bearer modification request to the first packet gateway, where the dedicated bearer modification request is used to request to modify the dedicated bearer.
  • the first lightweight packet gateway may further send a dedicated bearer deletion request to the first packet gateway, where the dedicated bearer deletion request is used to request to delete the dedicated bearer.
  • the first lightweight packet gateway sends, to the first packet gateway, charging information generated by the first UE accessing the foregoing resource, so that the first packet gateway performs charging.
  • the charging information generated by the UE accessing the resource is sent by the first lightweight packet gateway to the first packet gateway for charging, so that the operation of the first lightweight packet gateway can be simplified.
  • the charging information generated by the UE is charged by the first packet gateway.
  • the first packet gateway counts the UE to access the resource through the first lightweight packet gateway. The generated charging can make the solution of the embodiment of the present invention have better compatibility with the prior art.
  • the solution provided by the embodiment of the present invention may further include an Option 1: a scheme in which the UE accesses the resource when the terminal switches between different serving gateways.
  • the UE accessing the resource may be performed on the basis of performing the method shown in FIG. 3, or may not be performed based on the scheme shown in FIG. 3.
  • the different service gateways may correspond to the same packet gateway, or may correspond to different packet gateways.
  • the scheme for the UE to access the resources may refer to the schemes of different service gateways corresponding to different packet gateways, and details are not described herein.
  • the following uses the different service gateways as the first service gateway and the second service gateway.
  • the first service gateway corresponds to the first packet gateway
  • the second service gateway corresponds to the second packet gateway.
  • the scheme for accessing resources by the second UE in the case of a handover may include the following parts, wherein the embodiment of the present invention does not limit the execution order of the respective sections.
  • the second serving gateway may have a first bearer (eg, a default bearer) corresponding to the second UE, and the second serving gateway and the second lightweight packet gateway correspond to the first The second bearer of the two UEs.
  • a first bearer eg, a default bearer
  • the mobility management network element sends first information to the first serving gateway, where the first information is used to indicate the first serving gateway and
  • the second lightweight packet gateway establishes a third bearer corresponding to the second UE.
  • the second serving gateway may receive the setup session request message sent by the mobility management network element, where the setup session request message may be used to indicate that the bearer corresponding to the second UE is established between the first serving gateway and the second packet gateway. (ie default bearer).
  • the setup session request message may carry the first information.
  • the first information may be carried on a private extension information element IE that establishes a session request message.
  • the first serving gateway may establish a bearer with the first packet gateway, and may send a setup session request response message to the mobility management network element after establishing the bearer.
  • the first serving gateway determines whether the first serving gateway supports establishing a bearer corresponding to the second UE with the second lightweight packet gateway. And sending the second information to the mobility management network element, where the second information is used to notify the mobility management network element that the first serving gateway supports or does not support directly establishing the bearer between the first serving gateway and the second lightweight packet gateway.
  • the above establishment session request response message may carry the second information.
  • the second information can be carried on a private extension IE that establishes a session request response message.
  • the foregoing second information may also be used to explain why the first serving gateway does not support the first lightweight packet gateway.
  • the first serving gateway may not send the second information, and the mobility management network element determines that the second information is not received, or When the second information is not included in the establishment session request response message, it is determined that the first service gateway does not support establishing a bearer with the first lightweight packet gateway.
  • the first serving gateway when the first serving gateway supports directly establishing a bearer between the first serving gateway and the second lightweight packet gateway, the first serving gateway is in the first serving gateway and the second lightweight packet gateway.
  • the bearer is directly established; or, when the first serving gateway does not support establishing a bearer directly between the first serving gateway and the second lightweight packet gateway, the first serving gateway may be corresponding to the second lightweight packet gateway.
  • a bearer corresponding to the second UE is established between the second packet gateway and the first serving gateway. So that the first serving gateway is related to the second lightweight packet gateway via the second packet gateway.
  • the interaction of the second UE (or the first serving gateway through the bearer between the first serving gateway and the second packet gateway and the bearer transmission between the second packet gateway and the second lightweight packet gateway corresponds to the second UE Resources).
  • the second packet gateway is a packet gateway corresponding to the default bearer of the second UE.
  • the first serving gateway may also be referred to as a target serving gateway, and the second serving gateway may also be referred to as a source serving gateway.
  • the first serving gateway or the second serving gateway may be the serving gateway in FIG. 1 to FIG.
  • the mobility management network element when the serving gateway is switched, sends the setup session request message to the first serving gateway, where the first information is used, where the first information is used to indicate the first serving gateway and the second lightweight
  • the type of packet gateway establishes a bearer.
  • the additional message is sent to the first serving gateway, which saves signaling overhead and improves the efficiency of accessing resources.
  • the first serving gateway when the serving gateway is switched, the first serving gateway sends a setup session request response message to the mobility management network element, where the second information is used to indicate whether the first serving gateway supports the first
  • the service gateway establishes a bearer with the first lightweight packet gateway, which avoids sending additional messages to the mobility management network element, saves signaling overhead, and improves the efficiency of accessing resources.
  • the solution provided by the embodiment of the present invention may further include Option 2: establishing a dedicated bearer between the packet gateway and the lightweight packet gateway to transmit resources accessed by the UE.
  • a dedicated bearer is established between the packet gateway and the lightweight packet gateway, and may be executed on the basis of performing the method shown in FIG. 3, or may not be performed based on the method shown in FIG. 3.
  • the packet gateway may be the first packet gateway in FIG. 3
  • the lightweight packet gateway may be the first lightweight packet gateway in FIG. 3
  • the UE may be the first UE in FIG.
  • the implementation of the dedicated bearer between the first packet gateway and the lightweight packet gateway may include the following parts, wherein the embodiment of the present invention does not limit the execution order of the respective parts.
  • the first packet gateway receives a dedicated bearer setup request sent by the lightweight packet gateway, and the dedicated bearer setup request is used to request to establish a first dedicated bearer corresponding to the UE between the first packet gateway and the lightweight packet gateway.
  • the default bearer refers to the bearer of data and signaling that meets the default Quality of Service (QoS).
  • QoS Quality of Service
  • a dedicated bearer is a bearer established on the basis of a PDN link to provide a specific QoS transmission requirement. In general, the QoS of a dedicated bearer is higher than the QoS requirement of a default bearer.
  • the first packet gateway establishes a first dedicated bearer according to the dedicated bearer setup request; the first packet gateway determines a second dedicated bearer between the first packet gateway and the UE; and the first packet gateway instructs the serving gateway to establish a serving gateway A third dedicated bearer with a lightweight packet gateway.
  • the first packet gateway determines the second dedicated bearer between the first packet gateway and the UE, where the first packet gateway determines that there is a dedicated bearer between the first packet gateway and the UE, and the dedicated bearer is used. Determining to be the second dedicated bearer; or, the first packet gateway determines that there is no dedicated bearer between the first packet gateway and the UE, and establishes a second dedicated bearer.
  • the second dedicated bearer between the first packet gateway and the UE refers to a dedicated bearer between the first packet gateway and the UE, and the first dedicated bearer and the second between the UE and the lightweight packet gateway may be adopted.
  • the second dedicated bearer may include a dedicated bearer between the first packet gateway and the serving gateway, a dedicated bearer between the serving gateway and the base station, and a wireless dedicated bearer between the base station and the UE.
  • the UE may also transmit resources through the third dedicated bearer and the dedicated bearer between the serving gateway and the UE simultaneously with the lightweight gateway.
  • the first packet gateway may only establish a first dedicated bearer corresponding to the UE with one gateway. For example, after the first packet gateway establishes the first dedicated bearer with the PGW2, the first packet gateway needs to establish a second dedicated bearer with the UE to establish a dedicated bearer between the UE and the PGW2.
  • the first packet gateway may establish a dedicated bearer with other gateways, which indicates that the first packet gateway and the UE are A dedicated bearer has been established. At this time, the first packet gateway does not need to establish the second dedicated bearer, and only the dedicated bearer existing between the first packet gateway and the UE is confirmed as the second dedicated bearer.
  • the first packet gateway establishes the second dedicated bearer, which can save network resources and improve the efficiency of the UE accessing resources.
  • the solution provided by the embodiment of the present invention may further include Option 3: modifying a dedicated bearer between the first packet gateway and the lightweight packet gateway.
  • Option 3 modifying a dedicated bearer between the first packet gateway and the lightweight packet gateway.
  • the first packet gateway receives a dedicated bearer modification request sent by the lightweight packet gateway, and the dedicated bearer modification request is used to request to modify the first dedicated bearer;
  • the first packet gateway modifies the first dedicated bearer according to the dedicated bearer modification request, and instructs the serving gateway to modify the third dedicated bearer;
  • the first packet gateway determines that there is a dedicated bearer corresponding to the UE between the first packet gateway and other gateways other than the lightweight packet gateway, and creates a dedicated bearer between the first packet gateway and the UE.
  • the first packet gateway after receiving the dedicated bearer modification request of the lightweight packet gateway, the first packet gateway needs to modify the first dedicated bearer between the first packet gateway and the lightweight packet gateway, and modify A third dedicated bearer between the first packet gateway and the UE.
  • the group gateway also needs to determine whether there is another gateway sharing the second dedicated bearer with the lightweight packet gateway, or the first packet gateway needs to determine between the first packet gateway and other gateways other than the lightweight packet gateway. Whether there is a dedicated bearer corresponding to the UE.
  • the first packet gateway needs to newly establish a dedicated bearer between the first packet gateway and the UE, that is, the lightweight packet gateway uses the newly created dedicated bearer to transmit data.
  • Other gateways use the second dedicated bearer to transmit data to ensure proper communication of the dedicated bearer between the UE and other gateways.
  • the second packet gateway modifies the second dedicated bearer.
  • the first packet gateway when modifying the first dedicated bearer between the packet and the lightweight packet gateway, simultaneously instructs the serving gateway to modify the third dedicated bearer, and determines the first packet gateway and the lightweight type.
  • the solution provided by the embodiment of the present invention may further include Option 4: deleting the dedicated bearer between the first packet gateway and the lightweight packet gateway. It should be noted that the method for deleting a dedicated bearer may be performed on the basis of establishing a dedicated bearer between the first packet gateway and the lightweight packet gateway. The following parts may be included, wherein the embodiment of the invention does not limit the order of execution of the various parts.
  • the first packet gateway receives a dedicated bearer deletion request sent by the lightweight packet gateway, and the dedicated bearer deletion request is used to request to delete the first dedicated bearer;
  • the first packet gateway deletes the first dedicated bearer, and instructs the serving gateway to delete the third dedicated bearer;
  • the first packet gateway determines that the first packet gateway and the other gateways other than the lightweight packet gateway do not have a dedicated bearer corresponding to the UE, and delete the second dedicated bearer.
  • the first packet gateway after receiving the dedicated bearer deletion request of the lightweight packet gateway, the first packet gateway needs to delete the first dedicated bearer between the first packet gateway and the lightweight packet gateway, and simultaneously indicate The serving gateway deletes the third dedicated bearer between the serving gateway and the lightweight packet gateway, and determines whether to delete the second dedicated bearer between the first packet gateway and the UE. At this time, the first packet gateway further needs to determine whether another gateway shares the second dedicated bearer with the lightweight packet gateway, or the first packet gateway needs to determine the first packet gateway and the light-weight packet gateway.
  • the first packet gateway does not delete the second dedicated bearer, when there is no dedicated bearer corresponding to the UE between the first packet gateway and other gateways.
  • the first packet gateway deletes the second dedicated bearer to ensure normal communication of the dedicated bearer between the UE and other gateways.
  • the first packet gateway is the first between the deletion and the lightweight packet gateway.
  • the serving gateway is instructed to delete the third dedicated bearer, and it is determined whether there is a dedicated bearer corresponding to the UE between the first packet gateway and the other gateway.
  • the first packet gateway does not The dedicated bearer between the first packet gateway and the UE is deleted to ensure normal communication of the dedicated bearer between the UE and other gateways.
  • the second dedicated bearer can be directly deleted.
  • FIG. 4 shows another method for accessing resources according to 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 local cache server corresponding to PGW1
  • the second cache server may be the target server, that is, the second cache server.
  • the PGW2 may be the first lightweight packet gateway, that is, the PGW2 is a gateway corresponding to the second cache server.
  • the cache controller is configured to schedule and control each cache server in the distributed cache system
  • the second bearer may 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 UE establishes a first TCP connection between the PGW1 and the first cache server;
  • the UE sends a first HTTP request message to the first cache server by using 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 UE of the IP address of the second cache server by using the HTTP redirect message, so that the UE re-initiates the second TCP setup request report to the second cache server according to the IP address of the second cache server.
  • 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.
  • An address if there is a bearer corresponding to the PGW2 (for example, an S5 bearer), if yes, a TCP connection is established between the S5 bearer and the second cache server, and if not, an S5 bearer connection establishment request message is sent to the PGW2;
  • the serving gateway determines the IP address of the PGW2 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 establishment request message, the PGW2 establishes an S5 bearer. And replying to the SGW with an S5 bearer connection setup response message;
  • the SGW establishes a TCP connection using the S5 bearer between 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 PGW2 sends the PBR1 the charging information generated by the UE accessing the second cache server, so that the PGW1 performs charging.
  • the service gateway determines the IP address of the target server by parsing the IP packet sent by the user equipment, and then determines the first lightweight packet gateway according to the IP address of the target server, and establishes the service gateway and the first lightweight type.
  • the second bearer between the packet gateways transmits the resource through the second bearer, where the charging information of the UE accessing the resource is sent by the first lightweight packet gateway to the first packet gateway for charging, thereby saving network resources. Increased efficiency in accessing resources.
  • FIG. 5 shows still another method for accessing resources according to an embodiment of the present invention.
  • the serving gateway connected by the UE is switched from the first serving gateway (SGW1) to the second serving gateway (SGW2). .
  • the first serving gateway may be referred to as a source serving gateway
  • the second serving gateway may be referred to as a target serving gateway.
  • the first serving gateway and the PGW1 have established a first bearer (for example, a default bearer), and the first serving gateway and the PGW2 have established a second bearer.
  • the methods for accessing resources include:
  • the UE communicates with the first base station, the SGW1, and the PGW2, the first base station exists between the SGW1 and the PGW1, and the second bearer exists between the SGW1 and the PGW2.
  • the UE may be connected to the PGW1 through the first base station and the SGW1 before the handover of the serving gateway. After the handover of the serving gateway, the UE may be connected to the PGW1 through the second base station and the SGW2.
  • the UE moves to the coverage edge of the first base station to perform handover preparation, and the first base station sends a path switch request to the MME.
  • the MME sends a create session request to the SGW2, where the setup session request is used to instruct the SGW2 to establish a bearer with the PGW1, where the setup session request includes first information, where the first information is used to indicate the SGW2 and PGW2 establishes a bearer;
  • the MME may carry the first information by establishing a private extension IE in the session request.
  • the SGW2 establishes a bearer between the SGW2 and the PGW1, and sends a bearer setup response (create session response) to the MME after the bearer is established. And after receiving the first information, the SGW2 determines whether the SGW2 supports establishing a second bearer with the PGW2.
  • SGW2 when SGW2 supports establishing a second bearer with PGW2, SGW2 is at SGW2. Establish a second bearer with PGW2.
  • the SGW2 may add the second information in the MME reply to the create session response, where the second information is used to notify the SGW2 to support the establishment of the PGW2.
  • the second bearer wherein the second information can be carried in the private extension IE of the bearer setup response.
  • SGW2 when SGW2 does not support establishing a second bearer with PGW2, SGW2 establishes a second bearer through PGW1 and PGW2;
  • the SGW2 may add the second information in the bearer setup response, where the second information is used to explain that the SGW2 does not support establishing the second with the PGW2.
  • the reason for the bearer may be carried in a private extension IE that carries a setup establishment response.
  • the MME may instruct the SGW1 to delete the first bearer between the SGW1 and the PGW1, and delete the second bearer between the SGW1 and the PGW2.
  • the UE can also establish a dedicated bearer with the lightweight packet gateway and access the resources by using a dedicated bearer.
  • a method of establishing, modifying, and deleting a dedicated bearer will be described below with reference to FIGS. 6 through 8.
  • the first bearer corresponding to the UE already exists between the SGW and the PGW1
  • the second bearer corresponding to the UE already exists between the SGW and the lightweight packet gateway.
  • FIG. 6 is a schematic diagram of communication of a dedicated bearer setup method according to an embodiment of the present invention.
  • the first packet gateway may be PGW1
  • the lightweight packet gateway may be PGW2
  • the service gateway may be a SGW.
  • the methods of hosting include:
  • the PGW2 sends a dedicated bearer setup request to the PGW1, where the dedicated bearer setup request is used to request to establish a first dedicated bearer between the PGW1 and the PGW2;
  • PGW1 determines whether there is a dedicated bearer between PGW1 and the UE;
  • the PGW1 determines the dedicated bearer as a second dedicated bearer between the PGW1 and the UE, and establishes a first dedicated bearer between the PGW1 and the PGW2, and instructs the SGW to establish an SGW between the SGW and the PGW2.
  • Third dedicated bearer when there is a dedicated bearer, the PGW1 determines the dedicated bearer as a second dedicated bearer between the PGW1 and the UE, and establishes a first dedicated bearer between the PGW1 and the PGW2, and instructs the SGW to establish an SGW between the SGW and the PGW2.
  • Third dedicated bearer when there is a dedicated bearer, the PGW1 determines the dedicated bearer as a second dedicated bearer between the PGW1 and the UE, and establishes a first dedicated bearer between the PGW1 and the PGW2, and instructs the SGW to establish an SGW between the SGW and the PGW2.
  • PGW1 when there is no dedicated bearer, PGW1 establishes a first dedicated bearer between PGW1 and PGW2, and establishes a second dedicated bearer between PGW1 and the UE, and instructs the SGW to establish a third between SGW and PGW2.
  • Dedicated bearer when there is no dedicated bearer, PGW1 establishes a first dedicated bearer between PGW1 and PGW2, and establishes a second dedicated bearer between PGW1 and the UE, and instructs the SGW to establish a third between SGW and PGW2.
  • the second dedicated bearer when the first packet gateway determines that there is a dedicated bearer between the first packet gateway and the UE, the second dedicated bearer does not need to be established, and the dedicated bearer is determined as the second dedicated bearer, and the second Dedicated bearers can be reused to conserve network resources.
  • FIG. 7 is a schematic diagram of communication of a modification method of a dedicated bearer. As shown in FIG. 7 , in the method shown in FIG. 7 , the same or similar content as FIG. 6 can refer to FIG. 6 , and details are not described herein again. .
  • the methods for modifying a dedicated bearer include:
  • the PGW2 sends a dedicated bearer setup request to the PGW1, where the dedicated bearer modification request is used to request to establish a first dedicated bearer between the PGW1 and the PGW2;
  • the PGW1 determines whether there is a dedicated bearer corresponding to the UE between the PGW1 and other gateways other than the PGW2;
  • the PGW1 when there is a dedicated bearer between the PGW1 and other gateways other than the PGW2, the PGW1 creates a dedicated bearer between the UE and the PGW1, modifies the first dedicated bearer between the PGW2 and the PGW1, and instructs the SGW to modify the SGW and A third dedicated bearer between PGW2 and may reply to PGW2 with a dedicated bearer modification response message.
  • the other gateways and the PGW2 share the second dedicated bearer between the PGW1 and the UE. If the second dedicated bearer is modified, the communication between the UE and other gateways will be affected. This step maintains communication between the UE and other gateways by creating a dedicated bearer between the UE and the PGW1.
  • PGW1 modifies the first dedicated bearer between PGW1 and PGW2, and modifies the second dedicated bearer between PGW1 and UE, and indicates
  • the SGW modifies the third dedicated bearer between the SGW and the PGW2, and may send a dedicated bearer modification response message to the PGW2.
  • the PGW1 instructs the serving gateway to modify the third dedicated bearer between the SGW and the PGW2 in the case of modifying the first dedicated bearer with the PGW2, and determines between the PGW1 and other gateways other than the PGW2.
  • There is a dedicated bearer corresponding to the UE that is, PGW2 shares the second dedicated bearer with other gateways, and PGW1 creates a dedicated bearer between the PGW1 and the UE to ensure communication between the UE and other gateways, and improve the efficiency of accessing resources.
  • FIG. 8 is a schematic diagram of communication of a deletion method of a dedicated bearer.
  • the same or similar content as FIG. 6 or FIG. 7 can refer to the description related to FIG. 6 or FIG. 7 .
  • the method for deleting a dedicated bearer includes:
  • the PGW1 receives the dedicated bearer deletion request sent by the PGW2, and the dedicated bearer deletion request is used to request to delete the first dedicated bearer between the PGW1 and the PGW2;
  • PGW1 determines whether there is a dedicated bearer corresponding to the UE between PGW1 and other gateways other than PGW2;
  • the PGW1 when there is a dedicated bearer between the PGW1 and the other gateway, the PGW1 deletes the first dedicated bearer between the PGW1 and the PGW2, and instructs the SGW to delete the third dedicated bearer between the SGW and the PGW2, and does not delete the PGW1 and the UE.
  • Second dedicated bearer
  • the PGW1 when there is no dedicated bearer between the PGW1 and the other gateway, the PGW1 deletes the first dedicated bearer between the PGW1 and the GW, deletes the second dedicated bearer between the PGW1 and the UE, and instructs the SGW to delete the SGW and the PGW2.
  • the first packet gateway when deleting the first dedicated bearer between the packet and the lightweight packet gateway, simultaneously instructs the serving gateway to delete the third dedicated bearer, and simultaneously determines the first packet gateway and other gateways. Whether there is a dedicated bearer corresponding to the UE. When there is a dedicated bearer with other gateways, the first packet gateway does not delete the dedicated bearer between the first packet gateway and the UE to ensure the normal bearer between the UE and other gateways. Communication, when there is no dedicated bearer with other gateways, the second dedicated bearer can be directly deleted.
  • the serving gateway may be an SGW or an SGSN
  • the first packet gateway may be a PGW or a GGSN.
  • the first packet gateway is an SGW
  • the packet gateway is a PGW.
  • each network element such as a service gateway, a lightweight packet gateway, a first packet gateway, a mobility management network element, etc.
  • each network element such as a service gateway, a lightweight packet gateway, a first packet gateway, a mobility management network element, etc.
  • each network element includes hardware structures and/or software modules corresponding to performing various functions.
  • 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 service gateway, a lightweight packet gateway, a first packet gateway, a mobility management network element, and the like according to the foregoing method.
  • each functional unit may be divided according to each function, or may be Two or more functions are integrated in 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. 9A shows a possible structural diagram of the service gateway involved in the above embodiment.
  • the service gateway 900 includes a processing unit 902 and a communication unit 903.
  • the processing unit 902 is configured to perform control management on the action of the serving gateway.
  • the processing unit 902 is configured to support the service gateway to perform the processes S310-S340 in FIG. 3, the processes S407-S410 in FIG. 4, and the process S530- in FIG. S560, processes S630, S640 in FIG. 6, processes S730, S740 of FIG. 7, processes S830, S840 of FIG. 8, and/or other processes for the techniques described herein.
  • the communication unit 903 is configured to support communication between the service gateway and other network entities, for example, Communication between the base station, MME, PGW, etc. shown in FIG.
  • the service gateway may further include a storage unit 901 for storing program codes and data of the service gateway.
  • the processing unit 902 can be a processor or a controller, and can 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 903 may be a transceiver, a transceiver circuit, a communication interface, or the like.
  • the storage unit 901 can be a memory.
  • the service gateway according to the embodiment of the present invention may be the service gateway shown in FIG. 9B.
  • the service gateway 910 includes a processor 912, a communication interface 913, and a memory 911.
  • the service gateway 910 may also include a bus 914.
  • the communication interface 913, the processor 912, and the memory 911 may be connected to each other through a bus 914.
  • the bus 914 may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (abbreviated). EISA) bus and so on.
  • the bus 914 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 9B, but it does not mean that there is only one bus or one type of bus.
  • FIG. 10A shows a possible structural diagram of the lightweight packet gateway involved in the above embodiment.
  • the lightweight packet gateway 1000 includes a processing unit 1002 and a communication unit 1003.
  • the processing unit 1002 is configured to control and manage the action of the lightweight packet gateway.
  • the processing unit 1002 is configured to support the lightweight packet gateway to perform the process S350, S360 in FIG. 3, and the processes S408 and S411 in FIG. Processes S550, S560 in 5, processes S610, S630, S640 in FIG. 6, processes S710, S730, S740 of FIG. 7, processes S810, S830, S840 of FIG. 8, and/or for the techniques described herein Other processes.
  • the communication unit 1003 is for supporting communication between the lightweight packet gateway and other network entities, such as communication with the serving gateway, MME, PGW, etc. shown in FIG. 2.
  • the lightweight packet gateway may further include a storage unit 1001 for storing program codes and data of the lightweight packet 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 Program 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 transceiver, a transceiver circuit, a communication interface, or the like.
  • the storage unit 1001 may be a memory.
  • the lightweight packet gateway may be a lightweight packet gateway as shown in FIG. 10B.
  • the lightweight packet gateway 1010 includes a processor 1012, a communication interface 1013, and a memory 1011.
  • the lightweight packet 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 FIG. 10B, but it does not mean that there is only one bus or one type of bus.
  • FIG. 11A shows a possible structural diagram of the packet gateway involved in the above embodiment.
  • the packet gateway can be the first packet gateway described above.
  • the packet gateway 1100 includes a processing unit 1102 and a communication unit 1103.
  • the processing unit 1102 is configured to perform control management on the action of the packet gateway.
  • the processing unit 1102 is configured to support the first packet gateway to perform the process S310, S360 in FIG. 3, and the processes S401-S403 and S411 in FIG. Processes S510, S540-S560, processes S610-S640 in FIG. 6, processes S710-S740 of FIG. 7, processes S810-S840 of FIG. 8, and/or other processes for the techniques described herein.
  • repeated descriptions are omitted as appropriate.
  • 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 repeated description is omitted here.
  • 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 storage unit 1201, a processing unit 1202, and a communication unit 1203.
  • the storage unit 1201 is configured to store programs
  • the communication unit 1203 is configured to communicate with other devices
  • the processing unit 1202 is configured to execute programs in the storage unit 1201, the processing unit is configured to support mobility when the program is executed.
  • Tube The network element performs processes S520-S550 in Figure 5, and/or other processes for the techniques described herein. For the sake of brevity, 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 service gateway, the lightweight packet gateway, the packet gateway, or the mobility management network element in the embodiment of the present invention may be a central processing unit (CPU), a general-purpose processor, and digital signal processing. (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 random combination. 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 media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one location to another.
  • the storage medium can be any one that can be accessed by a general purpose or special purpose computer. Use the media.

Landscapes

  • Mobile Radio Communication Systems (AREA)

Abstract

A resource access method, device and system, capable of increasing resource access efficiency. The method comprises: a lightweight packet gateway receives an access request of a user equipment (UE) sent by a server gateway via a second bearer, the access request being used for requesting access to a resource stored in a target server corresponding to the lightweight packet gateway, the second bearer being a bearer between the server gateway and the lightweight packet gateway and corresponding to the UE, a first bearer corresponding to the UE being arranged between the server gateway and a first packet gateway; the lightweight packet gateway transmits the resource to the UE via the second bearer; the lightweight packet gateway sends billing information generated by the UE accessing the resource to the first packet gateway, so as the enable the first packet gateway to perform billing.

Description

访问资源的方法、装置和***Method, device and system for accessing resources 技术领域Technical field
本发明涉及通信技术领域，尤其涉及访问资源的方法、装置和***。The present invention relates to the field of communications technologies, and in particular, to a method, apparatus, and system for accessing resources.
背景技术Background technique
现有技术中，随着长期演进(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获取资源。In the prior art, with the development of a Long Term Evolution (LTE) system, a Content Delivery Network (CDN) has a cache server deployed at a gateway at various edges, wherein the cache server can cache the remote server. resource of. Through the scheduling of the central platform, the user equipment (User Equipment, UE) can obtain resources from the cache servers in the periphery. Generally, the UE is connected to the external network through a base station, a Serving Gateway (SGW), and a Packet Data Network Gateway (PGW). 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. This path of accessing resources causes a round trip of the route, which is not conducive to the UE acquiring resources.
发明内容Summary of the invention
本发明提供了一种访问资源的方法、轻量型分组网关、服务网关、分组网关、移动性管理网元和***，以提高访问资源的效率。The invention provides a method for accessing resources, a lightweight packet gateway, a service gateway, a packet gateway, a mobility management network element and a system, so as to improve the efficiency of accessing resources.
一方面，本发明实施例提供了一种访问资源的方法，包括：服务网关接收备第一UE的IP报文，IP报文中携带目标服务器的IP地址，目标服务器存储有第一UE待访问的资源，其中，服务网关与第一分组网关之间具有对应于第一UE的第一承载；服务网关根据IP地址确定目标服务器对应的第一轻量型分组网关；服务网关确定服务网关与第一轻量型分组网关之间的对应于第一UE的第二承载；服务网关通过第二承载向第一轻量型分组网关发送第一UE的访问请求，访问请求用于请求访问目标服务器中存储的资源。轻量型分组网关向第一分组网关发送第一UE访问资源所产生的计费信息，以使得第一分组网关进行计费。通过本发明实施提供的方法，服务网关在接收到UE的访问请求之后，可以通过上述第二承载向第一轻量型分组网关发送UE的访问请求，以访问第一轻量型分组网关对应的目标服务器中存储的资源，且UE访问所述资源的计费信息由第一轻量型分组网关发送至第一分组网关进行计费，从而能够避免访问路径的路由迂回，有利于提高UE访问的 速度和效率，以及节约网络资源。On the one hand, the embodiment of the present invention provides a method for accessing a resource, including: the serving gateway receives the IP packet of the first UE, where the IP packet carries the IP address of the target server, and the target server stores the first UE to be accessed. a resource, wherein the serving gateway and the first packet gateway have a first bearer corresponding to the first UE; the serving gateway determines a first lightweight packet gateway corresponding to the target server according to the IP address; the serving gateway determines the serving gateway and the first a second bearer corresponding to the first UE between the lightweight packet gateways; the serving gateway sends an access request of the first UE to the first lightweight packet gateway by using the second bearer, where the access request is used to request access to the target server Stored resources. The lightweight packet gateway sends the charging information generated by the first UE accessing the resource to the first packet gateway, so that the first packet gateway performs charging. The method provided by the implementation of the present invention, after receiving the access request of the UE, the serving gateway may send an access request of the UE to the first lightweight packet gateway by using the second bearer to access the corresponding one of the first lightweight packet gateway. The resource stored in the target server, and the charging information of the UE accessing the resource is sent by the first lightweight packet gateway to the first packet gateway for charging, thereby avoiding routing detour of the access path, which is beneficial to improving UE access. Speed and efficiency, as well as saving network resources.
在一个可能的设计中，可以通过以下方式之一确定服务网关与第一轻量型分组网关之间的第二承载：第一种方式，服务网关向第一轻量型分组网关发送承载建立请求，承载建立请求用于请求建立第二承载；服务网关接收第一轻量型分组网关发送的承载建立响应，承载建立响应用于指示第二承载已建立；第二种方式：服务网关从至少两个已有的承载中确定第二承载，至少两个已有的承载为服务网关与至少两个网关之间的对应于第一UE的承载。In a possible design, the second bearer between the serving gateway and the first lightweight packet gateway may be determined in one of the following manners: In the first manner, the serving gateway sends a bearer setup request to the first lightweight packet gateway. The bearer setup request is used to request to establish the second bearer; the serving gateway receives the bearer setup response sent by the first lightweight packet gateway, and the bearer setup response is used to indicate that the second bearer has been established; the second manner: the service gateway is from at least two The second bearer is determined in the existing bearer, and the at least two existing bearers are bearers corresponding to the first UE between the serving gateway and the at least two gateways.
在一个可能的设计中，服务网关可以接收移动性管理网元发送的第一信息，第一信息用于指示在服务网关与第二轻量型分组网关之间建立对应于第二UE的第三承载；当服务网关支持在服务网关与第二轻量型分组网关之间建立承载时，服务网关在服务网关与第二轻量型分组网关之间建立第三承载；或者，当服务网关不支持在服务网关与第二轻量型分组网关之间建立承载时，服务网关在对应于第二轻量型分组网关的第二分组网关与服务网关之间建立对应于第二UE的承载，从而使得服务网关能够经由第二分组网关与第二轻量型分组网关进行有关第二UE的交互。In a possible design, the serving gateway may receive the first information sent by the mobility management network element, where the first information is used to indicate that the third gateway corresponding to the second UE is established between the serving gateway and the second lightweight packet gateway. Bearer; when the serving gateway supports establishing a bearer between the serving gateway and the second lightweight packet gateway, the serving gateway establishes a third bearer between the serving gateway and the second lightweight packet gateway; or, when the serving gateway does not support When the bearer is established between the serving gateway and the second lightweight packet gateway, the serving gateway establishes a bearer corresponding to the second UE between the second packet gateway corresponding to the second lightweight packet gateway and the serving gateway, thereby The serving gateway is capable of interacting with the second UE via the second packet gateway and the second lightweight packet gateway.
在一个可能的设计中，服务网关可以向移动性管理网元发送第二信息，第二信息用于通知移动性管理网元服务网关支持或者不支持在服务网关与第二轻量型分组网关之间建立承载。In a possible design, the serving gateway may send the second information to the mobility management network element, where the second information is used to notify the mobility management network element service gateway to support or not support the service gateway and the second lightweight packet gateway. Establish a bearer between.
在一个可能的设计中，还可以建立第一分组网关与轻量型分组网关之间对应于UE的专用承载。例如，轻量型分组网关向第一分组网关发送专用承载建立请求，该专用承载建立请求用于请求建立轻量型分组网关与第一分组网关之间的对应于UE的第一专用承载。第一分组网关根据专用承载建立请求，建立第一专用承载；第一分组网关确定第一分组网关与UE之间的第二专用承载；第一分组网关指示服务网关建立服务网关与轻量型分组网关之间的第三专用承载。进一步的，第一分组网关可以通过以下方式确定第一分组网关与UE之间的第二专用承载：所述第一分组网关确定所述第一分组网关与所述UE之间存在专用承载，并将所述专用承载确定为所述第二专用承载；或者，所述第一分组网关确定所述第一分组网关与所述UE之间不存在专用承载，并建立所述第二专用承载。而无需再建立其他承载，从而可以提高承载资源的利用率，以节约网络资源。In one possible design, a dedicated bearer corresponding to the UE between the first packet gateway and the lightweight packet gateway may also be established. For example, the lightweight packet gateway sends a dedicated bearer setup request to the first packet gateway for requesting establishment of a first dedicated bearer corresponding to the UE between the lightweight packet gateway and the first packet gateway. The first packet gateway establishes a first dedicated bearer according to the dedicated bearer setup request; the first packet gateway determines a second dedicated bearer between the first packet gateway and the UE; and the first packet gateway instructs the serving gateway to establish a serving gateway and a lightweight packet The third dedicated bearer between the gateways. Further, the first packet gateway may determine, by using the following manner, a second dedicated bearer between the first packet gateway and the UE: the first packet gateway determines that a dedicated bearer exists between the first packet gateway and the UE, and Determining the dedicated bearer as the second dedicated bearer; or, the first packet gateway determines that there is no dedicated bearer between the first packet gateway and the UE, and establishing the second dedicated bearer. There is no need to establish other bearers, so that the utilization of the bearer resources can be improved to save network resources.
在一个可能的设计中，还可以修改第一分组网关与轻量型分组网关之间的专用承载。例如：轻量型分组网关向第一分组网关发送专用承载修改请求，该专用承载修改请求用于请求修改第一专用承载；在接收到该专用承载修改请求之后，所述第一分组网关根据所述专用承载修改请求修改所述第一专用 承载，以及指示所述服务网关修改所述第三专用承载；所述第一分组网关确定所述第一分组网关与所述轻量型分组网关之外的其他网关之间存在对应于所述UE的专用承载，并新建所述第一分组网关与所述UE之间的专用承载。第一分组网关在修改第一专用承载的情况下，确定第一分组网关与轻量型分组网关以外的其他网关之间存在对应于UE的专用承载，即轻量型分组网关与其他网关共用第二专用承载，第一分组网关新建第一分组网关与UE之间的专用承载，以确保UE与其他网关之间的专用承载的通信，提高访问资源的效率。In one possible design, a dedicated bearer between the first packet gateway and the lightweight packet gateway can also be modified. For example, the lightweight packet gateway sends a dedicated bearer modification request to the first packet gateway, where the dedicated bearer modification request is used to request to modify the first dedicated bearer; after receiving the dedicated bearer modification request, the first packet gateway is configured according to the Dedicating a dedicated bearer modification request to modify the first dedicated Carrying, and instructing the serving gateway to modify the third dedicated bearer; the first packet gateway determines that there is a corresponding to the UE between the first packet gateway and other gateways other than the lightweight packet gateway Dedicated bearer, and newly create a dedicated bearer between the first packet gateway and the UE. When the first packet gateway modifies the first dedicated bearer, it is determined that there is a dedicated bearer corresponding to the UE between the first packet gateway and other gateways other than the lightweight packet gateway, that is, the lightweight packet gateway shares the same with other gateways. The two dedicated bearers, the first packet gateway establishes a dedicated bearer between the first packet gateway and the UE, to ensure communication of the dedicated bearer between the UE and other gateways, and improve the efficiency of accessing resources.
在一个可能的设计中，还可以删除第一分组网关与轻量型分组网关之间的第一专用承载，还包括：轻量型分组网关向第一分组网关发送专用承载删除请求，专用承载删除请求用于请求删除第一专用承载；在接收该专用承载删除请求之后，所述第一分组网关删除所述第一专用承载，以及指示所述服务网关删除所述第三专用承载；所述第一分组网关确定所述第一分组网关与所述轻量型分组网关之外的其他网关不存在对应于所述UE的专用承载，并删除所述第二专用承载。第一分组网关在删除与轻量型分组网关之间的第一专用承载的情况下，同时确定第一分组网关其他网关之间是否存在对应于UE的专用承载，当存在专用承载时，第一分组网关不删除第一分组网关与UE之间的专用承载，以确保UE与其他网关之间的专用承载的正常通信。In a possible design, the first dedicated bearer between the first packet gateway and the lightweight packet gateway may also be deleted, and the method further includes: the lightweight packet gateway sends a dedicated bearer deletion request to the first packet gateway, and the dedicated bearer is deleted. The request is for requesting to delete the first dedicated bearer; after receiving the dedicated bearer deletion request, the first packet gateway deletes the first dedicated bearer, and instructs the serving gateway to delete the third dedicated bearer; A packet gateway determines that the first packet gateway and other gateways other than the lightweight packet gateway do not have a dedicated bearer corresponding to the UE, and deletes the second dedicated bearer. The first packet gateway determines whether there is a dedicated bearer corresponding to the UE between the other gateways of the first packet gateway in the case of deleting the first dedicated bearer between the first packet gateway, and when there is a dedicated bearer, the first The packet gateway does not delete the dedicated bearer between the first packet gateway and the UE to ensure normal communication of the dedicated bearer between the UE and other gateways.
在上述方法示例中，该目标服务器可以是业务服务器，也可以是缓存服务器。该轻量型分组网关可以与该目标服务器位于同一节点。In the above method example, the target server may be a service server or a cache server. The lightweight packet gateway can be located at the same node as the target server.
在上述方法示例中，服务网关可以为SGW或服务通用分组无线技术支持节点(Serving General Packet Radio Service Support Node，SGSN)；第一分组网关可以为分组数据网络网关PGW或网关通用分组无线技术支持节点(Gateway General Packet Radio Service Support Node,GGSN)。In the foregoing method example, the serving gateway may be an SGW or a Serving General Packet Radio Service Support Node (SGSN); the first packet gateway may be a packet data network gateway PGW or a gateway general packet radio technical support node. (Gateway General Packet Radio Service Support Node, GGSN).
另一方面，本发明实施例提供了一种服务网关，该服务网关具有实现上述方法设计中服务网关行为的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。On the other hand, 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.
在一个可能的设计中，服务网关的结构中包括处理单元和通信单元，所述处理单元被配置为支持服务网关执行上述方法中相应的功能。所述通信单元用于支持服务网关与其他设备之间的通信。所述服务网关还可以包括存储单元，所述存储单元用于与处理单元耦合，其保存服务网关必要的程序指令和数据。作为示例，处理单元可以为处理器，通信单元可以为通信接口，存储单元可以为存储器。 In one possible design, 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. As an example, the processing unit can be a processor, the communication unit can be a communication interface, and the storage unit can be a memory.
又一方面，本发明实施例提供了一种轻量型分组网关，该轻量型分组网关可以称为目标轻量型分组网关，目标轻量型分组网关具有实现上述方法设计中目标轻量型分组网关行为的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。In another aspect, an embodiment of the present invention provides a lightweight packet gateway, which may be referred to as a target lightweight packet gateway, and the target lightweight packet gateway has a lightweight target for implementing the foregoing method design. The function of grouping gateway behavior. 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.
在一个可能的设计中，目标轻量型分组网关的结构中包括处理单元和通信单元，所述处理单元被配置为支持目标轻量型分组网关执行上述方法中相应的功能。所述通信单元用于支持目标轻量型分组网关与其他设备之间的通信。所述目标轻量型分组网关还可以包括存储单元，所述存储单元用于与处理单元耦合，其保存目标轻量型分组网关必要的程序指令和数据。作为示例，处理单元可以为处理器，通信单元可以为通信接口，存储单元可以为存储器。In one possible design, the structure of the target lightweight packet gateway includes a processing unit and a communication unit, the processing unit being configured to support the target lightweight packet gateway to perform the corresponding function in the above method. The communication unit is configured to support communication between the target lightweight packet gateway and other devices. The target lightweight packet gateway may also include a storage unit for coupling with the processing unit to store program instructions and data necessary for the target lightweight packet gateway. As an example, the processing unit can be a processor, the communication unit can be a communication interface, and the storage unit can be a memory.
又一方面，本发明实施例提供了一种分组网关，该分组网关可以称为第一分组网关，第一分组网关具有实现上述方法设计中第一分组网关行为的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。In another aspect, an embodiment of the present invention provides a packet gateway, which may be referred to as a first packet gateway, and the first packet gateway has a function of implementing a behavior of a first packet gateway 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.
在一个可能的设计中，第一分组网关的结构中包括处理单元和通信单元，所述处理单元被配置为支持第一分组网关执行上述方法中相应的功能。所述通信单元用于支持第一分组网关与其他设备之间的通信。所述第一分组网关还可以包括存储单元，所述存储单元用于与处理单元耦合，其保存第一分组网关必要的程序指令和数据。作为示例，处理单元可以为处理器，通信单元可以为通信接口，存储单元可以为存储器。In one possible design, the first packet gateway structure includes a processing unit and a communication unit, the processing unit being configured to support the first packet gateway to perform a corresponding function in the above method. The communication unit is configured to support communication between the first packet gateway and other devices. The first packet gateway may further comprise a storage unit for coupling with the processing unit, which stores program instructions and data necessary for the first packet gateway. As an example, the processing unit can be a processor, the communication unit can be a communication interface, and the storage unit can be a memory.
又一方面，本发明实施例提供了一种移动性管理网元，该移动性管理网元可以称为第一移动性管理网元，第一移动性管理网元具有实现上述方法设计中第一移动性管理网元行为的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。In another aspect, the embodiment of the present invention provides a mobility management network element, which may be referred to as a first mobility management network element, where the first mobility management network element has the first implementation in the foregoing method design. The function of mobility management network element behavior. 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.
在一个可能的设计中，第一移动性管理网元的结构中包括处理单元和通信单元，所述处理单元被配置为支持第一移动性管理网元执行上述方法中相应的功能。所述通信单元用于支持第一移动性管理网元与其他设备之间的通信。所述第一移动性管理网元还可以包括存储单元，所述存储单元用于与处理单元耦合，其保存第一移动性管理网元必要的程序指令和数据。作为示例，处理单元可以为处理器，通信单元可以为通信接口，存储单元可以为存储器。In a possible design, the first mobility management network element includes a processing unit and a communication unit, and the processing unit is configured to support the first mobility management network element to perform a corresponding function in the foregoing method. The communication unit is configured to support communication between the first mobility management network element and other devices. The first mobility management network element may further include a storage unit, where the storage unit is configured to be coupled to the processing unit, where the program instructions and data necessary for the first mobility management network element are saved. As an example, the processing unit can be a processor, the communication unit can be a communication interface, and the storage unit can be a memory.
又一方面，本发明实施例提供了一种通信***，该***包括上述方面所述的服务网关和轻量型分组网关；或者该***包括上述方面所述的服务网关、 轻量型分组网关、第一分组网关和移动性管理网元。In another aspect, an embodiment of the present invention provides a communication system, including the service gateway and the lightweight packet gateway described in the foregoing aspect; or the system includes the service gateway described in the foregoing aspect, Lightweight packet gateway, first packet gateway, and mobility management network element.
再一方面，本发明实施例提供一种计算机存储介质，用于储存为上述服务网关所用的计算机软件指令，其包含用于执行上述方面所设计的程序。In still another 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.
再一方面，本发明实施例提供一种计算机存储介质，用于储存为上述轻量型分组网关所用的计算机软件指令，其包含用于执行上述方面所设计的程序。In still another aspect, an embodiment of the present invention provides a computer storage medium for storing computer software instructions for use in the lightweight packet gateway, including a program designed to perform the above aspects.
再一方面，本发明实施例提供一种计算机存储介质，用于储存为上述第一分组网关所用的计算机软件指令，其包含用于执行上述方面所设计的程序。In still another aspect, an embodiment of the present invention provides a computer storage medium for storing computer software instructions for use in the first packet gateway, which includes a program designed to perform the above aspects.
再一方面，本发明实施例提供一种计算机存储介质，用于储存为上述移动性管理网元所用的计算机软件指令，其包含用于执行上述方面所设计的程序。In still another aspect, 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.
相较于现有技术，本发明实施例提供的方案中，在服务网关与第一分组网关之间具有对应于UE的承载的情况下，服务网关在接收UE的IP报文后，可以根据IP报文中携带的目标服务器的IP地址确定目标服务器对应的第一轻量型分组网关，确定基站与第一轻量型分组网关之间的对应于UE的第二承载，并通过第二承载传输UE的访问请求，该访问请求用于请求访问目标服务器中存储的资源。因此，本发明实施例提供的方案能够避免访问路径的路由迂回，以提高UE访问资源的效率。进一步的，UE访问所述资源的计费信息由第一轻量型分组网关发送至第一分组网关进行计费，由此有利于简化第一轻量型分组网关的功能。Compared with the prior art, in the solution provided by the embodiment of the present invention, when the serving gateway and the first packet gateway have a bearer corresponding to the UE, the serving gateway may receive the IP packet of the UE according to the IP address. The IP address of the target server carried in the packet determines the first lightweight packet gateway corresponding to the target server, determines the second bearer corresponding to the UE between the base station and the first lightweight packet gateway, and transmits the second bearer through the second bearer. An access request of the UE for requesting access to a 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. Further, the charging information of the UE accessing the resource is sent by the first lightweight packet gateway to the first packet gateway for charging, thereby facilitating the function of the first lightweight packet gateway.
附图说明DRAWINGS
为了更清楚地说明本发明实施例的技术方案，下面将对本发明实施例中所需要使用的附图作简单地介绍，显而易见地，下面所描述的附图仅仅是本发明的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings to be used in the embodiments of the present invention will be briefly described below. It is obvious that the drawings described below are only some embodiments of the present invention, Those skilled in the art can also obtain other drawings based on these drawings without paying any creative work.
图1是本发明实施例的一种可能的应用场景的示意图；1 is a schematic diagram of a possible application scenario of an embodiment of the present invention;
图2是本发明实施例应用的一种可能的***架构的示意图；2 is a schematic diagram of a possible system architecture applied by an embodiment of the present invention;
图3是本发明实施例提供的一种访问资源的方法的流程示意图；3 is a schematic flowchart of a method for accessing resources according to an embodiment of the present invention;
图4是本发明实施例提供的另一种访问资源的方法的通信示意图；4 is a schematic diagram of communication of another method for accessing resources according to an embodiment of the present invention;
图5是本发明实施例提供的又一种访问资源的方法的通信示意图；FIG. 5 is a schematic diagram of communication of another method for accessing resources according to an embodiment of the present invention; FIG.
图6是本发明实施例提供的一种专用承载的建立方法的通信示意图；FIG. 6 is a schematic diagram of communication of a method for establishing a dedicated bearer according to an embodiment of the present invention; FIG.
图7是本发明实施例提供的一种专用承载的修改方法的通信示意图；FIG. 7 is a schematic diagram of communication of a method for modifying a dedicated bearer according to an embodiment of the present invention; FIG.
图8是本发明实施例提供的一种专用承载的删除方法的通信示意图； FIG. 8 is a schematic diagram of communication of a method for deleting a dedicated bearer according to an embodiment of the present invention; FIG.
图9A是本发明实施例提供的一种服务网关的结构示意图；9A is a schematic structural diagram of a service gateway according to an embodiment of the present invention;
图9B是本发明实施例提供的另一种服务网关的结构示意图；FIG. 9B is a schematic structural diagram of another service gateway according to an embodiment of the present disclosure;
图10A是本发明实施例提供的一种轻量型分组网关的结构示意图；FIG. 10A is a schematic structural diagram of a lightweight packet gateway according to an embodiment of the present invention; FIG.
图10B是本发明实施例提供的另一种轻量型分组网关的结构示意图；FIG. 10B is a schematic structural diagram of another lightweight packet gateway according to an embodiment of the present disclosure;
图11A是本发明实施例提供的一种分组网关的结构示意图；11A is a schematic structural diagram of a packet gateway according to an embodiment of the present invention;
图11B是本发明实施例提供的另一种分组网关的结构示意图；FIG. 11B is a schematic structural diagram of another packet gateway according to an embodiment of the present disclosure;
图12A是本发明实施例提供的一种移动性管理网元的结构示意图；FIG. 12A is a schematic structural diagram of a mobility management network element according to an embodiment of the present disclosure;
图12B是本发明实施例提供的另一种移动性管理网元的结构示意图。FIG. 12B is a schematic structural diagram of another mobility management network element according to an embodiment of the present invention.
具体实施方式detailed description
为使本发明实施例的目的、技术方案和优点更加清楚，下面将结合本发明实施例中的附图，对本发明实施例中的技术方案进行描述。The technical solutions in the embodiments of the present invention will be described below in conjunction with the accompanying drawings in the embodiments 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.
如图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网络。As shown in FIG. 1, 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). System, IMS) network, Packet Switched Streaming Service (Packet Switched Streaming Service, Simple PSS) network. The technical solution described in the present invention can be applied to a Long Term Evolution (LTE) system, or other wireless communication systems using various radio access technologies, for example, using Code Division Multiple Access (CDMA), and frequency. Frequency Division Multiple Access (FDMA), Time Division Multiple Access (TDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single Carrier Frequency Division Multiple Access (Single Carrier Frequency) A system of access technologies such as Division Multiple Access (SC-FDMA). In addition, it can also be applied to subsequent evolution systems of the LTE system, such as a 5th Generation (5G) system. For the sake of clarity, only the LTE system is taken as an example here. In the LTE system, an Evolved Universal Terrestrial Radio Access Network (E-UTRAN) is used as a radio access network, and an Evolved Packet Core (EPC) is used as a core network. The UE accesses the IMS network through E-UTRAN and EPC.
本发明实施例中，名词“网络”和“***”经常交替使用，但本领域技术人员可以理解其含义。本发明实施例所涉及到的用户设备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。In the embodiments of the present invention, the terms "network" and "system" are often used interchangeably, but those skilled in the art can understand the meaning thereof. The user equipment UE involved in the embodiment of the present invention may include each Handheld devices with wireless communication capabilities, in-vehicle devices, wearable devices, computing devices or other processing devices connected to wireless modems, and various forms of User Equipment (UE), Mobile Station (MS) , terminal, terminal device, etc. For convenience of description, in the embodiment of the present invention, the devices mentioned above are collectively referred to as user equipments or UEs. 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. In systems with different radio access technologies, the names of devices with base station functionality may vary. For example, in an LTE network, an evolved NodeB (eNB or eNodeB) is called a Node B or the like in a 3rd generation (3G) network. For convenience of description, in the embodiment of the present invention, the foregoing apparatus for providing a wireless communication function to the UE is collectively referred to as a base station or a BS.
图2示出了本发明实施例的一种可能的***架构示意图。如图1所示，UE通过基站接入到SGW，并通过SGW接入到PGW，其中移动性管理实体(Mobility Management Entity，MME)作为控制面网元，通过端口分别与基站以及SGW连接，MME用于向基站和SGW传输控制面的信令。此外，图2所示的***架构中还包括其他网关，例如轻量型分组网关。轻量型分组网关可以是具有数据路由和转发功能的网关，当然轻量型分组网关也可以称为lightweight PGW，本发明实施例不对其名称进行限定。例如，轻量型分组网关可以不包括计费功能，轻量型分组网关可以将UE通过轻量型分组网关访问资源时产生的计费信息发送至PGW，由PGW进行计费。其中，在PGW、轻量型分组网关等处通常部署有本地服务器，例如，本地服务器可以为与相应分组网关部署在相同节点的缓存服务器(cache server)或业务服务器。需要说明的是，图2仅作为一种示例，当本发明实施例的方案应用于2G或3G的网络架构时，上述SGW的功能可以由SGSN完成，上述PGW的功能可以由GGSN完成。FIG. 2 shows a schematic diagram of a possible system architecture of an embodiment of the present invention. As shown in Figure 1, the UE accesses the SGW through the base station and accesses the PGW through the SGW. The Mobility Management Entity (MME) is used as the control plane network element, and is connected to the base station and the SGW through the port respectively. Signaling for transmitting control planes to base stations and SGWs. In addition, other gateways, such as lightweight packet gateways, are also included in the system architecture shown in FIG. 2. The lightweight packet gateway may be a gateway with data routing and forwarding functions. Of course, the lightweight packet gateway may also be referred to as a lightweight PGW. For example, the lightweight packet gateway may not include a charging function, and the lightweight packet gateway may send charging information generated when the UE accesses the resource through the lightweight packet gateway to the PGW, and the PGW performs charging. Wherein, a local server is usually deployed at a PGW, a lightweight packet gateway, etc., for example, the local server may be a cache server or a service server deployed on the same node as the corresponding packet gateway. It should be noted that FIG. 2 is only an example. When the solution of the embodiment of the present invention is applied to a 2G or 3G network architecture, the function of the SGW may be completed by the SGSN, and the function of the PGW may be completed by the GGSN.
图2中，SGW与PGW之间已建立对应于UE的承载。当UE访问网络资源时，可以首先查找PGW对应的本地服务器中是否存储有该资源，当本地服务器存储有该资源时，UE可以就近从本地服务器中获取资源，从而能够避免网络拥堵的状况，提高用户访问资源的响应速度。当PGW对应的本地服务器中未存储该资源时，PGW可以查询其他本地服务器中是否存储有该资源，当其他本地服务器中存储有该资源时，PGW可以与其他本地服务其对应的分组网关建立承载，以获取该资源。然而，在PGW通过与其他分组网关建立承载以获取资源的情况中，获取资源的路径迂回，影响UE的访问速度，且不利于节约网络资源。 In FIG. 2, a bearer corresponding to the UE has been established between the SGW and the PGW. When the UE accesses the network resource, it may first find whether the resource is stored in the local server corresponding to the PGW. When the local server stores the resource, 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. When the resource is not stored in the local server corresponding to the PGW, the PGW can query whether the resource is stored in the other local server. When the resource is stored in the other local server, the PGW can establish a bearer with the corresponding packet gateway of the other local service. To get the resource. However, in the case that the PGW establishes a bearer with other packet gateways to acquire resources, the path of the obtained resource is bypassed, affecting the access speed of the UE, and is not conducive to saving network resources.
基于此，本发明实施例提出了一种访问资源的方法，其主要思想是，在单一PDN链接下，服务网关除了与默认的分组网关建立承载之外，还可以与至少一个轻量型分组网关建立对应于同一UE的承载，从而有利于UE获取资源。例如，该方法可以包括：服务网关接收UE的IP报文，该IP报文中携带目标服务器的IP地址，该目标服务器存储有该UE待访问的资源，其中，服务网关与第一分组网关之间具有对应于该UE的第一承载；服务网关根据上述IP地址确定目标服务器对应的第一轻量型分组网关；服务网关确定服务网关与第一轻量型分组网关之间的对应于该UE的第二承载，例如，可以建立该第二承载或从已存在的承载中选择该第二承载；以及，服务网关通过该第二承载向第一轻量型分组网关发送UE的访问请求，该访问请求用于请求访问目标服务器中存储的上述资源。对应的，第一轻量型分组网关接收上述访问请求后，可以通过上述第二承载向UE传输上述资源；第一轻量型分组网关还可以向第一分组网关发送UE访问上述资源所产生的计费信息，以使得第一分组网关进行计费。Based on this, 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 be combined with at least one lightweight packet gateway in addition to the default packet gateway. A bearer corresponding to the same UE is established, thereby facilitating the UE to acquire resources. For example, 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 first lightweight packet gateway corresponding to the target server according to the IP address; the serving gateway determines that the serving gateway and the first lightweight packet gateway correspond to the UE a second bearer, for example, the second bearer may be established or selected from an existing bearer; and the serving gateway sends an access request of the UE to the first lightweight packet gateway by using the second bearer, where The access request is used to request access to the above resources stored in the target server. Correspondingly, after receiving the foregoing access request, the first lightweight packet gateway may transmit the resource to the UE by using the second bearer; the first lightweight packet gateway may further send, by the first packet gateway, the UE to access the resource. Billing information to enable the first packet gateway to perform charging.
通过本发明实施例提供的方案，服务网关在接收到UE的访问请求之后，可以通过上述第二承载向第一轻量型分组网关发送UE的访问请求，以访问第一轻量型分组网关对应的目标服务器中存储的资源，而不必需通过服务网关与第一分组网关之间的第一承载向第一轻量型分组网关对应的目标服务器请求资源，从而能够避免访问路径的路由迂回，有利于提高UE访问的速度和效率，以及节约网络资源。进一步的，UE访问所述资源的计费信息由第一轻量型分组网关发送至第一分组网关进行计费，由此有利于简化第一轻量型分组网关的功能，并使得本发明实施例的方案与现有技术具有较好的兼容性。With the solution provided by the embodiment of the present invention, after receiving the access request of the UE, the serving gateway may send an access request of the UE to the first lightweight packet gateway by using the second bearer to access the first lightweight packet gateway. The resource stored in the target server does not need to request resources from the first bearer corresponding to the first lightweight packet gateway through the first bearer between the serving gateway and the first packet gateway, thereby avoiding route routing of the access path, It is beneficial to improve the speed and efficiency of UE access and save network resources. Further, the charging information of the UE accessing the resource is sent by the first lightweight packet gateway to the first packet gateway for charging, thereby facilitating the function of the first lightweight packet gateway, and implementing the present invention. The solution of the example has better compatibility with the prior art.
下面结合附图3，对本发明实施例提供的方案进行说明。图3是本发明实施例提供的一种访问资源的方法300的流程示意图，如图3所示，该方法300包括：The solution provided by the embodiment of the present invention will be described below with reference to FIG. FIG. 3 is a schematic flowchart of a method 300 for accessing a resource according to an embodiment of the present invention. As shown in FIG. 3, the method 300 includes:
在S310部分，服务网关接收第一UE的IP报文，IP报文中携带目标服务器的IP地址，目标服务器存储有第一UE待访问的资源，其中，服务网关与第一分组网关之间具有对应于第一UE的第一承载。In S310, the serving gateway receives the IP packet of the first UE, where the IP packet carries the IP address of the target server, and the target server stores the resource to be accessed by the first UE, where the serving gateway and the first packet gateway have Corresponding to the first bearer of the first UE.
例如，该IP报文可以是传输控制协议(Transmission Control Protocol，TCP)建立请求报文，或者该IP报文也可以是其他格式的IP报文。For example, the IP packet may be a Transmission Control Protocol (TCP) setup request packet, or the IP packet may be an IP packet in other formats.
在一个示例中，第一UE向服务网关发送该IP报文之前，还可以获取目标服务器的IP地址。例如，第一UE可以接收第一分组网关发送的目标服务器的IP地址。其中，第一分组网关可以向第一UE发送重定向消息(例如 HTTP重定向消息)，该重定向消息中包含目标服务器的IP地址。In an example, before the first UE sends the IP packet to the serving gateway, the IP address of the target server may also be obtained. For example, the first UE may receive the IP address of the target server sent by the first packet gateway. Wherein, the first packet gateway may send a redirect message to the first UE (for example HTTP redirect message), the redirect message contains the IP address of the target server.
在另一个示例中，服务网关与第一分组网关之间的第一承载，可以是第一UE在与核心网建立PDN链接时，第一UE与第一分组网关之间建立的默认承载，该默认承载随着PDN的建立而建立，在PDN链接持续的情况下该默认承载始终存在。In another example, the first bearer between the serving gateway and the first packet gateway may be a default bearer established between the first UE and the first packet gateway when the first UE establishes a PDN link with the core network, where The default bearer is established with the establishment of the PDN, and the default bearer always exists if the PDN link continues.
在S320部分，服务网关根据所述IP地址确定目标服务器对应的第一轻量型分组网关；In S320, the serving gateway determines, according to the IP address, a first lightweight packet gateway corresponding to the target server;
在一个示例中，基站根据该IP地址，确定目标服务器后，然后确定目标服务器对应的第一轻量型分组网关。上述确定第一轻量型分组网关可以是确定第一轻量型分组网关的IP地址。其中，第一轻量型分组网关可以是与目标服务器部署在同一节点的网关；或者，第一轻量型分组网关也可以是与目标服务器位于同一局域网(Local Area Network，LAN)的网关。第一轻量型分组网关可以不包括计费功能，第一轻量型分组网关可以将第一UE访问目标服务器产生的计费信息发送给第一分组网关，由第一分组网关进行计费。In an example, the base station determines the target server according to the IP address, and then determines the first lightweight packet gateway corresponding to the target server. The determining the first lightweight packet gateway may be determining an IP address of the first lightweight packet gateway. The first lightweight packet gateway may be a gateway deployed on the same node as the target server; or the first lightweight packet gateway may be a gateway located on the same local area network (LAN) as the target server. The first lightweight packet gateway may not include the charging function, and the first lightweight packet gateway may send the charging information generated by the first UE to the target server to the first packet gateway, and the first packet gateway performs charging.
在S330部分，服务网关确定服务网关与第一轻量型分组网关之间的对应于第一UE的第二承载；In S330, the serving gateway determines a second bearer corresponding to the first UE between the serving gateway and the first lightweight packet gateway;
在一个示例中，服务网关可以从至少两个已有的承载中确定第二承载，该至少两个已有的承载为服务网关分别与至少两个网关之间的对应于第一UE的承载。例如，该至少两个网关可以包括第一分组网关，也可以包括至少一个轻量型分组网关。In an example, the serving gateway may determine the second bearer from the at least two existing bearers, where the at least two existing bearers are the bearers corresponding to the first UE between the serving gateway and the at least two gateways respectively. For example, the at least two gateways may include a first packet gateway, and may also include at least one lightweight packet gateway.
在另一个示例中，可以通过以下方式确定该第二承载：服务网关向第一轻量型分组网关发送承载建立请求，该承载建立请求用于请求建立第二承载。其中，该承载请求消息中可以包含第二承载的参数信息，该参数信息可用于建立该第二承载。进一步的，第一轻量型分组网关还可以在第二承载建立后向服务网关发送承载建立响应，该承载建立响应用于指示该第二承载已建立。例如，该承载建立请求可以是S5连接建立请求消息，该承载建立响应可以是S5连接建立响应消息。In another example, the second bearer can be determined by the serving gateway sending a bearer setup request to the first lightweight packet gateway, the bearer setup request for requesting to establish the second bearer. The bearer request message may include parameter information of the second bearer, where the parameter information may be used to establish the second bearer. Further, the first lightweight packet gateway may further send a bearer setup response to the serving gateway after the second bearer is established, where the bearer setup response is used to indicate that the second bearer has been established. For example, the bearer setup request may be an S5 connection setup request message, and the bearer setup response may be an S5 connection setup response message.
在S340部分，服务网关通过第二承载向第一轻量型分组网关发送第一UE的访问请求，访问请求用于请求访问目标服务器中存储的所述资源，其中第一UE访问所述资源所产生的计费信息是由第一轻量型分组网关发送至所述第一分组网关的，以使得所述第一分组网关进行计费。In the S340 part, the serving gateway sends an access request of the first UE to the first lightweight packet gateway by using the second bearer, where the access request is used to request access to the resource stored in the target server, where the first UE accesses the resource The generated charging information is sent by the first lightweight packet gateway to the first packet gateway, so that the first packet gateway performs charging.
在一个示例中，访问请求中可以包括目标服务器的IP地址，服务网关可以根据访问请求中的IP地址确定或选择第二承载传输第一UE的访问请求。In an example, the access request may include an IP address of the target server, and the serving gateway may determine or select a second bearer to transmit an access request of the first UE according to the IP address in the access request.
需要说明的是，该第一承载可以是第一UE通过基站、服务网关以及第 一分组网关建立的对应于该第一UE的承载的一部分，可以理解的是，在第一UE经由服务网关通过第一承载向第一分组网关发送请求消息，或经由服务网关通过第二承载向第一轻量型分组网关发送访问请求的两种情况中，第一UE与服务网关之间的承载可以重用，从而提高了承载的利用效率。It should be noted that the first bearer may be the first UE through the base station, the serving gateway, and the first A part of the bearer established by the packet gateway corresponding to the first UE, it may be understood that the first UE sends a request message to the first packet gateway through the first bearer via the serving gateway, or through the second bearer via the serving gateway. In the two cases in which the first lightweight packet gateway sends an access request, the bearer between the first UE and the serving gateway can be reused, thereby improving the utilization efficiency of the bearer.
在S350部分，第一轻量型分组网关通过第二承载向第一UE传输上述资源。In the S350 part, the first lightweight packet gateway transmits the foregoing resource to the first UE by using the second bearer.
可选地，第一轻量型分组网关可以向第一分组网关发送专用承载建立请求，该专用承载建立请求用于请求建立轻量型分组网关与第一分组网关之间的对应于第一UE的专用承载。Optionally, the first lightweight packet gateway may send a dedicated bearer setup request to the first packet gateway, where the dedicated bearer setup request is used to request to establish a correspondence between the lightweight packet gateway and the first packet gateway corresponding to the first UE. Dedicated bearer.
可选地，第一轻量型分组网关还可以向第一分组网关发送专用承载修改请求，该专用承载修改请求用于请求修改上述专用承载。Optionally, the first lightweight packet gateway may further send a dedicated bearer modification request to the first packet gateway, where the dedicated bearer modification request is used to request to modify the dedicated bearer.
可选地，第一轻量型分组网关还可以向第一分组网关发送专用承载删除请求，该专用承载删除请求用于请求删除上述专用承载。Optionally, the first lightweight packet gateway may further send a dedicated bearer deletion request to the first packet gateway, where the dedicated bearer deletion request is used to request to delete the dedicated bearer.
在S360部分，第一轻量型分组网关向第一分组网关发送第一UE访问上述资源所产生的计费信息，以使得第一分组网关进行计费。In the S360 part, the first lightweight packet gateway sends, to the first packet gateway, charging information generated by the first UE accessing the foregoing resource, so that the first packet gateway performs charging.
在本发明实施例中，在服务网关与第一分组网关之间存在对应于UE的第一承载的情况下，在服务网关与第一轻量型分组网关之间确定第二承载，使得UE能够通过第二承载访问轻量型分组网关对应的目标服务器中的资源，从而减少访问路径的路由迂回，节约了网络资源，提高了访问资源的效率。进一步的，UE访问所述资源所产生的计费信息由第一轻量型分组网关发送至第一分组网关进行计费，从而能够简化第一轻量型分组网关的操作。现有技术中，在单一PDN链接的情况下，UE产生的计费信息由第一分组网关进行计费，本发明实施例中由第一分组网关统计UE通过第一轻量型分组网关访问资源产生的计费，可以使本发明实施例的方案与现有技术具有较好的兼容性。In the embodiment of the present invention, when there is a first bearer corresponding to the UE between the serving gateway and the first packet gateway, determining a second bearer between the serving gateway and the first lightweight packet gateway, so that the UE can The second bearer accesses the resources in the target server corresponding to the lightweight packet gateway, thereby reducing the route bypass of the access path, saving network resources and improving the efficiency of accessing resources. Further, the charging information generated by the UE accessing the resource is sent by the first lightweight packet gateway to the first packet gateway for charging, so that the operation of the first lightweight packet gateway can be simplified. In the prior art, in the case of a single PDN link, the charging information generated by the UE is charged by the first packet gateway. In the embodiment of the present invention, the first packet gateway counts the UE to access the resource through the first lightweight packet gateway. The generated charging can make the solution of the embodiment of the present invention have better compatibility with the prior art.
本发明实施例提供的方案还可以包括可选方案一：终端在不同服务网关之间发生切换的情况下，UE访问资源的方案。需要说明的是，切换情况下UE访问资源的方案可以在执行图3所示方法的基础上执行，也可以不基于图3所示的方案执行。需要说明的是，上述不同服务网关可以对应于同一分组网关，也可以对应不同分组网关。可以理解的是，当不同服务网关对应同一分组网关时，UE访问资源的方案可以参考不同服务网关对应不同分组网关的方案，此处不作赘述。下面以不同服务网关为第一服务网关和第二服务网关，第一服务网关对应第一分组网关，以及第二服务网关对应第二分组网关为例。下面以切换的UE为第二UE为例进行描述，其中第二UE可以与 第一UE为相同的或不同的UE。The solution provided by the embodiment of the present invention may further include an Option 1: a scheme in which the UE accesses the resource when the terminal switches between different serving gateways. It should be noted that, in the case of a handover, the UE accessing the resource may be performed on the basis of performing the method shown in FIG. 3, or may not be performed based on the scheme shown in FIG. 3. It should be noted that the different service gateways may correspond to the same packet gateway, or may correspond to different packet gateways. It can be understood that, when different service gateways correspond to the same packet gateway, the scheme for the UE to access the resources may refer to the schemes of different service gateways corresponding to different packet gateways, and details are not described herein. The following uses the different service gateways as the first service gateway and the second service gateway. The first service gateway corresponds to the first packet gateway, and the second service gateway corresponds to the second packet gateway. The following describes the handover UE as the second UE, where the second UE can The first UE is the same or a different UE.
切换情况下第二UE访问资源的方案可以包括以下几个部分，其中，本发明实施例不限定各个部分的执行顺序。The scheme for accessing resources by the second UE in the case of a handover may include the following parts, wherein the embodiment of the present invention does not limit the execution order of the respective sections.
在可选方案一中，假设第二UE与第二服务网关已存在连接。例如，第二服务网关可以与第二分组网关之间存在对应于第二UE的第一承载(例如，默认承载)，且第二服务网关与第二轻量型分组网关之间存在对应于第二UE的第二承载。In Option 1, it is assumed that the second UE and the second serving gateway already have a connection. For example, the second serving gateway may have a first bearer (eg, a default bearer) corresponding to the second UE, and the second serving gateway and the second lightweight packet gateway correspond to the first The second bearer of the two UEs.
在第一部分中，在第二UE从第二服务网关切换至第一服务网关的情况下，移动性管理网元向第一服务网关发送第一信息，第一信息用于指示第一服务网关与第二轻量型分组网关建立对应于第二UE的第三承载。In the first part, in a case that the second UE is handed over from the second serving gateway to the first serving gateway, the mobility management network element sends first information to the first serving gateway, where the first information is used to indicate the first serving gateway and The second lightweight packet gateway establishes a third bearer corresponding to the second UE.
可选地，第二服务网关可以接收移动性管理网元发送的建立会话请求消息，该建立会话请求消息可以用于指示第一服务网关与第二分组网关之间建立对应于第二UE的承载(即默认承载)。Optionally, the second serving gateway may receive the setup session request message sent by the mobility management network element, where the setup session request message may be used to indicate that the bearer corresponding to the second UE is established between the first serving gateway and the second packet gateway. (ie default bearer).
作为一个示例，该建立会话请求消息可以携带该第一信息。例如，该第一信息可以承载于建立会话请求消息的私有扩展信息单元IE上。第一服务网关在接收到建立会话请求消息之后，可以与第一分组网关建立承载，并可以在建立承载之后，向移动性管理网元发送建立会话请求响应消息。As an example, the setup session request message may carry the first information. For example, the first information may be carried on a private extension information element IE that establishes a session request message. After receiving the setup session request message, the first serving gateway may establish a bearer with the first packet gateway, and may send a setup session request response message to the mobility management network element after establishing the bearer.
在第二部分中，第一服务网关确定第一服务网关是否支持与第二轻量型分组网关建立对应于第二UE的承载。并向移动性管理网元发送第二信息，第二信息用于通知移动性管理网元第一服务网关支持或者不支持在第一服务网关与第二轻量型分组网关之间直接建立承载。In the second part, the first serving gateway determines whether the first serving gateway supports establishing a bearer corresponding to the second UE with the second lightweight packet gateway. And sending the second information to the mobility management network element, where the second information is used to notify the mobility management network element that the first serving gateway supports or does not support directly establishing the bearer between the first serving gateway and the second lightweight packet gateway.
作为一个示例，上述建立会话请求响应消息可以携带该第二信息。例如，第二信息可以承载于建立会话请求响应消息的私有扩展IE上。As an example, the above establishment session request response message may carry the second information. For example, the second information can be carried on a private extension IE that establishes a session request response message.
可选地，上述第二信息还可以用于解释第一服务网关不支持第一轻量型分组网关的原因。可选地，在第一服务网关不支持与第一轻量型分组网关的情况下，第一服务网关也可以不发送第二信息，移动性管理网元在确定没有接收到第二信息，或者建立会话请求响应消息中不包括第二信息时，由此确定第一服务网关不支持与第一轻量型分组网关建立承载。Optionally, the foregoing second information may also be used to explain why the first serving gateway does not support the first lightweight packet gateway. Optionally, in a case that the first serving gateway does not support the first lightweight packet gateway, the first serving gateway may not send the second information, and the mobility management network element determines that the second information is not received, or When the second information is not included in the establishment session request response message, it is determined that the first service gateway does not support establishing a bearer with the first lightweight packet gateway.
在第三部分中，当第一服务网关支持在第一服务网关与第二轻量型分组网关之间直接建立承载时，第一服务网关在第一服务网关与第二轻量型分组网关之间直接建立承载；或者，当第一服务网关不支持在第一服务网关与第二轻量型分组网关之间直接建立承载时，第一服务网关可以在对应于第二轻量型分组网关的第二分组网关与第一服务网关之间建立对应于第二UE的承载。以使得第一服务网关经由第二分组网关与第二轻量型分组网关进行有关 第二UE的交互(或者说，第一服务网关通过第一服务网关与第二分组网关之间的承载以及第二分组网关与第二轻量型分组网关之间的承载传输第二UE对应的资源)。In the third part, when the first serving gateway supports directly establishing a bearer between the first serving gateway and the second lightweight packet gateway, the first serving gateway is in the first serving gateway and the second lightweight packet gateway. The bearer is directly established; or, when the first serving gateway does not support establishing a bearer directly between the first serving gateway and the second lightweight packet gateway, the first serving gateway may be corresponding to the second lightweight packet gateway. A bearer corresponding to the second UE is established between the second packet gateway and the first serving gateway. So that the first serving gateway is related to the second lightweight packet gateway via the second packet gateway. The interaction of the second UE (or the first serving gateway through the bearer between the first serving gateway and the second packet gateway and the bearer transmission between the second packet gateway and the second lightweight packet gateway corresponds to the second UE Resources).
其中，上述第二分组网关为第二UE的默认承载对应的分组网关。The second packet gateway is a packet gateway corresponding to the default bearer of the second UE.
其中，上述第一服务网关也可以称为目标服务网关，上述第二服务网关也可以称为源服务网关。上述第一服务网关或第二服务网关可以为图1至图3中的服务网关。The first serving gateway may also be referred to as a target serving gateway, and the second serving gateway may also be referred to as a source serving gateway. The first serving gateway or the second serving gateway may be the serving gateway in FIG. 1 to FIG.
在本发明实施例中，在服务网关发生切换时，移动性管理网元向第一服务网关发送建立会话请求消息中包括第一信息，第一信息用于指示第一服务网关与第二轻量型分组网关建立承载。避免了额外向第一服务网关发送消息，节省了信令开销，提高了访问资源的效率。In the embodiment of the present invention, when the serving gateway is switched, the mobility management network element sends the setup session request message to the first serving gateway, where the first information is used, where the first information is used to indicate the first serving gateway and the second lightweight The type of packet gateway establishes a bearer. The additional message is sent to the first serving gateway, which saves signaling overhead and improves the efficiency of accessing resources.
在本发明实施例中，在服务网关发生切换时，第一服务网关向移动性管理网元发送建立会话请求响应消息中包括第二信息，第二信息用于指示第一服务网关是否支持第一服务网关与第一轻量型分组网关建立承载，避免了额外向移动性管理网元发送消息，节省了信令开销，提高了访问资源的效率。In the embodiment of the present invention, when the serving gateway is switched, the first serving gateway sends a setup session request response message to the mobility management network element, where the second information is used to indicate whether the first serving gateway supports the first The service gateway establishes a bearer with the first lightweight packet gateway, which avoids sending additional messages to the mobility management network element, saves signaling overhead, and improves the efficiency of accessing resources.
本发明实施例提供的方案还可以包括可选方案二：建立分组网关与轻量型分组网关之间的专用承载，以传输UE访问的资源。需要说明的是，分组网关与轻量型分组网关之间建立专用承载，可以在执行图3所示方法的基础上执行，也可以不基于图3所示的方法的基础上执行。本方案中，分组网关可以为图3中的第一分组网关，轻量型分组网关可以为图3中的第一轻量型分组网关，UE可以为图3中的第一UE。The solution provided by the embodiment of the present invention may further include Option 2: establishing a dedicated bearer between the packet gateway and the lightweight packet gateway to transmit resources accessed by the UE. It should be noted that a dedicated bearer is established between the packet gateway and the lightweight packet gateway, and may be executed on the basis of performing the method shown in FIG. 3, or may not be performed based on the method shown in FIG. 3. In this solution, the packet gateway may be the first packet gateway in FIG. 3, the lightweight packet gateway may be the first lightweight packet gateway in FIG. 3, and the UE may be the first UE in FIG.
建立第一分组网关与轻量型分组网关之间的专用承载可以包括以下几个部分，其中，本发明实施例不限定各个部分的执行顺序。The implementation of the dedicated bearer between the first packet gateway and the lightweight packet gateway may include the following parts, wherein the embodiment of the present invention does not limit the execution order of the respective parts.
在第一部分，第一分组网关接收轻量型分组网关发送的专用承载建立请求，专用承载建立请求用于请求在第一分组网关与轻量型分组网关之间建立对应于UE的第一专用承载；In the first part, the first packet gateway receives a dedicated bearer setup request sent by the lightweight packet gateway, and the dedicated bearer setup request is used to request to establish a first dedicated bearer corresponding to the UE between the first packet gateway and the lightweight packet gateway. ;
应理解，在一个PDN链接中，可以存在默认承载和专用承载。其中默认承载是指满足默认的服务质量(Quality of Service，QoS)的数据和信令的承载。而专用承载是指在PDN链接的基础上，为了提供某种特定的QoS传输需求而建立的承载。通常情况下，专用承载的QoS比默认承载的QoS要求高。It should be understood that in a PDN link, there may be a default bearer and a dedicated bearer. The default bearer refers to the bearer of data and signaling that meets the default Quality of Service (QoS). A dedicated bearer is a bearer established on the basis of a PDN link to provide a specific QoS transmission requirement. In general, the QoS of a dedicated bearer is higher than the QoS requirement of a default bearer.
在第二部分，第一分组网关根据专用承载建立请求，建立第一专用承载；第一分组网关确定第一分组网关与UE之间的第二专用承载；第一分组网关指示服务网关建立服务网关与轻量型分组网关之间的第三专用承载。 In a second part, the first packet gateway establishes a first dedicated bearer according to the dedicated bearer setup request; the first packet gateway determines a second dedicated bearer between the first packet gateway and the UE; and the first packet gateway instructs the serving gateway to establish a serving gateway A third dedicated bearer with a lightweight packet gateway.
可选地，上述第一分组网关确定第一分组网关与UE之间的第二专用承载，可以采用以下方式：第一分组网关确定第一分组网关与UE之间存在专用承载，并将专用承载确定为第二专用承载；或者，第一分组网关确定第一分组网关与UE之间不存在专用承载，并建立第二专用承载。Optionally, the first packet gateway determines the second dedicated bearer between the first packet gateway and the UE, where the first packet gateway determines that there is a dedicated bearer between the first packet gateway and the UE, and the dedicated bearer is used. Determining to be the second dedicated bearer; or, the first packet gateway determines that there is no dedicated bearer between the first packet gateway and the UE, and establishes a second dedicated bearer.
应理解，上述第一分组网关与UE之间的第二专用承载，是指第一分组网关与UE之间的专用承载，UE和轻量型分组网关之间可以通过第一专用承载、第二专用承载传输资源。其中，第二专用承载可以包括第一分组网关与服务网关之间的专用承载，服务网关与基站之间的专用承载，以及基站与UE之间的无线专用承载。其中UE也可以和轻量型网关之间也可以同时通过第三专用承载以及服务网关与UE之间的专用承载传输资源。It should be understood that the second dedicated bearer between the first packet gateway and the UE refers to a dedicated bearer between the first packet gateway and the UE, and the first dedicated bearer and the second between the UE and the lightweight packet gateway may be adopted. Dedicated bearer transmission resources. The second dedicated bearer may include a dedicated bearer between the first packet gateway and the serving gateway, a dedicated bearer between the serving gateway and the base station, and a wireless dedicated bearer between the base station and the UE. The UE may also transmit resources through the third dedicated bearer and the dedicated bearer between the serving gateway and the UE simultaneously with the lightweight gateway.
现有技术中第一分组网关只可能与一个网关建立对应UE的第一专用承载。例如，第一分组网关在与PGW2建立第一专用承载后，第一分组网关需要与UE之间建立第二专用承载，以建立UE到PGW2之间的专用承载。而在本发明实施例中，第一分组网关在接收到轻量型分组网关的专用承载建立请求时，第一分组网关可能与其他网关已建立专用承载，这说明第一分组网关和UE之间已经建立专用承载，此时第一分组网关无需再建立第二专用承载，只需将第一分组网关和UE之间已存在的专用承载确认为第二专用承载。并通过第一专用承载和第二专用承载传输UE访问的资源。当第一分组网关与UE之间不存在专用承载时，第一分组网关建立该第二专用承载，能够节约网络资源，提高UE访问资源的效率。In the prior art, the first packet gateway may only establish a first dedicated bearer corresponding to the UE with one gateway. For example, after the first packet gateway establishes the first dedicated bearer with the PGW2, the first packet gateway needs to establish a second dedicated bearer with the UE to establish a dedicated bearer between the UE and the PGW2. In the embodiment of the present invention, when the first packet gateway receives the dedicated bearer setup request of the lightweight packet gateway, the first packet gateway may establish a dedicated bearer with other gateways, which indicates that the first packet gateway and the UE are A dedicated bearer has been established. At this time, the first packet gateway does not need to establish the second dedicated bearer, and only the dedicated bearer existing between the first packet gateway 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. When there is no dedicated bearer between the first packet gateway and the UE, the first packet gateway establishes the second dedicated bearer, which can save network resources and improve the efficiency of the UE accessing resources.
本发明实施例提供的方案还可以包括可选方案三：修改第一分组网关与轻量型分组网关之间的专用承载。需要说明的是，修改专用承载的方法可以在已建立第一分组网关与轻量型分组网关之间的专用承载的基础上执行。可以包括以下几个部分，其中，本发明实施例不限定各个部分的执行顺序。The solution provided by the embodiment of the present invention may further include Option 3: modifying a dedicated bearer between the first packet gateway and the lightweight packet gateway. It should be noted that the method for modifying the dedicated bearer may be performed on the basis of establishing a dedicated bearer between the first packet gateway and the lightweight packet gateway. The following parts may be included, wherein the embodiment of the invention does not limit the order of execution of the various parts.
在第一部分，第一分组网关接收轻量型分组网关发送的专用承载修改请求，专用承载修改请求用于请求修改第一专用承载；In the first part, the first packet gateway receives a dedicated bearer modification request sent by the lightweight packet gateway, and the dedicated bearer modification request is used to request to modify the first dedicated bearer;
在第二部分，第一分组网关根据专用承载修改请求修改第一专用承载，以及指示服务网关修改第三专用承载；In the second part, the first packet gateway modifies the first dedicated bearer according to the dedicated bearer modification request, and instructs the serving gateway to modify the third dedicated bearer;
在第三部分，第一分组网关确定第一分组网关与轻量型分组网关之外的其他网关之间存在对应于UE的专用承载，并新建第一分组网关与UE之间的专用承载。In the third part, the first packet gateway determines that there is a dedicated bearer corresponding to the UE between the first packet gateway and other gateways other than the lightweight packet gateway, and creates a dedicated bearer between the first packet gateway and the UE.
应理解，在本发明实施例中，第一分组网关接收到轻量型分组网关的专用承载修改请求后，需要修改第一分组网关与轻量型分组网关之间的第一专用承载，并且修改第一分组网关与UE之间的第三专用承载。此时，第一分 组网关还需确定是否存在其他网关与轻量型分组网关共用该第二专用承载，或者说，第一分组网关还需要确定第一分组网关与除轻量型分组网关之外的其他网关之间是否存在对应于UE的专用承载，当与其他网关存在专用承载时，第一分组网关需要新建第一分组网关与UE之间的专用承载，即轻量型分组网关使用新建的专用承载传输数据，其他网关使用第二专用承载传输数据，以确保UE与其他网关之间的专用承载的正常通信。当与其他网关不存在专用承载时，第二分组网关修改第二专用承载。It should be understood that, in the embodiment of the present invention, after receiving the dedicated bearer modification request of the lightweight packet gateway, the first packet gateway needs to modify the first dedicated bearer between the first packet gateway and the lightweight packet gateway, and modify A third dedicated bearer between the first packet gateway and the UE. At this point, the first point The group gateway also needs to determine whether there is another gateway sharing the second dedicated bearer with the lightweight packet gateway, or the first packet gateway needs to determine between the first packet gateway and other gateways other than the lightweight packet gateway. Whether there is a dedicated bearer corresponding to the UE. When there is a dedicated bearer with other gateways, the first packet gateway needs to newly establish a dedicated bearer between the first packet gateway and the UE, that is, the lightweight packet gateway uses the newly created dedicated bearer to transmit data. Other gateways use the second dedicated bearer to transmit data to ensure proper communication of the dedicated bearer between the UE and other gateways. When there is no dedicated bearer with other gateways, the second packet gateway modifies the second dedicated bearer.
在本发明实施例中，第一分组网关在修改与轻量型分组网关之间的第一专用承载的情况下，同时指示服务网关修改第三专用承载，并确定第一分组网关与轻量型分组网关以外的其他网关之间存在对应于UE的专用承载，即轻量型分组网关与其他网关共用第二专用承载，第一分组网关新建第一分组网关与UE之间的专用承载，以确保UE与其他网关之间的专用承载的通信，提高访问资源的效率。In the embodiment of the present invention, the first packet gateway, when modifying the first dedicated bearer between the packet and the lightweight packet gateway, simultaneously instructs the serving gateway to modify the third dedicated bearer, and determines the first packet gateway and the lightweight type. There is a dedicated bearer corresponding to the UE between the other gateways other than the packet gateway, that is, the lightweight packet gateway shares the second dedicated bearer with other gateways, and the first packet gateway establishes a dedicated bearer between the first packet gateway and the UE to ensure Communication of dedicated bearers between the UE and other gateways improves the efficiency of accessing resources.
本发明实施例提供的方案还可以包括可选方案四：删除第一分组网关与轻量型分组网关之间的专用承载。需要说明的是，删除专用承载的方法可以在已建立第一分组网关与轻量型分组网关之间的专用承载的基础上执行。可以包括以下几个部分，其中，本发明实施例不限定各个部分的执行顺序。The solution provided by the embodiment of the present invention may further include Option 4: deleting the dedicated bearer between the first packet gateway and the lightweight packet gateway. It should be noted that the method for deleting a dedicated bearer may be performed on the basis of establishing a dedicated bearer between the first packet gateway and the lightweight packet gateway. The following parts may be included, wherein the embodiment of the invention does not limit the order of execution of the various parts.
在第一部分，第一分组网关接收轻量型分组网关发送的专用承载删除请求，专用承载删除请求用于请求删除第一专用承载；In the first part, the first packet gateway receives a dedicated bearer deletion request sent by the lightweight packet gateway, and the dedicated bearer deletion request is used to request to delete the first dedicated bearer;
在第二部分，第一分组网关删除第一专用承载，以及指示服务网关删除第三专用承载；In the second part, the first packet gateway deletes the first dedicated bearer, and instructs the serving gateway to delete the third dedicated bearer;
在第三部分，第一分组网关确定第一分组网关与轻量型分组网关之外的其他网关不存在对应于UE的专用承载，并删除第二专用承载。In the third part, the first packet gateway determines that the first packet gateway and the other gateways other than the lightweight packet gateway do not have a dedicated bearer corresponding to the UE, and delete the second dedicated bearer.
应理解，在本发明实施例中，第一分组网关接收到轻量型分组网关的专用承载删除请求后，需要删除第一分组网关与轻量型分组网关之间的第一专用承载，同时指示服务网关删除服务网关与轻量型分组网关之间的第三专用承载，并且确定是否删除第一分组网关与UE之间的第二专用承载。此时，第一分组网关还需确定是否有其他网关与轻量型分组网关共用该第二专用承载，或者说，第一分组网关还需要确定第一分组网关与除轻量型分组网关之外的其他网关之间是否存在对应于UE的专用承载，当存在专用承载时，第一分组网关不删除第二专用承载，当第一分组网关与其他网关之间不存在对应于UE的专用承载时，第一分组网关删除第二专用承载，以确保UE与其他网关之间的专用承载的正常通信。It should be understood that, in the embodiment of the present invention, after receiving the dedicated bearer deletion request of the lightweight packet gateway, the first packet gateway needs to delete the first dedicated bearer between the first packet gateway and the lightweight packet gateway, and simultaneously indicate The serving gateway deletes the third dedicated bearer between the serving gateway and the lightweight packet gateway, and determines whether to delete the second dedicated bearer between the first packet gateway and the UE. At this time, the first packet gateway further needs to determine whether another gateway shares the second dedicated bearer with the lightweight packet gateway, or the first packet gateway needs to determine the first packet gateway and the light-weight packet gateway. Whether there is a dedicated bearer corresponding to the UE between the other gateways, when there is a dedicated bearer, the first packet gateway does not delete the second dedicated bearer, when there is no dedicated bearer corresponding to the UE between the first packet gateway and other gateways The first packet gateway deletes the second dedicated bearer to ensure normal communication of the dedicated bearer between the UE and other gateways.
在本发明实施例中，第一分组网关在删除与轻量型分组网关之间的第一 专用承载的情况下，同时指示服务网关删除第三专用承载，同时确定第一分组网关与其他网关之间是否存在对应于UE的专用承载，当与其他网关存在专用承载时，第一分组网关不删除第一分组网关与UE之间的专用承载，以确保UE与其他网关之间的专用承载的正常通信，当与其他网关不存在专用承载时，可以直接删除第二专用承载。In the embodiment of the present invention, the first packet gateway is the first between the deletion and the lightweight packet gateway. In the case of a dedicated bearer, the serving gateway is instructed to delete the third dedicated bearer, and it is determined whether there is a dedicated bearer corresponding to the UE between the first packet gateway and the other gateway. When there is a dedicated bearer with other gateways, the first packet gateway does not The dedicated bearer between the first packet gateway and the UE is deleted to ensure normal communication of the dedicated bearer between the UE and other gateways. When there is no dedicated bearer with other gateways, the second dedicated bearer can be directly deleted.
下面将结合更多的附图，对本发明实施例的方案作进一步说明。The solution of the embodiments of the present invention will be further described below in conjunction with the accompanying drawings.
图4示出了本发明实施例提出的另一种访问资源的方法。如图4所示，服务网关可以为SGW，第一分组网关可以为PGW1，第一缓存服务器可以为PGW1对应的本地缓存服务器，第二缓存服务器可以为所述目标服务器，即第二缓存服务器存储有UE访问的资源。PGW2可以为所述第一轻量型分组网关，即PGW2为第二缓存服务器对应的网关。缓存控制器用于调度和控制分布式缓存***内的各缓存服务器，该第二承载可以为S5承载。FIG. 4 shows another method for accessing resources according to an embodiment of the present invention. As shown in FIG. 4, the serving gateway may be an SGW, the first packet gateway may be PGW1, the first cache server may be a local cache server corresponding to PGW1, and the second cache server may be the target server, that is, the second cache server. There are resources accessed by the UE. The PGW2 may be the first lightweight packet gateway, that is, the PGW2 is a gateway corresponding to the second cache server. The cache controller is configured to schedule and control each cache server in the distributed cache system, and the second bearer may be an S5 bearer.
如图4所示，访问资源的方法可以如下所述：As shown in Figure 4, the method of accessing resources can be as follows:
在S401部分，UE与PGW1之间建立PDN链接；In the S401 part, a PDN link is established between the UE and the PGW1;
在S402部分，UE通过PGW1与第一缓存服务器之间建立第一TCP连接；In the S402 part, the UE establishes a first TCP connection between the PGW1 and the first cache server;
在S403部分，UE通过PGW1向第一缓存服务器发送第一HTTP请求报文，该第一HTTP请求报文用于请求访问资源；In the S403 part, the UE sends a first HTTP request message to the first cache server by using the PGW1, where the first HTTP request message is used to request access to the resource;
在S404部分，第一缓存服务器进行本地缓存查询，如果本地缓存没有命中，则向缓存控制器发送查询消息；In the S404 part, 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;
在S405部分，缓存控制器接收查询消息之后，在分布式缓存范围内进行缓存命中查询，在确定所述资源存储于第二缓存服务器中后，将第二缓存服务器的IP地址反馈给第一缓存服务器；In the S405 part, after receiving the query message, the cache controller 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;
在S406部分，第一缓存服务器通过HTTP重定向消息将第二缓存服务器的IP地址通知UE，以便于UE根据该第二缓存服务器的IP地址，重新向第二缓存服务器发起第二TCP建立请求报文；In the S406 part, the first cache server notifies the UE of the IP address of the second cache server by using the HTTP redirect message, so that the UE re-initiates the second TCP setup request report to the second cache server according to the IP address of the second cache server. Text
在S407部分，SGW接收UE发送的第二TCP建立请求报文，该第二TCP建立请求报文中包括第二缓存服务器的IP地址，SGW根据该第二缓存服务器的IP地址，确定PGW2的IP地址，查找本地是否有对应PGW2的承载(例如，S5承载)，若存在，则利用S5承载与第二缓存服务器之间建立TCP连接，若不存在，则向PGW2发送S5承载连接建立请求消息；In the S407 part, 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. An address, if there is a bearer corresponding to the PGW2 (for example, an S5 bearer), if yes, a TCP connection is established between the S5 bearer and the second cache server, and if not, an S5 bearer connection establishment request message is sent to the PGW2;
本发明实施例中，服务网关通过解析UE发送的IP报文，确定PGW2的IP地址，无需控制面的信令，直接建立第二承载，节约了网络资源。In the embodiment of the present invention, the serving gateway determines the IP address of the PGW2 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.
在S408部分，PGW2收到S5承载连接建立请求消息后，建立S5承载， 并向SGW回复S5承载连接建立响应消息；In the S408 part, after receiving the S5 bearer connection establishment request message, the PGW2 establishes an S5 bearer. And replying to the SGW with an S5 bearer connection setup response message;
在S409部分，SGW利用与PGW2之间的S5承载建立TCP连接。In section S409, the SGW establishes a TCP connection using the S5 bearer between PGW2.
在S410部分，SGW接收UE发送的第二HTTP请求报文，该第二HTTP请求报文用于请求从第二缓存服务器中访问资源，SGW利用与PGW2之间的S5承载向UE传输资源。In the S410 part, 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.
在S411部分，PGW2向PGW1发送UE访问第二缓存服务器产生的计费信息，以便于PGW1进行计费。In the S411 part, the PGW2 sends the PBR1 the charging information generated by the UE accessing the second cache server, so that the PGW1 performs charging.
本发明实施例中，服务网关通过解析用户设备发送的IP报文，确定目标服务器的IP地址，进而根据目标服务器的IP地址确定第一轻量型分组网关，建立服务网关与第一轻量型分组网关之间的第二承载，通过第二承载传输资源，其中UE访问所述资源的计费信息由第一轻量型分组网关发送至第一分组网关进行计费，进而节约了网络资源，提高了访问资源的效率。In the embodiment of the present invention, the service gateway determines the IP address of the target server by parsing the IP packet sent by the user equipment, and then determines the first lightweight packet gateway according to the IP address of the target server, and establishes the service gateway and the first lightweight type. The second bearer between the packet gateways transmits the resource through the second bearer, where the charging information of the UE accessing the resource is sent by the first lightweight packet gateway to the first packet gateway for charging, thereby saving network resources. Increased efficiency in accessing resources.
图5示出了本发明实施例提出的又一种访问资源的方法，在图5所示的方法中，UE连接的服务网关由第一服务网关(SGW1)切换至第二服务网关(SGW2)。或者第一服务网关可以称为源服务网关，第二服务网关可以称为目标服务网关。第一服务网关与PGW1已建立第一承载(例如，默认承载)，第一服务网关与PGW2已建立第二承载。图5所示的方法中，与图4相同或相似的内容可以参考图5有关描述，此处不再赘述。该访问资源的方法包括：FIG. 5 shows still another method for accessing resources according to an embodiment of the present invention. In the method shown in FIG. 5, the serving gateway connected by the UE is switched from the first serving gateway (SGW1) to the second serving gateway (SGW2). . Or the first serving gateway may be referred to as a source serving gateway, and the second serving gateway may be referred to as a target serving gateway. The first serving gateway and the PGW1 have established a first bearer (for example, a default bearer), and the first serving gateway and the PGW2 have established a second bearer. For the method shown in FIG. 5, the same or similar content as FIG. 4 can be described with reference to FIG. 5, and details are not described herein again. The methods for accessing resources include:
在S510部分，UE通过第一基站、SGW1和PGW2进行通信，UE通过第一基站、SGW1与PGW1之间存在第一承载，SGW1与PGW2之间存在第二承载；In the S510 part, the UE communicates with the first base station, the SGW1, and the PGW2, the first base station exists between the SGW1 and the PGW1, and the second bearer exists between the SGW1 and the PGW2.
其中，在切换服务网关之前，UE可以通过第一基站、SGW1与PGW1连接，在切换服务网关之后，UE可以通过第二基站、SGW2与PGW1连接。The UE may be connected to the PGW1 through the first base station and the SGW1 before the handover of the serving gateway. After the handover of the serving gateway, the UE may be connected to the PGW1 through the second base station and the SGW2.
在S520部分，UE移动到第一基站覆盖边缘，进行切换准备，第一基站向MME发送路径切换请求(path switch request)；In S520, the UE moves to the coverage edge of the first base station to perform handover preparation, and the first base station sends a path switch request to the MME.
在S530部分，MME向SGW2发送建立会话请求(create session request)，该建立会话请求用于指示SGW2与PGW1建立承载，该建立会话请求中包括第一信息，所述第一信息用于指示SGW2和PGW2建立承载；In the S530 part, the MME sends a create session request to the SGW2, where the setup session request is used to instruct the SGW2 to establish a bearer with the PGW1, where the setup session request includes first information, where the first information is used to indicate the SGW2 and PGW2 establishes a bearer;
可选地，在本步骤中，MME可以通过建立会话请求中的私有扩展IE携带第一信息。Optionally, in this step, the MME may carry the first information by establishing a private extension IE in the session request.
在S540部分，SGW2建立SGW2与PGW1之间的承载，并在建立承载后向MME发送承载建立响应(create session response)。并且SGW2在接收到第一信息后，确定SGW2是否支持与PGW2建立第二承载；In S540, the SGW2 establishes a bearer between the SGW2 and the PGW1, and sends a bearer setup response (create session response) to the MME after the bearer is established. And after receiving the first information, the SGW2 determines whether the SGW2 supports establishing a second bearer with the PGW2.
在S550部分，当SGW2支持与PGW2建立第二承载时，SGW2在SGW2 和PGW2之间建立第二承载。In S550, when SGW2 supports establishing a second bearer with PGW2, SGW2 is at SGW2. Establish a second bearer with PGW2.
可选地，在本步骤中，当SGW2支持和PGW2建立第二承载时，SGW2可以在MME回复承载建立响应(create session response)添加第二信息，该第二信息用于通知SGW2支持与PGW2建立第二承载，其中，该第二信息可以承载于承载建立响应的私有扩展IE中。Optionally, in this step, when the SGW2 supports the establishment of the second bearer with the PGW2, the SGW2 may add the second information in the MME reply to the create session response, where the second information is used to notify the SGW2 to support the establishment of the PGW2. The second bearer, wherein the second information can be carried in the private extension IE of the bearer setup response.
在S560部分，当SGW2不支持和PGW2建立第二承载时，SGW2通过PGW1与PGW2建立第二承载；In S560, when SGW2 does not support establishing a second bearer with PGW2, SGW2 establishes a second bearer through PGW1 and PGW2;
可选地，在本步骤中，当SGW2不支持和PGW2建立PGW2建立第二承载时，SGW2可以在承载建立响应中添加第二信息，该第二信息用于解释SGW2不支持与PGW2建立第二承载的原因。其中，该第二信息可以承载于承载建立响应的私有扩展IE中。MME在接收到该承载建立响应后，可以指示SGW1删除SGW1与PGW1之间的第一承载，以及删除SGW1与PGW2之间的第二承载。Optionally, in this step, when the SGW2 does not support the establishment of the PGW2 and the PGW2 to establish the second bearer, the SGW2 may add the second information in the bearer setup response, where the second information is used to explain that the SGW2 does not support establishing the second with the PGW2. The reason for the bearer. The second information may be carried in a private extension IE that carries a setup establishment response. After receiving the bearer setup response, the MME may instruct the SGW1 to delete the first bearer between the SGW1 and the PGW1, and delete the second bearer between the SGW1 and the PGW2.
上文结合图1至图5详细的阐述了本发明实施例的访问资源的方法。在此基础上，根据业务的QoS等级需求不同，UE还可以和轻量型分组网关建立专用承载，并利用专用承载访问资源。下文将结合图6至图8说明建立、修改以及删除专用承载的方法。其中，图6至图8所示的方法中，SGW与PGW1之间已存在对应于UE的第一承载，SGW与轻量型分组网关之间也已存在对应于UE的第二承载。The method for accessing resources in the embodiment of the present invention is described in detail above with reference to FIGS. 1 through 5. On this basis, depending on the QoS level requirements of the service, the UE can also establish a dedicated bearer with the lightweight packet gateway and access the resources by using a dedicated bearer. A method of establishing, modifying, and deleting a dedicated bearer will be described below with reference to FIGS. 6 through 8. In the method shown in FIG. 6 to FIG. 8 , the first bearer corresponding to the UE already exists between the SGW and the PGW1, and the second bearer corresponding to the UE already exists between the SGW and the lightweight packet gateway.
图6是本发明实施例提供的一种专用承载建立方法的通信示意图，如图6所示，第一分组网关可以为PGW1，轻量型分组网关可以为PGW2，服务网关可以为SGW，建立专用承载的方法包括：FIG. 6 is a schematic diagram of communication of a dedicated bearer setup method according to an embodiment of the present invention. As shown in FIG. 6, the first packet gateway may be PGW1, the lightweight packet gateway may be PGW2, and the service gateway may be a SGW. The methods of hosting include:
在S610部分，PGW2向PGW1发送专用承载建立请求，该专用承载建立请求用于请求建立PGW1与PGW2之间的第一专用承载；In the S610 part, the PGW2 sends a dedicated bearer setup request to the PGW1, where the dedicated bearer setup request is used to request to establish a first dedicated bearer between the PGW1 and the PGW2;
在S620部分，PGW1确定PGW1与UE之间是否存在专用承载；In part S620, PGW1 determines whether there is a dedicated bearer between PGW1 and the UE;
在S630部分，当存在专用承载时，PGW1将该专用承载确定为PGW1与UE之间的第二专用承载，以及建立PGW1与PGW2之间的第一专用承载，并指示SGW建立SGW与PGW2之间的第三专用承载；In the S630 part, when there is a dedicated bearer, the PGW1 determines the dedicated bearer as a second dedicated bearer between the PGW1 and the UE, and establishes a first dedicated bearer between the PGW1 and the PGW2, and instructs the SGW to establish an SGW between the SGW and the PGW2. Third dedicated bearer;
在S640部分，当不存在专用承载时，PGW1建立PGW1与PGW2之间的第一专用承载，以及建立PGW1与与UE之间的第二专用承载，并指示SGW建立SGW与PGW2之间的第三专用承载。In the S640 part, when there is no dedicated bearer, PGW1 establishes a first dedicated bearer between PGW1 and PGW2, and establishes a second dedicated bearer between PGW1 and the UE, and instructs the SGW to establish a third between SGW and PGW2. Dedicated bearer.
在本发明实施例中，第一分组网关在确定第一分组网关与UE之间存在专用承载的情况下，无需再建立第二专用承载，将该专用承载确定为第二专用承载，该第二专用承载可以重用，以节约网络资源。 In the embodiment of the present invention, when the first packet gateway determines that there is a dedicated bearer between the first packet gateway and the UE, the second dedicated bearer does not need to be established, and the dedicated bearer is determined as the second dedicated bearer, and the second Dedicated bearers can be reused to conserve network resources.
图7是一种专用承载的修改方法的通信示意图，如图7所示，图7所示的方法中，与图6或相同或相似的内容可以参考图6有关的描述，此处不再赘述。修改专用承载的方法包括：FIG. 7 is a schematic diagram of communication of a modification method of a dedicated bearer. As shown in FIG. 7 , in the method shown in FIG. 7 , the same or similar content as FIG. 6 can refer to FIG. 6 , and details are not described herein again. . The methods for modifying a dedicated bearer include:
在S710部分，PGW2向PGW1发送专用承载建立请求，该专用承载修改请求用于请求建立PGW1与PGW2之间的第一专用承载；In the S710 part, the PGW2 sends a dedicated bearer setup request to the PGW1, where the dedicated bearer modification request is used to request to establish a first dedicated bearer between the PGW1 and the PGW2;
在S720部分，PGW1确定PGW1与除PGW2之外的其他网关之间是否存在对应于UE的专用承载；In the S720 part, the PGW1 determines whether there is a dedicated bearer corresponding to the UE between the PGW1 and other gateways other than the PGW2;
在S730部分，当PGW1与除PGW2之外的其他网关之间存在专用承载时，PGW1新建UE到PGW1之间的专用承载，修改PGW2与PGW1之间的第一专用承载，以及指示SGW修改SGW与PGW2之间的第三专用承载，并可以向PGW2回复专用承载修改响应消息。In the S730 part, when there is a dedicated bearer between the PGW1 and other gateways other than the PGW2, the PGW1 creates a dedicated bearer between the UE and the PGW1, modifies the first dedicated bearer between the PGW2 and the PGW1, and instructs the SGW to modify the SGW and A third dedicated bearer between PGW2 and may reply to PGW2 with a dedicated bearer modification response message.
其中，当与其他网关之间存在专用承载时，说明其他网关和PGW2共用PGW1与UE之间的第二专用承载，若修改第二专用承载，将影响UE和其他网关之间的通信。本步骤通过新建UE到PGW1之间的专用承载，保持UE和其他网关之间的通信。When there is a dedicated bearer between the other gateways, the other gateways and the PGW2 share the second dedicated bearer between the PGW1 and the UE. If the second dedicated bearer is modified, the communication between the UE and other gateways will be affected. This step maintains communication between the UE and other gateways by creating a dedicated bearer between the UE and the PGW1.
在S740部分，当PGW1与除PGW2之外的其他网关之间不存在专用承载时，PGW1修改PGW1至PGW2之间的第一专用承载，以及修改PGW1至UE之间的第二专用承载，以及指示SGW修改SGW与PGW2之间的第三专用承载，并可以向PGW2发送专用承载修改响应消息。In the S740 part, when there is no dedicated bearer between PGW1 and other gateways other than PGW2, PGW1 modifies the first dedicated bearer between PGW1 and PGW2, and modifies the second dedicated bearer between PGW1 and UE, and indicates The SGW modifies the third dedicated bearer between the SGW and the PGW2, and may send a dedicated bearer modification response message to the PGW2.
在本发明实施例中，PGW1在修改与PGW2之间的第一专用承载的情况下，同时指示服务网关修改SGW与PGW2之间的第三专用承载，并确定PGW1与PGW2以外的其他网关之间存在对应于UE的专用承载，即PGW2与其他网关共用第二专用承载，PGW1新建PGW1与UE之间的专用承载，以确保UE与其他网关之间的专用承载的通信，提高访问资源的效率。In the embodiment of the present invention, the PGW1 instructs the serving gateway to modify the third dedicated bearer between the SGW and the PGW2 in the case of modifying the first dedicated bearer with the PGW2, and determines between the PGW1 and other gateways other than the PGW2. There is a dedicated bearer corresponding to the UE, that is, PGW2 shares the second dedicated bearer with other gateways, and PGW1 creates a dedicated bearer between the PGW1 and the UE to ensure communication between the UE and other gateways, and improve the efficiency of accessing resources.
例如，图8是一种专用承载的删除方法的通信示意图，图8所示的方法中，与图6或图7相同或相似的内容可以参考图6或图7有关的描述，此处不再赘述。如图8所示，删除专用承载的方法包括：For example, FIG. 8 is a schematic diagram of communication of a deletion method of a dedicated bearer. In the method shown in FIG. 8 , the same or similar content as FIG. 6 or FIG. 7 can refer to the description related to FIG. 6 or FIG. 7 . Narration. As shown in FIG. 8, the method for deleting a dedicated bearer includes:
在S810部分，PGW1接收PGW2发送的专用承载删除请求，所述专用承载删除请求用于请求删除PGW1与PGW2之间的第一专用承载；In the S810 part, the PGW1 receives the dedicated bearer deletion request sent by the PGW2, and the dedicated bearer deletion request is used to request to delete the first dedicated bearer between the PGW1 and the PGW2;
在S820部分，PGW1确定PGW1与除PGW2之外的其他网关之间是否存在对应于UE的专用承载；In part S820, PGW1 determines whether there is a dedicated bearer corresponding to the UE between PGW1 and other gateways other than PGW2;
在S830部分，当PGW1与其他网关之间存在专用承载时，PGW1删除PGW1与PGW2之间的第一专用承载，以及指示SGW删除SGW与PGW2之间的第三专用承载，不删除PGW1与UE之间的第二专用承载； In the S830 part, when there is a dedicated bearer between the PGW1 and the other gateway, the PGW1 deletes the first dedicated bearer between the PGW1 and the PGW2, and instructs the SGW to delete the third dedicated bearer between the SGW and the PGW2, and does not delete the PGW1 and the UE. Second dedicated bearer
在S840部分，当PGW1与其他网关之间不存在专用承载时，PGW1删除PGW1与GW之间的第一专用承载，删除PGW1与UE之间的第二专用承载，以及指示SGW删除SGW与PGW2之间的第三专用承载。In the S840 part, when there is no dedicated bearer between the PGW1 and the other gateway, the PGW1 deletes the first dedicated bearer between the PGW1 and the GW, deletes the second dedicated bearer between the PGW1 and the UE, and instructs the SGW to delete the SGW and the PGW2. The third dedicated bearer between.
在本发明实施例中，第一分组网关在删除与轻量型分组网关之间的第一专用承载的情况下，同时指示服务网关删除第三专用承载，同时确定第一分组网关与其他网关之间是否存在对应于UE的专用承载，当与其他网关存在专用承载时，第一分组网关不删除第一分组网关与UE之间的专用承载，以确保UE与其他网关之间的专用承载的正常通信，当与其他网关不存在专用承载时，可以直接删除第二专用承载。In the embodiment of the present invention, the first packet gateway, when deleting the first dedicated bearer between the packet and the lightweight packet gateway, simultaneously instructs the serving gateway to delete the third dedicated bearer, and simultaneously determines the first packet gateway and other gateways. Whether there is a dedicated bearer corresponding to the UE. When there is a dedicated bearer with other gateways, the first packet gateway does not delete the dedicated bearer between the first packet gateway and the UE to ensure the normal bearer between the UE and other gateways. Communication, when there is no dedicated bearer with other gateways, the second dedicated bearer can be directly deleted.
需要说明的是，本发明实施例提供的方案在应用于不同的***架构时，服务网关可以为SGW或SGSN，第一分组网关可以为PGW或GGSN。例如，当应用于图2所示的***架构时，第一分组网关为SGW，分组网关为PGW。It should be noted that, when the solution provided by the embodiment of the present invention is applied to different system architectures, the serving gateway may be an SGW or an SGSN, and the first packet gateway may be a PGW or a GGSN. For example, when applied to the system architecture shown in FIG. 2, the first packet gateway is an SGW, and the packet gateway is a PGW.
上述主要从各个网元之间交互的角度对本发明实施例的方案进行了介绍。可以理解的是，各个网元，例如服务网关、轻量型分组网关、第一分组网关、移动性管理网元等为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，本发明能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本发明的范围。The foregoing describes the solution of the embodiment of the present invention mainly from the perspective of interaction between the network elements. It can be understood that each network element, such as a service gateway, a lightweight packet gateway, a first packet gateway, a mobility management network element, etc., in order to implement the above functions, includes hardware structures and/or software modules corresponding to performing various functions. . Those skilled in the art will readily appreciate that 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 service gateway, a lightweight packet gateway, a first packet gateway, a mobility management network element, and the like according to the foregoing method. For example, each functional unit may be divided according to each function, or may be Two or more functions are integrated in 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.
在采用集成的单元的情况下，图9A示出了上述实施例中所涉及的服务网关的一种可能的结构示意图。服务网关900包括：处理单元902和通信单元903。处理单元902用于对服务网关的动作进行控制管理，例如，处理单元902用于支持服务网关执行图3中的过程S310～S340，图4中的过程S407～S410，图5中的过程S530～S560，图6中的过程S630，S640，图7的过程S730，S740，图8的过程S830，S840，和/或用于本文所描述的技术的其它过程。通信单元903用于支持服务网关与其他网络实体的通信，例如与 图2中示出的基站、MME、PGW等之间的通信。服务网关还可以包括存储单元901，用于存储服务网关的程序代码和数据。In the case of employing an integrated unit, FIG. 9A shows a possible structural diagram of the service gateway involved in the above embodiment. The service gateway 900 includes a processing unit 902 and a communication unit 903. The processing unit 902 is configured to perform control management on the action of the serving gateway. For example, the processing unit 902 is configured to support the service gateway to perform the processes S310-S340 in FIG. 3, the processes S407-S410 in FIG. 4, and the process S530- in FIG. S560, processes S630, S640 in FIG. 6, processes S730, S740 of FIG. 7, processes S830, S840 of FIG. 8, and/or other processes for the techniques described herein. The communication unit 903 is configured to support communication between the service gateway and other network entities, for example, Communication between the base station, MME, PGW, etc. shown in FIG. The service gateway may further include a storage unit 901 for storing program codes and data of the service gateway.
其中，处理单元902可以是处理器或控制器，例如可以是中央处理器(Central Processing Unit，CPU)，通用处理器，数字信号处理器(Digital Signal Processor，DSP)，专用集成电路(Application-Specific Integrated Circuit，ASIC)，现场可编程门阵列(Field Programmable Gate Array，FPGA)或者其他可编程逻辑器件、晶体管逻辑器件、硬件部件或者其任意组合。其可以实现或执行结合本发明公开内容所描述的各种示例性的逻辑方框，模块和电路。所述处理器也可以是实现计算功能的组合，例如包含一个或多个微处理器组合，DSP和微处理器的组合等等。通信单元903可以是收发器、收发电路或通信接口等。存储单元901可以是存储器。The processing unit 902 can be a processor or a controller, and can 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 903 may be a transceiver, a transceiver circuit, a communication interface, or the like. The storage unit 901 can be a memory.
当处理单元902为处理器，通信单元903为通信接口，存储单元901为存储器时，本发明实施例所涉及的服务网关可以为图9B所示的服务网关。When the processing unit 902 is a processor, the communication unit 903 is a communication interface, and the storage unit 901 is a memory, the service gateway according to the embodiment of the present invention may be the service gateway shown in FIG. 9B.
参阅图9B所示，该服务网关910包括：处理器912、通信接口913、存储器911。可选的，服务网关910还可以包括总线914。其中，通信接口913、处理器912以及存储器911可以通过总线914相互连接；总线914可以是外设部件互连标准(Peripheral Component Interconnect，简称PCI)总线或扩展工业标准结构(Extended Industry Standard Architecture，简称EISA)总线等。所述总线914可以分为地址总线、数据总线、控制总线等。为便于表示，图9B中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。Referring to FIG. 9B, the service gateway 910 includes a processor 912, a communication interface 913, and a memory 911. Alternatively, the service gateway 910 may also include a bus 914. The communication interface 913, the processor 912, and the memory 911 may be connected to each other through a bus 914. The bus 914 may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (abbreviated). EISA) bus and so on. The bus 914 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 9B, but it does not mean that there is only one bus or one type of bus.
在采用集成的单元的情况下，图10A示出了上述实施例中所涉及的轻量型分组网关的一种可能的结构示意图。轻量型分组网关1000包括：处理单元1002和通信单元1003。处理单元1002用于对轻量型分组网关的动作进行控制管理，例如，处理单元1002用于支持轻量型分组网关执行图3中的过程S350，S360，图4中的过程S408、S411，图5中的过程S550、S560，图6中的过程S610、S630，S640，图7的过程S710、S730，S740，图8的过程S810、S830、S840，和/或用于本文所描述的技术的其它过程。通信单元1003用于支持轻量型分组网关与其他网络实体的通信，例如与图2中示出的服务网关、MME、PGW等之间的通信。轻量型分组网关还可以包括存储单元1001，用于存储轻量型分组网关的程序代码和数据。In the case of employing an integrated unit, FIG. 10A shows a possible structural diagram of the lightweight packet gateway involved in the above embodiment. The lightweight packet gateway 1000 includes a processing unit 1002 and a communication unit 1003. The processing unit 1002 is configured to control and manage the action of the lightweight packet gateway. For example, the processing unit 1002 is configured to support the lightweight packet gateway to perform the process S350, S360 in FIG. 3, and the processes S408 and S411 in FIG. Processes S550, S560 in 5, processes S610, S630, S640 in FIG. 6, processes S710, S730, S740 of FIG. 7, processes S810, S830, S840 of FIG. 8, and/or for the techniques described herein Other processes. The communication unit 1003 is for supporting communication between the lightweight packet gateway and other network entities, such as communication with the serving gateway, MME, PGW, etc. shown in FIG. 2. The lightweight packet gateway may further include a storage unit 1001 for storing program codes and data of the lightweight packet gateway.
其中，处理单元1002可以是处理器或控制器，例如可以是中央处理器(Central Processing Unit，CPU)，通用处理器，数字信号处理器(Digital Signal Processor，DSP)，专用集成电路(Application-Specific Integrated Circuit，ASIC)，现场可编程门阵列(Field Programmable Gate Array，FPGA)或者其他可编 程逻辑器件、晶体管逻辑器件、硬件部件或者其任意组合。其可以实现或执行结合本发明公开内容所描述的各种示例性的逻辑方框，模块和电路。所述处理器也可以是实现计算功能的组合，例如包含一个或多个微处理器组合，DSP和微处理器的组合等等。通信单元1003可以是收发器、收发电路或通信接口等。存储单元1001可以是存储器。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 Program 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 transceiver, a transceiver circuit, a communication interface, or the like. The storage unit 1001 may be a memory.
当处理单元1002为处理器，通信单元1003为通信接口，存储单元1001为存储器时，本发明实施例所涉及的轻量型分组网关可以为图10B所示的轻量型分组网关。When the processing unit 1002 is a processor, the communication unit 1003 is a communication interface, and the storage unit 1001 is a memory, the lightweight packet gateway according to the embodiment of the present invention may be a lightweight packet gateway as shown in FIG. 10B.
参阅图10B所示，该轻量型分组网关1010包括：处理器1012、通信接口1013、存储器1011。可选的，轻量型分组网关1010还可以包括总线1014。其中，通信接口1013、处理器1012以及存储器1011可以通过总线1014相互连接；总线1014可以是外设部件互连标准(Peripheral Component Interconnect，简称PCI)总线或扩展工业标准结构(Extended Industry Standard Architecture，简称EISA)总线等。所述总线1014可以分为地址总线、数据总线、控制总线等。为便于表示，图10B中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。Referring to FIG. 10B, the lightweight packet gateway 1010 includes a processor 1012, a communication interface 1013, and a memory 1011. Alternatively, the lightweight packet 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 FIG. 10B, but it does not mean that there is only one bus or one type of bus.
在采用集成的单元的情况下，图11A示出了上述实施例中所涉及的分组网关的一种可能的结构示意图。该分组网关可以为上述的第一分组网关。分组网关1100包括：处理单元1102和通信单元1103。处理单元1102用于对分组网关的动作进行控制管理，例如，处理单元1102用于支持第一分组网关执行图3中的过程S310，S360，图4中的过程S401～S403、S411，图5中的过程S510、S540～S560，图6中的过程S610～S640，图7的过程S710～S740，图8的过程S810～S840，和/或用于本文所描述的技术的其它过程。为了简洁，适当省略重复的描述。In the case of employing an integrated unit, FIG. 11A shows a possible structural diagram of the packet gateway involved in the above embodiment. The packet gateway can be the first packet gateway described above. The packet gateway 1100 includes a processing unit 1102 and a communication unit 1103. The processing unit 1102 is configured to perform control management on the action of the packet gateway. For example, the processing unit 1102 is configured to support the first packet gateway to perform the process S310, S360 in FIG. 3, and the processes S401-S403 and S411 in FIG. Processes S510, S540-S560, processes S610-S640 in FIG. 6, processes S710-S740 of FIG. 7, processes S810-S840 of FIG. 8, and/or other processes for the techniques described herein. For the sake of brevity, repeated descriptions are omitted as appropriate.
当处理单元1102为处理器，通信单元1103为通信接口，存储单元1101为存储器时，本发明实施例所涉及的分组网关可以为图11B所示的分组网关。When the processing unit 1102 is a processor, the communication unit 1103 is a communication interface, and the storage unit 1101 is a memory, the packet gateway involved in the embodiment of the present invention may be the packet gateway shown in FIG. 11B.
参阅图11B所示，该分组网关1110包括：处理器1112、通信接口1113、存储器1111。可选的，分组网关1110还可以包括总线1114。为了简洁，此处省略重复的描述。Referring to FIG. 11B, the packet gateway 1110 includes a processor 1112, a communication interface 1113, and a memory 1111. Optionally, the packet gateway 1110 may further include a bus 1114. For the sake of brevity, the repeated description is omitted here.
在采用集成的单元的情况下，图12A示出了上述实施例中所涉及的移动性管理网元的一种可能的结构示意图。移动性管理网元1200包括：存储单元1201，处理单元1202和通信单元1203。其中，存储单元1201用于存储程序，通信单元1203用于和其他设备通信，处理单元1202用于执行存储单元1201中的程序，当所述程序被执行时，所述处理单元用于支持移动性管 理网元执行图5中的过程S520～S550，和/或用于本文所描述的技术的其它过程。为了简洁，适当省略重复的描述。In the case of employing an integrated unit, 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 storage unit 1201, a processing unit 1202, and a communication unit 1203. The storage unit 1201 is configured to store programs, the communication unit 1203 is configured to communicate with other devices, and the processing unit 1202 is configured to execute programs in the storage unit 1201, the processing unit is configured to support mobility when the program is executed. Tube The network element performs processes S520-S550 in Figure 5, and/or other processes for the techniques described herein. For the sake of brevity, repeated descriptions are omitted as appropriate.
其中，当处理单元1202为处理器，通信单元1203为通信接口，存储单元1201为存储器时，本发明实施例所涉及的移动性管理网元可以为图12B所示的移动性管理网元。参阅图12B所示，该移动性管理网元1210包括：处理器1212、通信接口1213、存储器1211，总线1214。为了简洁，适当省略重复的描述。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. Referring to FIG. 12B, 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.
用于执行本发明实施例上述服务网关、轻量型分组网关、分组网关或移动性管理网元的功能的处理器可以是中央处理器(Central Processing Unit，CPU)，通用处理器、数字信号处理器(Digital Signal Processor，DSP)、专用集成电路(Application-Specific Integrated Circuit，ASIC)，现场可编程门阵列(Field Programmable Gate Array，FPGA)或者其他可编程逻辑器件、晶体管逻辑器件，硬件部件或者其任意组合。其可以实现或执行结合本发明实施例公开内容所描述的各种示例性的逻辑方框，模块和电路。所述处理器也可以是实现计算功能的组合，例如包含一个或多个微处理器组合，DSP和微处理器的组合等等。The processor for performing the functions of the service gateway, the lightweight packet gateway, the packet gateway, or the mobility management network element in the embodiment of the present invention may be a central processing unit (CPU), a general-purpose processor, and digital signal processing. (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 random combination. 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.
结合本发明实施例公开内容所描述的方法或者算法的步骤可以硬件的方式来实现，也可以是由处理器执行软件指令的方式来实现。软件指令可以由相应的软件模块组成，软件模块可以被存放于随机存取存储器(Random Access Memory，RAM)、闪存、只读存储器(Read Only Memory，ROM)、可擦除可编程只读存储器(Erasable Programmable ROM，EPROM)、电可擦可编程只读存储器(Electrically EPROM，EEPROM)、寄存器、硬盘、移动硬盘、只读光盘(CD-ROM)或者本领域熟知的任何其它形式的存储介质中。一种示例性的存储介质耦合至处理器，从而使处理器能够从该存储介质读取信息，且可向该存储介质写入信息。当然，存储介质也可以是处理器的组成部分。处理器和存储介质可以位于ASIC中。另外，该ASIC可以位于网关设备或移动性管理网元中。当然，处理器和存储介质也可以作为分立组件存在于网关设备或移动性管理网元中。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. Of course, the storage medium can also be an integral part of the processor. The processor and the storage medium can be located in an ASIC. Additionally, the ASIC can be located in a gateway device or mobility management network element. Of course, the processor and the storage medium may also exist as discrete components in the gateway device or the mobility management network element.
本领域技术人员应该可以意识到，在上述一个或多个示例中，本发明实施例所描述的功能可以用硬件、软件、固件或它们的任意组合来实现。当使用软件实现时，可以将这些功能存储在计算机可读介质中或者作为计算机可读介质上的一个或多个指令或代码进行传输。计算机可读介质包括计算机存储介质和通信介质，其中通信介质包括便于从一个地方向另一个地方传送计算机程序的任何介质。存储介质可以是通用或专用计算机能够存取的任何可 用介质。Those skilled in the art should appreciate that in one or more of the above examples, the functions described in the embodiments of the present invention may be implemented in hardware, software, firmware, or any combination thereof. When implemented in software, the functions may be stored in a computer readable medium or transmitted as one or more instructions or code on a computer readable medium. Computer readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one location to another. The storage medium can be any one that can be accessed by a general purpose or special purpose computer. Use the media.
以上所述的具体实施方式，对本发明实施例的目的、技术方案和有益效果进行了进一步详细说明，所应理解的是，以上所述仅为本发明实施例的具体实施方式而已，并不用于限定本发明实施例的保护范围，凡在本发明实施例的技术方案的基础之上，所做的任何修改、等同替换、改进等，均应包括在本发明实施例的保护范围之内。 The specific embodiments of the present invention have been described in detail with reference to the embodiments of the embodiments of the present invention. The scope of the present invention is defined by the scope of the present invention. Any modifications, equivalents, improvements, etc., which are included in the embodiments of the present invention, are included in the scope of the present invention.

Claims (19)

  1. 一种访问资源的方法，其特征在于，包括：A method for accessing resources, comprising:
    轻量型分组网关接收服务网关通过第二承载发送的用户设备UE的访问请求，所述访问请求用于请求访问所述轻量型分组网关对应的目标服务器中存储的资源，所述第二承载为所述服务网关与所述轻量型分组网关之间的对应于所述UE的承载，其中，所述服务网关与第一分组网关之间具有对应于所述UE的第一承载；The lightweight packet gateway receives an access request of the user equipment UE that is sent by the serving gateway by using the second bearer, and the access request is used to request access to the resource stored in the target server corresponding to the lightweight packet gateway, where the second bearer a bearer corresponding to the UE between the serving gateway and the lightweight packet gateway, where the serving gateway and the first packet gateway have a first bearer corresponding to the UE;
    所述轻量型分组网关通过所述第二承载向所述UE传输所述资源；Transmitting, by the second bearer, the resource to the UE by using the second bearer;
    所述轻量型分组网关向所述第一分组网关发送所述UE访问所述资源所产生的计费信息，以使得所述第一分组网关进行计费。The lightweight packet gateway sends, to the first packet gateway, charging information generated by the UE accessing the resource, so that the first packet gateway performs charging.
  2. 如权利要求1所述的方法，其特征在于，所述方法还包括：The method of claim 1 wherein the method further comprises:
    所述轻量型分组网关接收所述服务网关发送的承载建立请求，所述承载建立请求用于请求建立所述第二承载；The lightweight packet gateway receives a bearer setup request sent by the serving gateway, where the bearer setup request is used to request to establish the second bearer;
    所述轻量型分组网关在所述第二承载建立后向所述服务网关发送承载建立响应，所述承载建立响应用于指示所述第二承载已建立。The lightweight packet gateway sends a bearer setup response to the serving gateway after the second bearer is established, and the bearer setup response is used to indicate that the second bearer has been established.
  3. 如权利要求1或2所述的方法，其特征在于，所述方法还包括：The method of claim 1 or 2, wherein the method further comprises:
    所述轻量型分组网关向所述第一分组网关发送专用承载建立请求，所述专用承载建立请求用于请求建立所述轻量型分组网关与所述第一分组网关之间的对应于所述UE的专用承载。The lightweight packet gateway sends a dedicated bearer setup request to the first packet gateway, the dedicated bearer setup request for requesting establishment of a correspondence between the lightweight packet gateway and the first packet gateway Dedicated bearer of the UE.
  4. 如权利要求3所述的方法，其特征在于，所述方法还包括：The method of claim 3, wherein the method further comprises:
    所述轻量型分组网关向所述第一分组网关发送专用承载修改请求，所述专用承载修改请求用于请求修改所述专用承载。The lightweight packet gateway sends a dedicated bearer modification request to the first packet gateway, where the dedicated bearer modification request is used to request to modify the dedicated bearer.
  5. 如权利要求3或4所述的方法，其特征在于，所述方法还包括：The method of claim 3 or 4, wherein the method further comprises:
    所述轻量型分组网关向所述第一分组网关发送专用承载删除请求，所述专用承载删除请求用于请求删除所述专用承载。The lightweight packet gateway sends a dedicated bearer deletion request to the first packet gateway, where the dedicated bearer deletion request is used to request to delete the dedicated bearer.
  6. 一种访问资源的方法，其特征在于，包括：A method for accessing resources, comprising:
    服务网关接收第一用户设备UE的互联网协议IP报文，所述IP报文中携带目标服务器的IP地址，所述目标服务器存储有所述第一UE待访问的资源，其中，所述服务网关与第一分组网关之间具有对应于所述第一UE的第一承载；The serving gateway receives the Internet Protocol IP packet of the first user equipment UE, where the IP packet carries the IP address of the target server, and the target server stores the resource to be accessed by the first UE, where the service gateway Having a first bearer corresponding to the first UE with the first packet gateway;
    所述服务网关根据所述IP地址确定所述目标服务器对应的第一轻量型分组网关；Determining, by the serving gateway, a first lightweight packet gateway corresponding to the target server according to the IP address;
    所述服务网关确定所述服务网关与所述第一轻量型分组网关之间的对应于所述第一UE的第二承载； Determining, by the serving gateway, a second bearer corresponding to the first UE between the serving gateway and the first lightweight packet gateway;
    所述服务网关通过所述第二承载向所述第一轻量型分组网关发送所述第一UE的访问请求，所述访问请求用于请求访问所述目标服务器中存储的所述资源，其中，所述第一UE访问所述资源所产生的计费信息是由所述第一轻量型分组网关发送至所述第一分组网关的，以使得所述第一分组网关进行计费。The serving gateway sends an access request of the first UE to the first lightweight packet gateway by using the second bearer, where the access request is used to request access to the resource stored in the target server, where The charging information generated by the first UE accessing the resource is sent by the first lightweight packet gateway to the first packet gateway, so that the first packet gateway performs charging.
  7. 如权利要求6所述的方法，其特征在于，所述服务网关确定所述服务网关与所述第一轻量型分组网关之间的第二承载，包括：The method of claim 6, wherein the serving gateway determines a second bearer between the serving gateway and the first lightweight packet gateway, comprising:
    所述服务网关向所述第一轻量型分组网关发送承载建立请求，所述承载建立请求用于请求建立所述第二承载；Sending, by the serving gateway, a bearer setup request to the first lightweight packet gateway, where the bearer setup request is used to request to establish the second bearer;
    所述服务网关接收所述第一轻量型分组网关发送的承载建立响应，所述承载建立响应用于指示所述第二承载已建立；Receiving, by the serving gateway, a bearer setup response sent by the first lightweight packet gateway, where the bearer setup response is used to indicate that the second bearer has been established;
    或者，or,
    所述服务网关从至少两个已有的承载中确定所述第二承载，所述至少两个已有的承载为所述服务网关与至少两个网关之间的对应于所述第一UE的承载。Determining, by the serving gateway, the second bearer from at least two existing bearers, where the at least two existing bearers are corresponding to the first UE between the serving gateway and at least two gateways Hosted.
  8. 如权利要求6或7所述的方法，其特征在于，所述方法还包括：The method of claim 6 or claim 7, wherein the method further comprises:
    所述服务网关接收移动性管理网元发送的第一信息，所述第一信息用于指示在所述服务网关与第二轻量型分组网关之间建立对应于第二UE的第三承载；Receiving, by the serving gateway, first information that is sent by the mobility management network element, where the first information is used to indicate that a third bearer corresponding to the second UE is established between the serving gateway and the second lightweight packet gateway;
    当所述服务网关支持在所述服务网关与所述第二轻量型分组网关之间建立承载时，所述服务网关在所述服务网关与所述第二轻量型分组网关之间建立所述第三承载；或者，When the serving gateway supports establishing a bearer between the serving gateway and the second lightweight packet gateway, the serving gateway establishes between the serving gateway and the second lightweight packet gateway Said third bearer; or,
    当所述服务网关不支持在所述服务网关与所述第二轻量型分组网关之间建立承载时，所述服务网关在对应于所述第二轻量型分组网关的第二分组网关与所述服务网关之间建立对应于所述第二UE的承载。When the serving gateway does not support establishing a bearer between the serving gateway and the second lightweight packet gateway, the serving gateway is in a second packet gateway corresponding to the second lightweight packet gateway A bearer corresponding to the second UE is established between the serving gateways.
  9. 如权利要求8所述的方法，其特征在于，所述方法还包括：The method of claim 8 wherein the method further comprises:
    所述服务网关向所述移动性管理网元发送第二信息，所述第二信息用于通知所述移动性管理网元所述服务网关支持或者不支持在所述服务网关与所述第二轻量型分组网关之间建立承载。The serving gateway sends second information to the mobility management network element, where the second information is used to notify the mobility management network element that the serving gateway supports or does not support the serving gateway and the second A bearer is established between the lightweight packet gateways.
  10. 一种轻量型分组网关，其特征在于，包括：处理单元和通信单元，A lightweight packet gateway, comprising: a processing unit and a communication unit,
    所述处理单元用于通过所述通信单元接收服务网关通过第二承载发送的用户设备UE的访问请求，所述访问请求用于请求访问所述轻量型分组网关对应的目标服务器中存储的资源，所述第二承载为所述服务网关与所述轻量型分组网关之间的对应于所述UE的承载，其中，所述服务网关与第一分 组网关之间具有对应于所述UE的第一承载；以及通过所述通信单元通过所述第二承载向所述UE传输所述资源；以及通过所述通信单元向所述第一分组网关发送所述UE访问所述资源所产生的计费信息，以使得所述第一分组网关进行计费。The processing unit is configured to receive, by using the communication unit, an access request of the user equipment UE that is sent by the serving gateway by using the second bearer, where the access request is used to request access to the resource stored in the target server corresponding to the lightweight packet gateway. The second bearer is a bearer corresponding to the UE between the serving gateway and the lightweight packet gateway, where the serving gateway and the first point are Having a first bearer corresponding to the UE between the group gateways; and transmitting, by the communication unit, the resource to the UE by the second bearer; and transmitting, by the communication unit, to the first packet gateway The UE accesses the charging information generated by the resource, so that the first packet gateway performs charging.
  11. 如权利要求10所述的轻量型分组网关，其特征在于，所述处理单元还用于通过所述通信单元接收所述服务网关发送的承载建立请求，所述承载建立请求用于请求建立所述第二承载；以及在所述第二承载建立后，通过所述通信单元向所述服务网关发送承载建立响应，所述承载建立响应用于指示所述第二承载已建立。The lightweight packet gateway according to claim 10, wherein the processing unit is further configured to receive, by the communication unit, a bearer setup request sent by the serving gateway, where the bearer setup request is used to request to establish a And the second bearer; and after the second bearer is established, sending, by the communications unit, a bearer setup response to the serving gateway, where the bearer setup response is used to indicate that the second bearer has been established.
  12. 如权利要求10或11所述的轻量型分组网关，其特征在于，所述处理单元还用于通过所述通信单元向所述第一分组网关发送专用承载建立请求，所述专用承载建立请求用于请求建立所述轻量型分组网关与所述第一分组网关之间的对应于所述UE的专用承载。The lightweight packet gateway according to claim 10 or 11, wherein the processing unit is further configured to send, by using the communication unit, a dedicated bearer setup request, the dedicated bearer setup request, to the first packet gateway. And configured to request to establish a dedicated bearer corresponding to the UE between the lightweight packet gateway and the first packet gateway.
  13. 如权利要求12所述的轻量型分组网关，其特征在于，所述处理单元还用于通过所述通信单元向所述第一分组网关发送专用承载修改请求，所述专用承载修改请求用于请求修改所述专用承载。The lightweight packet gateway according to claim 12, wherein the processing unit is further configured to send, by using the communication unit, a dedicated bearer modification request to the first packet gateway, where the dedicated bearer modification request is used for Request to modify the dedicated bearer.
  14. 如权利要求12或13所述的轻量型分组网关，其特征在于，所述处理单元还用于通过所述通信单元向所述第一分组网关发送专用承载删除请求，所述专用承载删除请求用于请求删除所述专用承载。The lightweight packet gateway according to claim 12 or 13, wherein the processing unit is further configured to send, by using the communication unit, a dedicated bearer deletion request, the dedicated bearer deletion request, to the first packet gateway. Used to request to delete the dedicated bearer.
  15. 一种服务网关，其特征在于，包括：处理单元和通信单元，A service gateway, comprising: a processing unit and a communication unit,
    所述处理单元用于通过所述通信单元接收第一用户设备UE的互联网协议IP报文，所述IP报文中携带目标服务器的IP地址，所述目标服务器存储有所述第一UE待访问的资源，其中，所述服务网关与第一分组网关之间具有对应于所述第一UE的第一承载；以及根据所述IP地址确定所述目标服务器对应的第一轻量型分组网关；以及确定所述服务网关与所述第一轻量型分组网关之间的对应于所述第一UE的第二承载；以及通过所述通信单元通过所述第二承载向所述第一轻量型分组网关发送所述第一UE的访问请求，所述访问请求用于请求访问所述目标服务器中存储的所述资源，其中，所述第一UE访问所述资源所产生的计费信息是由所述第一轻量型分组网关发送至所述第一分组网关的，以使得所述第一分组网关进行计费。The processing unit is configured to receive, by using the communication unit, an Internet Protocol IP packet of the first user equipment UE, where the IP packet carries an IP address of the target server, where the target server stores the first UE to be accessed. a resource, wherein the serving gateway and the first packet gateway have a first bearer corresponding to the first UE; and determining, according to the IP address, a first lightweight packet gateway corresponding to the target server; And determining, between the serving gateway and the first lightweight packet gateway, a second bearer corresponding to the first UE; and transmitting, by the communication unit, the first bearer by using the second bearer The type packet gateway sends the access request of the first UE, where the access request is used to request access to the resource stored in the target server, where the charging information generated by the first UE accessing the resource is And being sent by the first lightweight packet gateway to the first packet gateway, so that the first packet gateway performs charging.
  16. 如权利要求15所述的服务网关，其特征在于，所述处理单元具体用于通过所述通信单元向所述第一轻量型分组网关发送承载建立请求，所述承载建立请求用于请求建立所述第二承载；以及通过所述通信单元接收所述第一轻量型分组网关发送的承载建立响应，所述承载建立响应用于指示所述 第二承载已建立；或者，从至少两个已有的承载中确定所述第二承载，所述至少两个已有的承载为所述服务网关与至少两个网关之间的对应于所述第一UE的承载。The service gateway according to claim 15, wherein the processing unit is configured to send a bearer setup request to the first lightweight packet gateway by using the communication unit, where the bearer setup request is used to request to establish Receiving, by the communication unit, a bearer setup response sent by the first lightweight packet gateway, where the bearer setup response is used to indicate the The second bearer is established; or the second bearer is determined from the at least two existing bearers, where the at least two existing bearers are between the serving gateway and the at least two gateways. Bearer of the first UE.
  17. 如权利要求15或16所述的服务网关，其特征在于，所述处理单元还用于通过所述通信单元接收移动性管理网元发送的第一信息，所述第一信息用于指示在所述服务网关与第二轻量型分组网关之间建立对应于第二UE的第三承载；当所述服务网关支持在所述服务网关与所述第二轻量型分组网关之间建立承载时，所述处理单元还用于在所述服务网关与所述第二轻量型分组网关之间建立所述第三承载；或者，当所述服务网关不支持在所述服务网关与所述第二轻量型分组网关之间建立承载时，所述处理单元还用于在对应于所述第二轻量型分组网关的第二分组网关与所述服务网关之间建立对应于所述第二UE的承载，以使得所述服务网关经由所述第二分组网关与所述第二轻量型分组网关进行有关所述第二UE的交互。The service gateway according to claim 15 or 16, wherein the processing unit is further configured to receive, by the communication unit, first information sent by a mobility management network element, where the first information is used to indicate that Establishing a third bearer corresponding to the second UE between the serving gateway and the second lightweight packet gateway; and when the serving gateway supports establishing a bearer between the serving gateway and the second lightweight packet gateway The processing unit is further configured to establish the third bearer between the serving gateway and the second lightweight packet gateway; or, when the serving gateway does not support the serving gateway and the first When the bearer is established between the two lightweight packet gateways, the processing unit is further configured to establish, between the second packet gateway corresponding to the second lightweight packet gateway, and the serving gateway, corresponding to the second The bearer of the UE, such that the serving gateway performs interaction with the second UE via the second packet gateway and the second lightweight packet gateway.
  18. 如权利要求17所述的服务网关，其特征在于，所述处理单元还用于通过所述通信单元向所述移动性管理网元发送第二信息，所述第二信息用于通知所述移动性管理网元所述服务网关支持或者不支持在所述服务网关与所述第二轻量型分组网关之间建立承载。The service gateway according to claim 17, wherein the processing unit is further configured to send, by the communication unit, second information to the mobility management network element, where the second information is used to notify the mobile The service management gateway supports or does not support establishing a bearer between the service gateway and the second lightweight packet gateway.
  19. 一种通信***，其特征在于，包括如权利要求10至14中任一项所述的轻量型分组网关和如权利要求15至18中任一项所述的服务网关。 A communication system, comprising the lightweight packet gateway according to any one of claims 10 to 14 and the service gateway according to any one of claims 15 to 18.
PCT/CN2016/081918 2016-05-12 2016-05-12 Resource access method, device and system WO2017193346A1 (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN201680085627.9A CN109155752A (en) 2016-05-12 2016-05-12 Access the methods, devices and systems of resource
PCT/CN2016/081918 WO2017193346A1 (en) 2016-05-12 2016-05-12 Resource access method, device and system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2016/081918 WO2017193346A1 (en) 2016-05-12 2016-05-12 Resource access method, device and system

Publications (1)

Publication Number Publication Date
WO2017193346A1 true WO2017193346A1 (en) 2017-11-16

Family

ID=60266869

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/081918 WO2017193346A1 (en) 2016-05-12 2016-05-12 Resource access method, device and system

Country Status (2)

Country Link
CN (1) CN109155752A (en)
WO (1) WO2017193346A1 (en)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2011025421A1 (en) * 2009-08-25 2011-03-03 Telefonaktiebolaget L M Ericsson (Publ) Mobility anchor relocation
CN102014053A (en) * 2010-11-17 2011-04-13 华为技术有限公司 Service transmitting method and device and communication system
CN102740439A (en) * 2011-04-01 2012-10-17 株式会社日立制作所 Network system and communication log analyzer
CN105432045A (en) * 2013-06-13 2016-03-23 瑞典爱立信有限公司 Methods, apparatus, network node, and computer program product for dynamically providing CDN service through mobile network

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103596157A (en) * 2012-08-15 2014-02-19 中兴通讯股份有限公司 Method and device for billing local traffic on wireless side
EP2919528B1 (en) * 2012-11-28 2018-01-10 Huawei Technologies Co., Ltd. Mobile network communication method, communication device and communication system
US9271197B2 (en) * 2013-05-22 2016-02-23 Futurewei Technologies, Inc. System and method for distributed evolved packet core architecture
CN106063354B (en) * 2013-12-10 2020-09-29 天地拓印(广州)数据科技有限公司 Transmission device and method for uplink service data stream
EP3138352A4 (en) * 2014-04-28 2018-02-21 Intel IP Corporation Communication via dedicated network nodes

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2011025421A1 (en) * 2009-08-25 2011-03-03 Telefonaktiebolaget L M Ericsson (Publ) Mobility anchor relocation
CN102014053A (en) * 2010-11-17 2011-04-13 华为技术有限公司 Service transmitting method and device and communication system
CN102740439A (en) * 2011-04-01 2012-10-17 株式会社日立制作所 Network system and communication log analyzer
CN105432045A (en) * 2013-06-13 2016-03-23 瑞典爱立信有限公司 Methods, apparatus, network node, and computer program product for dynamically providing CDN service through mobile network

Also Published As

Publication number Publication date
CN109155752A (en) 2019-01-04

Similar Documents

Publication Publication Date Title
US10608842B2 (en) GTP-U downlink packet sending method and apparatus
US9942748B2 (en) Service provisioning system and method, and mobile edge application server and support node
JP2021517799A (en) Communication method and communication device
WO2019214729A1 (en) Data processing method and device
EP2741544B1 (en) Method, flow-distribution equipment and user terminal for data transmission
US20190090167A1 (en) Communication method in handover process and apparatus
JP2019521588A (en) Communication control method and related network element
US20190090169A1 (en) Communication method in handover process and apparatus
US10827348B2 (en) Data transmission method and apparatus
WO2020233249A1 (en) Packet transmission method and related apparatus
US9860869B2 (en) Method and apparatus for offloading data traffic in a wireless communication system
US11930358B2 (en) Seamless handoff between wireless access gateways
US20180242188A1 (en) Quality of service control method, device, and system
WO2013053133A1 (en) Service data transmission processing method, device and communication system
EP3840426B1 (en) Method and device for sending multicast data
WO2017084042A1 (en) Service flow transmission method and apparatus
WO2017101076A1 (en) Method and apparatus for transmitting downlink data notification message
US20190082482A1 (en) Resource access method, apparatus, and system
US10616110B2 (en) Packet transmission method, apparatus, and system
US11997547B2 (en) Mobility management in information centric networking
WO2017193346A1 (en) Resource access method, device and system
CN116097751A (en) Re-anchoring with SMF reselection
WO2017193348A1 (en) Resource access method, device and system
WO2017193698A1 (en) Apparatus control method and device
WO2016074468A1 (en) Optimal switching method supporting multiple pdn connections, network node and system

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

Country of ref document: EP

Kind code of ref document: A1

122 Ep: pct application non-entry in european phase

Ref document number: 16901301

Country of ref document: EP

Kind code of ref document: A1