Classifications

• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L12/00—Data switching networks
  • H04L12/02—Details
  • H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
  • H04L12/1403—Architecture for metering, charging or billing
  • H04L12/1407—Policy-and-charging control [PCC] architecture
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
  • H04L41/08—Configuration management of networks or network elements
  • H04L41/0803—Configuration setting
  • H04L41/0806—Configuration setting for initial configuration or provisioning, e.g. plug-and-play
• • 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/50—Address allocation
  • H04L61/5007—Internet protocol [IP] 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/20—Network architectures or network communication protocols for network security for managing network security; network security policies in general
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04M—TELEPHONIC COMMUNICATION
  • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
  • H04M15/41—Billing record details, i.e. parameters, identifiers, structure of call data record [CDR]
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04M—TELEPHONIC COMMUNICATION
  • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
  • H04M15/66—Policy and charging system
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
  • H04W4/24—Accounting or billing
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W40/00—Communication routing or communication path finding
  • H04W40/02—Communication route or path selection, e.g. power-based or shortest path routing
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
  • H04L41/04—Network management architectures or arrangements
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
  • H04L41/34—Signalling channels for network management communication
  • H04L41/344—Out-of-band transfers
• • 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/50—Address allocation
  • H04L61/5007—Internet protocol [IP] addresses
  • H04L61/5014—Internet protocol [IP] addresses using dynamic host configuration protocol [DHCP] or bootstrap protocol [BOOTP]
• • 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/50—Address allocation
  • H04L61/5007—Internet protocol [IP] addresses
  • H04L61/503—Internet protocol [IP] addresses using an authentication, authorisation and accounting [AAA] protocol, e.g. remote authentication dial-in user service [RADIUS] or Diameter

Definitions

