EP3451785A1 - Ressourcenzugriffsverfahren, -vorrichtung und -system - Google Patents

Ressourcenzugriffsverfahren, -vorrichtung und -system Download PDF

Info

Publication number
EP3451785A1
EP3451785A1 EP16901303.4A EP16901303A EP3451785A1 EP 3451785 A1 EP3451785 A1 EP 3451785A1 EP 16901303 A EP16901303 A EP 16901303A EP 3451785 A1 EP3451785 A1 EP 3451785A1
Authority
EP
European Patent Office
Prior art keywords
gateway
bearer
dedicated bearer
serving gateway
packet
Prior art date
Legal status (The legal status 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 status listed.)
Withdrawn
Application number
EP16901303.4A
Other languages
English (en)
French (fr)
Other versions
EP3451785A4 (de
Inventor
Huadong Chen
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
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 Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Publication of EP3451785A1 publication Critical patent/EP3451785A1/de
Publication of EP3451785A4 publication Critical patent/EP3451785A4/de
Withdrawn legal-status Critical Current

Links

Images

Classifications

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

Definitions

  • the present invention relates to the communications field, and in particular, to a resource access method, an apparatus, and a system.
  • cache servers are deployed on edge gateways at vaious locations in a content delivery network (Content Delivery Network, CDN).
  • the cache server may cache a resource in a remote server.
  • user equipment User Equipment
  • UE may obtain a resource from a nearby cache server of the edge cache servers at various locations.
  • the UE accesses an external network through a base station, a serving gateway (Serving Gateway, SGW), and a packet data network gateway (Packet Data Network Gateway, PGW).
  • SGW Serving Gateway
  • PGW Packet Data Network Gateway
  • the UE accesses the external network through a PGW (for example, a PGW 1).
  • a PGW for example, a PGW 1
  • the PGW 1 needs to be connected to the PGW 2, to obtain the resource from the PGW 2, and then the PGW 1 sends the resource to the UE.
  • This resource access path causes route recurvation, and is unfavorable to the UE for obtaining a resource.
  • the present invention provides a resource access method, a serving gateway, a packet gateway, a mobility management network element, and a system, to avoid route recurvation of an access path, and improve resource access efficiency of UE.
  • an embodiment of the present invention provides a resource access method, including: receiving, by a serving gateway, an IP packet of UE, where the IP packet carries an IP address of a target server, the target server stores a resource to be accessed by the UE, and a first bearer corresponding to the UE exists between the serving gateway and a first packet gateway; determining, by the serving gateway based on the IP address, a second packet gateway corresponding to the target server; determining a second bearer that is between the serving gateway and the second packet gateway and that corresponds to the UE; and sending an access request of the UE by using the second bearer, where the access request is used to request to access the resource stored in the target server.
  • the second bearer when the first bearer corresponding to the UE exists between the serving gateway and the first packet gateway, the second bearer may be further determined between the serving gateway and the second packet gateway corresponding to the target server, and the access request of the UE is transmitted by using the second bearer, to access the resource stored in the target server. Therefore, the solution provided in this embodiment of the present invention can avoid route recurvation of an access path, to improve resource access efficiency of the UE.
  • the second bearer that is between the serving gateway and the second packet gateway and that corresponds to the UE may be determined in one of the following manners: First manner: The serving gateway determines the second bearer from at least two existing bearers, where the at least two existing bearers are bearers that are between the serving gateway and at least two packet gateways and that correspond to the UE. Second manner: The serving gateway sends a bearer setup request to the second packet gateway, where the bearer setup request is used to set up the second bearer; and the second packet gateway sets up the second bearer after receiving the bearer setup request. In the second manner, the second packet gateway may further send a bearer setup response message to the serving gateway.
  • the serving gateway may send the bearer setup request to the second packet gateway as instructed by a mobility management network element or the first packet gateway.
  • the serving gateway receives an instruction message sent by the mobility management network element or the first packet gateway, the instruction message carries an IP address of the second packet gateway, and the instruction message is used to instruct to set up the second bearer between the serving gateway and the second packet gateway. Therefore, the serving gateway may determine the IP address of the second packet gateway by using the instruction message sent by the mobility management network element or the first packet gateway, and set up the second bearer in advance as instructed by the instruction message, thereby reducing time used by the UE to access the resource.
  • the access request of the UE may be transmitted by using the second bearer in the following manner:
  • the serving gateway sends the access request to the second packet gateway by using the second bearer; and after receiving the access request of the UE that is sent by the serving gateway by using the second bearer, the second packet gateway may further return a response message to the serving gateway, to complete a response process.
  • the resource stored on the target server may be transmitted between the serving gateway and the second packet gateway by using the second bearer.
  • a dedicated bearer that is between the serving gateway and the second packet gateway and that corresponds to the UE may be further set up.
  • the second packet gateway may send a dedicated bearer setup request to the serving gateway, and the dedicated bearer setup request is used to set up a first dedicated bearer that is between the serving gateway and the second packet gateway and that corresponds to the UE; after receiving the dedicated bearer setup request, the serving gateway sets up the first dedicated bearer according to the dedicated bearer setup request; and the serving gateway determines a second dedicated bearer between the serving gateway and the UE.
  • the serving gateway may determine the second dedicated bearer between the serving gateway and the UE in the following manner: The serving gateway determines that a dedicated bearer exists between the serving gateway and the UE, and determines the dedicated bearer as the second dedicated bearer; or the serving gateway determines that no dedicated bearer exists between the serving gateway and the UE, and sets up the second dedicated bearer.
  • the resource may be transmitted by using the first dedicated bearer and the second dedicated bearer, to meet transmission requirements of services with different quality of service (Quality of Service, QoS) requirements.
  • QoS Quality of Service
  • the dedicated bearer may be used as the second dedicated bearer, and no other bearers need to be set up, thereby improving bearer resource utilization, and saving a network resource.
  • the first dedicated bearer between the serving gateway and the second packet gateway may be further modified.
  • the second packet gateway may send a dedicated bearer modify request to the serving gateway, and the dedicated bearer modify request is used to request to modify the first dedicated bearer; after receiving the dedicated bearer modify request, the serving gateway modifies the first dedicated bearer according to the dedicated bearer modify request; and the serving gateway determines that a dedicated bearer corresponding to the UE exists between the serving gateway and another packet gateway other than the second packet gateway, and modifies the dedicated bearer between the serving gateway and the another packet gateway other than the second packet gateway.
  • the serving gateway may also modify the dedicated bearer between the serving gateway and the another packet gateway other than the second packet gateway, to ensure communication of a dedicated bearer between the UE and the another packet gateway.
  • the first dedicated bearer between the serving gateway and the second packet gateway may be further deleted.
  • the second packet gateway may send a dedicated bearer delete request to the serving gateway, and the dedicated bearer delete request is used to request to delete the first dedicated bearer; after receiving the dedicated bearer delete request, the serving gateway deletes the first dedicated bearer according to the dedicated bearer delete request; and the serving gateway determines that no dedicated bearer corresponding to the UE exists between the serving gateway and another packet gateway other than the second packet gateway, and deletes the second dedicated bearer. Therefore, when deleting the first dedicated bearer between the serving gateway and the second packet gateway, the serving gateway may also determine whether a dedicated bearer corresponding to the UE exists between the serving gateway and another packet gateway.
  • the serving gateway does not delete the second dedicated bearer between the serving gateway and the UE, to ensure normal communication of a dedicated bearer between the UE and the another packet gateway. If no dedicated bearer exists, the serving gateway may delete the second dedicated bearer, to release a bearer resource.
  • the target server may be a service server, or may be a cache server.
  • the second packet gateway and the target server may be located on a same node.
  • the serving gateway may be an SGW or a serving general packet radio service support node (Serving General Packet Radio Service Support Node, SGSN), and the first packet gateway and the second packet gateway each may be a PGW or a gateway general packet radio service 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 serving gateway.
  • the serving gateway has a function of implementing behavior of the serving gateway in the foregoing method design.
  • the function may be implemented by using hardware, or may be implemented by hardware by executing corresponding software.
  • the hardware or the software includes one or more modules corresponding to the function.
  • a structure of the serving gateway includes a processing unit and a communications unit.
  • the processing unit is configured to support the serving gateway in performing a corresponding function in the foregoing method.
  • the communications unit is configured to support communication between the serving gateway and another device.
  • the serving gateway may further include a storage unit.
  • the storage unit is configured to be coupled to the processing unit, and stores necessary program instructions and data for the serving gateway.
  • the processing unit may be a processor
  • the communications unit may be a communications interface
  • the storage unit may be a memory.
  • an embodiment of the present invention provides a packet gateway.
  • the packet gateway may be referred to as a second packet gateway, and the second packet gateway has a function of implementing behavior of the second packet gateway in the foregoing method design.
  • the function may be implemented by using hardware, or may be implemented by hardware by executing corresponding software.
  • the hardware or the software includes one or more modules corresponding to the function.
  • a structure of the second packet gateway includes a processing unit and a communications unit.
  • the processing unit is configured to support the second packet gateway in performing a corresponding function in the foregoing method.
  • the communications unit is configured to support communication between the second packet gateway and another device.
  • the second packet gateway may further include a storage unit.
  • the storage unit is configured to be coupled to the processing unit, and stores necessary program instructions and data for the second packet gateway.
  • the processing unit may be a processor
  • the communications unit may be a communications interface
  • the storage unit may be a memory.
  • an embodiment of the present invention provides a mobility management network element.
  • the mobility management network element has a function of implementing behavior of the mobility management network element in the foregoing method design.
  • the function may be implemented by using hardware, or may be implemented by hardware by executing corresponding software.
  • the hardware or the software includes one or more modules corresponding to the function.
  • a structure of the mobility management network element includes a processing unit and a communications unit.
  • the processing unit is configured to support the mobility management network element in performing a corresponding function in the foregoing method.
  • the communications unit is configured to support communication between the mobility management network element and another device.
  • the mobility management network element may further include a storage unit.
  • the storage unit is configured to be coupled to the processing unit, and stores necessary program instructions and data for the mobility management network element.
  • the processing unit may be a processor
  • the communications unit may be a communications interface
  • the storage unit may be a memory.
  • an embodiment of the present invention provides a communications system.
  • the system includes the serving gateway and the second packet gateway in the foregoing aspects; or the system includes the serving gateway, the second packet gateway, and the mobility management network element in the foregoing aspects.
  • an embodiment of the present invention provides a computer storage medium, configured to store a computer software instruction to be used by the serving gateway, and the computer storage medium includes a program designed to perform the foregoing aspect.
  • an embodiment of the present invention provides a computer storage medium, configured to store a computer software instruction to be used by the second packet gateway, and the computer storage medium includes a program designed to perform the foregoing aspect.
  • an embodiment of the present invention provides a computer storage medium, configured to store a computer software instruction to be used by the mobility management network element, and the computer storage medium includes a program designed to perform the foregoing aspect.
  • the serving gateway may determine, based on the IP address of the target server that is carried in the IP packet, the second packet gateway corresponding to the target server, determine the second bearer that is between the serving gateway and the second packet gateway and that corresponds to the UE, and transmit the access request of the UE by using the second bearer.
  • the access request is used to request to access the resource stored on the target server. Therefore, the solutions provided in the embodiments of the present invention can avoid route recurvation of an access path, to improve resource access efficiency of the UE.
  • Network architectures and service scenarios described in the embodiments of the present invention are intended to describe the technical solutions in the embodiments of the present invention more clearly, and do not limit the technical solutions provided in the embodiments of the present invention.
  • a person of ordinary skill in the art may know that as the network architectures evolve and a new business scenario emerges, the technical solutions provided in the embodiments of the present invention are also applicable to a similar technical problem.
  • IP Internet Protocol
  • IMS IP Multimedia System
  • PSS Packet Switched Streaming Service
  • the technical solutions described in the present invention may be applied to a Long Term Evolution (Long Term Evolution, LTE) system, or other wireless communications systems using various wireless access technologies, for example, systems using access technologies such as code division multiple access (Code Division Multiple Access, CDMA), frequency division multiple access (Frequency Division Multiple Access, FDMA), time division multiple access (Time Division Multiple Access, TDMA), orthogonal frequency division multiple access (Orthogonal Frequency Division Multiple Access, OFDMA), and single carrier frequency division multiple access (Single Carrier Frequency Division Multiple Access, SC-FDMA).
  • CDMA code division multiple access
  • Frequency Division Multiple Access Frequency Division Multiple Access
  • TDMA time division multiple access
  • OFDMA Orthogonal frequency division multiple access
  • SC-FDMA single carrier frequency division multiple access
  • the technical solutions may also be applied to a subsequent evolved system of the LTE system, for example, a fifth generation (5th Generation, 5G) system.
  • 5G fifth generation
  • an evolved universal terrestrial radio access network (Evolved Universal Terrestrial Radio Access Network, E-UTRAN) is used as a radio access network
  • an evolved packet core (Evolved Packet Core, EPC) is used as a core network.
  • EPC evolved Packet Core
  • the user equipment UE in the embodiments of the present invention may include various handheld devices with a wireless communication function, an in-vehicle device, a wearable device, a computing device or another processing device connected to a wireless modem, various forms of user equipments (User Equipment, UE), a mobile station (Mobile Station, MS), a terminal (terminal), a terminal device (terminal device), and the like.
  • user equipment User Equipment
  • UE User Equipment
  • MS Mobile Station
  • terminal terminal
  • terminal device terminal device
  • a base station (Base Station, BS) in the embodiments of the present invention is an apparatus deployed in the radio access network to provide a wireless communication function for the UE.
  • the base station may include various forms such as a macro base station, a micro base station, a relay station, and an access point.
  • devices with a base station function may have different names.
  • a device with a base station function is referred to as an evolved NodeB (evolved NodeB, eNB or eNodeB); in a third generation (3rd Generation, 3G) network, a device with a base station function is referred to as a NodeB (NodeB).
  • the apparatuses providing the wireless communication function for the UE are collectively referred to as a base station or a BS.
  • FIG. 2 is a schematic diagram of a possible system architecture according to an embodiment of the present invention.
  • UE is connected to an SGW by using a base station, and connected to a PGW 1 by using the SGW.
  • a mobility management entity (Mobility Management Entity, MME) is used as a control plane network element, and is separately connected to the base station and the SGW by using ports.
  • the MME is configured to transmit control plane signaling to the base station and the SGW.
  • the system architecture shown in FIG. 2 further includes other PGWs such as a PGW 2 and a PGW 3. Local servers are usually deployed at the PGW 1, the PGW 2, the PGW 3, and the like.
  • the local server may be a cache server (cache server) or a service server deployed on a same node as a corresponding PGW.
  • FIG. 2 is used only as an example, and when the solutions in the embodiments of the present invention are applied to a 2G or 3G network architecture, a function of the SGW may be completed by an SGSN, and a function of the PGW may be completed by a GGSN.
  • a bearer corresponding to the UE is already set up between the SGW and the PGW 1.
  • the UE may first search a local server corresponding to the PGW 1 to determine whether the local server corresponding to the PGW 1 stores the resource.
  • the UE may obtain the resource from the nearby local server, thereby avoiding network congestion, and increasing a response speed to resource access of a user.
  • the PGW 1 may query whether another local server stores the resource.
  • the PGW 1 may set up a bearer to the PGW 2 corresponding to the another local server, to obtain the resource.
  • a resource obtaining path is roundabout, thereby affecting an access speed of the UE, and wasting a network resource.
  • an embodiment of the present invention provides a resource access method whose main idea is that in a case of a single PDN link, in addition to setting up a bearer to a default packet gateway, a serving gateway may further set up a bearer corresponding to same UE to at least one other packet gateway, to help the UE obtain a resource.
  • the method may include: receiving, by the serving gateway, an IP packet of the UE, where the IP packet carries an IP address of a target server, the target server stores a resource to be accessed by the UE, and a first bearer corresponding to the UE exists between the serving gateway and a first packet gateway; determining, by the serving gateway based on the IP address, a second packet gateway corresponding to the target server; determining a second bearer that is between the serving gateway and the second packet gateway and that corresponds to the UE, for example, the second bearer may be set up or the second bearer may be selected from existing bearers; and sending an access request of the UE by using the second bearer, where the access request is used to request to access the resource stored on the target server.
  • the serving gateway may send the access request of the UE to the second packet gateway by using the second bearer, to access the resource stored on the target server corresponding to the second packet gateway, thereby avoiding route recurvation of an access path, helping increase an access speed of the UE and improve access efficiency of the UE, and saving a network resource.
  • FIG. 3 shows a resource access method 300 according to an embodiment of the present invention. As shown in FIG. 3 , the method 300 includes the following steps.
  • a serving gateway receives an IP packet of UE, where the IP packet carries an IP address of a target server, the target server stores a resource to be accessed by the UE, and a first bearer corresponding to the UE exists between the serving gateway and a first packet gateway.
  • the IP packet may be a Transmission Control Protocol (Transmission Control Protocol, TCP) setup request packet, or the IP packet may be an IP packet in another format.
  • TCP Transmission Control Protocol
  • the UE may further obtain the IP address of the target server. For example, the UE may receive the IP address of the target server that is sent by the first packet gateway.
  • the first packet gateway may send a redirection message (for example, an HTTP redirection message) to the UE, and the redirection message includes the IP address of the target server.
  • the first bearer between the serving gateway and the first packet gateway may be a default bearer that is set up between the UE and the first packet gateway when the UE sets up a PDN link to a core network.
  • the default bearer is set up as the PDN connection is set up, and the default bearer always exists when the PDN link is maintained.
  • the serving gateway determines, based on the IP address, a second packet gateway corresponding to the target server.
  • the serving gateway determines, based on the IP address, the target server and the second packet gateway corresponding to the target server.
  • the second packet gateway may be a packet gateway deployed on a same node as the target server; or the second packet gateway may be a packet gateway located in a same local area network (Local Area Network, LAN) as the target server.
  • LAN Local Area Network
  • a second bearer that is between the serving gateway and the second packet gateway and that corresponds to the UE is determined.
  • the serving gateway may determine the second bearer that is between the serving gateway and the second packet gateway and that corresponds to the UE. For example, the serving gateway may determine the second bearer from at least two existing bearers, and the at least two existing bearers are bearers that are between the serving gateway and at least two packet gateways and that correspond to the UE.
  • the second bearer may be determined in the following manner:
  • the serving gateway sends a bearer setup request to the second packet gateway, where the bearer setup request is used to set up the second bearer; and the second packet gateway sets up the second bearer after receiving the bearer setup request.
  • the bearer setup request may include parameter information of the second bearer, and the second packet gateway may set up the second bearer based on the parameter information.
  • the second packet gateway may further send a bearer setup response message to the serving gateway.
  • the bearer setup request may be an S5 connection setup request message
  • the bearer setup response message may be an S5 connection setup response message.
  • the serving gateway may further receive an instruction message sent by a mobility management network element or the first packet gateway.
  • the instruction message carries an IP address of the second packet gateway, and the instruction message is used to instruct to set up the second bearer between the serving gateway and the second packet gateway.
  • the mobility management network element may be an MME.
  • the instruction message may be an S5 connection setup request message.
  • the mobility management network element or the first packet gateway may further receive the IP address of the target server that is sent by a cache controller.
  • an access request of the UE is transmitted by using the second bearer, where the access request is used to request to access the resource stored on the target server.
  • the access request of the UE may be an HTTP request.
  • the access request of the UE may be transmitted by using the second bearer in the following manner:
  • the serving gateway sends the access request to the second packet gateway by using the second bearer; and after receiving the access request of the UE that is sent by the serving gateway by using the second bearer, the second packet gateway may further return a response message to the serving gateway, to complete a response process.
  • the resource stored on the target server may be transmitted between the serving gateway and the second packet gateway by using the second bearer.
  • the access request may include the IP address of the target server, and the serving gateway may determine or choose, based on the IP address in the access request, to transmit the access request of the UE by using the second bearer.
  • the first bearer may be one of bearers that are set up by the UE by using a base station, the serving gateway, and the first packet gateway and that correspond to the UE.
  • the first bearer may be an S5 bearer between the serving gateway and the first packet gateway. It may be understood that, when the UE sends a request message to the first packet gateway through the serving gateway by using the first bearer, and sends a request message to the second packet gateway through the serving gateway by using the second bearer, a bearer between the UE and the serving gateway may be reused, thereby improving bearer use efficiency.
  • the first bearer and the second bearer correspond to a same PDN link.
  • the serving gateway can be connected to a plurality of packet gateway anchors based on a same PDN link.
  • an SGW can be connected to a plurality of PGW anchors.
  • the second bearer when the first bearer corresponding to the UE exists between the serving gateway and the first packet gateway, the second bearer is determined between the serving gateway and the second packet gateway, so that the UE can access the resource in the target server corresponding to the second packet gateway by using the second bearer, thereby reducing route recurvation of an access path, and improving resource access efficiency.
  • the serving gateway may further receive a dedicated bearer setup request sent by the second packet gateway, where the dedicated bearer setup request is used to request to set up a first dedicated bearer that is between the serving gateway and the second packet gateway and that corresponds to the UE; the serving gateway sets up the first dedicated bearer according to the dedicated bearer setup request; and the serving gateway determines a second dedicated bearer between the serving gateway and the UE.
  • the serving gateway sets up the first dedicated bearer to the second packet gateway, and determines the second dedicated bearer between the serving gateway and the UE, to transmit the resource by using the first dedicated bearer and the second dedicated bearer, and meet transmission requirements of services with different QoS requirements.
  • the default bearer is a data and signaling bearer that meets default QoS.
  • the default bearer is set up during setup of the PDN link.
  • a dedicated bearer is a bearer that is set up based on the PDN link to provide a particular QoS transmission requirement. In other words, the dedicated bearer is set up based on setup of the default bearer.
  • the QoS requirement on the dedicated bearer is higher than the QoS requirement on the default bearer.
  • the first dedicated bearer may be a dedicated bearer that is set up between the serving gateway and the packet gateway after a default bearer is set up between the serving gateway and the packet gateway, to transmit data with a higher QoS requirement. For example, when a resource, such as video data, with a relatively high QoS requirement needs to be transmitted between the serving gateway and the packet gateway, a dedicated bearer used to transmit the video data may be set up between the serving gateway and the packet gateway.
  • the second dedicated bearer between the serving gateway and the UE is a dedicated bearer between the serving gateway and the UE, and the resource is transmitted between the UE and a PGW 2 by using the first dedicated bearer and the second dedicated bearer.
  • the second dedicated bearer may include a dedicated bearer between the serving gateway and the base station and a radio dedicated bearer between the base station and the UE.
  • the determining, by the serving gateway, a second dedicated bearer between the serving gateway and the UE includes: determining, by the serving gateway, that a dedicated bearer exists between the serving gateway and the UE, and determining the dedicated bearer as the second dedicated bearer; or determining, by the serving gateway, that no dedicated bearer exists between the serving gateway and the UE, and setting up the second dedicated bearer.
  • the serving gateway when determining that a dedicated bearer exists between the serving gateway and the UE, determines the dedicated bearer as the second dedicated bearer, and does not need to set up the second dedicated bearer, and the second dedicated bearer can be reused, to save a network resource.
  • an SGW can set up a first dedicated bearer corresponding to UE to only one packet gateway. For example, in the prior art, after the SGW sets up a first dedicated bearer to a PGW 1, the SGW needs to set up a second dedicated bearer to the UE, to set up a dedicated bearer between the UE and the PGW 1. However, in this embodiment of the present invention, when the SGW receives a request for a first dedicated bearer to a PGW 2, the SGW may have set up a first dedicated bearer to another PGW. It indicates that a dedicated bearer has been set up between the SGW and the UE.
  • the SGW does not need to set up a second dedicated bearer, but only needs to determine the dedicated bearer between the SGW and the UE as the second dedicated bearer, and transmits, by using the first dedicated bearer and the second dedicated bearer, a resource to be accessed by the UE.
  • the serving gateway sets up the second dedicated bearer. This can save a network resource, and improve resource access efficiency of the UE.
  • the serving gateway when the serving gateway receives a dedicated bearer setup request sent by the first packet gateway, the second packet gateway in the foregoing dedicated bearer setup method may be replaced with the first packet gateway. Details are not described herein again.
  • the method provided in this embodiment of the present invention may further include: receiving, by the serving gateway, a dedicated bearer modify request sent by the second packet gateway, where the dedicated bearer modify request is used to request to modify the first dedicated bearer; modifying, by the serving gateway, the first dedicated bearer according to the dedicated bearer modify request; and determining, by the serving gateway, that a dedicated bearer corresponding to the UE exists between the serving gateway and another packet gateway other than the second packet gateway, and modifying the dedicated bearer between the serving gateway and the another packet gateway other than the second packet gateway.
  • the serving gateway when modifying the first dedicated bearer between the serving gateway and the second packet gateway, the serving gateway also modifies the dedicated bearer between the serving gateway and the another packet gateway other than the second packet gateway, to ensure communication of a dedicated bearer between the UE and the another packet gateway, and improve resource access efficiency.
  • the serving gateway after receiving the dedicated bearer modify request of the second packet gateway, the serving gateway needs to modify the first dedicated bearer between the serving gateway and the second packet gateway, and modify the second dedicated bearer between the serving gateway and the UE.
  • the serving gateway further needs to determine whether another packet gateway shares the second dedicated bearer with the second packet gateway, or in other words, the serving gateway further needs to determine whether a dedicated bearer corresponding to the UE exists between the serving gateway and another gateway other than the second packet gateway.
  • the serving gateway further needs to modify the dedicated bearer between the serving gateway and the another gateway, to ensure normal communication of a dedicated bearer between the UE and the another packet gateway.
  • the serving gateway when the serving gateway receives a dedicated bearer modify request sent by the first packet gateway, the second packet gateway in the foregoing dedicated bearer modification method may be replaced with the first packet gateway. Details are not described herein again.
  • the method provided in this embodiment of the present invention further includes: receiving, by the serving gateway, a dedicated bearer delete request sent by the second packet gateway, where the dedicated bearer delete request is used to request to delete the first dedicated bearer; deleting, by the serving gateway, the first dedicated bearer according to the dedicated bearer request; and determining, by the serving gateway, that no dedicated bearer corresponding to the UE exists between the serving gateway and another packet gateway other than the second packet gateway, and deleting the second dedicated bearer, to improve resource access efficiency.
  • the serving gateway when deleting the first dedicated bearer between the serving gateway and the second packet gateway, the serving gateway also determines whether a dedicated bearer corresponding to the UE exists between the serving gateway and another packet gateway. When the dedicated bearer exists, the serving gateway does not delete the second dedicated bearer between the serving gateway and the UE, to ensure normal communication of a dedicated bearer between the UE and the another packet gateway.
  • the serving gateway after receiving the dedicated bearer delete request of the second packet gateway, the serving gateway needs to delete the first dedicated bearer between the serving gateway and the second packet gateway, and determine whether to delete the second dedicated bearer between the serving gateway and the UE.
  • the serving gateway further needs to determine whether another packet gateway shares the second dedicated bearer with the second packet gateway, or in other words, the serving gateway further needs to determine whether a dedicated bearer corresponding to the UE exists between the serving gateway and another gateway other than the second packet gateway.
  • the serving gateway does not delete the second dedicated bearer.
  • the serving gateway deletes the second dedicated bearer, to ensure normal communication of a dedicated bearer between the UE and the another packet gateway.
  • the serving gateway when the serving gateway receives a dedicated bearer delete request sent by the first packet gateway, the second packet gateway in the foregoing dedicated bearer deletion method may be replaced with the first packet gateway. Details are not described herein again.
  • a serving gateway when UE has a single PDN link, can set up a connection corresponding to the UE to only one packet gateway, and when a resource to be accessed by the UE is located in a local server corresponding to another local packet gateway, the serving gateway is not supported to set up a bearer corresponding to the UE to the another packet gateway while maintaining the same PDN link, thereby affecting resource obtaining efficiency of the UE.
  • a second bearer between the serving gateway and at least one other packet gateway may be further determined, so that the access request of the UE can be transmitted by using the second bearer, to obtain the resource stored on the target server corresponding to the second packet gateway. Therefore, the solution in this embodiment of the present invention can avoid route recurvation of an access path, and help improve resource access efficiency.
  • FIG. 4 shows another resource access method according to an embodiment of the present invention.
  • the serving gateway may be an SGW
  • the first packet gateway may be a PGW 1
  • a first cache server may be a cache server corresponding to the PGW 1
  • a second cache server may be the target server; in other words, the second cache server stores a resource to be accessed by UE.
  • a PGW 2 may be the second packet gateway, or in other words, the PGW 2 is a packet gateway corresponding to the second cache server.
  • a cache controller may be configured to schedule and control cache servers in a distributed cache system.
  • the second bearer may be an S5 bearer.
  • the resource access method may be as follows:
  • the UE sets up a PDN link to the PGW 1.
  • An S5 bearer is set up between the SGW and the PGW 1.
  • the UE sets up a first TCP connection to the first cache server by using the PGW 1.
  • the UE sends a first HTTP request packet to the first cache server by using the PGW 1.
  • the first HTTP request packet is used to request to access the resource.
  • the first cache server queries for a local cache, and sends a query message to the cache controller if no local cache is hit.
  • the cache controller performs cache hit query in a distributed cache range after receiving the query message, and feeds back an IP address of the second cache server to the first cache server after determining that the resource is stored on the second cache server.
  • the first cache server notifies the UE of the IP address of the second cache server by using an HTTP redirection message, so that the UE initiates a second HTTP request packet to the second cache server based on the IP address of the second cache server; and the first cache server sends a notification message to the cache controller, where the notification message is used to notify that the first cache server is to send the HTTP redirection message.
  • the cache controller after receiving the notification message sent by the first cache server, notifies an MME of the IP address of the second cache server; or the cache controller determines an IP address of the PGW 2 based on the IP address of the second cache, and notifies an MME of the IP address of the second packet gateway.
  • the MME obtains the IP address of the PGW 2, or the MME determines the IP address of the PGW 2 based on the IP address of the second cache server, and sends an S5 connection setup instruction message to the SGW.
  • the S5 connection setup instruction message includes the IP address of the PGW 2.
  • the serving gateway determines the IP address of the second packet gateway by using the instruction message sent by the MME, and the serving gateway sets up the second bearer in advance as instructed by the MME, thereby reducing time used by the UE to access the resource.
  • the SGW determines the IP address of the PGW 2, and sends an S5 bearer connection setup request message to the PGW 2.
  • the S5 bearer setup request message includes parameter information of an S5 bearer.
  • the PGW 2 sets up the S5 bearer, and returns an S5 connection setup response message to the SGW.
  • the SGW receives a second TCP setup request packet sent by the UE, where the second TCP setup request packet includes the IP address of the second cache server; and the SGW determines the IP address of the PGW 2 based on the IP address of the second cache server, performs searching to determine whether a corresponding S5 bearer exists locally, and if the corresponding S5 bearer exists, sets up a TCP connection to the second cache server by using the S5 bearer, or if no corresponding S5 bearer exists, sets up the corresponding S5 bearer and then sets up a TCP connection to the second cache server.
  • the SGW receives the second HTTP request packet sent by the UE.
  • the second HTTP request packet is used to request to access the resource in the second cache server.
  • the SGW transmits the resource to the UE by using the S5 bearer between the SGW and the PGW 2.
  • FIG. 5 shows still another resource access method according to an embodiment of the present invention.
  • content that is in the method shown in FIG. 5 and that is the same as or similar to content in the method shown in FIG. 4 , refer to the detailed descriptions related to FIG. 4 . Details are not described herein again.
  • the resource access method may be as follows:
  • S501 to S506 in FIG. 5 are the same as or similar to S401 to S406 in FIG. 4 . Refer to the detailed descriptions in corresponding parts in FIG. 4 . Details are not described herein again.
  • the cache controller after receiving the notification message sent by the first cache server, notifies the PGW 1 of the IP address of the second cache server; or the cache controller determines an IP address of the PGW 2 based on the IP address of the second cache, and notifies the PGW 1 of the IP address of the second packet gateway.
  • the PGW 1 determines the IP address of the PGW 2 based on the IP address of the second cache server, and sends an S5 connection setup instruction message to the SGW.
  • the S5 connection setup instruction message includes the IP address of the PGW 2.
  • the serving gateway determines the IP address of the second packet gateway by using the instruction message sent by the first packet gateway, and sets up the second bearer in advance as instructed by the first packet gateway, thereby reducing time used by the UE to access the resource.
  • the SGW After receiving the S5 connection setup instruction message of the PGW 1, the SGW determines the IP address of the PGW 2, and sends an S5 bearer connection setup request message to the PGW 2.
  • the PGW 2 sets up an S5 bearer, and returns an S5 connection setup response message to the SGW.
  • the SGW receives a second TCP setup request packet sent by the UE, where the second TCP setup request packet includes the IP address of the second cache server; and the SGW performs searching, based on the IP address of the second cache server, to determine whether a corresponding S5 bearer exists locally, and if the corresponding S5 bearer exists, sets up a TCP connection to the second cache server by using the S5 bearer, or if no corresponding S5 bearer exists, sets up the corresponding S5 bearer and then sets up a TCP connection to the second cache server.
  • the SGW receives the second HTTP request packet sent by the UE, where the second HTTP request packet is used to request to access the resource in the second cache server; and the SGW transmits the resource to the UE by using the S5 bearer between the SGW and the PGW 2.
  • FIG. 6 shows yet another resource access method according to an embodiment of the present invention.
  • content that is in the method shown in FIG. 6 and that is the same as or similar to content in the method shown in FIG. 4 or FIG. 5 , refer to the detailed descriptions related to FIG. 4 or FIG. 5 . Details are not described herein again.
  • the resource access method may be as follows:
  • S601 to S606 in FIG. 6 are the same as or similar to S401 to S406 in FIG. 4 . Refer to the detailed descriptions in corresponding parts in FIG. 4 . Details are not described herein again.
  • the SGW receives a second TCP setup request packet sent by the UE, where the second TCP setup request packet includes the IP address of the second cache server; and the SGW determines an IP address of the PGW 2 based on the IP address of the second cache server, performs searching to whether an S5 bearer corresponding to the PGW 2 exists locally, and if the corresponding S5 bearer exists, sets up a TCP connection to the second cache server by using the S5 bearer, or if no corresponding S5 bearer exists, sends an S5 bearer connection setup request message to the PGW 2.
  • the serving gateway determines the IP address of the second packet gateway by parsing the IP packet sent by the UE, and directly sets up the second bearer without control plane signaling, thereby saving a network resource.
  • the PGW 2 sets up an S5 bearer, and returns an S5 bearer connection setup response message to the SGW.
  • the SGW sets up a TCP connection by using the S5 bearer between the SGW and the PGW 2.
  • the SGW receives the second HTTP request packet sent by the UE, where the second HTTP request packet is used to request to access the resource in the second cache server; and the SGW transmits the resource to the UE by using the S5 bearer between the SGW and the PGW 2.
  • the UE may further set up a dedicated bearer to the second packet gateway, and access a resource by using the dedicated bearer.
  • Dedicated bearer setup, modification, and deletion methods are described below with reference to FIG. 7 to FIG. 9 .
  • a default bearer for example, an S5 bearer
  • a default bearer for example, an S5 bearer
  • FIG. 7 is a schematic communication diagram of a dedicated bearer setup method according to an embodiment of the present invention. As shown in FIG. 7 , the dedicated bearer setup method includes the following parts:
  • an SGW receives a dedicated bearer setup request sent by a PGW 2.
  • the dedicated bearer setup request is used to request to set up a first dedicated bearer between the SGW and the PGW 2.
  • the SGW determines whether a dedicated bearer exists between the SGW and UE.
  • the SGW determines the dedicated bearer as a second dedicated bearer between the SGW and the UE, and sets up the first dedicated bearer between the SGW and the PGW 2. After setting up the first dedicated bearer, the SGW sends a dedicated bearer setup response message to the PGW 2.
  • the dedicated bearer setup response message includes parameter information (for example, a bearer ID identifier) of the first dedicated bearer and the second dedicated bearer.
  • the SGW sets up the first dedicated bearer between the SGW and the PGW 2, and sets up a second dedicated bearer between the SGW and the UE. After setting up the first dedicated bearer, the SGW sends a dedicated bearer setup response message to the PGW 2.
  • the serving gateway determines whether a dedicated bearer exists between the serving gateway and the UE, and when the dedicated bearer exists, determines the dedicated bearer as the second dedicated bearer between the serving gateway and the UE, sets up only the first dedicated bearer between the serving gateway and the second packet gateway, and transmits, by using the first dedicated bearer and a second resource, a resource to be accessed by the UE, thereby saving a network resource, and improving resource access efficiency of the UE.
  • FIG. 8 is a schematic communication diagram of a dedicated bearer modification method. As shown in FIG. 8 , the dedicated bearer modification method includes the following parts:
  • an SGW receives a dedicated bearer modify request sent by a PGW 2.
  • the dedicated bearer modify request is used to request to modify a dedicated bearer between the SGW and the PGW 2.
  • the SGW determines whether a dedicated bearer corresponding to UE exists between the SGW and another PGW other than the PGW 2.
  • the SGW modifies the dedicated bearer between the SGW and the PGW 2, and modifies the dedicated bearer between the SGW and the another packet gateway and a dedicated bearer between the SGW and the UE.
  • the SGW modifies the dedicated bearer between the SGW and the PGW 2 and a dedicated bearer between the SGW and the UE.
  • the serving gateway determines whether a dedicated bearer exists between the serving gateway and the another packet gateway, and when the dedicated bearer exists between the serving gateway and the another packet gateway, not only modifies the dedicated bearer between the second packet gateway and the serving gateway, but also modifies the dedicated bearer between the another packet gateway and the serving gateway, to ensure communication between the serving gateway and the another packet gateway, thereby improving resource access efficiency.
  • FIG. 9 is a schematic communication diagram of a dedicated bearer deletion method. As shown in FIG. 9 , the dedicated bearer deletion method includes the following parts:
  • an SGW receives a dedicated bearer delete request sent by a PGW 2.
  • the SGW determines whether a first dedicated bearer corresponding to UE exists between the SGW and another PGW other than the PGW 2.
  • the SGW when a dedicated bearer exists between the SGW and the another PGW, the SGW deletes a dedicated bearer between the SGW and the PGW 2, but does not delete a second dedicated bearer between the SGW and the UE.
  • the SGW when no dedicated bearer exists between the SGW and the another PGW, the SGW deletes a dedicated bearer between the SGW and the PGW 2, and deletes a second dedicated bearer between the SGW and the UE.
  • the serving gateway determines whether the dedicated bearer corresponding to the UE exists between the serving gateway and the another packet gateway, and when the dedicated bearer exists between the serving gateway and the another packet gateway, deletes only the dedicated bearer between the second packet gateway and the serving gateway, and retains the second dedicated bearer between the serving gateway and the UE and the dedicated bearer between the serving gateway and the another packet gateway, thereby ensuring communication between the serving gateway and the another packet gateway, and improving resource access efficiency.
  • the serving gateway may be an SGW or an SGSN, and the packet gateway may be a PGW or a GGSN.
  • the serving gateway is an SGW, and the packet gateway is a PGW.
  • network elements such as the serving gateway, the second packet gateway, and the mobility management network element include corresponding hardware structures and/or software modules for performing the functions.
  • network elements such as the serving gateway, the second packet gateway, and the mobility management network element include corresponding hardware structures and/or software modules for performing the functions.
  • a person of ordinary skill in the art should be easily aware that, the units and algorithm steps in the examples described with reference to the embodiments disclosed in this specification may be implemented by hardware or a combination of hardware and computer software. Whether a particular function is performed by hardware or computer software driving hardware depends on particular applications and design constraint conditions of the technical solutions. A person skilled in the art may use different methods to implement the described functions for each particular application, but it should not be considered that the implementation goes beyond the scope of the present invention.
  • the serving gateway, the packet gateway (for example, the second packet gateway), and the like may be divided into function units based on the foregoing method examples.
  • each function unit may be obtained through division based on each function, or two or more functions may be integrated into one processing unit.
  • the integrated unit may be implemented in a form of hardware, or may be implemented in a form of a software function unit.
  • the unit division in the embodiments of the present invention is an example, and is only logical function division. There may be another division manner in actual implementation.
  • FIG. 10A is a possible schematic structural diagram of the serving gateway in the foregoing embodiments.
  • a serving gateway 1000 includes a processing unit 1002 and a communications unit 1003.
  • the processing unit 1002 is configured to control and manage an action of the serving gateway.
  • the processing unit 1002 is configured to support the serving gateway in performing processes 310 to 340 in FIG. 3 , processes 401, 409, 411, and 412 in FIG. 4 , processes 501, 509, 511, and 512 in FIG. 5 , processes 601, 607, 608, 609, and 610 in FIG. 6 , processes 702 to 704 in FIG. 7 , processes 802 to 804 in FIG. 8 , processes 902 to 904 in FIG.
  • the communications unit 1003 is configured to support the serving gateway in communicating with another network entity, for example, communicating with the base station, the MME, the PGW, and the like shown in FIG. 2 .
  • the serving gateway may further include a storage unit 1001, configured to store program code and data of the serving gateway.
  • the processing unit 1002 may be a processor or a controller, for example, may be a central processing unit (Central Processing Unit, CPU), a general-purpose processor, a digital signal processor (Digital Signal Processor, DSP), an application-specific integrated circuit (Application-Specific Integrated Circuit, ASIC), a field programmable gate array (Field Programmable Gate Array, FPGA) or another programmable logic device, a transistor logic device, a hardware component, or any combination thereof.
  • the processing unit may implement or execute various example logical blocks, modules, and circuits that are described with reference to the content disclosed in the present invention.
  • the processor may alternatively be a combination for implementing a computing function, for example, a combination of one or more microprocessors or a combination of a DSP and a microprocessor.
  • the communications unit 1003 may be a communications interface, a transceiver, a transceiver circuit, or the like.
  • the communications interface is a general name.
  • the communications interface may include a plurality of interfaces, for example, may include an interface between the serving gateway and a packet gateway, an interface between the serving gateway and a mobility management network element, and/or another interface.
  • the storage unit 1001 may be a memory.
  • the serving gateway in this embodiment of the present invention may be a serving gateway shown in FIG. 10B .
  • the serving gateway 1010 includes a processor 1012, a communications interface 1013, and a memory 1011.
  • the serving gateway 1010 may further include a bus 1014.
  • the communications interface 1013, the processor 1012, and the memory 1011 may be connected to each other by using the bus 1014.
  • the bus 1014 may be a peripheral component interconnect (Peripheral Component Interconnect, PCI for short) bus, an extended industry standard architecture (Extended Industry Standard Architecture, EISA for short) bus, or the like.
  • PCI peripheral component interconnect
  • EISA Extended Industry Standard Architecture
  • the bus 1014 may be classified into an address bus, a data bus, a control bus, or the like. For ease of indication, the bus is indicated by using only one bold line in FIG. 10B . However, it does not indicate that there is only one bus or only one type of bus.
  • FIG. 11A is a possible schematic structural diagram of the packet gateway in the foregoing embodiments.
  • a packet gateway 1100 includes a processing unit 1102 and a communications unit 1103.
  • the processing unit 1102 is configured to control and manage an action of the packet gateway.
  • the processing unit 1102 is configured to support the packet gateway in performing processes 330 and 340 in FIG. 3 , processes 410 and 412 in FIG. 4 , processes 510 and 512 in FIG. 5 , processes 608 and 610 in FIG. 6 , a process 701 in FIG. 7 , a process 801 in FIG. 8 , a process 901 in FIG. 9 , and/or another process used for the technology described in this specification.
  • the communications unit 1103 is configured to support the packet gateway in communicating with another network entity, for example, communicating with the base station, the MME, the PGW, and the like shown in FIG. 2 .
  • the packet gateway may further include a storage unit 1101, configured to store program code and data of the packet gateway.
  • the processing unit 1102 may be a processor or a controller, for example, may be a central processing unit (Central Processing Unit, CPU), a general-purpose processor, a digital signal processor (Digital Signal Processor, DSP), an application-specific integrated circuit (Application-Specific Integrated Circuit, ASIC), a field programmable gate array (Field Programmable Gate Array, FPGA) or another programmable logic device, a transistor logic device, a hardware component, or any combination thereof.
  • the processing unit may implement or execute various example logical blocks, modules, and circuits that are described with reference to the content disclosed in the present invention.
  • the processor may alternatively be a combination for implementing a computing function, for example, a combination of one or more microprocessors or a combination of a DSP and a microprocessor.
  • the communications unit 1103 may be a communications interface, a transceiver, a transceiver circuit, or the like.
  • the communications interface is a general name.
  • the communications interface may include a plurality of interfaces, for example, may include an interface between the packet gateway and a serving gateway, and/or another interface.
  • the storage unit 1101 may be a memory.
  • the packet gateway in this embodiment of the present invention may be a packet gateway shown in FIG. 11B .
  • the packet gateway 1110 includes a processor 1112, a communications interface 1113, and a memory 1111.
  • the packet gateway 1110 may further include a bus 1114.
  • the communications interface 1113, the processor 1112, and the memory 1111 may be connected to each other by using the bus 1114.
  • the bus 1114 may be a peripheral component interconnect (Peripheral Component Interconnect, PCI for short) bus, an extended industry standard architecture (Extended Industry Standard Architecture, EISA for short) bus, or the like.
  • PCI peripheral component interconnect
  • EISA Extended Industry Standard Architecture
  • the bus 1114 may be classified into an address bus, a data bus, a control bus, or the like. For ease of indication, the bus is indicated by using only one bold line in FIG. 11B . However, it does not indicate that there is only one bus or only one type of bus.
  • FIG. 12A is a possible schematic structural diagram of the mobility management network element in the foregoing embodiments.
  • a mobility management network element 1200 includes a processing unit 1202 and a communications unit 1203.
  • the mobility management network element 1200 may further include a storage unit 1201.
  • the storage unit 1201 is configured to store a program.
  • the communications unit 1203 is configured to communicate with another device.
  • the processing unit 1202 is configured to execute the program in the storage unit 1201.
  • the processing unit is configured to perform steps performed by a mobility management network element in FIG. 1 to FIG. 9 .
  • repeated descriptions are appropriately omitted.
  • the mobility management network element in this embodiment of the present invention may be a mobility management network element shown in FIG. 12B .
  • the mobility management network element 1210 includes a processor 1212, a communications interface 1213, a memory 1211, and a bus 1214. For brevity, repeated descriptions are appropriately omitted.
  • the processor configured to perform a function of the serving gateway, the packet gateway, or the mobility management network element in the foregoing embodiment of the present invention may be a central processing unit (Central Processing Unit, CPU), a general-purpose processor, a digital signal processor (Digital Signal Processor, DSP), an application-specific integrated circuit (Application-Specific Integrated Circuit, ASIC), a field programmable gate array (Field Programmable Gate Array, FPGA) or another programmable logic device, a transistor logic device, a hardware component, or any combination thereof.
  • the processor may implement or execute various example logical blocks, modules, and circuits that are described with reference to the content disclosed in the embodiments of the present invention.
  • the processor may alternatively be a combination for implementing a computing function, for example, a combination of one or more microprocessors or a combination of a DSP and a microprocessor.
  • the methods or algorithm steps described with reference to the content disclosed in the embodiments of the present invention may be implemented by hardware, or may be implemented by a processor by executing a software instruction.
  • the software instruction may include a corresponding software module.
  • the software module may be stored in a random access memory (Random Access Memory, RAM), a flash memory, a read-only memory (Read Only Memory, ROM), an erasable programmable read-only memory (Erasable Programmable ROM, EPROM), an electrically erasable programmable read-only memory (Electrically EPROM, EEPROM), a register, a hard disk, a removable hard disk, a compact disc read-only memory (CD-ROM), or a storage medium in any other form well known in the art.
  • RAM Random Access Memory
  • ROM read-only memory
  • EPROM erasable programmable read-only memory
  • Electrically erasable programmable read-only memory Electrically erasable programmable read-only memory
  • EEPROM electrical
  • An example storage medium is coupled to the processor, so that the processor can read information from the storage medium, and can write information into the storage medium.
  • the storage medium may be a part of the processor.
  • the processor and the storage medium may be located in an ASIC.
  • the ASIC may be located in a gateway device or a mobility management network element.
  • the processor and the storage medium may exist in the gateway device or the mobility management network element as discrete components.
  • the functions described in the embodiments of the present invention may be implemented by using hardware, software, firmware, or any combination thereof.
  • these functions may be stored in a computer-readable medium or transmitted as one or more instructions or code in the computer-readable medium.
  • the computer-readable medium includes a computer storage medium and a communications medium.
  • the communications medium includes any medium that enables a computer program to be transmitted from one place to another.
  • the storage medium may be any available medium accessible to a general-purpose or dedicated computer.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
EP16901303.4A 2016-05-12 2016-05-12 Ressourcenzugriffsverfahren, -vorrichtung und -system Withdrawn EP3451785A4 (de)

Applications Claiming Priority (1)

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

Publications (2)

Publication Number Publication Date
EP3451785A1 true EP3451785A1 (de) 2019-03-06
EP3451785A4 EP3451785A4 (de) 2019-05-15

Family

ID=60266863

Family Applications (1)

Application Number Title Priority Date Filing Date
EP16901303.4A Withdrawn EP3451785A4 (de) 2016-05-12 2016-05-12 Ressourcenzugriffsverfahren, -vorrichtung und -system

Country Status (3)

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

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112312426B (zh) * 2019-07-31 2023-07-21 中国移动通信集团吉林有限公司 核心网网关的选择方法、移动性管理实体和网关设备
CN115134937B (zh) * 2021-03-25 2024-07-26 中国移动通信集团河南有限公司 专用承载建立方法、网关设备和计算机可读存储介质

Family Cites Families (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101232724B (zh) * 2008-01-15 2013-08-07 中兴通讯股份有限公司 一种ip多媒体子系统中终呼的实现方法
CN101552978B (zh) * 2008-03-31 2011-04-13 华为技术有限公司 实现路由优化的方法、系统及装置
JP5538544B2 (ja) * 2009-08-25 2014-07-02 テレフオンアクチーボラゲット エル エム エリクソン（パブル） モビリティアンカーの移転
CN102036325B (zh) * 2009-09-28 2013-06-05 华为终端有限公司 一种建立或修改本地ip接入承载的方法和设备
JPWO2011132662A1 (ja) * 2010-04-20 2013-07-18 日本電気株式会社 配信システム、配信制御装置及び配信制御方法
US8848516B2 (en) * 2010-09-15 2014-09-30 Telefonaktiebolaget L M Ericsson (Publ) Methods and apparatus for relocating and restoring connections through a failed serving gateway and traffic offloading
CN103841607A (zh) * 2012-11-21 2014-06-04 中兴通讯股份有限公司 一种网关重定位的方法、移动管理实体及宿主基站
WO2014082232A1 (zh) * 2012-11-28 2014-06-05 华为技术有限公司 一种移动网络通信方法、通信装置及通信系统
EP2844022B1 (de) * 2013-08-29 2019-07-31 Alcatel Lucent Verfahren und System zur Weiterleitung von Inhaltausgabenetzwerkverkehr mit einem Schatten-Paketdatennetzwerk-Gateway
CN110430607B (zh) * 2013-12-30 2021-04-09 华为技术有限公司 业务连续性的处理方法和设备

Also Published As

Publication number Publication date
EP3451785A4 (de) 2019-05-15
CN109076625A (zh) 2018-12-21
WO2017193348A1 (zh) 2017-11-16

Similar Documents

Publication Publication Date Title
US11172521B2 (en) System and method for management of session information in data communication network
US11558783B2 (en) Communication method, network element, terminal apparatus, and system
EP3720048A1 (de) Erfassung von benutzerrichtlinien
EP3703339B1 (de) Verfahren, vorrichtung und system zur sitzungsverarbeitung
US10798620B2 (en) Communication method in handover process and apparatus
EP3422752B1 (de) Verfahren und vorrichtung zur verarbeitung von datenpaketen
US20190090169A1 (en) Communication method in handover process and apparatus
US20180242188A1 (en) Quality of service control method, device, and system
US10827348B2 (en) Data transmission method and apparatus
EP3687259B1 (de) Kommunikationsverfahren und -vorrichtung
KR102390546B1 (ko) 사용자 평면 링크 설립 방법, 기지국 및 이동성 관리 장치
KR20200097336A (ko) 세션 확립을 위한 방법 및 장치
KR102121733B1 (ko) 단말장치 및 기지국장치와, QoS 제어방법
US11343724B2 (en) User equipment context management method, apparatus, and device
EP3451785A1 (de) Ressourcenzugriffsverfahren, -vorrichtung und -system
US20190082482A1 (en) Resource access method, apparatus, and system
CN110677925B (zh) 一种无线承载处理的方法及终端设备
US10616110B2 (en) Packet transmission method, apparatus, and system
KR102121730B1 (ko) 기지국장치와 QoS 제어방법
WO2017193346A1 (zh) 访问资源的方法、装置和系统
EP3162149B1 (de) Planung von volumenfristen
CN115413063A (zh) 建立连接的方法、装置和系统

Legal Events

Date Code Title Description
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE INTERNATIONAL PUBLICATION HAS BEEN MADE

PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE

17P Request for examination filed

Effective date: 20181130

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

AX Request for extension of the european patent

Extension state: BA ME

A4 Supplementary search report drawn up and despatched

Effective date: 20190411

RIC1 Information provided on ipc code assigned before grant

Ipc: H04L 29/08 20060101ALI20190405BHEP

Ipc: H04W 76/22 20180101AFI20190405BHEP

Ipc: H04W 36/12 20090101ALI20190405BHEP

Ipc: H04W 92/24 20090101ALN20190405BHEP

Ipc: H04W 88/16 20090101ALN20190405BHEP

DAV Request for validation of the european patent (deleted)
DAX Request for extension of the european patent (deleted)
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: EXAMINATION IS IN PROGRESS

17Q First examination report despatched

Effective date: 20200331

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: EXAMINATION IS IN PROGRESS

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION IS DEEMED TO BE WITHDRAWN

18D Application deemed to be withdrawn

Effective date: 20210209