EP3322256B1 - Method, device and system for processing user data - Google Patents

Method, device and system for processing user data Download PDF

Info

Publication number
EP3322256B1
EP3322256B1 EP15902513.9A EP15902513A EP3322256B1 EP 3322256 B1 EP3322256 B1 EP 3322256B1 EP 15902513 A EP15902513 A EP 15902513A EP 3322256 B1 EP3322256 B1 EP 3322256B1
Authority
EP
European Patent Office
Prior art keywords
unit
service
user data
information
data
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.)
Active
Application number
EP15902513.9A
Other languages
German (de)
English (en)
French (fr)
Other versions
EP3322256A4 (en
EP3322256A1 (en
Inventor
Jin Zhang
Han ZHOU
Zhongping 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 EP3322256A4 publication Critical patent/EP3322256A4/en
Publication of EP3322256A1 publication Critical patent/EP3322256A1/en
Application granted granted Critical
Publication of EP3322256B1 publication Critical patent/EP3322256B1/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
    • H04L63/0876—Network architectures or network communication protocols for network security for authentication of entities based on the identity of the terminal or configuration, e.g. MAC address, hardware or software configuration or device fingerprint
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/09—Mapping addresses
    • H04L61/10—Mapping addresses of different types
    • H04L61/106—Mapping addresses of different types across networks, e.g. mapping telephone numbers to data network addresses
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/10—Network architectures or network communication protocols for network security for controlling access to devices or network resources
    • H04L63/102—Entity profiles
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/12—Setup of transport tunnels
    • 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
    • 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
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0019—Control or signalling for completing the hand-off for data sessions of end-to-end connection adapted for mobile IP [MIP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/15—Setup of multiple wireless link connections

Definitions

  • the present invention relates to the field of communications technologies, and in particular, to a user data processing method, apparatus and a system.
  • a serving general packet radio service support node (Serving GPRS Supporting Node, SGSN) in a core network (Core Network, CN) is configured to implement functions such as routing and forwarding, mobility management, session management, and user information storage in a general packet radio service (General Packet Radio Service, GPRS) or Universal Mobile Telecommunications System (Universal Mobile Terrestrial Service, UMTS) network.
  • GPRS General Packet Radio Service
  • Universal Mobile Terrestrial Service Universal Mobile Terrestrial Service
  • UMTS Universal Mobile Terrestrial Service
  • a gateway general packet radio service support node (Gateway GPRS Supporting Node, GGSN) is configured to connect to an external packet data network (Packet Data Network, PDN).
  • PDN Packet Data Network
  • UE user equipment
  • UTRAN Universal Terrestrial Radio Access Network
  • GSM/EDGE Radio Access Network GSM/EDGE Radio Access Network
  • GERAN GSM/EDGE Radio Access Network
  • the UE When the UE needs to use a user service, the UE sends a request to the SGSN to establish a Packet Data Protocol context (Packet Data Protocol Context, PDP context).
  • PDP context Packet Data Protocol Context
  • the SGSN finds an associated GGSN according to an access point name (Access Point Name, APN) in the user subscription information, and requests the GGSN to add a PDP context.
  • APN Access Point Name
  • the GGSN After receiving the request for adding a PDP context, the GGSN returns to the SGSN an IP address and a GPRS Tunneling Protocol (GPRS Tunnel Protocol, GTP) tunnel endpoint identifier (Tunnel End Identifier, TEID) that are assigned to the UE.
  • GTP GPRS Tunneling Protocol
  • Tunnel End Identifier, TEID tunnel endpoint identifier
  • uplink data of the UE is forwarded by the GGSN to a corresponding PDN.
  • Downlink data from the external PDN is transmitted by the GGSN to an SGSN of the UE through a corresponding GTP tunnel according to the IP address of the UE, and is then sent to the UE by the SGSN by using the GERAN/UTRAN.
  • an evolved network developed at the 3GPP specification release (Release, R) 8 stage includes an evolved universal terrestrial radio access network (Evolved Universal Terrestrial Radio Access Network, E-UTRAN), which may be also considered as a type of a radio access network RAN and is configured to implement a wireless function related to an evolved network.
  • E-UTRAN evolved Universal Terrestrial Radio Access Network
  • a mobility management entity MME is responsible for mobility management of a control plane, including management on a user context and mobile state, allocation of a temporary mobile subscriber identity (Temporary Mobile Subscriber Identity, TMSI), or the like.
  • a serving gateway entity is a user plane anchor between 3GPP radio access networks (such as an E-UTRAN, a UTRAN, and a GERAN).
  • a packet data network gateway entity (Packet Data Network Gateway, P-GW) is a user plane anchor between a 3GPP radio access network and a non-3GPP radio access network, and provides an interface with an external PDN.
  • UE is first attached to the MME; after the MME completes UE authentication according to user subscription data and authentication information that are obtained from a home subscriber server (Home Subscriber Server, HSS), the UE or the MME initiates a procedure of establishing a bearer used to transmit user data.
  • the MME instructs the S-GW to establish the bearer for the UE, and the S-GW establishes for the UE a bearer from the E-UTRAN to the P-GW used to transmit user data.
  • the P-GW forwards, to the UE by using the established bearer, downlink data from the external PDN, and forwards, to the PDN, uplink data from the UE.
  • the UE may alternatively access the MME by using the UTRAN or the GERAN, and an SGSN, and may establish a GTP tunnel connection to the S-GW by using the UTRAN/GERAN and the SGSN.
  • the S-GW converts the GTP tunnel into a corresponding P-GW-connected bearer that is used to transmit user data.
  • the UTRAN may alternatively establish a GTP tunnel directly connected to the S-GW.
  • the MME is a network element that processes only control plane signaling.
  • the S-GW and the P-GW may be combined into one network element, generally collectively referred to as a gateway.
  • the S-GW, the P-GW, and the GGSN may be collectively referred to as a gateway which is used as an interface between a radio access network and an external PDN to implement user data forwarding.
  • a gateway is divided into a user plane gateway (User Plane Gateway, GW-U) and a control plane gateway (Control Plane Gateway, GW-C).
  • GW-U User Plane Gateway
  • GW-C Control Plane Gateway
  • UE accesses a wireless communications system shown in FIG. 3 by using a radio access network.
  • the radio access network is connected to an MME/SGSN and a GW-U.
  • a GW-C is connected to the MME/SGSN and may be configured to perform session management, IP address assignment, and the like.
  • the GW-U is configured to forward user data.
  • the GW-U forwards, to a PDN, user data from the radio access network, and forwards, to the radio access network, user data from the PDN.
  • the GW-C may be referred to as a control plane gateway (Control Plane Gateway), or may be referred to as a gateway controller (Gateway Controller), a control node (Control Node), or a control gateway (Control Gateway).
  • Control Plane Gateway Control Plane Gateway
  • Gateway controller Gateway controller
  • Control Node Control Node
  • Control Gateway Control Gateway
  • the GW-U may alternatively be referred to as a packet data forwarding gateway (Packet Data Forwarding Gateway), a routing forwarding node (Routing Forwarding Node), or a switch node (Switch Node).
  • Packet Data Forwarding Gateway Packet Data Forwarding Gateway
  • Routing Forwarding Node routing forwarding node
  • Switch Node switch node
  • the GW-U needs to process user data according to a control message of the GW-C. This lacks flexibility.
  • WO 2015/096005 A1 discloses a message processing method and a gateway.
  • the gateway includes: a control plane module configured to implement a control plane function of the gateway and at least one user plane module configured to implement a user plane function of the gateway, where the control plane module is connected to the at least one user plane module by using an interface; the control plane module is configured to generate a service control rule, and deliver the service control rule to the user plane module, where the service control rule is used to indicate a data operation that needs to be executed by the user plane module of the gateway; and the user plane module is configured to forward or process data according to the received service control rule.
  • the present invention provides a user data processing method according to claim 1, a gateway user plane according to claim 12, and a system according to claim 13, so as to provide a solution in which a GW-U flexibly processes user data.
  • Possible implementation manners are disclosed in the dependent claims. In the following, embodiments not covered by the claims shall be considered as examples helpful for understanding the invention.
  • an embodiment of the present invention provides a user data processing method, including:
  • an embodiment of the present invention provides a communications system, including a gateway user plane GW-U and a gateway control plane GW-C, where the GW-C is configured to send a first request message to the GW-U, where the first request message is used to request to add a service module processing user data to the GW-U;
  • the service module processing the user data includes a session module and at least one of a bearer module, a service flow module, or a content module;
  • the session module is configured to perform session processing, the bearer module is configured to perform bearer processing, the service flow module is configured to perform service flow processing, and the content module is configured to perform content processing;
  • the GW-U comprises an interface management unit which is configured to perform the method of the first aspect.
  • the GW-U after receiving the user data, determines the service unit configured to process the user data, and processes the user data by using the service unit determined by the GW-U, improving processing flexibility of the GW-U.
  • the GW-C performs a configuration operation, such as adding, modification, and deletion, on the service unit in the GW-U, so that service units in the GW-U can be flexibly combined. Different from that in an existing network, this can avoid frequently changing the GW-U, and the GW-U does not always need to be modified each time service function logic is added. In this way, user data can be flexibly processed according to a service requirement of the user data. For example, a service unit can be flexibly added or removed in a process of processing the user data, so that the GW-U is able to adapt to a future new service type of user data.
  • the GW-U can independently process the user data without interacting with the GW-C. This decreases coupling between the GW-U and the GW-C and reduces signaling overheads, and also decreases coupling between service units in the GW-U.
  • the GW-C may further configure the template of the service unit in the GW-U, so that a service unit can be modified or added to the GW-U based on the existing template. This reduces signaling exchange between the GW-C and the GW-U.
  • the GW-C may deliver, to the GW-U, processing order information of each service unit that is configured to process the user data.
  • the processing order information and the user data may be transmitted between the service units, instead of being returned to the interface management unit to reallocate a service unit to process the user data.
  • the GW-C when configuring the service unit in the GW-U, adds the user data forwarding information to the service unit configuration information, and configures the service unit configuration information for the service unit, to instruct the service unit to send the processed user data to the another GW-U used as a mobile anchor, or to forward the processed user data to the PDN.
  • the GW-C adds the user data forwarding information to the service unit configuration information, and configures the service unit configuration information for the service unit, to instruct the service unit to send the processed user data to the another GW-U used as a mobile anchor, or to forward the processed user data to the PDN.
  • user data that does not need to be processed by the mobile anchor directly enters the PDN. This reduces processing load of the mobile anchor and reduces a delay of transmitting the user data.
  • whether the user data is processed by the mobile anchor may be determined according to the service type of the user data.
  • User data that ensures service continuity is sent to the mobile anchor for processing, so as to ensure service continuity when the terminal moves.
  • Embodiments of the present invention provide a user data processing apparatus and method, and a system, so as to provide a solution in which a GW-U flexibly processes user data.
  • a GW-U receives user data, determines a service unit configured to process the received user data, and processes the received user data by using the determined service unit.
  • the service unit configured to process the received user data includes a session unit and at least one of a bearer unit, a service flow unit, or a content unit.
  • the session unit is configured to perform session processing
  • the bearer unit is configured to perform bearer processing
  • the service flow unit is configured to perform service flow processing
  • the content unit is configured to perform content processing.
  • the GW-U After receiving the user data, the GW-U determines the service unit configured to process the user data, and processes the user data by using the service unit determined by the GW-U. This improves processing flexibility of the GW-U.
  • a class, an object, and instantiation are concepts in an object-oriented approach.
  • a class is an abstract attribute and/or behavior of a thing.
  • a gateway has an IP address attribute, and the gateway also has behavior of assigning a terminal IP address and forwarding data.
  • An object is an instance of a class.
  • a gateway is used as an object, and an attribute of the gateway includes: an IP address is X.X.X.X, and behavior of the gateway may include: assigning an Internet Protocol (Internet Protocol, IP) version (version, v) 4/IPv6 address to user equipment (User Equipment, UE), and forwarding user data between a packet data network (Packet Data Network, PDN) and the UE by the gateway.
  • IP Internet Protocol
  • version version
  • PDN Packet Data Network
  • the object may also be referred to as an "object instance" or an "instance” for short.
  • Instantiation is a process of generating a concrete object based on a template being a class.
  • a gateway object is added that has an IP address and a function such as IP address assignment or data forwarding.
  • a user service includes but is not limited to one of the following services: accessing a network by a terminal to establish a data connection, forwarding terminal service data by a network, processing terminal service data by a network, or the like.
  • the user service may be referred to as a "service" for short, and the two concepts are equivalent.
  • User data may also be referred to as "service data" and is data transmitted between a terminal and a network and used to carry a specific user service.
  • the user data is different from control signaling.
  • the control signaling is signaling that is transmitted between a terminal and a network or within a network to implement connection control, network security, bearer allocation, and the like.
  • a PDN is an external packet data network connected to a gateway, and may be the Internet (Internet), a virtual private network (Virtual Private Network, VPN), an Internet Protocol (Internet Protocol, IP) multimedia service (IP Mutimedia Service, IMS) network, or a Wireless Application Protocol (Wireless Application Protocol, WAP) network provided by an operator.
  • Internet Internet
  • VPN Virtual Private Network
  • IP Internet Protocol
  • IMS IP Mutimedia Service
  • WAP Wireless Application Protocol
  • Mobile anchor Mobile Anchor
  • FIG. 4 shows an optional process of transmitting service data and control signaling in a wireless network.
  • a GGSN or a P-GW is used as a mobile anchor of downlink data and can remain an IP address of a terminal unchanged when the terminal moves between different base stations and/or different S-GWs, thereby ensuring mobile service continuity.
  • Using a mobile anchor can keep mobile service continuity, but results in problems, such as alternative routing, increase of a service latency, and increase of a backhaul network bandwidth.
  • problems such as alternative routing, increase of a service latency, and increase of a backhaul network bandwidth.
  • GSM Global System for Mobile communications
  • UMTS Universal Mobile Subscriber Identity
  • LTE Long Term Evolution
  • all mobile services need to be transmitted by using the mobile anchor GGSN or P-GW.
  • Communications standards to which the embodiments of the present invention are applicable include but are not limited to: the Global System for Mobile Communications (Global System of Mobile communication, GSM), the Code Division Multiple Access (Code Division Multiple Access, CDMA) IS-95, the Code Division Multiple Access (Code Division Multiple Access, CDMA) 2000, the Time Division-Synchronous Code Division Multiple Access (Time Division-Synchronous Code Division Multiple Access, TD-SCDMA), the Wideband Code Division Multiple Access (Wideband Code Division Multiple Access, WCDMA), the Time Division Duplex-Long Term Evolution (Time Division Duplexing-Long Term Evolution, TDD LTE), the Frequency Division Duplex-Long Term Evolution (Frequency Division Duplexing-Long Term Evolution, FDD LTE), the Long Term Evolution-Advanced (Long Term Evolution-Advanced, LTE-advanced), the personal handy-phone system (Personal Handy-phone System, PHS), the Wireless Fidelity (Wireless Fidelity, WiFi) stipulated in
  • a terminal may be a wireless terminal.
  • the wireless terminal may be a device providing voice and/or data connectivity for a user, or may be a handheld device having a wireless connection function, or another processing device connected to a wireless modem.
  • the wireless terminal may communicate with one or more core networks by using a radio access network (for example, RAN, Radio Access Network).
  • the wireless terminal may be a mobile terminal, such as a mobile phone (also referred to as a "cellular" phone) or a computer having a mobile terminal.
  • the computer having a mobile terminal may be a portable, pocket-sized, handheld, computer built-in, or in-vehicle mobile apparatus, which exchanges voice and/or data with the radio access network.
  • the wireless terminal may be a personal communications service (PCS, Personal Communication Service) phone, a cordless telephone set, a Session Initiation Protocol (SIP) phone, a wireless local loop (WLL, Wireless Local Loop) station, a personal digital assistant (PDA, Personal Digital Assistant), or another device.
  • PCS personal communications service
  • SIP Session Initiation Protocol
  • WLL Wireless Local Loop
  • PDA Personal Digital Assistant
  • the wireless terminal may alternatively be referred to as a subscriber unit (Subscriber Unit), a subscriber station (Subscriber Station), a mobile station (Mobile Station), a mobile station (Mobile), a remote station (Remote Station), an access point (Access Point), a remote terminal (Remote Terminal), an access terminal (Access Terminal), a user terminal (User Terminal), a user agent (User Agent), a user device (User Device), or user equipment (User Equipment).
  • system and “network” in this specification can often be used interchangeably in this specification.
  • network in this specification describes only an association relationship for describing associated objects and represents that three relationships may exist.
  • a and/or B may represent the following three cases: Only A exists, both A and B exist, and only B exists.
  • character "/" in this specification generally indicates an "or" relationship between the associated objects.
  • An identifier or identifier information is used to identify an object.
  • the object may be a terminal or a user.
  • the identifier may include at least one of a name, a number, or an ID (Identification), provided that the identified object can be distinguished from another object.
  • FIG. 5 is a schematic diagram of a communications system according to an embodiment of the present invention.
  • the communications system includes a GW-C 501 and a GW-U 502 that are separate, a terminal (for example, UE), a radio access network (for example, an LTE radio access network LTE-RAN and a WiFi access point AP), an MME, and a PDN (for example, an IMS and the Internet).
  • the terminal accesses the local gateway GW-U 502 by using the radio access network and then accesses the Internet from the local gateway GW-U 502.
  • the terminal accesses the IMS by using the local gateway GW-U 502 and an anchor GW-U 502.
  • the GW-C 501 is connected to the GW-U 502 and the MME.
  • the MME is responsible for mobility management of the UE.
  • the GW-C 501 is responsible for controlling the GW-U 502 to establish a service module or the like.
  • the GW-U may be deployed in a distributed manner, that is, the GW-U may be deployed at different locations in a network.
  • the GW-C 501 is configured to send a first request message to the GW-U 502.
  • the first request message is used to request to add a service unit processing user data to the GW-U.
  • the service unit processing the user data may be divided into a session (Session) unit and at least one of a bearer (Bearer) unit, a service flow (Flow) unit, or a content (Content) unit in descending order of granularities of processed services.
  • the session (Session) unit, the bearer (Bearer) unit, the service flow (Flow) unit, and the content (Content) unit are further described with reference to FIG. 6 .
  • the GW-U 502 is configured to: receive the first request message sent by the GW-C 501, and add, according to the first request message, the service unit processing the user data; and when receiving the user data, process the user data by using the added service unit processing the user data.
  • the GW-U 502 may be further divided into an anchor GW-U and a local GW-U according to a deployment location in a transport network.
  • the anchor GW-U (Anchor GW-U) is deployed at a core convergence point of the transport network, and used as a mobile anchor.
  • the local GW-U (Local GW-U) is deployed at a convergence point of the transport network or integrated into a base station, and used as a local access gateway.
  • the core convergence point may be deployed in a central city, for example, a national capital city or a convergence point of a backbone transport network.
  • the anchor GW-U deployed here can reduce alternative routing.
  • the convergence point may be deployed in an ordinary city and is used as a convergence point of a metropolitan area network, or deployed in a prefecture-level city or even a county-level city.
  • the GW-C 501 may interact with the GW-U 502, to manage and control the GW-U 502.
  • Control and management performed by the GW-U 502 on the GW-C 501 include at least one of the following:
  • the GW-C 501 may send a control message to the GW-U 502.
  • the GW-U 502 (which may be specifically an interface management unit 5021 in the GW-U 502 mentioned below) receives the control message, and adds, modifies, and deletes a service unit 5022 according to the received control message.
  • the GW-C 501 performs a configuration operation, such as adding, modification, or deletion, on a service unit 5022 in the GW-U 502, so that service units 5022 in the GW-U 502 can be flexibly combined. Different from that in an existing network, this can avoid frequently changing the GW-U 502, and the GW-U 502 does not always need to be modified each time service function logic is added.
  • the GW-U 502 can independently process the user data without interacting with the GW-C 501 again. This decreases coupling between the GW-U 502 and the GW-C 501 and reduces signaling overheads. In addition, this decreases coupling between service units in the GW-U 502.
  • the GW-C 501 may send a control message to the GW-U 502.
  • the GW-U 502 (which may be specifically an interface management unit 5021 in the GW-U 502 mentioned below) receives the control message, and adds a service unit 5022 based on a saved template, or modifies or deletes the saved template.
  • the GW-C 501 configures the template of a service unit 5022 in the GW-U 502, so that a service unit 5022 can be modified or added to the GW-U 502 based on the existing template. This reduces signaling exchange between the GW-C 501 and the GW-U 502.
  • the following describes an optional solution for the GW-C 501 to control and manage a service unit 5022 in the GW-U 502, and describes an optional solution for the GW-C 501 to control and manage the template in the GW-U 502.
  • the GW-C 501 may determine that a service unit 5022 needs to be added to the GW-U 502.
  • connection establishment message For an optional implementation of the connection establishment message, refer to a procedure shown in the following FIG. 12 .
  • the GW-C 501 sends the first request message to the GW-U 502, to request the GW-U 502 to add a service unit 5022.
  • a service unit 5022 When the service unit 5022 is added, multiple cases including the following two cases exist: Case 1: The added service unit 5022 includes a session unit and at least one of a bearer unit, a service flow unit, or a content unit.
  • the GW-C 501 adds service data information to the first request message.
  • the service data information may include:
  • the IP address of the terminal to which the user data belongs may include at least one of a source IP address of the terminal or a destination IP address of the terminal.
  • the tunnel information used to transmit the user data may include at least one of the following information: GTP tunnel information or IP tunnel information, such as Generic Routing Encapsulation (Generic Routing Encapsulation, GRE), Internet Protocol security (Internet Protocol Security, IPSec), Layer 2 Tunneling Protocol (Layer 2 Tunnel Protocol, L2TP), virtual local area network (Virtual Local Area Network, VLAN), Virtual Extensible Local Area Network (Virtual eXtensible Local Area Network, VxLAN), or multimedia information provider (Multimedia Information Provider, MIP) tunnel information.
  • GTP Generic Routing Encapsulation
  • GRE Generic Routing Encapsulation
  • Internet Protocol security Internet Protocol Security
  • IPSec Internet Protocol Security
  • Layer 2 Tunneling Protocol Layer 2 Tunneling Protocol
  • VLAN Virtual Local Area Network
  • VxLAN Virtual Extensible Local Area Network
  • MIP Multimedia Information Provider
  • Case 2 At least one of a bearer unit, a service flow unit, or a content unit is added, and the added service unit is associated with an existing session unit.
  • the GW-C 501 adds some items of service data information to the first request message.
  • the some items of the service data information may include at least one of tunnel information used to transmit the user data, IP 5-tuple information used to transmit the user data, or content information of the user data.
  • the added service unit 5022 may include a bearer unit; if the service data information includes the IP 5-tuple information, the added service unit 5022 may include a service flow unit; or if the service data information includes the content information, the added service unit 5022 may include a content unit.
  • the first request message includes service unit configuration information of the added service unit 5022.
  • the service unit configuration information may include information about an operation performed by the service unit 5022 and information about a parameter used by the service unit 5022 when the service unit 5022 processes the user data. For details, refer to the third and the fourth columns in the following Table 1, respectively.
  • the first request message includes identifier information of the service unit configuration information of the added service unit 5022.
  • the GW-U 502 determines the service unit configuration information according to the identifier information.
  • the GW-U 502 and the GW-C 501 need to reach an agreement in advance on an association relationship between the service unit configuration information and the identifier information of the service unit configuration information. In this way, after receiving the identifier information, the GW-U 502 may determine associated service unit configuration information.
  • multiple sets (Set) of service unit configuration information may be configured on the GW-U 502 in advance, and an identifier is allocated to each set of service unit configuration information.
  • the first request message sent by the GW-C 501 may include identifier information of service unit configuration information.
  • the GW-U 502 determines corresponding service unit configuration information according to the received identifier information.
  • the first request message includes the service data information associated with the user data and service unit configuration information of the service unit.
  • the interface management unit 5021 in the GW-U 502 After receiving the first request message, the interface management unit 5021 in the GW-U 502 adds the service unit 5022 and associates the service unit 5022 with the saved service data information and the service unit configuration information, that is, saves the service data information and the service unit configuration information, and saves association relationships between the foregoing two types of information and the service unit 5022.
  • the first request message includes the service data information associated with the user data and identifier information of the service unit configuration information of the service unit 5022.
  • the interface management unit 5021 in the GW-U 502 After receiving the first request message, the interface management unit 5021 in the GW-U 502 adds the service unit 5022, determines the service unit configuration information according to the identifier information of the service unit configuration information, and associates the service unit 5022 with the saved service data information and the determined service unit configuration information.
  • the first request message includes identifier information of the existing session unit, the service unit configuration information of the service unit 5022, and some items in the service data information.
  • the interface management unit 5021 in the GW-U 502 adds the service unit 5022, where the added service unit 5022 is associated with the session unit identified by the identifier information of the existing session unit; adds the foregoing some items to the original service data information, saves an association relationship between the session unit configured to process the user data and the service unit 5022, and associates the service unit 5022 with the saved service data information to which the some items have been added and the service unit configuration information, that is, saves the service data information and the service unit configuration information, and saves association relationships between the foregoing two types of information and the service unit 5022.
  • the first request message includes identifier information of the session unit configured to process the user data, identifier information of the service unit configuration information of the service unit 5022, and some items in the service data information.
  • the interface management unit 5021 in the GW-U 502 adds the service unit 5022, associates the added service unit 5022 with the existing session unit configured to process the user data, adds the some items to the original service data information, saves an association relationship between the session unit configured to process the user data and the service unit 5022, determines the service unit configuration information according to the identifier information of the service unit configuration information, and associates the service unit 5022 with the service data information to which the some items have been added and the service unit configuration information, that is, saves the service data information and the service unit configuration information, and saves association relationships between the foregoing two types of information and the service unit 5022.
  • the case 2 includes two sub-cases.
  • One sub-case is to add a bearer unit to an existing user data processing branch.
  • a bearer unit is added on the basis of session unit 2-service flow unit 1-content unit 3 on the right of FIG. 7 .
  • the branch is session unit 2-added bearer unit-service flow unit 1-content unit 3.
  • tunnel information corresponding to the added bearer unit needs to be added to original service data information corresponding to the branch.
  • the other sub-case is to add a user data processing branch. Still using the session unit 2 on the right of FIG. 7 as an example, it is assumed that there is no service flow unit 2 previously, and the service flow unit 2 needs to be added now. This branch does not exist previously, and therefore, service data information corresponding to the branch does not exist either. In this case, the service data information of the added branch needs to be saved.
  • the service data information includes an IP address, of a terminal to which the user data belongs, corresponding to the session unit 2, and IP 5-tuple information corresponding to the added service flow unit 2.
  • the GW-U 502 may process the user data in a predetermined processing order.
  • the GW-C 501 may add processing order information of the foregoing predetermined processing order of the service unit 5022 that processes the user data.
  • the GW-U 502 determines, according to the processing order information, the processing order of the service unit 5022 that processes the user data.
  • the GW-C 501 delivers, to the GW-U 502, processing order information of each service unit 5022 that is configured to process the user data. Therefore, when the GW-U 502 internally processes the user data, the processing order information and the user data may be transmitted between the service units 5022, instead of being returned to the interface management unit 5021 to reallocate a service unit 5022 to process the user data. This reduces signaling overheads.
  • the first request message may further include identifier information of the added service unit 5022.
  • the identifier information is used to identify the added service unit 5022.
  • the identifier information may be optional.
  • the GW-U 502 After receiving the first request message and adding the service unit 5022, the GW-U 502 further needs to save the identifier information of the service unit 5022 in the first request message.
  • the first request message may exclude identifier information of the added service unit 5022.
  • the GW-U 502 may allocate the identifier information.
  • the service unit 5022 may be added based on an existing template.
  • the first request message further includes unit type information of the service unit 5022.
  • the unit type information may include:
  • the GW-U 502 may determine, according to the unit type information of the service unit 5022, the service unit template used by the service unit 5022, and add the service unit 5022 based on the determined service unit template.
  • each type of service unit is corresponding to one or more templates of the type of service unit, and one of the templates is a default template. If the first request message includes the type identifier of the added service unit 5022, the GW-U 502 may determine a type of the added service unit 5022 according to the type identifier, and add the service unit 5022 according to a default template corresponding to the type.
  • the GW-U 502 may determine a template used by the added service unit 5022 according to the identifier of the template, and add the service unit 5022 based on the determined template.
  • the template of the service unit 5022 may be specifically a class in an object-oriented technology.
  • a class corresponding to a template of a session unit is referred to as a "session class”
  • a class corresponding to a template of a bearer unit is referred to as a "bearer class”
  • a class corresponding to a template of a service flow unit is referred to as a "service flow class”
  • a class corresponding to a template of a content unit is referred to as a "content class”.
  • the service unit 5022 may be specifically an object instance of class instantiation, and the object instance may be referred to as an "object” or an “instance” for short.
  • the object instance may be loaded onto or installed in the GW-U 502.
  • the GW-U 502 Before the object instances are loaded/installed, the GW-U 502 needs to allocate corresponding resources to these object instances, for example, allocate a memory, or a CPU process (Process) or thread (thread) to the object instance.
  • a network port, network bandwidth, or the like may be further allocated to the object instance, or a virtual machine or the like in a virtualized system is allocated to the object instance.
  • the class may be corresponding to a "a type of a service unit” in the following Table 1; an ID of the object instance may be corresponding to a "session unit ID", a "bearer unit ID”, a “service flow unit ID”, a “content unit ID”, or the like in Table 1.
  • the ID of the object instance may be allocated by the GW-C 501, or may be allocated and associated by the GW-U 502. If the ID of the object instance is allocated by the GW-U 502, when the GW-U 502 generates the object instance, the allocated ID of the object instance is needed.
  • the GW-C 501 may send to the GW-U 502 a control message used to modify the service unit 5022.
  • the message may carry identifier information of the to-be-modified service unit 5022 and service unit configuration information of the to-be-modified service unit 5022.
  • the GW-U 502 may determine the to-be-modified service unit 5022 according to the identifier information of the service unit 5022 in the control information, and update, according to the service unit configuration information in the control information, saved service unit configuration information associated with the service unit 5022.
  • the GW-C 501 may send to the GW-U 502 a control message used to delete the service unit 5022.
  • the message may carry identifier information of the to-be-deleted service unit 5022.
  • the GW-U 502 may determine the to-be-deleted service unit 5022 according to the identifier information of the service unit 5022 in the control information, and deletes the service unit 5022.
  • the GW-C 501 may send a control message to the GW-U 502.
  • the GW-U 502 receives the control message, and adds a template, or modifies or deletes a saved template according to the received control message.
  • the control message may include a template identifier and description information of the template.
  • description information of the template refer to the third and the fourth columns in Table 1.
  • the control message may also include a template identifier of the to-be-modified template and description information of the to-be-modified template.
  • the GW-U 502 determines the to-be-modified template according to the template identifier, and performs corresponding modification on the template according to the description information of the to-be-modified template in the message.
  • the control message may include a template identifier of the to-be-deleted template.
  • the GW-U 502 determines the to-be-deleted template according to the template identifier and deletes the determined template.
  • compositions of the GW-U 502 and optional solutions for processing user data with reference to FIG. 6 to FIG. 10
  • FIG. 6 shows compositions of the GW-U 502 and an optional solution for processing user data.
  • the GW-U 502 includes an interface management unit 5021, and includes, for each terminal, one or more service units 5022 corresponding to the terminal, or includes, for each user service of each terminal, one or more service units 5022 corresponding to the user service of the terminal.
  • the interface management unit 5021 is configured to interact with the GW-C 501, so that the GW-C 501 manages the service unit 5022 on the GW-U 502.
  • the service unit 5022 is configured to process user data of the terminal.
  • the interface management unit 5021 is specifically configured to perform at least one of the following processing operations by interacting with the GW-C 501:
  • the foregoing fourth processing operation may alternatively be performed by an independent interface data unit.
  • the interface data unit receives the user data and sends the user data to the interface management unit 5021.
  • the interface management unit 5021 obtains the IP address of the terminal to which the user data belongs from the user data, and determines the session unit configured to process the user data.
  • the interface management unit 5021 performs matching between the IP address obtained from the user data and an IP address saved by an associated session unit; if the two addresses are consistent, uses the matched session unit as the session unit configured to process the data, and sends, to the interface data unit, information used for indicating an association relationship between the IP address of the terminal to which the user data belongs and the session unit, and the interface data unit sends the user data to the associated session unit according to the association relationship.
  • the interface data unit may send a request to the interface management unit 5021, to request the interface management unit 5021 to determine the associated session unit; save the association relationship after receiving information sent by the interface management unit 5021 for indicating the association relationship; and after receiving user data from the same IP address subsequently, directly send the user data to the associated session unit according to the saved association relationship, instead of determining the association relationship by using the interface management unit 5021.
  • the GW-U 502 may include at least two service units 5022.
  • the service unit 5022 may be divided into the following four types in descending order of granularities of processed services: a session (Session) unit, a bearer (Bearer) unit, a service flow (Flow) unit, and a content (Content) unit.
  • Session Session
  • Bearer Bearer
  • Flow service flow
  • Content Content
  • the session unit may be configured to perform session processing on the user data, for example, maintaining aggregation QoS control of a terminal in an APN (for example, aggregation bandwidth control, that is, for an APN, limiting a total bandwidth occupied by all services corresponding to the APN), or an IP address management function.
  • aggregation QoS control of a terminal in an APN for example, aggregation bandwidth control, that is, for an APN, limiting a total bandwidth occupied by all services corresponding to the APN
  • IP address management function for example, maintaining aggregation QoS control of a terminal in an APN (for example, aggregation bandwidth control, that is, for an APN, limiting a total bandwidth occupied by all services corresponding to the APN), or an IP address management function.
  • the bearer unit may be configured to perform bearer processing on the user data, for example, one or more of data forwarding, QoS control, charging, bearer routing control, or bearer event reporting of a terminal bearer.
  • Bearer QoS control may include QoS control on bandwidth, a delay, jitter, a priority, and the like of the user data.
  • Bearer charging may include bearer traffic statistics or the like.
  • Bearer event reporting may include bearer charging event reporting or the like, and the GW-C 501 may configure a trigger point of reporting a bearer event.
  • the service flow unit may be configured to perform transport layer processing on the user data, for example, one or more of parsing on an IP 5-tuple level data flow, QoS control, charging, service flow routing control, or service flow event reporting of a terminal data service flow.
  • Service flow QoS control may include QoS control on bandwidth, a delay, jitter, a priority, and the like of the user data.
  • Service flow charging may include service flow traffic statistics or the like.
  • Service flow event reporting may include service flow charging event reporting or the like, and the GW-C 501 may configure a trigger point of reporting a service flow event.
  • the content unit may be configured to perform content processing on the user data, for example, data flow parsing, content data flow-level QoS control, content data flow charging and a content data flow switch function, content routing control, or content event reporting.
  • the content unit may parse a data packet at layer 7 of an open system interconnection (Open System Interconnect, OSI) model, for example, a uniform resource locator (Uniform Resource Locator, URL).
  • Service QoS control may include QoS control on bandwidth, a delay, jitter, a priority, and the like of the user data.
  • Content charging may include content data traffic statistics.
  • Content event reporting may include content charging event reporting or the like, and the GW-C 501 may configure a trigger point of reporting a content event.
  • the service unit may be also referred to as a "service module”; the session unit may be also referred to as a "session module”; the bearer unit may be also referred to as a “bearer module”; the service flow unit may be also referred to as a “service flow module”; and the content unit may be also referred to as a "content module”.
  • a service module in the GW-U 502 processes the user data.
  • the GW-U 502 may add a service unit by creating a service context.
  • the created service context is a session context
  • the added service unit is a session unit.
  • the created service context is a bearer context
  • the added service unit is a bearer unit.
  • a service flow unit is added.
  • the created service context is a content context
  • the added service unit is a content unit.
  • the GW-U 502 may process the user data according to the service context.
  • the GW-C 501 may control the GW-U 502 to add a session unit and a bearer unit.
  • One bearer may be corresponding to one GTP tunnel.
  • the bearer unit is configured to encapsulate the user data. For a web page browsing service, only a session unit and a bearer unit may be added. Alternatively, a bearer unit may not be added, and a default bearer unit is used for processing the user data.
  • the GW-C 501 obtains, from a PCRF, information about a user policy of the terminal, for example, an IP 5-tuple and QoS information.
  • the GW-C 501 determines, according to the obtained user policy, that a service flow unit needs to be added to the GW-U 502 for the terminal.
  • a session unit has been established, and association is established between the added service flow unit and the existing session unit. For example, for services such as VoIP, a video call, and games, a service flow unit needs to be added.
  • one or more session units that are associated with each other may generally exist on the GW-U 502.
  • One session unit may be associated with one or more bearer units.
  • One session unit may be associated with one or more service flow units.
  • One session unit may be associated with one or more content units.
  • the service unit 5022 in the GW-U 502 may include a session unit 1 and a session unit 2.
  • the session unit 1 is associated with a bearer unit 1, a bearer unit 2, and a bearer unit 3.
  • the session unit 2 is associated with a service flow unit 1, a service flow unit 2, and a content unit 4.
  • the service flow unit 1 is further associated with a content unit 3.
  • the content unit 4 is further associated with the service flow unit 3.
  • the bearer unit may be corresponding to a default bearer (default bearer) of the terminal, or may be corresponding to a dedicated bearer (dedicated bearer) of the terminal.
  • the GW-U 502 needs to process user data of a terminal by using a combination of one or more service units 5022 corresponding to the terminal, for example, a combination of a session unit and a bearer unit.
  • FIG. 14 to FIG. 19 further describe procedures of processing user data of a terminal by the GW-U 502 by using a service unit 5022 corresponding to the terminal.
  • the service unit 5022 processing the user data in the GW-U 502 may include a session unit and at least one of a bearer unit, a service flow unit, or a content unit.
  • FIG. 11 shows a procedure of processing user data by a GW-U 502 according to an embodiment of the present invention. As shown in FIG. 11 , the procedure of processing user data by a GW-U 502 may include the following steps:
  • the interface management unit 5021 in the GW-U 502 may use a session unit associated with an IP address in service data information, as the session unit configured to process the user data.
  • the session unit may obtain the service data information from the user data, and determine, according to the obtained service data information, the another service unit 5022 configured to process the user data.
  • the session unit may determine the another service unit 5022 configured to process the user data in the following manners: If the service data information includes tunnel information, the session unit uses a bearer unit associated with the tunnel information in the service data information, as a bearer unit configured to process the user data.
  • the session unit uses a service flow unit associated with the IP 5-tuple information in the service data information, as a service flow unit configured to process the user data.
  • the session unit uses a content unit associated with the content information in the service data information, as a content unit configured to process the user data.
  • the session unit may process the user data by using saved service unit configuration information associated with the session unit.
  • the service unit 5022 may process the user data by using saved service unit configuration information associated with the service unit 5022.
  • the service unit configuration information may include information about an operation performed by the service unit 5022 and information about a parameter used by the service unit 5022 when the service unit 5022 processes the user data. For details, refer to the third and the fourth columns in the following Table 1.
  • Table 1 Description information of the service unit Service unit type Service unit function Service unit attribute (operation function list (Operation List or Operation Group) or component group (Component or Component Group)) Service unit configuration information (service unit configuration information, operation function configuration information or component information) Session unit Session -level QoS control and IP address management Data matching, QoS control, IP address management, event reporting, and data forwarding Session unit ID Terminal identifier (optional) APN (optional) Session QoS information (optional) Session data forwarding table (optional) Terminal IP address List of service units matching session data Session event list information (optional) Bearer unit Bearer data forwarding, bearer QoS control, Data forwarding, bearer QoS control, bearer charging, bearer routing control
  • a function that each service unit 5022 can execute may be configured when the GW-C 501 adds/modifies the service unit 5022, and may be associated with service unit configuration information of the service unit 5022 that is saved in the service unit 5022. That means the service unit configuration information is saved, and an association relationship between the service unit configuration information and the service unit 5022 is saved.
  • the description information of the service unit provided in Table 1 is an optional implementation.
  • the first, the second, and the fourth columns may be content in the description information of the service unit.
  • the second column of service unit function is used to explain a function implemented by a corresponding service unit type, and may not be included in the description information.
  • service units 5022 in the GW-U 502 may process the user data in order.
  • the session unit in the GW-U 502 processes the user data; and then, the session unit configured to process the user data sends the user data and information about a predetermined processing order to a next-hop service unit indicated by the predetermined processing order, in the predetermined processing order, to instruct a subsequent service unit 5022 including the next-hop service unit to process the user data in the predetermined processing order.
  • the user data can be transmitted directly between the service units 5022, instead of being returned to the interface management unit 5021 or the GW-C 501 to reallocate another service unit 5022. This reduces data and signaling exchange, and improves processing efficiency of user data.
  • the predetermined processing order may be defined when the GW-C 501 adds the service unit 5022 configured to process the user data.
  • the GW-U 502 saves the information about the predetermined processing order, so as to process the user data in the predetermined processing order subsequently.
  • the processing order information may be implicitly stored on the "list of service units matching service data" in the "service unit configuration information" of the session unit in Table 1.
  • the list may include a list of multiple service units 5022 configured to process one piece of user data.
  • An order of the service units 5022 on the list is the predetermined processing order.
  • the information about the predetermined processing order may be implemented by meta data (meta data).
  • the meta data may be generated by the session unit, attached to a header of the user data, and sent with the user data.
  • the service unit 5022 receiving the user data obtains the meta data from the header of the user data, determines, according to the meta data, whether to forward the user data to another service unit 5022 after the service unit 5022 completes processing the user data, determines a service unit 5022 to which the user data needs to be forwarded if the user data needs to be forwarded to another service unit 5022, and after determining the service unit 5022 to which the user data needs to be forwarded, still attaches the meta data to a header of service data and sends the service data to the determined target service unit 5022, so as to facilitate further processing by the target service unit 5022.
  • the meta data may be a list of service units 5022, and used to indicate one or more service units 5022 that the user data passes through and an order of the service units 5022 that the user data passes through.
  • the list may be mapped as a label, and the label is added to the user data and sent to a next service unit 5022.
  • a processing order of user data that is indicated by meta data generated by the session unit 2 may be shown in FIG. 8 .
  • a processing order of user data that is indicated by meta data generated by the session unit 2 may be shown in FIG. 9 .
  • a processing order of user data that is indicated by meta data generated by the session unit 1 may be shown in FIG. 10 .
  • the GW-U 502 determines the service unit configured to process the user data, and processes the user data by using the service unit determined by the GW-U 502. This improves processing flexibility of the GW-U.
  • FIG. 12 shows an optional procedure of controlling, by a GW-U 502, a GW-U 502 to add a service unit.
  • the GW-U 502 receives a create session request.
  • a request for adding/modifying a service unit 5022 in step S1202 of FIG. 12 is the aforementioned first request message.
  • the user data is packet (Packet) data.
  • the procedure shown in FIG. 12 includes the following steps.
  • the GW-C 501 receives a connection establishment message sent by another network element.
  • a create session request sent by an MME or an S-GW is used as an example herein.
  • the connection establishment message may be a create session request (Create Session Request) message sent by an MME or an S-GW.
  • the message is used to request to create a session and a bearer.
  • the message may include user plane GTP tunnel information.
  • connection establishment message may be a create bearer response (Create Bearer Response) message in a dedicated bearer establishment procedure triggered by the GW-C 501 or a PCRF.
  • the message may include user plane GTP tunnel information of a peer-end network element, for example, GTP tunnel information of a connection between a peer-end network element and a user plane.
  • connection establishment message may be a multimedia information provider binding update (Multimedia Information Provider Binding Update, MIP BU) message sent by a terminal or an access gateway.
  • the message may include mobile IP information, which may be MIPv4, proxy MIP (Proxy MIP, PMIP) v6, dual stack MIP (Dual Stack, DSMIP) v6, or other information.
  • the access gateway includes but is not limited to an evolved packet data gateway (evolved Packet Data Gateway, ePDG), a high rate packet data serving gateway (High Rate Packet Data Serving Gateway, HSGW) in a code division multiple access (Code Division Multiple Access, CDMA) system, and an access router of a WiFi/wireless local area network (Wireless Local Access Network, WLAN).
  • ePDG evolved Packet Data Gateway
  • HSGW High Rate Packet Data Serving Gateway
  • CDMA Code Division Multiple Access
  • WLAN Wireless Local Access Network
  • the GW-C 501 sends, to the GW-U 502, a request for adding/modifying a service unit 5022 (Add/modify Module Request), that is, the aforementioned first request message, where the first request message is used to request to add/modify a session unit and a bearer unit, the added/modified service unit 5022 is configured to process and forward user data of a terminal, and the first request message includes service unit configuration information of the added/modified service unit 5022.
  • a request for adding/modifying a service unit 5022 (Add/modify Module Request)
  • An interface management unit 5021 in the GW-U 502 adds/modifies the service unit 5022 (for example, the session unit and the bearer unit).
  • the interface management unit 5021 in the GW-U 502 returns a response message for adding/modifying the service unit 5022, where the message may carry a cause value for representing whether the service unit 5022 is successfully added or not.
  • the GW-C 501 may return a create session response to another network element.
  • the service unit 5022 is successfully added, for example, the session unit and bearer unit are successfully added, the added session unit and bearer unit start processing the user data of the terminal.
  • the session unit receives the user data such as packet (packet) data.
  • the session unit determines, according to service data information in the user data, another service unit configured to process the user data.
  • the another service unit determined by the session unit includes the bearer unit in FIG. 12 .
  • the session unit sends the user data to the bearer unit for processing.
  • the bearer unit performs bearer QoS control, bearer charging, and the like on the received user data, and forwards user data, for example, forwards a bearer packet in FIG. 12 .
  • the bearer unit may further report a bearer event report, to report a service data forwarding status, for example, a success or a failure, a charging event, and a service event.
  • the service unit 5022 that the GW-C 501 requests the GW-U 502 to add may include the session unit and the bearer unit. If only the bearer unit is to be established, the GW-C 501 may request to add only the bearer unit, and request the GW-U 502 to modify bearer unit matching information in service data information in the session unit, that is, the aforementioned tunnel information in the service data information, so that after receiving corresponding user data subsequently, the session unit can forward the received user data to a corresponding bearer unit.
  • the GW-C 501 may further request the GW-U 502 to add a service flow unit, which is configured to forward and process user data matching a service flow policy and rule.
  • the service flow policy and rule may include the aforementioned IP 5-tuple information.
  • the GW-C 501 may generate service unit configuration information of the service flow unit according to the service flow policy and rule, and modify service flow unit matching information in service data information in the session unit, that is, the aforementioned IP 5-tuple information in the service flow unit, so that after receiving corresponding user data subsequently, the session unit can forward the received user data to a corresponding service flow unit.
  • the GW-C 501 may receive the service flow policy and rule from the PCRF, or obtain the service flow policy and rule from a PCC rule configured by the GW-C 501.
  • the GW-C 501 may alternatively request, based on a default service flow policy and rule configured by the GW-C 501, the GW-U 502 to add a service flow unit, to process and forward corresponding user data (for example, service flow data).
  • the GW-C 501 requests the GW-U 502 to add the service flow unit, and the GW-U 502 already has a corresponding session unit, the GW-C 501 further needs to request the GW-U 502 to modify service data information in service unit configuration information of the session unit.
  • the service data information is saved in the service unit configuration information of the session unit.
  • the session unit can forward the user data to a corresponding service flow unit for processing and forwarding.
  • the GW-C 501 may alternatively request, based on a default content policy and rule configured by the GW-C 501, the GW-U 502 to add a content unit, to process and forward corresponding user data (for example, content data, that is, data belonging to content).
  • the GW-U 502 generates content unit information according to the content policy and rule information.
  • the GW-C 501 requests the GW-U 502 to add the content unit, and the GW-U 502 already has a corresponding session unit, the GW-C 501 further needs to request the GW-U 502 to modify content unit matching information in service data information in service unit configuration information of the session unit, that is, the aforementioned content information, so that after receiving user data (for example, content data) subsequently, the session unit can forward the user data to a corresponding content unit for processing and forwarding.
  • service data information for example, content data
  • the first request message sent by the GW-C 501 to the GW-U 502 may include the service unit configuration information of the service unit 5022.
  • the service unit configuration information of the service unit 5022 For example, for a session unit, a data matching function and a list of service units matching session data may be included.
  • step S1202 further, if a session unit is to be newly established, the GW-C 501 needs to assign an IP address to the terminal.
  • the GW-U 502 may add the service unit 5022 according to the service unit configuration information in the first request message sent by the GW-C 501.
  • the service unit configuration information refer to descriptions in Table 1. Details are not further described herein.
  • sending the first request message to the GW-U 502 by the GW-C 501 is not triggered by a connection establishment message received from another network element.
  • An optional implementation includes: After receiving user data, the session unit in the GW-U 502 parses the user data to obtain service flow-related information or content-related information, that is, detects a new service flow or new content. The session unit reports this event to the gateway control plane GW-C 501. Thus, in step S1202, the GW-C 501 requests the GW-U 502 to add the service flow unit or the content unit, and to modify the service unit configuration information in the session unit, and optionally, to modify service flow unit matching information or content unit matching information in the service unit configuration information.
  • a GW-C performs a configuration operation, such as adding, modification, or deletion, on a service unit of a GW-U, so that service units in the GW-U can be flexibly combined. Different from that in an existing network, this can avoid frequently changing the GW-U, and the GW-U does not always need to be modified each time service function logic is added. In this way, user data can be flexibly processed according to a service requirement of the user data. For example, a service unit can be flexibly added or removed in a process of processing the user data, so that the GW-U is able to adapt to a future new service type of user data.
  • the GW-U can independently process the user data without interacting with the GW-C. This decreases coupling between the GW-U and the GW-C and reduces signaling overheads, and also decreases coupling between service units in the GW-U.
  • a procedure of controlling, by a GW-C 501, a GW-U 502 to add a service unit 5022 shown in FIG. 13A and FIG. 13B includes: a procedure of requesting, by the GW-C 501, to add a service unit 5022 in a local GW-U 502 and requesting, by the GW-C 501, to add a service unit 5022 in an anchor GW-U 502.
  • the GW-C 501 may determine whether user data passes through the GW-U used as a mobile anchor, in multiple manners including the following two:
  • the service types may be divided into:
  • communication service types such as voice communication and a video call are used as an example.
  • session service types such as Skype, IMS, QQ, WeChat, VoIP, and a video call
  • interaction service types such as shooting, an instant strategy, real-time interaction, and other network service types
  • service continuity needs to be ensured when a terminal moves.
  • This type of service requires that the terminal has an unchanged IP address in a moving process, so as to ensure service continuity and avoid interrupting a voice and video call service.
  • the GW-U 502 may be set as a mobile anchor, so as to keep the IP address of the terminal unchanged in a moving process, and avoid interrupting a voice and video call service.
  • this type of service does not have a high requirement on continuity, and therefore, a mobile anchor may not be set.
  • User data of this type of service may be directly transmitted to Internet without passing through a mobile anchor. This reduces a delay and an alternative route, and improves transmission efficiency and user experience.
  • the GW-C 501 initiates a credit control request (Credit Control Request, CCR) to the PCRF, and the CCR is used to request the policy and rule.
  • CCR Credit Control Request
  • the GW-C 501 obtains an IP 5-tuple from the policy and rule received from the PCRF; if an IP address in the obtained IP 5-tuple (for example, a source IP address or a destination IP address, or a source IP address and a destination IP address) is in an IP address segment of an anchor GW-U, determines that the user data needs to pass through the anchor gateway; or if an IP address in the obtained IP 5-tuple is in an IP address segment of a local GW-U, determines that the user data needs to pass through the local GW-U.
  • an IP address in the obtained IP 5-tuple for example, a source IP address or a destination IP address, or a source IP address and a destination IP address
  • the IP 5-tuple includes a source IP address, a source port number, a destination IP address, a destination port number, and a transport layer protocol.
  • the procedure shown in FIG. 13A and FIG. 13B is applicable to a scenario in which the GW-C 501 determines that the user data needs to pass through the GW-U 502 used as a mobile anchor, and specifically includes the following steps.
  • the GW-C 501 receives a connection establishment message sent by another network element.
  • the GW-C 501 requests a local GW-U 502 to add/modify a service unit 5022.
  • the local GW-U 502 installs a new service unit 5022 or modifies an existing service unit 5022, for example, a session unit and a service flow unit.
  • S1304 The local GW-U 502 returns a response to service unit 5022 adding/modification, where the message carries a cause value representing a success or a failure.
  • the GW-C 501 requests an anchor GW-U 502 to add/modify a service unit 5022.
  • a request message for adding/modifying a service unit includes service unit configuration information of the added/modified service unit 5022. Different from that in the procedure shown in FIG. 12 , the service unit configuration information further includes related information about forwarding of the user data between the local GW-U 502 and the anchor GW-U 502.
  • the anchor GW-U 502 installs a new service unit 5022 or modifies an existing service unit 5022, for example, a session unit and a service flow unit.
  • the anchor GW-U 502 returns a response to service unit 5022 adding/modification, where the message carries a cause value representing a success or a failure.
  • the GW-C 501 may return a connection establishment response message to another network element, for example, a PCC re-authorization answer (Re-Authorization Answer, RAA) message.
  • RAA Re-Authorization Answer
  • connection establishment message in step S1301 may alternatively be a policy and charging control (Policy and Charging Control, PCC) re-authorization request (Re-Authorization Request, RAR)/credit control answer (Credit Control Answer, CCA) message sent by a PCRF.
  • PCC Policy and Charging Control
  • RAR Re-Authorization Request
  • CCA Credit Control Answer
  • the CCA message may be sent by the PCRF in response to the credit control request (Credit Control Request, CCR) sent by the GW-C 501.
  • the RAR message may request to add a service flow for a user, and generally includes an IP 5-tuple.
  • the connection establishment message in step S1301 may be triggered by reporting a new user service event to the GW-C 501 when a service module in the local GW-U 502 detects a service flow and content service passing through an anchor that is newly initiated by a user terminal or a network side.
  • the GW-C 501 initiates an action of adding a service unit and modifying/updating a service unit on the anchor GW-U 502 and the local GW-U 502.
  • a session unit in the GW-U 502 parses the user data to obtain service flow-related information or content-related information, that is, detects a new service flow or new content.
  • the session unit reports this event to the gateway control plane GW-C 501.
  • the GW-C 501 requests the GW-U 502 to add the service flow unit or the content unit, and to modify the service unit configuration information in the session unit, and optionally, to modify service flow unit matching information or content unit matching information in the service unit configuration information.
  • the GW-C 501 may send the CCR to the PCRF, to request the policy and rule.
  • the policy and rule delivered by the PCRF may include information used for indicating an anchor that the user data of the terminal needs to pass through when being forwarded, and the information may be, for example, an IP 5-tuple of a service flow or an identifier of an IP 5-tuple of a service flow.
  • the GW-C 501 may obtain information about the terminal according to the policy and rule obtained from the PCRF or a signing rule (for example, based on signing information of an APN of the terminal or a policy and rule requirement obtained from the PCRF, an APN service needs to pass through the anchor GW-U 502, and another APN service does not need to pass through the anchor GW-U 502), assign two IP addresses to the terminal.
  • One IP address is used when the local GW-U 502 forwards user data between a packet data network and the terminal, and the other IP address is used when the anchor GW-U 502 forwards service data passing through the anchor GW-U 502.
  • a first request message sent by the GW-C 501 to the local GW-U 502 may carry a service flow data forwarding table in Table 1.
  • the service flow unit sets a next-hop address of uplink user data (for example, service flow data) as information of the anchor GW-U 502 (for example, address information or tunnel information of the anchor GW-U 502).
  • the information is, for example, at least one of the following information: an IP address of the anchor GW-U 502, an IP address of a terminal corresponding to the anchor GW-U 502 (the IP address may be used for IP address translation, which may use a technology such as network Address Translation (Network Address Translation, NAT)), a bearer TEID of the terminal (the identifier may be used for a GTP interface protocol), or a port number used in terminal service NAT (the port number is a port number of a NAT gateway, associated with an IP address of the terminal, and may be used for IP address translation, which may use a technology such as NAT).
  • NAT Network Address Translation
  • a first request message sent by the GW-C 501 to the anchor GW-U 502 may also carry a service flow data forwarding table in Table 1.
  • a service flow unit in the anchor GW-U 502 sets a next-hop address of downlink user data (for example, service flow data) as information of the local GW-U 502.
  • the information is, for example, at least one of the following information: an IP address of the local GW-U 502, an IP address of a terminal corresponding to the local GW-U 502 (the IP address may be used for IP address translation, which may use a technology such as NAT), a bearer TEID of the terminal (the identifier may be used for a GTP interface protocol), or a port number (the port number is a port number of a NAT gateway, associated with an IP address of the terminal, and may be used for IP address translation, which may use a technology such as NAT).
  • the GW-C 501 may alternatively request, based on a default service flow policy and rule configured by the GW-C 501, the anchor GW-U 502 and the local GW-U 502 to separately add a service flow unit, to process and forward corresponding service flow data.
  • the GW-C 501 requests the anchor GW-U 502 and the local GW-U 502 to separately add a service flow unit, and the anchor GW-U 502 and the local GW-U 502 each already have a corresponding session unit, the GW-C 501 further needs to request the GW-U 502 to modify or update service data information in service unit configuration information of each session unit.
  • the service data information is saved in the service unit configuration information of each session unit. In this way, after receiving user data (for example, service flow data, that is, user data belonging to a service flow) subsequently, the session unit can forward the user data to a corresponding service flow unit for processing and forwarding.
  • the first request message sent by the GW-C 501 to the anchor GW-U 502 and the local GW-U 502 may further include service unit configuration information of the service unit 5022.
  • service unit configuration information of the service unit 5022 For example, for a session unit, a data matching function, a list of service units matching session data, and the like may be included.
  • the GW-U 502 may add the service unit 5022 according to the service unit configuration information in the first request message sent by the GW-C 501.
  • the session units and service flow units added by the local GW-U 502 and the anchor GW-U 502 start processing user data.
  • the local GW-U 502 forwards user data to the anchor GW-U 502.
  • the anchor GW-U 502 forwards user data to the local GW-U 502.
  • the GW-C 501 when configuring the service unit in the GW-U 502, the GW-C 501 adds user data forwarding information to the service unit configuration information, and configures the service unit configuration information for the service unit.
  • the user data forwarding information is used to indicate whether the service unit sends the processed user data to another GW-U 502 used as a mobile anchor, or forwards the processed user data to a PDN.
  • the user data forwarding information is used, so that user data that does not need to be processed by the mobile anchor directly enters the PDN. This reduces processing load of the mobile anchor and reduces a delay of transmitting the user data.
  • Whether the user data is processed by the mobile anchor may be determined according to a service type of the user data. User data that ensures service continuity is sent to the mobile anchor for processing, so as to ensure service continuity when the terminal moves.
  • a session unit and a bearer unit in the GW-U 502 are configured to process the user data.
  • a procedure shown in FIG. 14 may include the following steps.
  • the session unit receives packet (packet) data.
  • the session unit receives packet data sent by another network element, for example, an evolved NodeB (evolved NodeB, eNodeB), an Internet server, an S-GW, a P-GW, an ePDG, or an HSGW.
  • an evolved NodeB evolved NodeB
  • eNodeB evolved NodeB
  • an Internet server for example, an S-GW, a P-GW, an ePDG, or an HSGW.
  • An interface management unit 5021 in the GW-U 502 may find a corresponding matched session unit, based on one or more pieces of service data information in the packet data.
  • Service data information of the session unit may be configured by a GW-C 501.
  • the session unit finds a matched service unit 5022 according to packet data that is used as user data, that is, a bearer unit in FIG. 14 ; for example, obtains tunnel information from a packet, performs matching between the tunnel information and that in saved service data information, to determine the bearer unit configured to process the packet data; and the session unit may add the service data information (for example, the aforementioned meta data) to the packet data and sends the packet data to the determined bearer unit.
  • packet data that is used as user data that is, a bearer unit in FIG. 14 ; for example, obtains tunnel information from a packet, performs matching between the tunnel information and that in saved service data information, to determine the bearer unit configured to process the packet data; and the session unit may add the service data information (for example, the aforementioned meta data) to the packet data and sends the packet data to the determined bearer unit.
  • the session unit forwards the packet data to the matched bearer unit.
  • the bearer unit performs bearer QoS control (bearer QoS Control) on the packet data.
  • the bearer unit performs bearer charging (bearer Charging) on the packet data.
  • the bearer unit forwards a bearer packet, to output the packet data.
  • the bearer unit may forward the packet data, based on the meta data in the packet data or service unit configuration information of the bearer unit that is configured when the GW-C 501 adds/modifies the bearer unit.
  • the bearer unit may forward the packet data to a next service unit 5022 or to another network element, for example, an anchor GW-U 502, an eNodeB, or a PDN, according to the service unit configuration information (for example, a bearer data forwarding table in Table 1) configured when the GW-C 501 adds/modifies the bearer unit.
  • the service unit configuration information for example, a bearer data forwarding table in Table 1
  • the GW-C 501 determines, according to the service unit configuration information (for example, the bearer data forwarding table in Table 1) configured when the bearer unit is added/modified, whether to forward uplink user data to an anchor GW-U 502 or to forward uplink user data to a PDN.
  • the service unit configuration information for example, the bearer data forwarding table in Table 1
  • the bearer unit reports a bearer event report (Bearer Event Report) to a GW-C 501.
  • the bearer unit may perform one or more of step S1404, step S1405, or step S1407.
  • a specific step performed by the bearer unit, that is, a function of the bearer unit, may be configured in the service unit configuration information of the bearer unit when the GW-C 501 adds/modifies the bearer unit. Refer to the third column of Table 1.
  • the user data may be forwarded, based on a bearer, to the anchor GW-U 502 or the PDN, for example, the Internet, and a service unit 5022 may be flexibly added or removed in a procedure of processing the user data, so that the GW-U 502 is able to adapt to a future new user data service.
  • FIG. 15 shows an optional implementation solution of processing user data by a GW-U 502.
  • a session unit and a service flow unit in the GW-U 502 are configured to process the user data.
  • a procedure shown in FIG. 15 may include the following steps.
  • the session unit receives packet data.
  • the session unit receives packet data sent by another network element, for example, an evolved NodeB (evolved NodeB, eNodeB), an Internet server, an S-GW, a P-GW, an ePDG, or an HSGW.
  • an evolved NodeB evolved NodeB
  • eNodeB evolved NodeB
  • an Internet server for example, an S-GW, a P-GW, an ePDG, or an HSGW.
  • the session unit finds a matched service unit 5022 according to packet data that is used as user data, that is, a service flow unit in FIG. 15 ; for example, obtains IP 5-tuple information from a packet, performs matching between the IP 5-tuple information and that in saved service data information, to determine the service flow unit configured to process the packet data; and the session unit adds the service data information (for example, the aforementioned meta data) to the packet data and sends the packet data to the determined service flow unit.
  • the service data information for example, the aforementioned meta data
  • S1503 The session unit forwards the packet data to the matched service flow unit.
  • the service flow unit performs service flow QoS control (flow QoS Control) on the packet data.
  • S1505 The service flow unit performs flow charging (flow Charging) on the packet data.
  • S1506 The service flow unit forwards a flow packet, to output the packet data.
  • the service flow unit may forward the packet data, based on the meta data in the packet data or service unit configuration information of the service flow unit that is configured when a GW-C 501 adds/modifies the service flow unit.
  • the service flow unit may forward the packet to a next service unit 5022 or to another network element, for example, an anchor GW-U 502, an eNodeB, or a PDN according to the service unit configuration information (for example, a service flow data forwarding table in Table 1) configured when the GW-C 501 adds/modifies the service flow unit.
  • the service unit configuration information for example, a service flow data forwarding table in Table 1
  • uplink user data is forwarded to an anchor GW-U or a PDN is specified in the service unit configuration information (for example, the service flow data forwarding table in Table 1) configured when the GW-C 501 adds/modifies the service flow unit.
  • the service unit configuration information for example, the service flow data forwarding table in Table 1
  • the service flow unit may alternatively forward the packet to a next service unit 5022 according to a list of service units 5022 in the meta data.
  • the meta data is also forwarded to the next service unit 5022 together with the packet.
  • the service flow unit reports a flow event report (Flow Event Report) to a GW-C 501.
  • the service flow unit may perform one or more of step S1504, step S1505, or step S1507.
  • a specific step performed by the service flow unit that is, a function of the service flow unit, may be configured in the service unit configuration information of the service flow unit when the GW-C 501 adds/modifies the service flow unit. Refer to the third column of Table 1.
  • service flows of a session service type or an interaction service type can be forwarded to the anchor GW-U 502, so as to ensure service continuity when a terminal moves.
  • Service flows of a download service type such as, an Internet download service type, can be directly forwarded to the Internet without passing through the anchor GW-U 502.
  • FIG. 16 shows a procedure of an optional implementation solution of processing the user data by the GW-U 502.
  • a session unit and a content unit in the GW-U 502 are configured to process the user data.
  • the procedure may include the following steps.
  • the session unit receives packet data.
  • the session unit receives packet data sent by another network element, for example, an evolved NodeB (evolved NodeB, eNodeB), an Internet server, an S-GW, a P-GW, an ePDG, or an HSGW.
  • an evolved NodeB evolved NodeB
  • eNodeB evolved NodeB
  • an Internet server for example, an S-GW, a P-GW, an ePDG, or an HSGW.
  • the session unit finds a matched service unit 5022 according to packet data that is used as user data, that is, a content unit in FIG. 16 ; for example, obtains content information from the packet data, performs matching between the content information and that in saved service data information, to determine the content unit configured to process the packet data; and the session unit adds the service data information (for example, the aforementioned meta data) to the packet data and sends the packet data to the determined content unit.
  • the service data information for example, the aforementioned meta data
  • S1603 The session unit forwards the packet data to the matched content unit.
  • the content unit performs content QoS control (flow QoS Control) on the packet data.
  • S1605 The content unit performs content charging (flow Charging) on the packet data.
  • S1606 The content unit forwards a content packet, to output the packet data.
  • the content unit may forward the packet data, based on the meta data in the packet or service unit configuration information configured when the GW-C 501 adds/modifies the content unit.
  • the content unit may forward the packet data to a next service unit 5022 or to another network element, for example, an anchor GW-U 502, an eNodeB, or a PDN, according to the service unit configuration information (for example, a content data forwarding table in Table 1, and the content data forwarding table includes an address or tunnel information of the next-hop service unit 5022 or the next-hop another network element) configured when the GW-C 501 adds/modifies the content unit.
  • the service unit configuration information for example, a content data forwarding table in Table 1, and the content data forwarding table includes an address or tunnel information of the next-hop service unit 5022 or the next-hop another network element
  • uplink user data is forwarded to an anchor GW-U or a PDN is specified in the service unit configuration information (for example, the content data forwarding table in Table 1) configured when the GW-C 501 adds/modifies the content unit.
  • the service unit configuration information for example, the content data forwarding table in Table 1
  • the content unit may alternatively forward the packet to a next service unit 5022 according to a list of service units 5022 in the meta data.
  • the meta data is also forwarded to the next service unit 5022 together with the packet.
  • the content unit reports a content event report (Flow Event Report) to a GW-C 501.
  • the content unit may perform one or more of step S1604, step S1605, or step S1607.
  • a specific step performed by the content unit that is, a function of the content unit, may be configured in the service unit configuration information of the content unit when the GW-C 501 adds/modifies the content unit. Refer to the third column of Table 1.
  • Using the procedure shown in FIG. 16 can implement forwarding, in different manners, of different user data based on user content data. For example, user data of a session service type or an interaction service type can be forwarded to the anchor GW-U 502, so as to ensure service continuity when a terminal moves. User data of a download service type, such as, an Internet download service type, can be directly forwarded to the Internet without passing through the anchor GW-U 502.
  • a download service type such as, an Internet download service type
  • FIG. 17 shows an optional implementation solution of processing user data by a GW-U 502.
  • a session unit, a bearer unit, and a service flow unit in the GW-U 502 are configured to process the user data.
  • a procedure shown in FIG. 17 may include the following steps.
  • steps S1701 to S1704 refer to steps S1401 to S1404, respectively.
  • the bearer unit may be based on a service requirement of the user data and service unit configuration information configured when the GW-C 501 adds/modifies the bearer unit.
  • the bearer unit may forward the packet data to the service flow unit.
  • the service flow unit performs flow QoS control (flow QoS Control) on the packet data.
  • the service flow unit performs flow charging (flow Charging) on the packet data.
  • S1708 The service flow unit forwards a flow packet, to output the packet data.
  • the service flow unit forwards the packet data, based on meta data in the packet data or service unit configuration information of the service flow unit that is configured when the GW-C 501 adds/modifies the service flow unit.
  • the service flow unit may forward the packet data to a next service unit 5022 or to another network element, for example, an anchor GW-U 502, an eNodeB, or a PDN, according to the service unit configuration information (for example, a service flow data forwarding table in Table 1) configured when the GW-C 501 adds/modifies the service flow unit.
  • the service unit configuration information for example, a service flow data forwarding table in Table 1
  • uplink user data is forwarded to an anchor GW-U or a PDN is specified in the service unit configuration information (for example, the service flow data forwarding table in Table 1) configured when the GW-C 501 adds/modifies the service flow unit.
  • the service unit configuration information for example, the service flow data forwarding table in Table 1
  • the service flow unit may alternatively forward the packet to a next service unit 5022 according to a list of service units 5022 in the meta data.
  • the meta data is also forwarded to the next service unit 5022 together with the packet data.
  • uplink user data is forwarded to an anchor GW-U or a PDN is specified in the service unit configuration information (for example, the service flow data forwarding table in Table 1) configured when the GW-C 501 adds/modifies the service flow unit.
  • the service unit configuration information for example, the service flow data forwarding table in Table 1
  • the service flow unit reports a flow event report (Flow Event Report) to a GW-C 501.
  • the service flow unit may perform one or more of step S1706, step S1707, or step S1709.
  • a specific step performed by the service flow unit that is, a function of the service flow unit, may be configured in the service unit configuration information of the service flow unit when the GW-C 501 adds/modifies the service flow unit. Refer to the third column of Table 1.
  • a performing sequence of the bearer unit and the service flow unit may be changeable. This does not affect service data processing. Using the procedure shown in FIG. 17 improves flexibility in user data processing.
  • FIG. 18 shows a procedure of an optional implementation solution of processing user data by a GW-U 502.
  • a session unit, a bearer unit, and a content unit in the GW-U 502 are configured to process the user data.
  • the procedure shown in FIG. 18 may include the following steps.
  • steps S1801 to S180 refer to steps S1401 to S1404, respectively.
  • Functions of the bearer unit such as bearer charging and bearer event reporting, may be removed based on a service requirement of the user data, and service unit configuration information configured when the GW-C 501 adds/modifies the bearer unit.
  • the content unit performs content QoS control (Content QoS Control) on the packet data.
  • the content unit performs content charging (Content Charging) on the packet data.
  • S1808 The content unit forwards a content packet, to output the packet data.
  • the content unit may forward the packet data, based on meta data in the packet data or service unit configuration information of the content unit that is configured when the GW-C 501 adds/modifies the content unit.
  • the content unit may forward the packet data to a next service unit 5022 or to another network element, for example, an anchor GW-U 502, an eNodeB, or a PDN, according to the service unit configuration information (for example, a content data forwarding table in Table 1, and the content data forwarding table includes an address or tunnel information of the next-hop service unit 5022 or the next-hop another network element) configured when the GW-C 501 adds/modifies the content unit.
  • the service unit configuration information for example, a content data forwarding table in Table 1, and the content data forwarding table includes an address or tunnel information of the next-hop service unit 5022 or the next-hop another network element
  • uplink user data is forwarded to an anchor GW-U or a PDN is specified in the service unit configuration information (for example, the content data forwarding table in Table 1) configured when the GW-C 501 adds/modifies the content unit.
  • the service unit configuration information for example, the content data forwarding table in Table 1
  • the content unit may alternatively forward the packet data to a next service unit 5022 according to a list of service units 5022 in the meta data.
  • the meta data is also forwarded to the next service unit 5022 together with the packet.
  • uplink user data is forwarded to an anchor GW-U or a PDN is specified in the service unit configuration information (for example, the content data forwarding table in Table 1) configured when the GW-C 501 adds/modifies the content unit.
  • the service unit configuration information for example, the content data forwarding table in Table 1
  • the content unit reports a content event report (Content Event Report) to a GW-C 501.
  • the content unit may perform one or more of step S1806, step S1807, or step S1809.
  • a specific step performed by the content unit that is, a function of the content unit, may be configured in the service unit configuration information of the content unit when the GW-C 501 adds/modifies the content unit. Refer to the third column of Table 1.
  • the bearer unit and the content unit may be arranged in a reverse order. This does not affect service data processing. Using the procedure shown in FIG. 18 improves flexibility in user data processing.
  • FIG. 19 shows a procedure of an optional implementation solution of processing user data by a GW-U 502.
  • a session unit, a bearer unit, a service flow unit, and a content unit in the GW-U 502 are configured to process the user data.
  • the procedure shown in FIG. 19 may include the following steps.
  • steps S1901 to S1906 refer to steps S1701 to S1706.
  • Functions of the bearer unit such as bearer charging and bearer event reporting, may be removed based on a service requirement of the user data, and service unit configuration information configured when the GW-C 501 adds/modifies the bearer unit.
  • Functions of the service flow unit such as service flow charging and service flow event reporting, may be also removed based on a service requirement of the user data, and service unit configuration information configured when the GW-C 501 adds/modifies the service flow unit.
  • the service flow unit may forward the packet data, based on meta data in a packet or service unit configuration information configured when the GW-C 501 adds/modifies the service flow unit.
  • the content unit performs content QoS control on the packet data.
  • the content unit performs content charging on the packet data.
  • the content unit forwards a content packet, to output the packet data.
  • the content unit may forward the packet data, based on the meta data in the packet or service unit configuration information of the content unit that is configured when the GW-C 501 adds/modifies the content unit.
  • the content unit may forward the packet to a next service unit 5022 or to another network element, for example, an anchor GW-U 502, an eNodeB, or a PDN, according to the service unit configuration information (for example, a content data forwarding table in Table 1) configured when the GW-C 501 adds/modifies the content unit.
  • the service unit configuration information for example, a content data forwarding table in Table 1
  • uplink user data is forwarded to an anchor GW-U or a PDN is specified in the service unit configuration information (for example, the content data forwarding table in Table 1) configured when the GW-C 501 adds/modifies the content unit.
  • the service unit configuration information for example, the content data forwarding table in Table 1
  • the content unit may alternatively forward the packet data to a next service unit 5022 according to a list of service units 5022 in the meta data.
  • the meta data is also forwarded to the next service unit 5022 together with the packet.
  • uplink user data is forwarded to an anchor GW-U or a PDN is specified in the service unit configuration information (for example, the content data forwarding table in Table 1) configured when the GW-C 501 adds/modifies the content unit.
  • the service unit configuration information for example, the content data forwarding table in Table 1
  • the content unit may perform one or more of step S1908, step S1909, or step S1911.
  • a specific step performed by the content unit that is, a function of the content unit, may be configured in the service unit configuration information of the content unit when the GW-C 501 adds/modifies the content unit. Refer to the third column of Table 1.
  • the bearer unit, the service flow unit, and the content unit may be arranged in a reverse order. This does not affect user data processing. Using the procedure shown in FIG. 19 improves flexibility in user data processing.
  • FIG. 20 is a schematic structural diagram of a user data processing apparatus according to an embodiment of the present invention. As shown in FIG. 20 , the apparatus includes:
  • the user data includes service data information
  • the service data information is used to determine a service unit 2002 configured to process the user data.
  • the interface management unit 2001 is specifically configured to determine, according to the service data information, the session unit configured to process the user data.
  • the session unit is specifically configured to determine, according to the service data information, the another service unit 2002 configured to process the user data.
  • the service data information includes:
  • the interface management unit 2001 is specifically configured to use a session unit associated with the IP address of the terminal to which the user data belongs, as the session unit configured to process the user data.
  • the session unit is specifically configured to: if the service data information includes the tunnel information, use a bearer unit associated with the tunnel information, as a bearer unit configured to process the user data; if the service data information includes the IP 5-tuple information, use a service flow unit associated with the IP 5-tuple information, as a service flow unit configured to process the user data; or if the service data information includes the content information, use a content unit associated with the content information, as a content unit configured to process the user data.
  • the service unit 2002 is specifically configured to process the user data separately according to saved service unit configuration information.
  • the service unit configuration information includes information about an operation performed by the service unit 2002 and information about a parameter used by the service unit 2002 when the service unit 2002 processes the user data.
  • the interface management unit 2001 is further configured to: before determining the session unit configured to process the user data, receive a first request message sent by a gateway control plane GW-C, where the first request message is used to add the service unit 2002, and the first request message includes the service data information and the service unit configuration information; add the service unit 2002, save the service data information and the configuration information of the service unit 2002, save an association relationship between the added service unit 2002 and the service data information, and save an association relationship between the added service unit 2002 and the service unit configuration information; or receive a first request message sent by a gateway control plane GW-C, where the first request message is used to add the service unit 2002, and the first request message includes the service data information and identifier information of the service unit configuration information; add the service unit 2002, determine the service unit configuration information according to the identifier information of the service unit configuration information, save the service data information and the determined service unit configuration information, save an association relationship between the added service unit 2002 and the service data information, and save an association relationship between the added service unit 2002 and the service unit.
  • the interface management unit 2001 is further configured to: before determining the session unit configured to process the user data, receive a first request message sent by a gateway control plane GW-C, where the first request message is used to add the service unit 2002 associated with the session unit configured to process the user data, the first request message includes identifier information of the session unit configured to process the user data, the service unit configuration information of the service unit 2002, and some items in the service data information, and the some items include at least one of the tunnel information, the IP 5-tuple, or the application layer identifier; add the service unit 2002, add the some items to the original service data information, save an association relationship between the session unit configured to process the user data and the service unit 2002, save the service data information to which the some items have been added and the service unit configuration information, save an association relationship between the added service unit 2002 and the service data information, and save an association relationship between the added service unit 2002 and the service unit configuration information; or receive a first request message sent by a gateway control plane GW-C, where the first request message is used to add the
  • the first request message further includes unit type information of the service unit 2002, and the unit type information includes a type identifier of the service unit 2002 or an identifier of a template used by the service unit 2002.
  • the interface management unit 2001 is specifically configured to: determine, according to the unit type information of the service unit 2002, the service unit template used by the service unit 2002, and add the service unit 2002 based on the determined service unit template.
  • the interface management unit 2001 is further configured to: before adding the service unit 2002 based on the determined service unit template, receive a second request message sent by the GW-C, where the second request message is used to request to add the service unit template; and add the service unit template after receiving the second request message.
  • the first request message further includes processing order information, and the processing order information is used to indicate a processing order of the service unit 2002 that processes the user data.
  • the session unit is further configured to: after the user data is processed, send, according to the processing order indicated by the processing order information, the user data and the processing order information to a next-hop service unit 2002 indicated by the processing order, so that a subsequent service unit 2002 including the next-hop service unit 2002 processes the user data in the processing order.
  • the GW-U is a local access gateway, and the user data is uplink user data.
  • the service unit configuration information further includes user data forwarding information, and the user data forwarding information is used to indicate: after the service unit 2002 configured to process the user data completes processing the user data, whether to send the processed user data to another GW-U used as a mobile anchor, or to forward the processed user data to a packet data network PDN.
  • the user data forwarding information is determined according to a service type of the user data.
  • a gateway user plane GW-U in which the apparatus shown in FIG. 20 is located is a mobile anchor; or a gateway user plane GW-U in which the apparatus shown in FIG. 20 is located is a local access gateway.
  • the interface management unit 2001 is specifically configured to add the service unit 2002 by creating a service context.
  • the service unit 2002 is specifically configured to process the user data according to the service context that is used when the interface management unit 2001 creates the service unit 2002.
  • the service context is a session context.
  • the service context is a bearer context.
  • the service context is a service flow context.
  • the service context is a content context.
  • GW-U 502. For another optional manner of the apparatus shown in FIG. 20 , refer to the aforementioned GW-U 502.
  • interface management unit 2001 For another optional implementation of the interface management unit 2001, refer to the aforementioned interface management unit 5021.
  • service unit 2002 For another optional implementation of the service unit 5022.
  • functions of receiving the user data and receiving the message in the interface management unit 2001 may be implemented by a receiver, and functions of sending the user data and sending the message may be implemented by a transmitter.
  • Processing functions such as adding the service unit 2002 and determining the service unit 2002 in the interface management unit 2001 may be implemented by a processor.
  • the receiver, the processor, and the transmitter may be integrated into one or more chips for implementation.
  • FIG. 21 is a schematic diagram of a gateway user plane GW-U according to an embodiment of the present invention. As shown in FIG. 21 , the GW-U includes the apparatus shown in FIG. 20 . For another optional implementation of the GW-U, refer to the aforementioned GW-U 502.
  • FIG. 22 is a schematic structural diagram of a gateway configuration apparatus according to an embodiment of the present invention. As shown in FIG. 22 , the apparatus includes:
  • the service unit processing the user data includes a session unit and at least one of a bearer unit, a service flow unit, or a content unit.
  • the session unit is configured to perform session processing
  • the bearer unit is configured to perform bearer processing
  • the service flow unit is configured to perform service flow processing
  • the content unit is configured to perform content processing.
  • the first request message includes service data information associated with the user data and service unit configuration information of the service unit, so that the GW-U saves the service data information and the service unit configuration information and saves an association relationship between the added service unit and the service data information and an association relationship between the added service unit and the service unit configuration information.
  • the first request message includes service data information associated with the user data and identifier information of the service unit configuration information of the service unit, so that the GW-U determines the service unit configuration information according to the identifier information of the service unit configuration information, saves the service data information and the determined service unit configuration information, and saves an association relationship between the added service unit and the service data information and an association relationship between the added service unit and the service unit configuration information.
  • the service data information includes an Internet Protocol IP address of a terminal to which the user data belongs, and at least one of tunnel information used to transmit the user data, IP 5-tuple information used to transmit the user data, or content information of the user data.
  • the service unit configuration information includes information about an operation performed by the service unit and information about a parameter used by the service unit when the service unit processes the user data.
  • the first request message includes identifier information of the session unit configured to process the user data, the service unit configuration information of the service unit, and some items in the service data information, so that the GW-U adds the some items to the original service data information, saves an association relationship between the session unit configured to process the user data and the service unit, saves the service data information to which the some items have been added and the service unit configuration information, and saves an association relationship between the service data information and the service unit and an association relationship between the service unit configuration information and the service unit.
  • the first request message includes identifier information of the session unit configured to process the user data, identifier information of the service unit configuration information of the service unit, and some items in the service data information, so that the GW-U adds the some items to the original service data information, saves an association relationship between the session unit configured to process the user data and the service unit, determines the service unit configuration information according to the identifier information of service unit configuration information, saves the service data information to which the some items have been added and the service unit configuration information, and saves an association relationship between the service data information and the service unit and an association relationship between the service unit configuration information and the service unit.
  • the service data information includes an IP address of a terminal to which the user data belongs, and at least one of tunnel information used to transmit the user data, IP 5-tuple information used to transmit the user data, or content information of the user data.
  • the some items include at least one of the tunnel information, the IP 5-tuple, or the application layer identifier.
  • the service unit configuration information includes information about an operation performed by the service unit and information about a parameter used by the service unit when the service unit processes the user data.
  • the service unit includes a bearer unit.
  • the service unit includes a service flow unit.
  • the service unit includes a content unit.
  • the first request message further includes unit type information of the service unit, and the unit type information includes a type identifier of the service unit or an identifier of a template used by the service unit, so that the GW-U: determines, according to the unit type information of the service unit, the service unit template used by the service unit, and adds the service unit based on the determined service unit template.
  • the sending unit 2202 is further configured to: before sending the first request message to the GW-U, send a second request message to the GW-U, where the second request message is used to request to add the service unit template.
  • the first request message further includes processing order information, and the processing order information is used to indicate a processing order of the service unit that processes the user data in the GW-U.
  • the GW-U is a local access gateway, and the user data is uplink user data.
  • the service unit configuration information further includes user data forwarding information, and the user data forwarding information is used to indicate: after the service unit configured to process the user data completes processing the user data, whether to send the processed user data to another GW-U used as a mobile anchor, or to forward the processed user data to a packet data network PDN.
  • the user data forwarding information is determined according to a service type of the user data.
  • the sending unit 2202 may be implemented by a transmitter, and the processing unit 2201 may be implemented by a processor.
  • the processor and the transmitter may be integrated into one or more chips for implementation.
  • FIG. 23 is a schematic diagram of a gateway control plane GW-C according to an embodiment of the present invention. As shown in FIG. 23 , the GW-C includes the apparatus shown in FIG. 22 . For another optional implementation of the GW-C, refer to the aforementioned GW-C 501.
  • FIG. 24 is a flowchart of a user data processing method according to an embodiment of the present invention. As shown in FIG. 24 , the method includes the following steps.
  • a gateway user plane GW-U receives user data, where the GW-U includes at least two service units configured to process the user data.
  • the GW-U determines a service unit configured to process the user data.
  • the service unit processing the user data includes a session unit and at least one of a bearer unit, a service flow unit, or a content unit.
  • the session unit is configured to perform session processing
  • the bearer unit is configured to perform bearer processing
  • the service flow unit is configured to perform service flow processing
  • the content unit is configured to perform content processing.
  • the GW-U processes the user data by using the determined service unit.
  • the user data includes service data information
  • the service data information is used to determine, in the GW-U, a service unit configured to process the user data.
  • That the GW-U determines a service unit configured to process the user data includes: The GW-U determines, according to the service data information, the service unit configured to process the user data.
  • the service data information includes:
  • the GW-U determines, according to the service data information, the service unit configured to process the user data includes: The GW-U uses a session unit associated with the IP address of the terminal to which the user data belongs, as the session unit configured to process the user data.
  • the GW-U uses a bearer unit associated with the tunnel information, as the bearer unit configured to process the user data. If the service data information includes the IP 5-tuple information, the GW-U uses a service flow unit associated with the IP 5-tuple information, as the service flow unit configured to process the user data. If the service data information includes the content information, the GW-U uses a content unit associated with the content information, as the content unit configured to process the user data.
  • That the GW-U processes the user data by using the determined service unit includes:
  • the GW-U processes the user data by using the determined service unit includes: the determined service unit processes the user data according to saved service unit configuration information of the service unit.
  • the service unit configuration information includes information about an operation performed by the determined service unit and information about a parameter used by the determined service unit when the determined service unit processes the user data.
  • the method further includes:
  • the method further includes:
  • the first request message further includes unit type information of the service unit, and the unit type information includes a type identifier of the service unit or an identifier of a template used by the service unit.
  • the adding the service unit includes: determining, according to the unit type information of the service unit, the service unit template used by the service unit, and adding the service unit based on the determined service unit template.
  • the method before the adding the service unit based on the determined service unit template, the method further includes:
  • the first request message further includes processing order information, and the processing order information is used to indicate a processing order of the service unit that processes the user data.
  • That the GW-U processes the user data by using the determined service unit includes:
  • the GW-U is a local access gateway, and the user data is uplink user data.
  • the service unit configuration information further includes user data forwarding information, and the user data forwarding information is used to indicate: after the service unit configured to process the user data completes processing the user data, whether to send the processed user data to another GW-U used as a mobile anchor, or to forward the processed user data to a packet data network PDN.
  • the user data forwarding information is determined according to a service type of the user data.
  • the GW-U is a mobile anchor, or the GW-U is a local access gateway.
  • the adding the service unit includes: adding the service unit by creating a service context.
  • That the GW-U processes the user data by using the determined service unit includes: The GW-U processes the user data by using the service context used when creating the service unit.
  • the service context is a session context.
  • the service context is a bearer context.
  • the service context is a service flow context.
  • the service context is a content context.
  • An embodiment of the present invention further provides a computer readable medium, including: computer programming code, where the computer programming code enables, when being executed by a computer unit, the computer unit to execute the method shown in FIG. 24 .
  • FIG. 25 is a flowchart of a gateway configuration method according to an embodiment of the present invention. As shown in FIG. 25 , the method includes the following steps.
  • a gateway control plane GW-C determines that a service unit processing user data needs to be added to a gateway user plane GW-U.
  • the GW-C sends a first request message to the GW-U, where the first request message is used to request to add the service unit processing the user data to the GW-U.
  • the service unit processing the user data includes a session unit and at least one of a bearer unit, a service flow unit, or a content unit.
  • the session unit is configured to perform session processing
  • the bearer unit is configured to perform bearer processing
  • the service flow unit is configured to perform service flow processing
  • the content unit is configured to perform content processing.
  • the first request message includes service data information associated with the user data and service unit configuration information of the service unit, so that the GW-U saves the service data information and the service unit configuration information and saves an association relationship between the added service unit and the service data information and an association relationship between the added service unit and the service unit configuration information.
  • the first request message includes service data information associated with the user data and identifier information of the service unit configuration information of the service unit, so that the GW-U determines the service unit configuration information according to the identifier information of the service unit configuration information, saves the service data information and the determined service unit configuration information, and saves an association relationship between the added service unit and the service data information and an association relationship between the added service unit and the service unit configuration information.
  • the service data information includes an Internet Protocol IP address of a terminal to which the user data belongs, and at least one of tunnel information used to transmit the user data, IP 5-tuple information used to transmit the user data, or content information of the user data.
  • the service unit configuration information includes information about an operation performed by the service unit and information about a parameter used by the service unit when the service unit processes the user data.
  • the first request message includes identifier information of the session unit configured to process the user data, the service unit configuration information of the service unit, and some items in the service data information, so that the GW-U adds the some items to the original service data information, saves an association relationship between the session unit configured to process the user data and the service unit, saves the service data information to which the some items have been added and the service unit configuration information, and saves an association relationship between the service data information and the service unit and an association relationship between the service unit configuration information and the service unit.
  • the first request message includes identifier information of the session unit configured to process the user data, identifier information of the service unit configuration information of the service unit, and some items in the service data information, so that the GW-U adds the some items to the original service data information, saves an association relationship between the session unit configured to process the user data and the service unit, determines the service unit configuration information according to the identifier information of service unit configuration information, saves the service data information to which the some items have been added and the service unit configuration information, and saves an association relationship between the service data information and the service unit and an association relationship between the service unit configuration information and the service unit.
  • the service data information includes an IP address of a terminal to which the user data belongs, and at least one of tunnel information used to transmit the user data, IP 5-tuple information used to transmit the user data, or content information of the user data.
  • the some items include at least one of the tunnel information, the IP 5-tuple, or the application layer identifier.
  • the service unit configuration information includes information about an operation performed by the service unit and information about a parameter used by the service unit when the service unit processes the user data.
  • the service unit includes a bearer unit.
  • the service unit includes a service flow unit.
  • the service unit includes a content unit.
  • the first request message further includes unit type information of the service unit, and the unit type information includes a type identifier of the service unit or an identifier of a template used by the service unit, so that the GW-U: determines, according to the unit type information of the service unit, the service unit template used by the service unit, and adds the service unit based on the determined service unit template.
  • the method further includes: sending, by the GW-C, a second request message to the GW-U, where the second request message is used to request to add the service unit template.
  • the first request message further includes processing order information, and the processing order information is used to indicate a processing order of the service unit that processes the user data in the GW-U.
  • the GW-U is a local access gateway, and the user data is uplink user data.
  • the service unit configuration information further includes user data forwarding information, and the user data forwarding information is used to indicate: after the service unit configured to process the user data completes processing the user data, whether to send the processed user data to another GW-U used as a mobile anchor, or to forward the processed user data to a packet data network PDN.
  • the user data forwarding information is determined according to a service type of the user data.
  • An embodiment of the present invention further provides a computer readable medium, including: computer programming code, where the computer programming code enables, when being executed by a computer unit, the computer unit to execute the method shown in FIG. 25 .
  • the GW-U after receiving the user data, determines the service unit configured to process the user data, and processes the user data by using the service unit determined by the GW-U, improving processing flexibility of the GW-U.
  • the GW-C performs a configuration operation, such as adding, modification, and deletion, on the service unit in the GW-U, so that service units in the GW-U can be flexibly combined. Different from that in an existing network, this can avoid frequently changing the GW-U, and the GW-U does not always need to be modified each time service function logic is added. In this way, user data can be flexibly processed according to a service requirement of the user data. For example, a service unit can be flexibly added or removed in a process of processing the user data, so that the GW-U is able to adapt to a future new service type of user data.
  • the GW-U can independently process the user data without interacting with the GW-C. This decreases coupling between the GW-U and the GW-C and reduces signaling overheads, and also decreases coupling between service units in the GW-U.
  • the GW-C may further configure the template of the service unit in the GW-U, so that a service unit can be modified or added to the GW-U based on the existing template. This reduces signaling exchange between the GW-C and the GW-U.
  • the GW-C may deliver, to the GW-U, processing order information of each service unit that is configured to process the user data.
  • the processing order information and the user data may be transmitted between the service units, instead of being returned to the interface management unit to reallocate a service unit to process the user data.
  • the GW-C when configuring the service unit in the GW-U, adds the user data forwarding information to the service unit configuration information, and configures the service unit configuration information for the service unit, to instruct the service unit to send the processed user data to the another GW-U used as a mobile anchor, or to forward the processed user data to the PDN.
  • the GW-C adds the user data forwarding information to the service unit configuration information, and configures the service unit configuration information for the service unit, to instruct the service unit to send the processed user data to the another GW-U used as a mobile anchor, or to forward the processed user data to the PDN.
  • user data that does not need to be processed by the mobile anchor directly enters the PDN. This reduces processing load of the mobile anchor and reduces a delay of transmitting the user data.
  • whether the user data is processed by the mobile anchor may be determined according to the service type of the user data.
  • User data that ensures service continuity is sent to the mobile anchor for processing, so as to ensure service continuity when the terminal moves.
  • the embodiments of the present invention may be provided as a method, a system, or a computer program product. Therefore, the present invention may use a form of hardware only embodiments, software only embodiments, or embodiments with a combination of software and hardware. Moreover, the present invention may use a form of a computer program product that is implemented on one or more computer-usable storage media (including but not limited to a disk memory, a CD-ROM, an optical memory, and the like) that include computer-usable program code.
  • computer-usable storage media including but not limited to a disk memory, a CD-ROM, an optical memory, and the like
  • These computer program instructions may be provided for a general-purpose computer, a dedicated computer, an embedded processor, or a processor of any other programmable data processing device to generate a machine, so that the instructions executed by a computer or a processor of any other programmable data processing device generate an apparatus for implementing a specific function in one or more processes in the flowcharts and/or in one or more blocks in the block diagrams.
  • These computer program instructions may be stored in a computer readable memory that can instruct the computer or any other programmable data processing device to work in a specific manner, so that the instructions stored in the computer readable memory generate an artifact that includes an instruction apparatus.
  • the instruction apparatus implements a specific function in one or more processes in the flowcharts and/or in one or more blocks in the block diagrams.
  • These computer program instructions may be loaded onto a computer or another programmable data processing device, so that a series of operations and steps are performed on the computer or the another programmable device, thereby generating computer-implemented processing. Therefore, the instructions executed on the computer or the another programmable device provide steps for implementing a specific function in one or more processes in the flowcharts and/or in one or more blocks in the block diagrams.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Hardware Design (AREA)
  • Computer Security & Cryptography (AREA)
  • Computing Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Power Engineering (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Telephonic Communication Services (AREA)
EP15902513.9A 2015-08-28 2015-08-28 Method, device and system for processing user data Active EP3322256B1 (en)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2015/088435 WO2017035706A1 (zh) 2015-08-28 2015-08-28 一种用户数据处理装置、方法及系统

Publications (3)

Publication Number Publication Date
EP3322256A4 EP3322256A4 (en) 2018-05-16
EP3322256A1 EP3322256A1 (en) 2018-05-16
EP3322256B1 true EP3322256B1 (en) 2021-06-16

Family

ID=58186449

Family Applications (1)

Application Number Title Priority Date Filing Date
EP15902513.9A Active EP3322256B1 (en) 2015-08-28 2015-08-28 Method, device and system for processing user data

Country Status (6)

Country Link
US (1) US10536457B2 (zh)
EP (1) EP3322256B1 (zh)
JP (1) JP6610976B2 (zh)
CN (1) CN107079523B (zh)
RU (1) RU2691083C1 (zh)
WO (1) WO2017035706A1 (zh)

Families Citing this family (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110620716B (zh) * 2018-06-19 2021-10-01 华为技术有限公司 数据传输方法、相关装置及系统
US11496441B2 (en) * 2018-08-11 2022-11-08 Parallel Wireless, Inc. Network address translation with TEID
WO2020034552A1 (en) 2018-12-28 2020-02-20 Zte Corporation Configuration of user plane functions for wireless systems
US11297075B2 (en) * 2019-07-03 2022-04-05 Microsoft Technology Licensing, Llc Determine suspicious user events using grouped activities
CN114791833B (zh) * 2021-01-25 2024-04-19 中国移动通信有限公司研究院 实现动态话单抽取的方法、装置、设备及存储介质
CN114726829B (zh) * 2022-04-02 2023-09-22 中国电信股份有限公司 通信方法、用户面网关及通信系统
CN116056061B (zh) * 2023-04-03 2023-06-06 深圳恒升应急科技有限公司 一种应急救援紧急通信方法及系统

Family Cites Families (21)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101232389B (zh) * 2007-01-22 2011-02-09 华为技术有限公司 一种提供组播业务的方法、设备及系统
CN101431780B (zh) 2007-11-09 2010-12-22 华为技术有限公司 一种实现网络优化切换的方法、设备及系统
CN102378280B (zh) * 2010-08-12 2015-01-28 中兴通讯股份有限公司 一种实现bbf接入的策略控制方法及系统
US8555067B2 (en) 2010-10-28 2013-10-08 Apple Inc. Methods and apparatus for delivering electronic identification components over a wireless network
EP2721769B1 (en) * 2011-06-17 2018-08-08 Telefonaktiebolaget LM Ericsson (publ) Quality of service for serving node and corresponding method
EP2740310B1 (en) * 2011-08-02 2017-06-14 Telefonaktiebolaget LM Ericsson (publ) Implementation of packet data service in a mobile communication network
CN103636283B (zh) * 2012-06-29 2018-06-05 华为技术有限公司 网关系统、设备和通信方法
CN103636284B (zh) * 2012-06-29 2018-06-05 华为技术有限公司 信息处理方法、转发面设备和控制面设备
US10097481B2 (en) * 2012-06-29 2018-10-09 Juniper Networks, Inc. Methods and apparatus for providing services in distributed switch
CN103731929B (zh) * 2012-10-11 2019-03-15 中兴通讯股份有限公司 承载管理方法、装置及系统
EP2922240B1 (en) * 2012-11-19 2018-01-10 Huawei Technologies Co., Ltd. Method for configuring user data monitoring path, monitoring method, apparatus and entity
US9060308B2 (en) * 2013-01-11 2015-06-16 Lenovo Enterprise Solutions (Singapore) Pte. Ltd. Avoiding network address translation in a mobile data network
JPWO2014199646A1 (ja) * 2013-06-13 2017-02-23 日本電気株式会社 通信システムにおけるサービス品質の制御方法および制御装置、ならびに通信装置
EP3036938A4 (en) * 2013-08-23 2017-04-12 Samsung Electronics Co., Ltd. Mobile software defined networking (mobisdn)
EP2843885A1 (en) * 2013-08-29 2015-03-04 NTT DoCoMo, Inc. Apparatus and method for implementing a packet gateway user plane
US9300453B2 (en) * 2013-11-21 2016-03-29 Cisco Technology, Inc. Providing in-line services through radio access network resources under control of a mobile packet core in a network environment
US9231871B2 (en) * 2013-11-25 2016-01-05 Versa Networks, Inc. Flow distribution table for packet flow load balancing
EP3086513B1 (en) * 2013-12-23 2020-07-29 Huawei Technologies Co., Ltd. Message processing method and gateway
RU2697735C2 (ru) * 2014-02-13 2019-08-19 Нек Корпорейшн Система связи, устройство связи, способ связи и энергонезависимый считываемый компьютером носитель, хранящий программу
CN106105382A (zh) * 2014-02-19 2016-11-09 康维达无线有限责任公司 用于系统间移动性的服务网关扩展
US9787776B2 (en) * 2014-08-29 2017-10-10 Pismo Labs Technology Limited Methods and systems for transmitting packets through an aggregated connection

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
None *

Also Published As

Publication number Publication date
CN107079523A (zh) 2017-08-18
JP2018526903A (ja) 2018-09-13
EP3322256A4 (en) 2018-05-16
US20180205732A1 (en) 2018-07-19
US10536457B2 (en) 2020-01-14
CN107079523B (zh) 2020-09-08
WO2017035706A1 (zh) 2017-03-09
JP6610976B2 (ja) 2019-11-27
EP3322256A1 (en) 2018-05-16
RU2691083C1 (ru) 2019-06-10

Similar Documents

Publication Publication Date Title
EP3322256B1 (en) Method, device and system for processing user data
US10531509B2 (en) Methods and apparatus to support network-based IP flow mobility via multiple wireless accesses for a wireless device
US9787537B2 (en) Customizable mobile broadband network system and method for customizing mobile broadband network
US11533730B2 (en) Network connection configuration method and apparatus
US11129212B2 (en) Core network functions
WO2017008252A1 (zh) 一种ip地址分配的方法和装置
US20130279336A1 (en) Communication system
US9872172B2 (en) Identifying a user equipment in a communication network
CN107431953B (zh) 业务流分流的方法和装置
WO2016180113A1 (zh) WiFi语音业务发起的方法、LTE通信设备、终端及通信系统
US20180027478A1 (en) A device and a method for controlling an ip core network
US20180255481A1 (en) Service flow transmission method and apparatus
KR102109605B1 (ko) 패킷 데이터 네트워크 연결 설정 방법 및 이를 위한 장치
US10701592B2 (en) Service data flow packet transmission method, apparatus, and system
EP3783948A1 (en) Bandwidth constraint in wireless communication networks

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

A4 Supplementary search report drawn up and despatched

Effective date: 20180328

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

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

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

Free format text: STATUS: EXAMINATION IS IN PROGRESS

RIC1 Information provided on ipc code assigned before grant

Ipc: H04W 76/12 20180101AFI20200715BHEP

Ipc: H04W 88/16 20090101ALI20200715BHEP

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

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

Free format text: STATUS: GRANT OF PATENT IS INTENDED

INTG Intention to grant announced

Effective date: 20200821

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAJ Information related to disapproval of communication of intention to grant by the applicant or resumption of examination proceedings by the epo deleted

Free format text: ORIGINAL CODE: EPIDOSDIGR1

GRAL Information related to payment of fee for publishing/printing deleted

Free format text: ORIGINAL CODE: EPIDOSDIGR3

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

Free format text: STATUS: EXAMINATION IS IN PROGRESS

INTC Intention to grant announced (deleted)
GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

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

Free format text: STATUS: GRANT OF PATENT IS INTENDED

RIC1 Information provided on ipc code assigned before grant

Ipc: H04W 88/16 20090101AFI20210115BHEP

Ipc: H04W 76/12 20180101ALI20210115BHEP

Ipc: H04W 76/22 20180101ALI20210115BHEP

Ipc: H04W 36/00 20090101ALN20210115BHEP

INTG Intention to grant announced

Effective date: 20210211

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

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

Free format text: STATUS: THE PATENT HAS BEEN GRANTED

AK Designated contracting states

Kind code of ref document: B1

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

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: CH

Ref legal event code: EP

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 602015070560

Country of ref document: DE

REG Reference to a national code

Ref country code: AT

Ref legal event code: REF

Ref document number: 1403410

Country of ref document: AT

Kind code of ref document: T

Effective date: 20210715

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: LT

Ref legal event code: MG9D

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: FI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210616

Ref country code: LT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210616

Ref country code: HR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210616

Ref country code: BG

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210916

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 1403410

Country of ref document: AT

Kind code of ref document: T

Effective date: 20210616

REG Reference to a national code

Ref country code: NL

Ref legal event code: MP

Effective date: 20210616

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: NO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210916

Ref country code: SE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210616

Ref country code: RS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210616

Ref country code: LV

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210616

Ref country code: GR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210917

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: EE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210616

Ref country code: CZ

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210616

Ref country code: SK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210616

Ref country code: SM

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210616

Ref country code: AT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210616

Ref country code: ES

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210616

Ref country code: RO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210616

Ref country code: PT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20211018

Ref country code: NL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210616

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: PL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210616

REG Reference to a national code

Ref country code: DE

Ref legal event code: R119

Ref document number: 602015070560

Country of ref document: DE

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MC

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210616

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

REG Reference to a national code

Ref country code: BE

Ref legal event code: MM

Effective date: 20210831

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

Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LI

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20210831

Ref country code: DK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210616

Ref country code: CH

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20210831

26N No opposition filed

Effective date: 20220317

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LU

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20210828

Ref country code: AL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210616

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210616

Ref country code: IE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20210828

Ref country code: FR

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20210831

Ref country code: DE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20220301

Ref country code: BE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20210831

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: HU

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT; INVALID AB INITIO

Effective date: 20150828

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: CY

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210616

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: GB

Payment date: 20230706

Year of fee payment: 9

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210616