• Gateway system Gateway system, device and communication method
• Embodiments of the present invention relate to the field of wireless communications and, more particularly, to gateway systems, devices, and communication methods. Background technique
• the Universal Terrestrial Radio Access Network is used to implement the wireless access function in the Universal Mobile Terrestrial Service (UMTS) network.
• the UTRAN usually includes multiple Radio Network Controllers (RNCs) and a wireless transmission node NodeB.
• RNCs Radio Network Controllers
• GSM/EDGE Radio Access Network GSM/EDGE Radio Access Network
• GPRS General Packet Radio Service
• GERAN usually includes multiple base stations and base station controllers (BSCs), serving the GPRS Supporting Node (SGSN), which is used to implement route forwarding, mobility management, and session in GPRS/UMTS networks. Functions such as management and user information storage.
• Gateway General Packet Radio Service Support Node is used to connect to the external packet data network (PDN, Packet Data Network).
• PDNs can be Internet (Internet), virtual private networks. (VPN, Virtual Private Network), Internet Protocol (IP, Internet Protocol) multimedia service (IMS, IP Multimedia Service) network, or the wireless application protocol (WAP) network provided by the operator.
• Home Location Register HLR
• the Home Location Register is used to store subscription information and authentication data about the network service.
• the SGSN, GGSN, and HLR are usually used as core network elements. Generally, there are multiple SGSNs, GGSNs, and HLRs in the core network.
• Network element 3GPP TS 23.060 standard are described in the GPRS network structure and processes.
• the user equipment accesses the UTRAN or GERAN through the wireless air interface.
• the UE first initiates a process of attaching to the SGSN through the UTRAN/GERAN.
• the SGSN obtains the subscriber's subscription data and authentication data from the HLR. After the SGSN completes the authentication, the UE is notified to attach and accept.
• PDP Context Password Data Protocol Context
• PDP Context is used to manage the GPRS tunneling protocol (GTP, GPRS) for transmitting user data between SGSN and GGSN. Tunnel Protocol ).
• the SGSN finds the associated GGSN according to the Access Point Name (APN) used in the subscription information, and requests the GGSN to create a PDP Context.
• the GGSN After receiving the PDP Context request, the GGSN returns the IP address and the GTP Tunnel End Identifier (TEID) assigned to the UE to the SGSN.
• the SGSN returns a PDP Context success message to the UE, and notifies the UTRAN or the GERAN to establish a corresponding wireless air interface connection for transmitting user data.
• the uplink data of the UE is forwarded to the corresponding PDN by the GGSN through the SGSN through the UTRAN/GERAN.
• the downlink data from the external PDN is transmitted by the GGSN to the SGSN where the UE is located through the corresponding GTP tunnel according to the IP address of the UE, and then sent by the SGSN to the UE through the GERAN/UTRAN.
• the general-purpose computing platform is more suitable for handling mobility management and session management (that is, the performance of PDP forwarding is very powerful, generally more than ten times that of the general-purpose computing platform, but the signaling processing performance is very weak.
• Gateways such as GGSN are The router data platform is often used to maximize the user data forwarding throughput.
• the SGSN focuses on the control plane signaling of the user equipment, and usually uses a general-purpose computing platform.
• the SGSN is responsible for handling the mobility management signaling and session management signaling of the control plane, and is also responsible for forwarding the user plane data from the RNC to the GGSN.
• the SGSN generally uses a general-purpose computing platform, which has strong ability to handle signaling and has weak data forwarding capabilities. Once the user data traffic grows rapidly, the SGSN needs to be continuously expanded or the number of SGSNs is greatly increased, and the cost is high.
• the user plane data is directly sent from the RNC to the GGSN and the GGSN is forwarded to the external Internet by establishing a direct tunnel in the GGSN and the RNC.
• the SGSN mainly processes the signaling of the control plane and does not forward the data of the user plane.
• the SGSN must reserve a part of the user plane forwarding function to forward the user plane data and increase the complexity of the SGSN.
• E-UTRAN Evolved Universal Terrestrial Radio Access Network
• MME Mobility Management Entity
• TMSI Temporary Mobile Subscriber Identity
• S-GW Serving Gateway
• P-GW Packet Data Network Gateway
• PDN Packet Data Network
• HSS Home Subscriber Server
• the user equipment After the user equipment accesses the E-UTRAN through the wireless air interface, it first attaches to the MME, and the MME obtains the subscription data and the authentication information of the user from the home subscriber server (HSS, Home Subscriber Server), and initiates a process of authenticating the UE.
• the MME completes the authentication process, the user equipment or the MME initiates a process of establishing a bearer for transmitting user data.
• the MME notifies the S-GW to establish a bearer for the user, and the notification message carries the address of the P-GW and the address information of the E-UTRAN network element where the user is located.
• the S-GW establishes a bearer for transmitting user data from the E-UTRAN to the P-GW for the user.
• the P-GW forwards the downlink data from the external PDN to the UE through the bearer, and forwards the uplink data from the UE to the corresponding PDN.
• UE can pass
• the UTRAN or the GERAN and the SGSN access the MME, and can establish a GTP tunnel connection with the S-GW through the UTRAN/GERAN, the SGSN.
• the S-GW converts the GTP tunnel into a corresponding bearer connected to the P-GW for transmitting user data.
• UTRAN can also establish a GTP tunnel that directly connects to the S-GW.
• the MME becomes a network element that only processes control plane signaling, and the S-GW and P-GW are mainly responsible for forwarding user plane data.
• the S-GW and the P-GW can be combined into one network element, generally referred to as a gateway.
• gateway devices need to gradually control the finer services based on the basic data forwarding functions.
• the fee is developed to support the operator's richer business implementation and control.
• the gateway still needs to retain a large number of external signaling interfaces.
• the signaling interfaces include: a GTP-C bearer interface between the MME and the gateway, a Policy Control and Charging (PCC) interface between the PCRF and the gateway, a charging interface between the charging system and the gateway, a lawful intercepting device, and The lawful interception interface between the gateways, the DHCP interface between the DHCP (Dynamic Host Configuration Protocol) server and the gateway, and the AAA (Authentication, Authorization and Accounting) server and the gateway L2TP (Layer 2 Tunneling Protocol)/GRE between interface, VPN and gateway (Generic Routing Encapsulation, general routing to armor) ten-party interface.
• PCC Policy Control and Charging
• a large number of external signaling interfaces of the gateway will bring a lot of interface signaling.
• a router-based gateway handles a large amount of interface signaling, it is limited by the hardware platform, and the performance of processing signaling is very low.
• the dedicated routing and forwarding processor chip has almost no ability to process signaling.
• the gateway needs to add a large number of hardware such as general-purpose computing processor chips on the router platform, which makes the hardware platform of the gateway device very complicated and costly, which is not conducive to the promotion and deployment of the mobile packet data network. . Summary of the invention
• the embodiment of the invention provides a gateway system, a device and a communication method, which can flexibly deploy a mobile packet data network.
• the first aspect provides a gateway system, including: a control plane entity and at least one user plane entity, where the control plane entity is configured to allocate an internet protocol IP address to the user equipment UE, and generate a data path according to the IP address.
• the configuration information, the configuration information of the data path is sent to the user plane entity, where the data path is used by the user plane entity to connect to a radio access network RAN, a packet data network PDN or other network element; And being located between the PDN and the RAN, and connected to the control plane entity, configured to receive configuration information of the data path sent by the control plane entity, according to configuration information of the data path,
• the uplink and downlink data of the UE are forwarded on the data path.
• the second aspect provides a control plane gateway device, including: an internet protocol IP address allocation module, configured to allocate an IP address to the user equipment UE; and a data path configuration module, configured to allocate an IP address according to the IP address allocation module Generating configuration information of the data path, and transmitting the configuration information of the data path to the user plane gateway device, where the data path is used by the user plane gateway device to connect to the radio access network RAN, the packet data network PDN, or other network element, where The user plane gateway device is located between the PDN and the RAN.
• an internet protocol IP address allocation module configured to allocate an IP address to the user equipment UE
• a data path configuration module configured to allocate an IP address according to the IP address allocation module Generating configuration information of the data path, and transmitting the configuration information of the data path to the user plane gateway device, where the data path is used by the user plane gateway device to connect to the radio access network RAN, the packet data network PDN, or other network element, where The user plane gateway device is located between the PDN and the RAN.
• a user plane gateway device including: a data path management module, configured to be connected to a control plane gateway device, configured to receive configuration information of a data path from the control plane gateway device, according to the configuration of the data path
• the data management module is configured to be connected to the data path management module, and configured to forward uplink and downlink data of the user equipment UE on the data path managed by the data path management module, where the data path is used by Connecting to the user plane gateway device, the radio access network RAN, the packet data network PDN or other network element, the user plane
• the gateway device is located between the PDN and the RAN and is independent of the control plane gateway device.
• a fourth aspect provides a communication method in a gateway system, where the gateway system includes a control plane entity and at least one user plane entity, the control plane entity is independent of the user plane entity, and the user plane entity is located in a grouping Between the data network PDN and the radio access network RAN, the method includes: the control plane entity allocates an internet protocol IP address to the user equipment UE, generates configuration information of the data path according to the IP address, and sends the data path Configuring information to the user plane entity, the data path is used by the user plane entity to connect to the radio access network RAN, the packet data network PDN or other network element; the user plane entity receives the location sent by the control plane entity The configuration information of the data path, and the uplink and downlink data of the UE is forwarded on the data path.
• the control plane entity allocates an internet protocol IP address to the user equipment UE, generates configuration information of the data path according to the IP address, and sends the data path Configuring information to the user plane entity, the data path is used by the user plane entity to
• the gateway system in the embodiment of the present invention is composed of control plane entities and user plane entities independent of each other, the control plane entity is responsible for configuring the data path, the user plane entity is responsible for data forwarding on the data path, and all gateway entities make network deployment more convenient. And the cost is lower.
• FIG. 1 is a block diagram of a gateway system in accordance with an embodiment of the present invention.
• FIG. 2 is a schematic structural diagram of a communication system applicable to a gateway system according to an embodiment of the present invention
• FIG. 3 is a schematic block diagram of a control plane gateway device according to an embodiment of the present invention
• FIG. 4 is a schematic block diagram of a user plane gateway device according to an embodiment of the present invention.
• FIG. 5 is a schematic structural diagram of a gateway system according to another embodiment of the present invention.
• FIG. 6 is a schematic structural diagram of a gateway system according to another embodiment of the present invention.
• FIG. 7 is a schematic structural diagram of a gateway system according to another embodiment of the present invention.
• FIG. 8 is a schematic structural diagram of a gateway system according to another embodiment of the present invention.
• FIG. 9 is a flow chart of a communication method according to an embodiment of the present invention.
• FIG. 10 is a schematic diagram of a process of configuring a data path between GW-C and GW-U;
• FIG. 13 is a schematic diagram of a communication flow between a gateway system and other network elements according to another embodiment of the present invention.
• FIG. 14 is a schematic diagram of a process for a gateway system to activate a PDP for a UE according to another embodiment of the present invention
• FIG. 15 is a schematic diagram of an interaction process between a gateway system and a Radius or Diameter server according to another embodiment of the present invention
• FIG. 16 is a schematic diagram of a policy control flow of a gateway system according to another embodiment of the present invention.
• FIG. 17 is a schematic diagram of a policy control flow of a gateway system according to another embodiment of the present invention.
• GSM Global System of Mobile Communication
• CDMA Code Division Multiple Access
• WCDMA Wideband Code Division Multiple Access
• GPRS General Packet Radio Service
• LTE Long Term Evolution
• a user equipment which may also be called a mobile terminal (Mobile Terminal), a mobile user equipment, etc., may communicate with one or more core networks via a radio access network (eg, RAN, Radio Access Network).
• the user equipment may be a mobile terminal, such as a mobile phone (or "cellular" phone) and a computer with a mobile terminal, for example, a mobile device that can be portable, pocket, handheld, computer built, or in-vehicle,
• the wireless access network exchanges languages and/or data.
• the base station system of the radio access network may include one or more BTS (BTS, Base Transceiver Station) supporting GSM or CDMA, and a Base Station Switch Center (BSC), and may also include one or more nodes supporting WCDMA.
• the mobility management network element may be an SGSN in the UTRAN or the GERAN, or may be an MME in the E-UTRAN, or may be an SGSN, an MME, or a combination of the two in the UTRAN/GERAN or E-UTRAN joint networking.
• the invention is not limited.
• the two components when a component is described as being "connected" to another component, the two components may be directly connected or indirectly connected through one or more other components.
• the above direct or indirect connections may include wired and/or wireless connections.
• the wired method may include, but is not limited to, a cable composed of various media, such as an optical fiber, a conductive cable, or a semiconductor circuit; or other forms such as an internal bus, a circuit, a backplane, and the like.
• the wireless mode is a connection method capable of wireless communication, including but not limited to radio frequency, infrared, Bluetooth, and the like.
• the gateway system 100 of Figure 1 includes a control plane entity 101 and one or more user plane entities 102-1 through 102-N, where N is a positive integer.
• the user plane entities 102-1 to 102-N may be collectively referred to as a user plane entity 102.
• the control plane entity 101 is configured to allocate an IP address to the UE, and configure the user plane entity 102 to connect to a radio access network (RAN), a packet data network (PDN), or other network element data according to the IP address. path.
• RAN radio access network
• PDN packet data network
• configuring the data path according to the IP address may include: generating configuration information of the data path according to the IP address allocated for the UE, and sending the data path to the user plane entity 102.
• the control plane entity can be connected to the mobility management entity or integrated with the mobility management entity.
• the control plane entity may also be connected to a Serving Gateway (S-GW), which connects to the Mobility Management Entity.
• S-GW Serving Gateway
• control plane entity may be referred to as a Control Plane Gateway, and may also be referred to as a Gateway Controller, a Control Node, or a Control Gateway.
• the control plane entity 101 is integrated with the mobility management network element, that is, the control plane entity 101 and the mobility management network element can be implemented on the same platform.
• the control plane entity 101 is connected to the mobility management network element, and the control plane entity 101 and the mobility management network element may be implemented by independent platforms and connected to each other, but the platforms for implementing the two may be of the same type or different types.
• the embodiment of the invention is not limited thereto.
• the user plane entity 102 is located between the PDN and the RAN and is connected to the control plane entity 101.
• User The polygon entity 102 is configured to receive configuration information of the data path sent by the control plane entity 101, and forward the uplink and downlink data of the UE on the data path configured by the control plane entity 101.
• GW-U user plane entity
• GW-U may be referred to as a User Plane Gateway, and may also be referred to as a Packet Data Forwarding Gateway, a Forwarding Node, or a Switching Node. Node ).
• the user plane entity 102 is the node to which the data path is connected, but the control plane entity 101 is not the node to which the data path is connected.
• control plane entity 101 and the user plane entity 102 of the present system can further expand its functions.
• control plane entity 101 may be further configured to acquire load information of the multiple user plane entities from multiple user plane entities or network management network elements, and select the user with the lightest load from the multiple user plane entities.
• the face entity generates configuration information of the data path according to the IP address and information of the lightest user plane entity, and sends configuration information of the data path to the user plane entity with the lightest load.
• control plane entity 101 may be further configured to obtain an IP address resource from the user plane entity or obtain an IP address resource from an internal configuration of the control plane entity, and allocate an IP to the UE from the IP address resource. address.
• control plane entity 101 can be further configured to forward an IP message between the user plane entity and the PDN.
• the user plane entity 102 may be further configured to collect usage information of the data path, and send the usage information to the control plane entity.
• the control plane entity 102 may further be configured to receive the usage information. The bill is generated according to the usage information, and the bill is reported to the billing system.
• control plane entity 101 may be further configured to acquire policy information from a policy and charging rule function PCRF device configured internally or located outside the control plane entity, and obtain QoS information from the policy information, where the data path
• the configuration information includes the QoS information.
• the user plane entity 102 is further configured to: when forwarding the uplink and downlink data of the UE on the data path, control uplink and downlink data of the UE according to the QoS information. service quality.
• the gateway system of the embodiment of the present invention is composed of control plane entities and user plane entities independent of each other, the control plane entity is responsible for configuring the data path, and the user plane entity is responsible for data on the data path. All gateway entities need to be replaced, making network deployment more convenient and less expensive. At the same time, due to the adoption of the separation of the control plane and the user plane, the design and implementation of the device is simplified compared to the original gateway device, and the processing performance is improved.
• the traffic can be shared without excessive modification of the control plane entity, which makes the network deployment more compact and reliable.
• a communication system there may be one or more groups of gateway systems 100, replacing all or part of the functions of the S-GW, P-GW or GGSN as a whole, or replacing any of them. combination.
• FIG. 2 is a schematic structural diagram of a communication system applicable to a gateway system according to an embodiment of the present invention.
• GW-C control plane entity
• GW-U user plane entity
• the communication system 200 further includes a UE 201, a RAN 202, a mobility management network element 203, a PDN 204, and the like.
• the number of these network elements is not limited in the embodiment of the present invention.
• the RAN 202 may include access network elements such as RNC, eNodeB, etc. of various systems (e.g., GERAN, UTRAN, or E-UTRAN).
• the PDN 204 may be in the form of a WAP, an Internet, a VPN, or the like, which is not limited in this embodiment of the present invention.
• control plane entity 101 can be implemented by a general purpose computing platform
• user plane entity 102 can be implemented by a dedicated router platform.
• the general-purpose computing platform is suitable for processing interface signaling; the signaling processing capability of the dedicated router platform is relatively low, but the efficiency of data forwarding is high. This can reduce the design of the hardware platform, reduce the cost of the hardware platform, and greatly improve the processing performance of the gateway control plane entity and user plane entity.
• the mobility management network element 203 can be an MME and/or an SGSN, typically implemented by a general purpose computing platform.
• the control plane entity 101 and the mobility control network element 203 can be grouped together, as shown by the dashed box 205 of Figure 2, which enables the number of network elements in the fine tube system.
• the radio link between the UE 201 and the RAN 202, the connection between the RAN 202 and the GW-U 102, and the connection between the GW-U 102 and the PDN 204 constitute data of the UE 201. path.
• the data path of the UE 201 is not limited to such a specific form.
• the data path may be a connection or tunnel between the RAN and the GW-U, between the GW-U and other gateways for forwarding data of the UE, eg, a GTP tunnel, a GRE connection, a traffic stream, and the like. Number
• the path can be either a bearer granularity or a granularity of the traffic data flow.
• the data path can also be a data connection between the user plane gateway and the VPN of the PDN.
• control plane gateway device 30 of FIG. 3 is an example of the control plane entity 101 of FIG. 1, including an IP address assignment module 31 and a data path configuration module 32.
• the IP address allocation module 31 is configured to allocate an IP address to the user equipment UE.
• the data path configuration module 32 is configured to generate configuration information of the data path according to the IP address assigned by the IP address allocation module 31.
• the data path configuration module 32 can also transmit the configuration information of the generated data path to the user plane gateway device 40.
• the configuration information can also be sent to the user plane gateway device 40 by other modules having the transmitting function.
• the above data path is used by the user plane gateway device 40 to connect to the RAN, PDN or other network element, wherein the user plane gateway device 40 is located between the PDN and the RAN and is independent of the control plane gateway device 30.
• IP address allocation module 31 or data path configuration module 32 can be implemented by a corresponding processor, circuit, receiver or transmitter.
• control plane gateway devices or referred to as control plane entities, gateway controllers, control nodes, control gateways, etc.
• control plane entities or referred to as control plane entities, gateway controllers, control nodes, control gateways, etc.
• connection between the IP address allocation module 31 and the data path configuration module 32 may be a direct connection or an indirect connection via one or more other modules, which is not limited by the embodiment of the present invention.
• FIG. 4 is a schematic block diagram of a user plane gateway device in accordance with an embodiment of the present invention.
• the user plane gateway device 40 of FIG. 4 is an example of the user plane entity 102 of FIG. 1, including a data path management module 41 and a data forwarding module 42.
• the data path management module 41 is connected to the control plane gateway device (for example, the control plane entity 101 shown in FIG. 1 or the control plane gateway device 30 shown in FIG. 3), and is configured to receive configuration information of the data path from the control plane gateway device, according to Configure the information management data path.
• control plane gateway device for example, the control plane entity 101 shown in FIG. 1 or the control plane gateway device 30 shown in FIG. 3
• the data forwarding module 42 is connected to the data path management module 41 for forwarding data on the data path managed by the data path management module 41, for example, forwarding uplink and downlink data of the user equipment UE.
• the above data path is used by the user plane gateway device 40 to connect to the RAN, PDN or other gateway.
• the user plane gateway device 40 is located between the PDN and the RAN and is independent of the above-described control plane gateway device.
• the connection between the data path management module 41 and the data forwarding module 42 may be a direct connection, or may be an indirect connection through one or more other modules, which is not limited by the embodiment of the present invention.
• the data path management module 41 in FIG. 4 can be implemented by a processor, or a corresponding circuit implementation, and the data forwarding module can be implemented by a receiver or a transmitter.
• FIG. 5 is a schematic structural diagram of a gateway system according to another embodiment of the present invention.
• the gateway system of Figure 5 includes GW-C 310 and GW-U 320.
• GW-C 310 and GW-U 320 For the sake of cleaning, only one GW-C and one GW-U are depicted in FIG. 5, but the number of entities of the gateway system in the embodiment of the present invention is not limited.
• the GW-C 310 includes a data path configuration module 311, configured to generate configuration information of a data path for forwarding uplink and downlink data of the UE.
• the data path configuration module 311 can also transmit configuration information of the generated data path to the GW-U 320.
• the GW-U 320 includes a data path management module 321 and a data forwarding module 322.
• the data path management module 321 is connected to the data path configuration module 311 of the GW-C 310, and is configured to receive the configuration information from the data path configuration module 311, and manage the data path of the uplink and downlink data of the forwarding UE according to the configuration information.
• the management of the data path may include the establishment, modification, update or deletion of the data path.
• the data forwarding module 322 is connected to the data path management module 321 for forwarding uplink and downlink data of the UE on the data path managed by the data path management module 321.
• the configuration information generated by the data path configuration module 311 may include at least one of the following: the identifier information of the GW-C 310, and the identifier information of the peer network element of the GW-U 320 on the data path. , data path information, associated information of the data path, and so on.
• the foregoing identification information may include at least one of the following: an IP address, a MAC (Media Access Control) address, a port number, a protocol type, and the like.
• the foregoing data path information may include at least one of the following: a data path protocol, a data path identifier, PDN connection information, bearer information, QoS (Quality of Service) information, and service data.
• Flow information billing method information.
• Examples of data path protocols include GTPvl, L2TP, GRE, IPsec, and the like.
• Examples of the data path identifier include a bearer identifier, a tunnel identifier of the L2TP protocol, a GRE key, a tunnel identifier, and the like.
• Examples of PDN connection information include PDN connection identification, APN, and the like.
• Examples of bearer information include bearer identification, proprietary bearer identification, and the like.
• QoS information examples include QCI (QoS Class Identifier, QoS) Classification ID), Maximum Bandwidth, Guaranteed Bandwidth, ARP (Allocation/Retention Priority), DSCP (Differentiated Services Code Point) Information, Service Data Flow Information (contains one or more IPs) A quintuple filter, and QoS information related to the traffic data flow).
• QCI QoS Class Identifier, QoS) Classification ID
• Maximum Bandwidth Guaranteed Bandwidth
• ARP Allocation/Retention Priority
• DSCP Differentiated Services Code Point
• Service Data Flow Information (contains one or more IPs)
• a quintuple filter A quintuple filter
• QoS information related to the traffic data flow examples include QCI (QoS Class Identifier, QoS) Classification ID), Maximum Bandwidth, Guaranteed Bandwidth, ARP (Allocation/Retention Priority), DSCP (Differentiated Services
• the peer network element may include at least one of the following: a RAN network element, a VPN network element, an S-GW, a P-GW, a packet data gateway PDG, and an SGSN for data forwarding. and many more.
• the peer network element can be a neighboring node of the GW-U on the data path.
• the association information of the foregoing data path may include at least one of the following: association information of the UE and the data path, association information of the service data flow and the data path of the UE, and a data path connecting the PDN and The association information between the data paths connecting the RAN, the association information between the data path connecting the PDN and the data path connecting the other gateways, the data path connecting the other gateways, and the association information between the data paths connecting the RANs.
• the associated information of the data path is typically used to forward the data packet to the associated data path when the GW-U receives the downstream data packet.
• the associated information of the data path can usually use UE information.
• the UE information typically includes at least one of the following: an IP address of the UE, a MAC address, other information used to identify the UE (e.g., IMSI, MSISDN, or IMEI, etc.).
• the GW-U when the GW-U receives the downlink data packet, it can forward the data packet to the data path of the uplink and downlink data of the forwarding UE matching the destination IP address according to the destination IP address of the data packet.
• the associated information of the data path can also use the service data flow information, such as the IP quintuple of the data packet (source IP address, destination IP address, source port number, destination port number, and protocol type).
• the GW-U can also forward the downlink data packet to the data path having the service data stream information matching the IP quintuple of the data packet.
• the association information of the data path may also be association information between the data path connecting the PDN and the data path connecting the RAN.
• the GW-U may forward the downlink data packet to the corresponding data path connected to the RAN according to the association information.
• the GW-U can forward the downlink data packet to the corresponding data path connected to the PDN according to the associated information.
• the data path configuration module 311 can also comprehensively consider the load conditions of multiple GW-Us 320. For example, the data path configuration module 311 can obtain load information of multiple GW-Us 320 from multiple GW-Us 320 or network management network elements, and according to load information of multiple GW-Us 320, to load lighter or most The light GW-U 320 sends configuration information for the data path. Alternatively, the data path configuration module 311 can generate configuration information of the data path according to the load weight information of the multiple GW-Us 320, so that the load between the multiple GW-Us 320 is balanced. This can make the load of the user plane entity more balanced and improve system efficiency.
• the GW-C 310 may further include a session management module 312.
• the session management module 312 is coupled to the data path configuration module 311.
• Session management module 312 is used to process session signaling.
• the session signaling includes at least one of: a GTP-C message (S11, S4 or GnGp interface message) between the GW-C 310 and the mobility management network element MME/SGSN, RAN (eg, GERAN, UTRAN or E-) GTP-U messages transmitted between the interface between UTRAN and GW-U 320 (S1-U interface or Iu interface), IP messages between GW-U 320 and PDN (including authentication, authorization, and accounting messages, L2TP messages and GRE protocol messages, etc.).
• GTP-C message S11, S4 or GnGp interface message
• MME/SGSN mobility management network element
• RAN eg, GERAN, UTRAN or E-
• GTP-U messages transmitted between the interface between UTRAN and GW
• the GTP-C message includes an interaction message for the UE to create, modify (update) and delete the bearer or the PDP.
• the bearer or PDP is used to forward the data of the user plane of the UE between the GW-U and the RAN.
• Examples of GTP-U messages include, but are not limited to, echo (Echo) messages and error indication (Error Indication) messages and the like.
• the GW-U 320 may further include an IP message forwarding module 323, and is connected to the session management module 312 of the GW-C 310 and the data forwarding module 322 of the GW-U 320. And for forwarding the foregoing IP message between the PDN and the session management module 312 via the data forwarding module 322.
• the IP message is a management message of the IP path between the GW-C 310 managing the GW-U 320 and the VPN gateway of the PDN, and may include, for example, L2TP, GRE, and other IP path management messages.
• the IP message forwarding module 323 can be combined with the data forwarding module 322 into one module, so that the IP message can be directly forwarded to the GW-C 310 or PDN.
• the GW-C 310 may further include an IP address allocation module 313.
• the IP address assignment module 313 assigns an IP address to the UE.
• the IP address assignment module 313 can be coupled to the session management module 312 of the GW-C 310 for assigning an IP address to the UE based on the request of the session management module 312.
• the IP address allocation module 313 can directly send the assigned IP address to the data path configuration module 311, or can be located via the session management module 312.
• the assigned IP address is sent to the data path configuration module 311, which is not limited in this embodiment of the present invention.
• the session management module 312 can request the IP address assignment module 313 to assign an IP address to the UE.
• the IP address assignment module 313 can obtain an IP address resource (eg, an IP pool) from the GW-U 320 or obtain an IP address resource from an internal configuration of the GW-C 310, select an IP address for the UE from the IP address resource, and select the IP address.
• the address is assigned to the UE.
• the IP address assignment module 313 may acquire an IP address from a server located outside the GW-C 310 (such as the AAA server or DHCP server illustrated in FIG. 5) and assign the acquired IP address to the UE.
• FIG. 6 is a schematic structural diagram of a gateway system according to another embodiment of the present invention.
• the gateway system of Figure 6 includes GW-C 410 and GW-U 420.
• GW-C 410 and GW-U 420 For the sake of cleaning, only one GW-C and one GW-U are depicted in FIG. 6, but the number of entities of the gateway system in the embodiment of the present invention is not limited.
• the GW-C 410 may also include a client module 411.
• the client module 411 is connected to the session management module 312 and is connected to the server 430 in the PDN for obtaining the result of the server 430 authenticating or authorizing the UE when the UE newly creates the data path.
• the server 430 in the above PDN may be a Radius (Remote Authentication Dial In User Service) or a Diameter server.
• the client module 411 can also obtain the newly created IP address of the UE by interacting with the server 430, and the IP address allocation module allocates the IP address to the newly created IP address of the UE.
• the client module 411 can obtain the peer network element information and data path information of the VPN through interaction with the server 430.
• the UE can be made to access the external PDN more securely.
• FIG. 7 is a schematic structural diagram of a gateway system according to another embodiment of the present invention.
• the gateway system of Figure 7 includes GW-C 510 and GW-U 520.
• GW-C 510 and GW-U 520 For the sake of cleaning, only one GW-C and one GW-U are depicted in FIG. 7, but the number of entities of the gateway system in the embodiment of the present invention is not limited.
• the GW-C 510 further includes a PCEF (Policy Control and Charging Enforcement Function) module 511.
• the PCEF module 511 is connected to the data path configuration module 311 or to the session management module 312 for internal configuration or at GW-C.
• 510 external PCRF (Policy and Charging Rules Function) device acquires policy information, obtains QoS information from the policy information, and sends QoS information to the data path configuration module 311 or to the data path through the session management module 312.
• the configuration module 311 sends QoS information.
• the data path configuration module 311 can receive the QoS information and include the QoS information in the data path information of the generated configuration information.
• the data forwarding module 322 can control the quality of service of the uplink and downlink data according to the QoS information in the process of forwarding the uplink and downlink data of the UE.
• FIG. 8 is a schematic structural diagram of a gateway system according to another embodiment of the present invention.
• the gateway system of Figure 8 includes GW-C 610 and GW-U 620.
• GW-C 610 and GW-U 620 For the sake of cleaning, only one GW-C and one GW-U are depicted in FIG. 8, but the number of entities of the gateway system in the embodiment of the present invention is not limited.
• the forwarding module 621 implements the IP message forwarding function and the data forwarding function at the same time, corresponding to the combination of the data forwarding module 322 and the IP message forwarding module 323 in FIG. 6, but the forwarding module 621 can also It is similarly implemented by two modules, which is not limited by the embodiment of the present invention.
• the GW-C 610 further includes a billing module 611. It is connected to the forwarding module 621 (or the data forwarding module 322) of the GW-U 620, and is connected to the charging system 640 located outside the GW-C 610.
• the forwarding module 621 (or the data forwarding module 322) can collect the usage information of the data path, for example, the data traffic of the data path, the data traffic of the service data stream, the duration, and the like, and report the usage information to the charging module 611.
• the billing module 611 can generate a bill according to the usage information, and report the generated bill to the billing system 640.
• the session management module 312 notifies the charging module 611 of the connection establishment, and the charging module 611 notifies the session management module 312 of the charging mode information (the user usage information reporting mode: for example, the reporting time interval, Traffic interval and reporting granularity, etc.).
• the charging mode information the user usage information reporting mode: for example, the reporting time interval, Traffic interval and reporting granularity, etc.
• the data path information in the data path configuration information includes the charging mode information.
• the data path management module 321 of the GW-U 620 configures the charging mode information in the data path.
• the forwarding module 621 (or the data forwarding module 322) reports the usage information to the charging module 611 according to the charging mode.
• gateway systems in accordance with embodiments of the present invention have been described above. It should be noted that the above examples are not intended to be exhaustive of all possible implementations of the gateway system of the embodiments of the present invention.
• the modules described in the embodiments of FIG. 3-8 may be recombined, merged, or split. Such modified gateway systems are all within the scope of the embodiments of the present invention, as long as the gateway system can implement the control. The separation of the surface function and the user plane function is sufficient.
• the gateway system 100 includes a control plane entity (GW-C) and one or more user plane entities (GW-U), and the control plane entity is connected to the mobility management network element or integrated with the mobility management network element, and the user plane entity is located. Between the PDN and the RAN, independent of the control plane entity and connected to the control plane entity.
• GW-C control plane entity
• GW-U user plane entities
• the control plane entity configures a data path of the user plane entity to connect to the RAN, the PDN, or other network element. For example, the control plane entity generates configuration information of the data path according to the IP address allocated for the UE, and sends configuration information of the data path to the user plane entity.
• the other network elements herein may be other gateways except the control plane entity and the user plane entity.
• the user plane entity forwards uplink and downlink data of the UE on a data path configured by the control plane entity. For example, the user plane entity receives configuration information of a data path sent by the control plane entity, and forwards the context of the UE on the data path according to the configuration information.
• the gateway system in the embodiment of the present invention is composed of control plane entities and user plane entities independent of each other, the control plane entity is responsible for configuring the data path, the user plane entity is responsible for data forwarding on the data path, and all gateway entities make network deployment more convenient. And the cost is lower.
• the design and implementation of the device is simplified compared to the original gateway device, and the processing performance is improved.
• the method of Fig. 9 can be implemented by the gateway system of Figs. 1-8, and thus the repeated description is omitted as appropriate.
• the control plane entity may generate configuration information of a data path for forwarding uplink and downlink data of the UE, and send the configuration information to the user plane entity.
• the user plane entity may receive the configuration information from the control plane entity, manage the data path of the uplink and downlink data of the forwarding UE according to the configuration information, and forward the uplink and downlink data of the UE on the managed data path.
• the configuration information may include at least one of the following: the identifier information of the user plane entity, the identifier information of the peer network element of the user plane entity on the data path, the data path information, and the data path. Associated information.
• the identifier information may include at least one of the following: an IP address, a MAC address, a port number, and a protocol type.
• the data path information may include at least one of the following: a data path protocol, a data path identifier, PDN connection information, bearer information, QoS information, service data flow information, and charging mode information.
• the association information of the data path may include at least one of: association information of the UE and the data path, association information of the service data flow and the data path of the UE, a data path and a connection of the PDN. Correlation information between the data paths of the RAN, the association information between the data path connecting the PDN and the data path connecting the other gateways, the data path connecting the other gateways, and the data path connecting the RAN.
• the peer network element may include at least one of the following: a RAN network element, a VPN network element, an S-GW, a P-GW, a PDG, and an SGSN for data forwarding.
• control plane entity may allocate an IP address to the UE when receiving the connection establishment request of the UE.
• control plane entity may obtain an IP address resource from the user plane entity or obtain an IP address resource from the internal configuration of the control plane entity, select an IP address for the UE from the IP address resource, and assign the selected IP address to the UE.
• control plane entity may obtain an IP address from a server located outside the control plane entity and assign the acquired IP address to the UE.
• control plane entity may send an access request message or an authorization and authentication request message to a server (such as a Radius or Diameter server) outside the control plane entity when receiving the connection establishment request of the UE. And assigning an IP address to the UE according to the access response message or the authentication and authorization response message returned by the server. At this point, the UE can be guaranteed to perform data transmission more securely.
• a server such as a Radius or Diameter server
• control plane entity may receive the policy information for the UE sent by the PCRF device, and obtain the QoS information from the policy information, so as to be in the configuration information of the generated data path. This QoS information is included. At this time, the quality of service of the data transmission of the UE can be better guaranteed.
• the user plane entity may also collect usage information of the data path, The usage information is reported to the control plane entity.
• the control plane entity can generate a bill according to the usage information, and report the generated bill to the billing system. In this way, the billing function of the data transmission of the UE can be realized.
• Figure 10 is a schematic diagram showing the flow of configuring a data path between GW-C and GW-U.
• the method of Figure 10 can be implemented by the gateway system of Figures 1-8.
• the GW-C receives a message for establishing a connection (for example, creating a session, creating a PDP, and the like).
• the message may include the IP address type (PDN type) of the UE, the access point name APN, the peer network element information (optional), and the data path identification information (optional).
• GW-C allocates an IP address to the UE.
• the IP address allocated by the GW-C may be obtained from an address pool inside the GW-C, or may be an IP address obtained from an external DHCP server or an AAA server.
• the IP address type of the UE is IPv4
• the GW-C allocates an IPv4 address to the UE.
• the IP address type (PDN type) of the UE is IPv6, the GW-C allocates an IPv6 address prefix to the UE.
• the IP address type (PDN type) of the UE is IPv4v6, the Bay' J GW-C must allocate an IPv4 address to the UE and also assign an IPv6 address prefix.
• the APN IP address type (PDN type) can be configured on the GW-C, and the IPv4 and/or IPv6 address is allocated to the UE according to the configured IP address type and the IP address type of the UE.
• the GW-C needs to interact with a server (radiius/Diameter/DHCP server) in the VPN to complete the VPN access authentication process, and obtain the peer VPN network element information ( IP address and port number) and data path information (data path protocol and data path identifier).
• the GW-C sends a configuration (establishment) data path message to the GW-U.
• the message carries configuration information of at least one data path.
• the configuration information of the data path includes local network element (GW-U) information (optional), peer network element information (optional), data path information, and data path association information (such as the IP address of the UE).
• the message carries at least one configuration information of a data path connected to the RAN.
• the message may further carry configuration information of a data path between the GW-U and the PDN, where the configuration information of the data path includes the local network element (GW). -U ) information, peer network element information, data path information, and data path association information.
• the peer network element information includes VPN network element information.
• Data path information includes connection VPN The protocol and data path identifier of the data path (for example, L2TP tunnel ID, session ID, GRE key, etc.).
• the GW-U establishes a data path for transmitting data.
• the GW-U returns a response message for configuring (establishing) the data path to the GW-C. If the GW-C does not have the local network element (GW-U) information in the configuration (establishment) data path message, the GW-U may carry the local network element information in the response message.
• GW-U local network element
• the GW-C returns a connection establishment response message.
• the message includes local network element (GW-U) information and UE IP address information.
• steps 807 to 810 may be further performed.
• the GW-C carries the peer NE information in the connection modification request message (for example, modifying the bearer request or updating the PDP request).
• the GW-C sends a configuration (modify) data path request message, where the message includes the peer network element information.
• the GW-U updates the peer network element information in the configuration information of the established data path.
• the GW-U returns a configuration (modification) data path response message.
• the GW-C returns a connection modification response message.
• the GW-C may obtain an IP address resource from the GW-U, and allocate an IP address to the UE from the obtained IP address resource.
• the GW-C may obtain the local network element (GW-U M message) from the GW-U or the local configuration, and send the local network element information to the GW-U through the configuration data path message. .
• the GW-U may allocate the data path identifier by itself, and send the data path identifier to the GW-C in step 805.
• the GW-C may obtain the data path identifier resource from the GW-U or the local configuration, and allocate the data path identifier from the data path identifier resource, and send the GW to the GW by configuring (establishing) the data path message. -U.
• the GW-C may obtain load information of multiple GW-Us from multiple GW-Us or network management network elements, and select a light load according to load information of multiple GW-Us.
• the GW-U configures the data path. Or, according to the load weight information of the multiple GW-Us, the GW-U configuration data path is selected, so that the load between the multiple GW-Us is balanced.
• the gateway system of the embodiment of the present invention is composed of control plane entities and user plane entities independent of each other.
• the control plane entity is responsible for the configuration of the data path
• the user plane entity is responsible for data forwarding on the data path
• all gateway entities make network deployment more convenient and less costly.
• the traffic can be shared without excessive modification of the control plane entity, which makes the network deployment more compact and reliable.
• the process of establishing a bearer for a UE includes an attach procedure and a UE requesting a PDN connection procedure.
• Figure 11 is a schematic diagram of the communication process between the gateway system and other network elements in the embodiment of the present invention under the SAE network architecture.
• the flow of Figure 11 contains a collection of the attach process and the UE request PDN connection process.
• the message names corresponding to the attach process in steps 901, 902, 909, and 911 have "attach", and the message name corresponding to the UE requesting the PDN connection process has "PDN connection”.
• the UE sends an attach request or a PDN connection request message to the eNodeB, where the message includes
• PDN type information for example: IPv4, IPv6, or IPv4v6
• APN optionally
• the eNodeB sends a UE attach request or a PDN connection request message to the MME.
• the MME sends a create session request message.
• the message may include the IP address type (PDN type) of the UE and the access point name APN.
• the GW-C allocates an IP address to the UE.
• the GW-C sends a configuration (establishment) data path message to the GW-U.
• the message carries configuration information of at least one data path, and the configuration information of the data path includes local network element (GW-U) information (optional), data path information, and data path association information.
• the message carries at least one configuration information of a data path connected to the eNodeB.
• the GW-U establishes a data path for transmitting data.
• the GW-U returns a response message for configuring (establishing) the data path to the GW-C.
• the GW-C returns a create session response message.
• the message includes the local network element (GW-U) information (IP address), the data path identification information (TEID) of the local network element, and the IP address information of the UE.
• GW-U local network element
• TEID data path identification information
• the MME sends an attach accept message or a PDN connection accept message to the eNodeB.
• the eNodeB and the UE perform a radio resource control connection reconfiguration process. 911.
• the eNodeB sends an attach complete message or a PDN connection complete message to the MME.
• the message includes the peer network element information (IP address) of the eNodeB and the peer data path identification information (TEID) of the eNodeB.
• IP address peer network element information
• TEID peer data path identification information
• the GW-C receives the bearer modification request message and carries the peer network element information.
• the GW-C sends a configuration (modification) data path request message, where the message includes the peer network element information and the peer data path identifier information.
• the GW-U updates the peer network element information and the peer data path identifier information in the configuration information of the established data path.
• the GW-U returns a configuration (modification) data path response message.
• the GW-C returns a bearer modification response message.
• FIG. 12 is a schematic diagram of a communication flow between a gateway system and other network elements in an embodiment of the present invention in the scenario.
• the UE sends an attach request or a PDN connection request message to the eNodeB, where the message includes PDN type information (for example: IPv4, IPv6, or IPv4v6) and APN (optional).
• PDN type information for example: IPv4, IPv6, or IPv4v6
• APN optionally
• the eNodeB sends a UE attach request or a PDN connection request message to the MME.
• the MME sends a create session request message.
• the message may include the IP address type (PDN type) of the UE and the access point name APN.
• the S-GW sends a create session request message to the GW-C.
• the message may include the IP address type (PDN type) of the UE, the access point name APN, the peer network element information of the S-GW, and the peer data path identifier (TEID) of the S-GW.
• PDN type IP address type
• APN access point name
• TEID peer data path identifier
• the GW-C allocates an IP address to the UE.
• the GW-C sends a configuration (establishment) data path message to the GW-U.
• the message carries configuration information of at least one data path, and the configuration information of the data path includes the local network element information (GW-U) (optional) and the peer network element information (S-GW) data path information (including the S-GW).
• the message carries at least one configuration information of a data path connected to the eNodeB.
• the GW-U establishes a data path for transmitting data.
• the GW-U returns a response message for configuring (establishing) the data path to the GW-C.
• the GW-C sends a create session response message.
• the message includes the local network element (GW-U) information, the data path identification information (TEID) of the local network element, and the IP address information of the UE.
• GW-U local network element
• TEID data path identification information
• IP address information of the UE 1010
• the S-GW sends a create session response message.
• the message includes the address of the S-GW, the TEID, and the IP address information of the UE.
• the MME sends an attach accept message or a PDN connection accept message to the eNodeB. 1012.
• the eNodeB and the UE perform a radio resource control connection reconfiguration process.
• the eNodeB sends an attach complete message or a PDN connection complete message to the MME.
• the message contains the IP address of the eNodeB and the TEID of the eNodeB.
• the MME sends the 7-load modification request message carrying the IP address of the eNodeB and the TEID of the eNodeB.
• the S-GW returns a bearer modification response message.
• FIG. 13 is a schematic diagram of a communication flow between a gateway system and other network elements in an embodiment of the present invention in the scenario.
• the UE sends an attach request or a PDN connection request message to the eNodeB, where the message includes PDN type information (for example: IPv4, IPv6, or IPv4v6) and APN (optional).
• PDN type information for example: IPv4, IPv6, or IPv4v6
• APN optionally
• the eNodeB sends a UE attach request or a PDN connection request message to the MME.
• the MME sends a create session request message.
• the message may include the UE's IP address type (PDN type), access point name APN, and UE information (IMSI or MSISDN).
• GW-C is a local network element information (the IP address of the GW-U) and a data path identifier (TEID) of the local network element.
• the GW-C sends a create session request message to the P-GW, where the message carries the local network element information and the data path identifier of the local network element.
• the P-GW sends a session creation response message to the GW-C, where the message carries the peer network element information (the address of the P-GW) and the data path identifier of the peer network element (the TEID of the P-GW), and the IP of the UE. address.
• the GW-C sends a configuration (establishment) data path message to the GW-U.
• the message carries configuration information of at least two data paths. One of them is the data path connected to the eNodeB, and the other is the data path connected to the P-GW.
• the configuration information of the data path connected to the eNodeB includes local network element information (GW-U) (optional), data path information, and data path association information (for example, information of the UE).
• the configuration information of the data path connected to the P-GW includes the local network element information (GW-U) (optional), the peer network element information, and the data path information (including the TEID of the local network element and the peer network element) and data. Path association information (such as information of the UE).
• the GW-U establishes a data path for transmitting data.
• the GW-U returns a response message for configuring (establishing) the data path to the GW-C.
• the GW-C returns a create session response message.
• the message includes the local network element (GW-U) information (IP address), the data path identification information (TEID) of the local network element, and the IP address information of the UE.
• GW-U local network element
• TEID data path identification information
• the MME sends an attach accept message or a PDN connection accept message to the eNodeB.
• the eNodeB and the UE perform a radio resource control connection reconfiguration process.
• the eNodeB sends an attach complete message or a PDN connection complete message to the MME.
• the message includes the peer network element information (IP address) of the eNodeB and the peer data path identification information (TEID) of the eNodeB.
• IP address peer network element information
• TEID peer data path identification information
• the GW-C receives the bearer modification request message and carries the peer network element information and the peer data path identifier information.
• the GW-C sends a configuration (modification) data path message to the eNodeB, where the message includes the peer network element information and the peer data path identifier information.
• the GW-U updates the peer network element information and the peer data path identifier information in the configuration information of the established data path.
• the GW-U returns a configuration (modification) data path response message.
• the GW-C returns a bearer modification response message.
• FIG. 14 is a schematic diagram of a process in which a gateway system activates a PDP for a UE according to another embodiment of the present invention.
• the embodiment of Figure 14 is applied to a GPRS network architecture.
• the UE (mobile station MS) sends an activation PDP request message to the SGSN, where the message includes
• PDN type information for example: IPv4, IPv6, or IPv4v6
• APN optionally
• the SGSN sends a create PDP request message.
• the message may include the IP address type (PDN type) of the UE, the access point name APN, the peer network element information (user plane IP address) of the SGSN, and the peer data path identifier (user plane TEID).
• PDN type IP address type
• APN access point name APN
• peer network element information user plane IP address
• user plane TEID peer data path identifier
• the GW-C allocates an IP address to the UE.
• the GW-C sends a configuration (establishment) data path message to the GW-U.
• the message carries configuration information of at least one data path, and the configuration information of the data path includes the information of the network element.
• the message carries at least one configuration information of a data path connected to the eNodeB.
• the GW-U establishes a data path for transmitting data. 1206.
• the GW-U sends a response message for configuring (establishing) the data path to the GW-C.
• the GW-C sends a PDP response message to the SGSN.
• the message includes the local network element (GW-U) information (IP address), the data path identification information of the local network element (the TEID of the GW-U),
• IP address information of the UE IP address information of the UE.
• the SGSN sends an Activate PDP Accept message to the UE (MS).
• FIG. 15 is a schematic diagram showing the flow of interaction between a gateway system and a Radius or Diameter server according to another embodiment of the present invention.
• the GW-C has a client module, such as the client module 411 of Figure 6.
• the GW-C receives a message for establishing a connection (for example, creating a session, creating a PDP, etc.).
• the message may include the IP address type (PDN type) of the UE, the access point name APN, the authentication information of the UE (for example, a username, a password, and the like), the peer network element information (optional), and the data path identifier information ( Optional).
• the GW-C obtains the domain name or address of the corresponding Radius or Diameter server according to the configuration of the APN, and sends an access request or an authorization and authentication (AA) request message to the Radius or Diameter server.
• the message contains the requested IP address type and the UE's authentication information.
• the 1301b, Radius or Diameter server returns an access response message or an Authorization and Authentication (AA) response message.
• the message carries an IPv4 address and/or an IPv6 prefix assigned to the UE.
• the GW-C allocates the IP address obtained in the lb to the UE. If the IP address type of the UE is IPv4, the GW-C allocates an IPv4 address to the UE. If the IP address type (PDN type) of the UE is IPv6, the GW-C allocates an IPv6 address prefix to the UE. If the IP address type (PDN type) of the UE is IPv4v6, the GW-C needs to allocate an IPv4 address to the UE and also assign an IPv6 address prefix. Further, the IP address type (PDN type) of the APN can be configured on the GW-C, and the IPv4 and/or IPv6 address is allocated to the UE according to the configured IP address type and the IP address type of the UE.
• the GW-C sends a configuration (establishment) data path message to the GW-U.
• the message carries configuration information of at least one data path, and the configuration information of the data path includes local network element information (GW-U) (optional), peer network element information (optional), and data path information.
• Information associated with the data path IP address of the UE.
• the message carries at least one configuration information of a data path connected to the RAN.
• the requested connection is a scenario of a VPN service
• the message may also carry at least The configuration information of the data path between the GW-U and the PDN
• the configuration information of the data path includes the local network element information (GW-U), the peer network element information, the data path information, and the data path association information.
• the peer network element information includes VPN network element information.
• the data path information includes a protocol and a data path identifier (for example, an L2TP tunnel identifier, a session identifier, a GRE key, and the like) of the data path connecting the VPN.
• the GW-U establishes a data path for transmitting data.
• the GW-U returns a response message for configuring (establishing) the data path to the GW-C. If the GW-C does not have the local network element (GW-U) information in the configuration (establishment) data path message, the GW-U may carry the local network element information in the response message.
• GW-U local network element
• the GW-C returns a connection establishment response message.
• the message includes the local network element (GW-U) information and the IP address information of the UE.
• steps 1307 to 1310 may be further performed.
• the GW-C carries the peer NE information in the connection modification request message (for example, modifying the bearer request or updating the PDP request).
• the GW-C sends a configuration (modification) data path request message, where the message includes the peer network element information.
• the GW-U updates the peer network element information in the configuration information of the established data path. GW-U returns configuration (modify) data path response message
• the GW-C returns a connection modification response message.
• the GW-C may include a PCEF module, such as the PCEF module 511 shown in FIG.
• the GW-C receives a message for establishing a connection (for example, creating a session, creating a PDP, etc.).
• the message may include the UE's IP address type (PDN type), access point name APN, peer network element information (optional), and data path identification information (optional).
• the IP address obtained by the GW-C is allocated to the UE. If the IP address type of the UE is IPv4, the GW-C allocates an IPv4 address to the UE. If the IP address type (PDN type) of the UE is IPv6, the Bay' J GW-C allocates an IPv6 address prefix to the UE. If the IP address type (PDN type) of the UE is IPv4v6, the GW-C needs to allocate an IPv4 address to the UE and also assign an IPv6 address prefix. Optionally, the IP address type (PDN type) of the APN can be configured on the GW-C, and The set IP address type and the IP address type of the UE determine to assign an IPv4 and/or IPv6 address to the UE.
• the GW-C sends a credit control request message (CCR) to the PCRF, where the message includes the UE's IP address, PDN identity (APN), and service data flow information (optional).
• CCR credit control request message
• the PCRF makes a decision according to the policy of the UE, obtains the policy information, and sends the policy information to the GW-C.
• the GW-C obtains service data flow information and QoS information (including bandwidth, priority, quality of service type identifier (QCI), etc.) from the policy information.
• QoS information including bandwidth, priority, quality of service type identifier (QCI), etc.
• the GW-C sends a configuration (establishment) data path message to the GW-U.
• the message carries configuration information of at least one data path, and the configuration information of the data path includes local network element information (GW-U) (optional), peer network element information (optional), and data path information. (including service data flow information and QoS information obtained from policy information) and data path association information (IP address of the UE).
• the message carries at least one configuration information of a data path connected to the RAN.
• the GW-U establishes a data path for transmitting data.
• the GW-U performs QoS control on the service data flow in the data path according to the service data flow information and the QoS information in the data path information.
• the GW-U returns a response message for configuring (establishing) the data path to the GW-C. If the GW-C does not have the local network element (GW-U) information in the configuration (establishment) data path message, the GW-U may carry the local network element information in the response message.
• GW-U local network element
• the GW-C returns a connection establishment response message.
• the message includes the local network element (GW-U) information and the IP address information of the UE.
• steps 1407 to 1410 may be further performed.
• the GW-C carries the peer NE information in the connection modification request message (for example, modifying the bearer request or updating the PDP request).
• the GW-C sends a configuration (modification) data path request message, where the message includes the peer network element information.
• the GW-U updates the peer network element information in the configuration information of the established data path.
• the GW-U returns a configuration (modification) data path response message.
• the GW-C returns a connection modification response message.
• the quality of service of the data transmission of the UE can be guaranteed according to the policy.
• FIG. 17 is a schematic diagram of a policy control flow of a gateway system according to another embodiment of the present invention.
• the embodiment initiates a service by an application server (AF, Application Function).
• AF Application Function
• PCEF Policy and Charging Function
• the process of configuring the policy information to the GW-C (PCEF) by the PCRF is triggered.
• the GW-C may include a PCEF module, such as the PCEF module 511 shown in FIG.
• the application server (AF) sends the service information to the PCRF.
• the service information includes service data flow information, service quality information (bandwidth, delay, etc.) required by the service, and the identity of the UE (IP address, PDN identity, IMSI, etc.).
• the PCRF returns a response, and according to the service information and the UE's policy subscription information decision, generates policy information of the service.
• the PCRF configures the policy information of the service to the GW-C (PCEF).
• the PCEF determines to establish or modify the connection according to the QoS information in the policy information of the service. If the QCI is the same as the existing connection, modify the existing connection. If the QCI is different from the existing connection, a new connection is established.
• the PCEF sends a setup or modify connection request message to the MME/SGSN. The message carries QoS information, local network element information, and data path information.
• the MME/SGSN interacts with the RAN to establish or modify a connection, and send or modify a connection response message. If the data path is established, the response message carries the peer network element information and the data path information.
• the GW-C sends a configuration data path message to the GW-U. If the connection is newly established, the local network element information (GW-U), the peer network element information, and the data path information (including the service data flow information and QoS information obtained from the policy information) including the newly added data path are included. Information associated with the data path (IP address of the UE). If the existing connection is modified, the message contains the associated information and data path information (including the identification and QoS information of the data path) of the existing data path.
• the GW-U creates or modifies a data path, and controls the service data flow in the data path according to the configured QoS information.
• the GW-U sends a configuration data path response to the GW-C.
• the GW-C sends a response message to the PCRF.
• the PCRF will also notify the AF transmission resource that it has been established.
• the quality of service of the data transmission of the UE can be guaranteed according to the policy.
• the embodiment of the invention can solve the problem that the gateway processes the bottleneck of the interface signaling, and separates the interface signaling processing function of the gateway from the user plane forwarding data function.
• the interface signaling processing function can be placed on the general-purpose computing platform to become a gateway control node.
• the function of forwarding data on the user plane is placed on a dedicated router platform to become a gateway forwarding node. Separate the gateway control node from the gateway forwarding node In this way, the design of the hardware platform can be reduced, the cost of the hardware platform can be reduced, and the deployment of the mobile packet data network can be accelerated.
• the disclosed systems, devices, and methods may be implemented in other ways.
• the device embodiments described above are merely illustrative.
• the division of the unit is only a logical function division.
• there may be another division manner for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored, or not executed.
• the coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be electrical, mechanical or otherwise.
• the units described as separate components may or may not be physically separate, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the solution of the embodiment.
• each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
• the functions may be stored in a computer readable storage medium if implemented in the form of a software functional unit and sold or used as a standalone product.
• the technical solution of the present invention which is essential to the prior art or part of the technical solution, may be embodied in the form of a software product stored in a storage medium, including
• the instructions are used to cause a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in various embodiments of the present invention.
• the storage medium includes: a USB flash drive, a removable hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, and the like, which can store program codes.

