WO2017193346A1 - Procédé, dispositif et système d'accès à une ressource - Google Patents

Procédé, dispositif et système d'accès à une ressource 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
English (en)
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 PCT/CN2016/081918 priority Critical patent/WO2017193346A1/fr
Priority to CN201680085627.9A priority patent/CN109155752A/zh
Publication of WO2017193346A1 publication Critical patent/WO2017193346A1/fr

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

La présente invention concerne un procédé, un dispositif et un système d'accès à une ressource, aptes à augmenter l'efficacité d'accès à une ressource. Le procédé comprend les opérations suivantes : une passerelle de paquet léger reçoit une requête d'accès d'un équipement utilisateur (UE) envoyée par une passerelle de serveur par l'intermédiaire d'un second support, la requête d'accès étant utilisée pour demander un accès à une ressource stockée dans un serveur cible correspondant à la passerelle de paquet léger, le second support étant un support entre la passerelle de serveur et la passerelle de paquet léger et correspondant à l'UE, un premier support correspondant à l'UE étant agencé entre la passerelle de serveur et une première passerelle de paquet ; la passerelle de paquet léger transmet la ressource à l'UE par l'intermédiaire du second support ; la passerelle de paquet léger envoie des informations de facturation générées par l'UE accédant à la ressource à la première passerelle de paquet, de façon à permettre à la première passerelle de paquet de réaliser une facturation.
PCT/CN2016/081918 2016-05-12 2016-05-12 Procédé, dispositif et système d'accès à une ressource WO2017193346A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/CN2016/081918 WO2017193346A1 (fr) 2016-05-12 2016-05-12 Procédé, dispositif et système d'accès à une ressource
CN201680085627.9A CN109155752A (zh) 2016-05-12 2016-05-12 访问资源的方法、装置和系统

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2016/081918 WO2017193346A1 (fr) 2016-05-12 2016-05-12 Procédé, dispositif et système d'accès à une ressource

Publications (1)

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

Family

ID=60266869

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/081918 WO2017193346A1 (fr) 2016-05-12 2016-05-12 Procédé, dispositif et système d'accès à une ressource

Country Status (2)

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

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2011025421A1 (fr) * 2009-08-25 2011-03-03 Telefonaktiebolaget L M Ericsson (Publ) Relocalisation d'ancre de mobilité
CN102014053A (zh) * 2010-11-17 2011-04-13 华为技术有限公司 业务下发方法、装置及通信系统
CN102740439A (zh) * 2011-04-01 2012-10-17 株式会社日立制作所 网络系统以及通信记录解析系统
CN105432045A (zh) * 2013-06-13 2016-03-23 瑞典爱立信有限公司 用于通过移动网络动态地提供cdn服务的方法、装置、网络节点和计算机程序产品

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103596157A (zh) * 2012-08-15 2014-02-19 中兴通讯股份有限公司 一种对无线侧本地流量进行计费的方法及装置
WO2014082232A1 (fr) * 2012-11-28 2014-06-05 华为技术有限公司 Procédé de communication de réseau mobile, dispositif de communication et système de communication
US9271197B2 (en) * 2013-05-22 2016-02-23 Futurewei Technologies, Inc. System and method for distributed evolved packet core architecture
WO2015085493A1 (fr) * 2013-12-10 2015-06-18 华为技术有限公司 Dispositif, procédé et système pour émettre un flux de données de service de liaison montante
CN106134282B (zh) * 2014-04-28 2020-02-07 英特尔Ip公司 经由专用网络节点的通信

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2011025421A1 (fr) * 2009-08-25 2011-03-03 Telefonaktiebolaget L M Ericsson (Publ) Relocalisation d'ancre de mobilité
CN102014053A (zh) * 2010-11-17 2011-04-13 华为技术有限公司 业务下发方法、装置及通信系统
CN102740439A (zh) * 2011-04-01 2012-10-17 株式会社日立制作所 网络系统以及通信记录解析系统
CN105432045A (zh) * 2013-06-13 2016-03-23 瑞典爱立信有限公司 用于通过移动网络动态地提供cdn服务的方法、装置、网络节点和计算机程序产品

Also Published As

Publication number Publication date
CN109155752A (zh) 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 (ja) 通信方法及び通信装置
WO2019214729A1 (fr) Procédé et dispositif de traitement de données
EP2741544B1 (fr) Procédé, équipement de distribution de débit et terminal d'utilisateur pour transmission de données
US20190090167A1 (en) Communication method in handover process and apparatus
US20190090169A1 (en) Communication method in handover process and apparatus
JP2019521588A (ja) 通信制御方法および関連するネットワーク要素
US10827348B2 (en) Data transmission method and apparatus
US20180242188A1 (en) Quality of service control method, device, and system
US11930358B2 (en) Seamless handoff between wireless access gateways
WO2020233249A1 (fr) Procédé de transmission de paquets et appareil associé
US9860869B2 (en) Method and apparatus for offloading data traffic in a wireless communication system
WO2013053133A1 (fr) Procédé de gestion de la transmission de données de service, dispositif et système de communication correspondants
CN116097751A (zh) 利用smf重新选择来重新锚定
EP3840426B1 (fr) Procédé et dispositif d'envoi de données de multidiffusion
WO2017084042A1 (fr) Procédé et appareil de transmission de flux de service
WO2017101076A1 (fr) Procédé et appareil de transmission de message de notification de données de liaison descendante
US20190082482A1 (en) Resource access method, apparatus, and system
US10616110B2 (en) Packet transmission method, apparatus, and system
WO2017193348A1 (fr) Procédé, dispositif et système d'accès à une ressource
US11997547B2 (en) Mobility management in information centric networking
WO2017193346A1 (fr) Procédé, dispositif et système d'accès à une ressource
WO2017193698A1 (fr) Procédé et dispositif de commande d'appareil
WO2016074468A1 (fr) Procédé de commutation optimale prenant en charge une pluralité de connexions pdn, nœud de réseau et système

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