Landscapes

• Engineering & Computer Science (AREA)
• Computer Networks & Wireless Communication (AREA)
• Signal Processing (AREA)
• Computer Security & Cryptography (AREA)
• Computer Hardware Design (AREA)
• Computing Systems (AREA)
• General Engineering & Computer Science (AREA)
• Business, Economics & Management (AREA)
• Accounting & Taxation (AREA)
• Mobile Radio Communication Systems (AREA)
• Data Exchanges In Wide-Area Networks (AREA)

Priority Applications (11)

Applications Claiming Priority (1)

Related Child Applications (1)

Publications (1)

Family

ID=49782125

Family Applications (1)

Country Status (6)

Cited By (13)

Families Citing this family (37)

Citations (4)

Family Cites Families (15)

• 2012
  • 2012-06-29 CN CN201810309516.2A patent/CN108737157B/zh active Active
  • 2012-06-29 WO PCT/CN2012/077960 patent/WO2014000286A1/zh unknown
  • 2012-06-29 EP EP20192989.0A patent/EP3826231B1/en active Active
  • 2012-06-29 EP EP18188457.8A patent/EP3493474B1/en active Active
  • 2012-06-29 PT PT12879884T patent/PT2854475T/pt unknown
  • 2012-06-29 ES ES20192989T patent/ES2967681T3/es active Active
  • 2012-06-29 EP EP12879884.0A patent/EP2854475B1/en active Active
  • 2012-06-29 EP EP23199963.2A patent/EP4336780A3/en active Pending
  • 2012-06-29 CN CN201280000540.9A patent/CN103636283B/zh active Active
• 2014
  • 2014-12-22 US US14/579,793 patent/US11368838B2/en active Active
• 2022
  • 2022-05-12 US US17/743,238 patent/US12015910B2/en active Active

Patent Citations (4)

Also Published As

Similar Documents

Legal Events