WO2017124231A1 - 分配互联网协议地址的方法、控制面网关和用户面网关 - Google Patents

分配互联网协议地址的方法、控制面网关和用户面网关 Download PDF

Info

Publication number
WO2017124231A1
WO2017124231A1 PCT/CN2016/071247 CN2016071247W WO2017124231A1 WO 2017124231 A1 WO2017124231 A1 WO 2017124231A1 CN 2016071247 W CN2016071247 W CN 2016071247W WO 2017124231 A1 WO2017124231 A1 WO 2017124231A1
Authority
WO
WIPO (PCT)
Prior art keywords
address
plane gateway
server
user plane
request message
Prior art date
Application number
PCT/CN2016/071247
Other languages
English (en)
French (fr)
Inventor
周润泽
曹龙雨
张艳平
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to PCT/CN2016/071247 priority Critical patent/WO2017124231A1/zh
Publication of WO2017124231A1 publication Critical patent/WO2017124231A1/zh

Links

Images

Classifications

    • 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

Definitions

  • the present invention relates to the field of communications, and in particular, to a method for allocating an Internet Protocol (IP) address, a control plane gateway, and a user plane gateway.
  • IP Internet Protocol
  • control plane In the network architecture of Control and User Plane Separation (CUPS), the control plane is separated from the user plane, and some or all of the network elements that have both the control plane and the user plane function are split into control planes. Two entities, the NE and the user plane NE.
  • CUPS Control and User Plane Separation
  • the control plane network element has a control plane function, which mainly includes signaling connection with other network elements, handling mobility management and session management requests of user equipment, managing user equipment context, and establishing transmission data. The channel and so on.
  • the user plane network element has a user plane function, which mainly includes sending uplink and downlink data packets of the user equipment, performing quality of service (QoS) control and traffic statistics for data packets.
  • QoS quality of service
  • the traditional Public Data Network GateWay is split into CGW (Control GateWay) and UGW (User GateWay).
  • the UGW has the control plane function of the PGW, and the UGW has the user plane function of the PGW.
  • IP Internet Protocol
  • a specific method for allocating an IP address by using a dynamic IP address allocation mechanism is as follows: a network device (such as an MME) determines that a dynamic IP address needs to be allocated to a UE according to a service requested by a user equipment (UE) and a subscription information of the UE. Requesting a PGW, the PGW is required to assign an address to the UE.
  • a network device such as an MME
  • the PGW If the PGW has the ability to assign an IP address (for example, if an IP address pool is configured), the PGW directly returns the assigned IP address to the UE; if the PGW does not have the ability to assign an IP address, it needs to have a server with an IP address assigned externally. (such as a DHCP server) request to assign an IP address. When the PGW receives the address assigned by the external server, it sends it to the UE.
  • a server with an IP address assigned externally such as a DHCP server
  • the present invention provides a method for allocating an IP address, a control plane gateway, and a user plane gateway, which are capable of allocating an IP address to a UE in a network separate from the CU.
  • the present invention provides a method of assigning an IP address.
  • the control plane gateway receives the first request message sent by the UE; then the control plane gateway determines, according to the first request message, whether the IP address is assigned by the control plane gateway; when the control plane gateway determines that the IP address is assigned by the control plane gateway, the IP address is allocated.
  • the control plane gateway determines that the IP address is not assigned by the control plane gateway, it sends policy information to the user plane gateway that triggers the user plane gateway to assign an IP address and/or carries a message indicating the policy information of the user plane gateway assigning the IP address.
  • the control plane gateway After receiving the IP address request message of the UE, the control plane gateway first determines whether the IP address is allocated by itself. If the control plane gateway determines to assign an IP address by itself, it continues to allocate the IP address; if the control plane gateway determines that the IP address is not assigned by itself, the control plane gateway sends a message to the user plane gateway to facilitate the assignment of the IP address by the user plane gateway.
  • the technical solution of the present invention makes it possible for the UE to be assigned an IP address by the control plane gateway or the user plane gateway in the CU-separated network.
  • the first request message carries at least one of a service type requested by the UE, an Access Point Name (APN) corresponding to the UE, identity information of the UE, and authentication key information of the UE.
  • a kind of information A kind of information.
  • the control plane gateway may determine whether the IP address is allocated by the control plane gateway according to the foregoing information carried by the first request.
  • the control plane gateway can also be determined based on the real-time status of its capabilities or capabilities.
  • the control plane gateway determines whether to assign an IP address by itself according to specific conditions, and can fully utilize network resources to improve the efficiency of allocating IP addresses.
  • the control plane gateway determines, according to the first request message, whether the IP address is allocated by the control plane gateway, specifically: the control plane gateway determines, according to the type of the first request message, whether the IP address is allocated by the control plane gateway. That is, after determining that the first request message is a message requesting the control plane gateway to allocate an IP address to the UE, the control plane gateway determines whether the IP address is allocated by the control plane gateway.
  • control plane gateway allocates an IP address in a specific manner: locally assigning an IP address or assigning an IP address through a server.
  • the control plane gateway allocates an IP address by using the server, where the control plane gateway sends a message to the user plane gateway for instructing the user plane gateway to send the second request message to the server, where the second request message is used.
  • the requesting server allocates an IP address; the control plane gateway connects to the IP address forwarded by the server through the user plane gateway.
  • the control plane gateway allocates an IP address through the server, specifically: The control plane gateway sends a third request message to the server, the third request message is used to request the server to allocate an IP address, and the control plane gateway receives the IP address sent by the server.
  • control plane gateway sends the third request message to the server, where the control plane gateway sends the third request message to the server by using the user plane gateway.
  • the IP address sent by the control plane gateway receiving server is specifically: the control plane gateway receives the IP address forwarded by the server through the user plane gateway.
  • the server is a Dynamic Host Configuration Protocol (DHCP) server.
  • DHCP Dynamic Host Configuration Protocol
  • the control plane gateway when the server is a DHCP server, before the control plane gateway allocates the IP address through the DHCP server, the control plane gateway sends a request for the UE to the server with the authentication function through the user plane gateway.
  • the control plane gateway receives the authentication response message forwarded by the server with the authentication function through the user plane gateway; the control plane gateway determines, according to the authentication response message, that the server having the authentication function successfully authenticates the UE.
  • the message for requesting authentication of the UE is sent to the server with the authentication function directly or through the user plane gateway, and directly or through the user plane gateway. Receiving an authentication response message sent by the server with the authentication function, and then determining that the UE is successfully authenticated according to the authentication response message.
  • the UE may be assigned an IP address after the UE is successfully authenticated.
  • the server with the authentication function may be an authentication, authorization, and accounting (AAA) server, and may perform remote authentication dial-in user service (RADIUS) authentication on the UE.
  • AAA authentication, authorization, and accounting
  • RADIUS remote authentication dial-in user service
  • the control plane gateway before the control plane gateway allocates the IP address, the control plane gateway receives the fourth request message sent by the user plane gateway, and the fourth request message is a message that the user plane gateway receives the request for sending the IP address by the UE.
  • control plane gateway after receiving the IP address request message of the UE, the control plane gateway also needs to receive the IP address request message sent by the UE reported by the user plane gateway through the user plane, and then allocate the IP address.
  • the IP address is sent to the UE.
  • the control plane gateway may directly send an IP address to the UE, or may forward the IP address to the UE through a network element such as a mobility management network element or a base station.
  • This implementation enables the UE to assign an IP address during the default bearer setup.
  • the present invention provides a method of assigning an IP address.
  • the user plane gateway determines, according to the first request message, that the user plane gateway locally allocates an IP address or allocates an IP address by using a server; and the user plane gateway receives the control plane gateway to send the
  • the message for triggering the IP address of the user plane gateway is triggered, it is determined that the IP address is locally allocated by the user plane gateway or the IP address is allocated by the server; and the user plane gateway receives the first request message sent by the UE and the bearer sent by the receiving control plane gateway.
  • the message indicating the policy information of the IP address is assigned by the user plane gateway, it is determined according to the first request message and the policy information that the IP address is locally allocated by the user plane gateway or the IP address is allocated by the server.
  • the user plane gateway determines that the IP address is locally allocated by the user plane gateway, the IP address is locally allocated; when the user plane gateway determines that the IP address is allocated by the server, the IP address is allocated by the server.
  • the user plane gateway determines whether to directly allocate the IP address by itself according to the request message or/and the policy information.
  • the server assigns an IP address and performs a corresponding process of assigning an IP address.
  • determining, by the first request message, that the IP address is locally allocated by the user plane gateway or the IP address is allocated by the server is: the user plane gateway determines the user plane gateway according to the type of the first request message. Assigning an IP address locally or assigning an IP address through a server; determining, according to the first request message and the policy information, that the IP address is locally allocated by the user plane gateway or the IP address is allocated by the server is: the type of the first request message is determined by the user plane gateway. And the policy information determines that the IP address is assigned locally by the user plane gateway or by the server.
  • the type of the first request message means that the request message is a message requesting the user plane gateway to allocate an IP address to the UE.
  • the user plane gateway determines whether the IP address is allocated by itself or through the server according to the policy message received from the control plane gateway, so that the user plane in the network separated by the CU The gateway allocates IP addresses according to the decision of the control plane gateway.
  • the user plane gateway allocates an IP address through the server, where the user plane gateway sends a message of the second request message to the server, the second request message is used to request the server to allocate the IP address, and the user plane gateway receives the server.
  • the server is a DHCP server.
  • the user plane gateway before the user plane gateway allocates the IP address by using the server, the user plane gateway sends a request message for requesting authentication of the UE to the server with the authentication function; the user plane gateway receives the authentication.
  • the authentication response message sent by the function server; the user plane gateway determines, according to the authentication response message, that the server having the authentication function successfully authenticates the UE.
  • the server with the authentication function sends a message for requesting authentication of the UE, and receives the authentication response sent by the server with the authentication function. The message is then determined to successfully authenticate the UE according to the authentication response message.
  • the UE may be assigned an IP address after the UE is successfully authenticated.
  • the server with the authentication function may be an AAA server, and may perform RADIUS authentication on the UE.
  • the method further includes: the user plane gateway sends an IP address to the UE, or sends an IP address to the control plane gateway, so that the control plane gateway sends the IP address to the UE.
  • a control plane gateway includes a receiving unit, configured to receive a first request message sent by the user equipment UE, and a determining unit, configured to determine, according to the first request message, whether an IP address is allocated by the control plane gateway, and an allocating unit, configured to determine, by the determining unit, by the control When the IP address is assigned by the gateway, the IP address is allocated; the sending unit is configured to send, when the determining unit determines that the IP address is not assigned by the control plane gateway, trigger the user plane gateway to allocate the IP address and/or carry the indication user plane to the user plane gateway.
  • the gateway assigns a message of the policy information of the IP address.
  • the control plane gateway of the present invention After receiving the IP address request message of the UE, the control plane gateway of the present invention first determines whether an IP address is allocated by itself. If the control plane gateway determines to assign an IP address by itself, it continues to allocate the IP address; if the control plane gateway determines that the IP address is not assigned by itself, the control plane gateway sends a message to the user plane gateway to facilitate the assignment of the IP address by the user plane gateway.
  • the technical solution of the present invention makes it possible for the UE to be assigned an IP address by the control plane gateway or the user plane gateway in the CU-separated network.
  • the first request message carries at least one of a service type requested by the UE, an APN corresponding to the UE, identity information of the UE, and authentication key information of the UE.
  • the determining unit may determine whether the IP address is allocated by the control plane gateway according to the foregoing information carried by the first request.
  • the determination unit can also be determined based on the real-time status of its capabilities or capabilities. The determining unit determines whether the IP address is assigned by itself according to the specific situation, and can fully utilize the network resources and improve the efficiency of allocating the IP address.
  • the determining unit is specifically configured to use the type of the first request message. Determine if the IP address is assigned by the control plane gateway.
  • the type of the first request message means that the request message is a message requesting the control plane gateway to allocate an IP address to the UE.
  • the allocating unit is specifically configured to locally allocate an IP address or allocate an IP address through a server.
  • the allocating unit is specifically configured to send, to the user plane gateway, a message for instructing the user plane gateway to send a second IP address request message to the server, where the second IP address request message is used to request the server to allocate the IP; And receive the IP address forwarded by the server through the user plane gateway.
  • the allocating unit is specifically configured to: send a third IP address request message to the server, where the third IP address request message is used to request the server to allocate an IP address; and receive an IP address sent by the server.
  • the allocating unit is specifically configured to send a third IP address request message to the server through the user plane gateway; and receive an IP address forwarded by the server through the user plane gateway.
  • the server is a DHCP server.
  • the allocating unit is further configured to send a request for authenticating the UE to the server having the authentication function through the user plane gateway before the IP address is allocated by the DHCP server. Receiving the request message; and receiving the authentication response message forwarded by the server with the authentication function through the user plane gateway; and then determining, according to the authentication response message, that the server having the authentication function successfully authenticates the UE.
  • the allocating unit before the allocation of the IP address locally, is further configured to: send a message for requesting authentication of the UE to the server having the authentication function directly or through the user plane gateway, and directly or The user plane gateway receives the authentication response message sent by the server with the authentication function, and then determines that the UE is successfully authenticated according to the authentication response message.
  • the UE may be assigned an IP address after the UE is successfully authenticated.
  • the server with the authentication function may be an AAA server, and may perform RADIUS authentication on the UE.
  • the receiving unit before receiving the IP address, is further configured to receive a fourth request message sent by the user plane gateway, where the fourth request message is used by the user plane gateway to receive the request sent by the UE to allocate an IP address.
  • the sending unit is further configured to send the IP address to the UE.
  • the fourth aspect provides a user plane gateway.
  • the username gateway includes a receiving unit for Receiving a first request message sent by the UE, receiving a message sent by the control plane gateway for triggering the user plane gateway to allocate an IP address, or receiving a first request message sent by the UE, and carrying by the control plane gateway to indicate that the user plane gateway allocates the IP address.
  • the message of the address's policy information includes
  • a determining unit configured to: when the receiving unit receives the first request message sent by the UE, determine, according to the first request message, that the IP address is locally allocated by the user plane gateway or the IP address is allocated by the server; and is used by the receiving unit to receive the control plane gateway When the message for triggering the user plane gateway to allocate the IP address is used, it is determined that the IP address is locally allocated by the user plane gateway or the IP address is allocated by the server; and the first request message sent by the UE and the carrying by the control plane gateway are received at the receiving unit.
  • the allocation unit is configured to determine in the determining unit When the user plane gateway locally allocates an IP address, the IP address is locally allocated; the allocating unit is further configured to determine, by the determining unit, the IP address by the server, and allocate the IP address by the server.
  • the user plane gateway of the present invention receives a message sent by the UE requesting to allocate an IP address, and determines whether it is determined whether to allocate an IP address by itself or through a server.
  • the technical solution of the present invention enables an IP address to be allocated to a UE by a user plane gateway or a server in a network separated by CUs.
  • the determining unit is specifically configured to determine, according to the type of the first request message, locally assigning an IP address by the user plane gateway or assigning an IP address by using a server; the determining unit is further configured to be used according to the type of the first request message.
  • the policy information determines that the IP address is assigned locally by the user plane gateway or by the server.
  • the type of the first request message means that the request message is a message requesting the user plane gateway to allocate an IP address to the UE.
  • the allocating unit is specifically configured to send a message of the second IP address request message to the server, where the second IP address request message is used to request the server to allocate an IP address; and receive the IP address sent by the server.
  • the allocating unit before assigning an IP address by the server, is further configured to send a request message for requesting authentication of the UE to the server having the authentication function; and receive the server with the authentication function. The sent authentication response message; and then determining, according to the authentication response message, that the server having the authentication function successfully authenticates the UE.
  • the allocating unit before the allocating unit locally allocates the IP address, the allocating unit is further configured to send a message for requesting authentication to the UE to the server having the authentication function, and receive the packet sent by the server with the authentication function. The right response message is then determined to successfully authenticate the UE according to the authentication response message.
  • the UE may be assigned an IP address after the UE is successfully authenticated.
  • the server with the authentication function may be an AAA server, and may perform RADIUS authentication on the UE.
  • the username gateway further includes a sending unit, configured to send an IP address to the UE or send an IP address to the control plane gateway, so that the control plane gateway sends the IP address to the UE.
  • a fifth aspect provides a control plane gateway.
  • the control plane gateway includes a receiver, a transmitter, a memory, a processor, and a bus system.
  • the receiver, the transmitter, the memory and the processor are connected by a bus system, the memory is for storing instructions, the receiver and the transmitter are respectively for receiving and transmitting messages, the processor is for executing instructions stored by the memory, and the receiver and the transmitter are called. Perform the first aspect or any of its possible implementations.
  • a user plane gateway includes a receiver, a transmitter, a memory, a processor, and a bus system.
  • the receiver, the transmitter, the memory and the processor are connected by a bus system, the memory is for storing instructions, the receiver and the transmitter are respectively for receiving and transmitting messages, the processor is for executing instructions stored by the memory, and the receiver and the transmitter are called. Perform the second aspect or any of its possible implementations.
  • FIG. 1 is a schematic diagram of a possible network architecture of the present invention.
  • FIG. 2 is a schematic flow chart of a method for allocating an IP address according to an embodiment of the present invention.
  • FIG. 3 is a schematic flowchart of a method for allocating an IP address according to another embodiment of the present invention.
  • FIG. 4 is a schematic flow chart of a method for allocating an IP address according to still another embodiment of the present invention.
  • FIG. 5 is a schematic flowchart of a method for allocating an IP address according to still another embodiment of the present invention.
  • FIG. 6 is a schematic flowchart of a method for allocating an IP address according to still another embodiment of the present invention.
  • FIG. 7 is a schematic flowchart of a method for allocating an IP address according to still another embodiment of the present invention.
  • FIG. 8 is a schematic block diagram of a control plane network element in accordance with one embodiment of the present invention.
  • FIG. 9 is a schematic block diagram of a control plane network element in accordance with another embodiment of the present invention.
  • FIG. 10 is a schematic block diagram of a user plane network element according to an embodiment of the present invention.
  • FIG. 11 is a schematic block diagram of a user plane network element according to another embodiment of the present invention.
  • FIG. 1 is a schematic diagram of a CPUS network architecture of an embodiment of the present invention, which mainly includes a UE, an Evolved Node B (eNB), a control plane gateway, a user plane gateway, and a server.
  • eNB Evolved Node B
  • control plane gateway a control plane gateway
  • user plane gateway a user plane gateway
  • server a server
  • the dashed line in Figure 1 indicates the transmission of a message through the control plane, which enables the transmission of messages or messages through the user plane.
  • a UE may be referred to as an access terminal, a terminal device, a subscriber unit, a subscriber station, a mobile station, a mobile station, a remote station, a remote terminal, a mobile device, a user terminal, a terminal, a wireless communication device, a user agent, or a user device.
  • the UE may be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), or a wireless communication function.
  • the UE can communicate with the control plane network through signaling messages, and can also send and receive data packets with the user plane gateway.
  • the eNB is only one possible component of a CP-separated network architecture to which the present invention is applicable. It may also be a Mobility Management Entity (MME) or a base station device or a small base station in a future 5G network. Equipment, etc.
  • MME Mobility Management Entity
  • the UE communicates with the control plane gateway and the user plane gateway through the eNB.
  • the UE can directly communicate with the control plane gateway and the user plane gateway, that is, the network architecture of the CP separation may not have an eNB, and the present invention does not limited.
  • the control plane gateway has a control plane interface, which is mainly used for signaling connection with other network elements, processing user mobility management and session management requests, managing user context and establishing a channel for transmitting data.
  • the control plane gateway can be used for gateway autonomous allocation when static IP address allocation or dynamic IP address allocation.
  • the control plane gateway may be a CGW having a control plane function after the PGW is separated.
  • the user plane gateway has a user plane interface, which is mainly used for sending user uplink and downlink data packets, performing QoS control for data packets, and traffic statistics.
  • the user plane gateway can be used for gateway autonomous allocation during dynamic IP address allocation and external network allocation when dynamic IP address allocation.
  • the server can assign an IP address and connect to the user plane gateway to send and receive data packets.
  • the user plane gateway may be a UGW with a user plane function after the PGW is separated.
  • the control plane gateway receives the first request message sent by the UE.
  • the first request message may carry information such as a service type requested by the UE, an APN corresponding to the UE, identity information of the UE, and authentication key information of the UE.
  • the control plane gateway may determine whether the IP address is allocated by the control plane gateway according to the foregoing information carried by the first request.
  • the control plane gateway can also be determined based on the real-time status of its capabilities or capabilities.
  • the control plane gateway determines whether to assign an IP address by itself according to specific conditions, and can fully utilize network resources to improve the efficiency of allocating IP addresses.
  • the UE When the UE needs to establish a session or establish a bearer, it sends an IP address request message to the control plane gateway, and the message may carry information of the UE and/or information of the server.
  • the control plane gateway determines whether an IP address is allocated by the control plane gateway.
  • the control plane gateway After receiving the IP address request message of the UE, the control plane gateway determines whether it is necessary to allocate an IP address by itself.
  • a possible implementation manner of the control plane gateway determining whether to allocate an IP address by itself is as follows: The control plane gateway may determine according to different service types requested by the UE (or service types subscribed by the UE). For example, if the UE requests services such as the MBB service, the Internet of Vehicles service, or the Internet of Things service, it is determined that the IP address is assigned by the control plane gateway; if the UE requests the services of the enterprise network service, the public security service, the private cloud service, etc., The control plane gateway assigns an IP address.
  • the control plane gateway can also be determined according to the APN requested by the UE. For example, when the UE requests to access an APN that provides an MBB service, a car network service, or an Internet of Things service, it is determined that the IP address is assigned by the control plane gateway, and when the request is made to provide an enterprise network service, a public security service, a private cloud service, or the like. At APN, it is determined that the IP address is not assigned by the control plane gateway.
  • the control plane gateway can also be determined according to its own capabilities. For example, if the control plane gateway is configured with a local IP address pool, it is determined that it is allocated by the control plane gateway. If not, it is not allocated by the control plane gateway.
  • the control plane gateway can also be determined based on the real-time status of its capabilities. For example, although the control plane gateway is configured with a local IP address pool, but the address in the address pool has been allocated, at this time, the IP address cannot be assigned by the control plane gateway.
  • the control plane gateway may further determine, according to the type of the first request message, whether the IP address is assigned by the control plane gateway, that is, when the control plane gateway determines that the first request message is a message requesting the control plane gateway to allocate an IP address for the UE, determining whether the control is controlled by the control plane The gateway assigns an IP address.
  • the control plane gateway determines that the IP address is assigned by the control plane gateway, the IP address is allocated.
  • control plane gateway determines that it has assigned an IP address by itself, it can further determine whether the IP address is assigned through the DHCP mechanism or the IP address is allocated through the non-DHCP mechanism.
  • the DHCP mechanism is an IP address allocation method. Usually two entities participate, one is a DHCP client and the other is a DHCP server.
  • the DHCP Client requests the DHCP Server to assign an IP address, and the DHCP Server assigns an IP address to the DHCP Client.
  • the IP address can be an IPv4 address, an IPv6 full address, or another address.
  • control plane gateway determines that the IP address is assigned through the DHCP mechanism, if it can act as a DHCP server, the control plane gateway directly assigns an IP address to the UE from the IP address pool, and directly sends the message to the UE or through the network with the control plane function.
  • the element sends the IP address to the UE.
  • control plane gateway determines that the IP address is assigned through the DHCP mechanism, but it cannot allocate an IP address by itself, it can request the DHCP server to assign an IP address as a DHCP Client.
  • the control plane gateway requests the DHCP server to assign an IP address.
  • the implementation method is that the control plane gateway constructs a DHCP request message and sends it to the DHCP server, but because the interface with the DHCP server is on the user plane gateway (such as The UGW after the PGW is separated, so the message must be sent to the user plane gateway first, and then forwarded to the DHCP server by the user plane gateway.
  • the DHCP server assigns an IP address, it sends it to the control plane gateway through the user plane gateway, and the control plane gateway sends the IP address to the UE.
  • control plane gateway notifies the user plane that the gateway sends a DHCP request message to the DHCP server, and the DHCP server allocates an IP address, and then the user plane gateway forwards the IP address to the control plane gateway, and the control plane gateway then sets the IP address. Send to the UE.
  • the control plane gateway may also notify the user plane gateway of the IP address.
  • control plane gateway determines to use the non-DHCP mechanism to allocate an IP address
  • one implementation manner is: the control plane gateway constructs the request message itself and sends it to the external server, but because the interface with the external server is at the user plane gateway, the message must first To be sent to the user plane gateway, the user plane gateway forwards it to the external server; the external server sends the assigned IP address to the control plane gateway, and then the control plane gateway sends it to the UE.
  • the control plane gateway may also notify the user plane gateway of the IP address.
  • the user plane gateway sends the message through the control plane gateway.
  • the indication information in the message or its own configuration information determines the address of the AAA server, and constructs a request message, and sends the UE information (including the authentication information) and the service information to the AAA server.
  • the AAA Server assigns an IP address, it returns the IP address to the user plane gateway.
  • the AAA Server may only authenticate and not return an IP address. If the AAA Server does not return an IP address, the user plane gateway needs to re-allocate the IP address through DHCP.
  • the above manner describes that an IP address is allocated and sent to the UE during the default bearer setup process.
  • the control plane gateway may also allocate and send an IP address to the UE after the default bearer setup procedure.
  • the control plane gateway does not immediately allocate the IP address.
  • the UE sends a user plane IP address request message to the user plane gateway, and the user plane gateway reports the message to the control plane gateway.
  • the control plane gateway will use the above DHCP mechanism or non-DHCP mechanism to allocate an IP address and send the IP address to the UE.
  • the server may fail to assign an IP address.
  • the server may return a response message to the control plane gateway to notify the control plane that the server fails to assign an IP address.
  • the control plane gateway can allocate an IP address by other means.
  • control plane gateway determines that the IP address is not assigned by the control plane gateway, the control plane gateway sends a message to the user plane gateway that triggers the user plane gateway to allocate an IP address and/or carries policy information indicating that the user plane gateway allocates an IP address.
  • the control plane gateway sends an IP address request message to the user plane gateway, and may carry the following information according to specific requirements: UE information, service information, bearer identifier, indication identifier, or external server identifier.
  • the indication identifier may be used to indicate that the address is assigned by the user plane gateway or the IP address is assigned by the user plane gateway in conjunction with the external server. If there is no indication, the user plane gateway can judge from the message name that the address is assigned by the user plane gateway or that the user plane gateway associates with the external server to allocate an IP address.
  • the indication identifier can be used to instruct the external server to allocate an IP address, and the request message can carry the IP address or identifier of the external server.
  • the user plane gateway after receiving the request message sent by the control plane gateway, the user plane gateway can allocate an IP address according to various information carried in the request message.
  • FIG. 3 is a schematic flowchart of a method for allocating an IP address according to an embodiment of the present invention.
  • the user plane gateway determines, according to the first request message, that the IP address is locally allocated by the user plane gateway or the IP address is allocated by the server; and the user plane gateway receives the control plane gateway for triggering the user.
  • the gateway allocates the IP address message it is determined that the IP address is locally allocated by the user plane gateway or the IP address is allocated by the server; and the user plane gateway receives the first request message sent by the UE and the bearer sent by the receiving control plane gateway is used to indicate the user plane.
  • the gateway allocates the message of the policy information of the IP address, it is determined according to the first request message and the policy information that the IP address is locally allocated by the user plane gateway or the IP address is allocated by the server.
  • the user plane gateway may be a UGW after the PGW is separated.
  • the type of the first request message is that the request message is a message for requesting the user plane gateway to allocate an IP address to the UE.
  • determining, according to the first request message, that the IP address is locally allocated by the user plane gateway or the IP address is allocated by the server is specifically: After determining that the first request message is a message requesting the user plane gateway to allocate an IP address to the UE, the user plane gateway determines that the IP address is locally allocated by the user plane gateway or the IP address is allocated by the server.
  • the user plane gateway determines, after determining that the first request message is a message requesting the user plane gateway to allocate an IP address for the UE, according to the message
  • the policy information determines that the IP address is assigned locally by the user plane gateway or by the server.
  • the policy information sent by the control plane gateway received by the user plane gateway may carry the following information according to specific requirements: UE information, service information, bearer identifier, indication identifier, or external server identifier.
  • the indication identifier can be used to indicate that the address is assigned by the user plane gateway. If there is no indication, the user plane gateway can determine from the message name that the address is assigned by the user plane gateway.
  • the indication identifier can also be used to indicate the IP address of the external server, or the IP address or identifier of the request server that can carry the external server.
  • the user plane gateway may determine, according to the policy information, whether to assign an IP address to the UE in the process of establishing the default bearer by itself or through the server; or may be configured to allocate an IP address upon receiving the request of the UE. After the request message, it is determined according to the request message whether the IP address is allocated to the UE after the default establishment process by itself or through the server. Certainly, the user plane gateway may also determine whether to directly allocate an IP address by itself according to the policy information and the request message after receiving the policy information sent by the control plane gateway and receiving the request message for requesting the IP address sent by the UE. The server assigns an IP address.
  • the IP address is locally allocated.
  • the user plane gateway determines that the IP address is determined by the user plane gateway according to the name of the IP address request message sent by the control plane gateway or the indication identifier or other information carried in the message, it is further determined whether the IP address is allocated through the DHCP mechanism.
  • the user plane gateway When the user plane determines that the IP address is assigned through the DHCP mechanism, and the DHCP server can be used as the DHCP server, the user plane gateway directly allocates the P address to the UE from the IP address pool, and then firstly goes to the control plane gateway in the process of establishing the default bearer.
  • the IP address is sent, and the IP address is sent by the control plane gateway to the UE, or the IP address is directly sent to the UE after the default bearer setup process.
  • the user plane gateway can request the DHCP server to assign an IP address as a DHCP client.
  • the specific implementation manner is: the user plane gateway sends a DHCP request message to the DHCP server, and the DHCP server allocates an IP address.
  • the user plane gateway receives the IP address sent by the DHCP server, the user plane gateway sends the IP address to the control plane gateway in the default bearer establishment process, and the control plane gateway sends the IP address to the UE, or the user plane gateway.
  • the IP address is directly sent to the UE after the default bearer setup process.
  • the user plane gateway may also notify the control plane gateway of the IP address.
  • the user plane gateway constructs the request message, sends the request to the external server, and requests the external server to allocate the IP address; then the user plane gateway receives the IP sent by the external server. After the address, the user plane gateway sends the IP address to the control plane gateway in the default bearer setup process, and the control plane gateway sends the IP address to the UE, or the user plane gateway directly IP address after the default bearer setup process. Send to the UE.
  • the user plane gateway may also notify the control plane gateway of the IP address.
  • the user plane gateway determines the address of the AAA Server through the indication information in the message sent by the control plane gateway or its own configuration information, and constructs a request message, and the UE information (including the authentication information) and the service.
  • the information is sent to the AAA Server.
  • the AAA Server assigns an IP address, it returns the IP address to the user plane gateway.
  • the AAA Server may only authenticate and not return an IP address. If the AAA Server does not return an IP address, the user plane gateway needs to re-allocate the IP address through DHCP.
  • UGW can directly contact the external server; if the request message carries the identifier of the external server, UGW needs to use it to associate with the IP address of the saved external server, or by (Domain Name System , DNS) The server queries the IP address of the external server.
  • DNS Domain Name System
  • the IP address request message sent by the control plane gateway to the user plane gateway carries the bearer identifier, when the user plane gateway allocates an IP address, or requests the server to allocate an IP address, it may determine that the IP address corresponds to the bearer identifier.
  • the bearer is associated.
  • the user plane gateway allocates an IP address request message after receiving the IP address request message sent by the control plane gateway, and the user plane gateway receives the IP address request message sent by the control plane gateway, if the message carries The policy information indicating that the user plane gateway allocates an IP address to the UE, the user plane gateway also needs to receive the IP address request message sent by the UE after the default bearer setup procedure, and then the IP address is allocated.
  • the user plane gateway determines whether to use the DHCP mechanism to allocate an IP address according to the policy information sent by the user plane gateway, and then uses the above DHCP mechanism or non-DHCP mechanism to allocate an IP address, and The UE sends the IP address.
  • the policy can be a packet format matching and forwarding mode. For example, if a DHCP request packet sent by the UE is received, it is assigned an IP address. If the RADIS authentication packet sent by the UE is received, it is forwarded to the AAA Server, and the AAA Server authenticates and assigns an IP address. Further, if the AAA Server only authenticates but does not assign an IP address, the UGW continues to use the DHCP mechanism to assign an IP address.
  • the server may fail to assign an IP address.
  • the server may return a response message to the user plane gateway to notify the user that the server fails to allocate an IP address.
  • the user interface gateway can assign an IP address by other means.
  • FIG. 4 is a schematic flowchart of a method for allocating an IP address according to an embodiment of the present invention.
  • the CGW in FIG. 4 is an example of a control plane gateway in the method shown in FIGS. 2 and 3.
  • the UE sends a request message to the CGW, and the CGW receives the request message sent by the UE.
  • the CGW determines, according to the received request message, that the IP address is allocated by itself.
  • the CGW can determine to assign an IP address by itself according to its own capabilities, the real-time status of the capabilities, or the information of the UE.
  • the CGW may also determine whether to assign an IP address by itself according to the information carried in the request message or the name of the request message.
  • the CGW can determine that it can directly allocate IP from the IP address pool as a DHCP server and allocate an IP address from the IP address pool.
  • the CGW returns the allocated IP address to the UE.
  • CGW can directly send the IP address
  • the UE can also forward the IP address to the UE through the network element with the control plane function.
  • an IP address is allocated by the CGW, and an IP address allocation in a network in which the CU is separated is implemented.
  • FIG. 5 is a schematic flowchart of a method for allocating an IP address according to another embodiment of the present invention.
  • the same reference numerals in Fig. 5 as those in Fig. 4 denote the same meanings, and are not described herein again.
  • the CGW determines that the IP address is assigned by itself, and needs to allocate an IP address through the DHCP mechanism, and further determines that it needs to be the DHCP client to request the DHCP server to allocate an IP address. Therefore, the CGW sends a second request message to the DHCP server.
  • the server in Figure 5 is a DHCP Server.
  • the CGW can generate a request message to the DHCP server.
  • the message since the interface between the CGW and the DHCP server is in the UGW, the message must be sent to the UGW first, and then forwarded to the DHCP server by the UGW.
  • the CGW may also send a notification message to the UGW, informing the UGW to send a DHCP request message to the DHCP server, requesting the DHCP server to allocate an IP address.
  • the CGW can send a request message to, for example, the AAA Server.
  • the server in Figure 5 is an AAA Server.
  • the CGW sends a notification message to the UGW, informing the UGW to request an IP address from the AAA Server.
  • the UGW determines the address of the AAA Server through the indication information in the message sent by the CGW or its own configuration information, and constructs a request message, and sends the UE information (including the authentication information) and the service information to the AAA server.
  • the server After receiving the IP address request message sent by the UGW, the server allocates an IP address. If the server is an AAA server, the UE needs to be authenticated.
  • the server sends the assigned IP address to the UGW.
  • the server is an AAA server
  • the AAA server may only authenticate, but does not return an IP address.
  • the UGW also needs to allocate an IP address through the DHCP mechanism.
  • an IP address is allocated by a CGW joint server, and an IP address allocation in a network separated by a CU is implemented.
  • FIG. 6 is a schematic flowchart of a method for allocating an IP address according to another embodiment of the present invention.
  • the same reference numerals in Fig. 6 as those in Fig. 4 denote the same meanings, and are not described herein again.
  • the CGW After receiving the IP address request message sent by the UE, the CGW determines that the IP address is not assigned by itself, and needs to send an IP address request message to the UGW.
  • the UGW is an example of a user plane network element in the method shown in Figures 2 and 3.
  • the CGW sends, to the UGW, policy information for indicating that the UGW allocates an IP address, and the UGW receives the policy information that is sent by the CGW to indicate that the UGW allocates an IP address.
  • the UGW determines that the UGW can be used as the DHCP server, and the IP address is allocated in the UGW direct IP address pool.
  • the UGW sends the allocated IP address to the CGW, so that the CGW can send the IP address to the UE.
  • UGW can also directly send the IP address to the UE.
  • the CGW determines that the IP address is not assigned by itself, the CGW sends a message to the UGW, and the UGW allocates an IP address, thereby realizing the allocation of the IP address in the network separated by the CU.
  • FIG. 7 is a schematic flowchart of a method for allocating an IP address according to another embodiment of the present invention.
  • the same reference numerals in Fig. 6 as those in Figs. 4 and 6 denote the same meanings, and are not described herein again.
  • the UGW determines that the DHCP server is used to allocate the IP address. However, when the DHCP server cannot allocate the address as the DHCP server, the DHCP client needs to be the DHCP client to allocate the address. At this time, the UGW sends a second request message to the DHCP server. That is, at this time, the server in FIG. 7 is a DHCP Server.
  • the UGW may send a request message to, for example, the AAA Server.
  • the server in Figure 7 is an AAA Server.
  • the UGW determines the address of the AAA Server through the indication information in the message sent by the CGW or its own configuration information, and constructs a request message, and sends the UE information (including the authentication information) and the service information to the AAA server.
  • the server After receiving the IP address request message sent by the UGW, the server allocates an IP address. If the server is an AAA server, the UE needs to be authenticated.
  • the server sends the assigned IP address to the UGW.
  • the server is an AAA server
  • the AAA server may only authenticate, but does not return an IP address.
  • the UGW also needs to allocate an IP address through the DHCP mechanism.
  • the UGW sends the allocated IP address to the UE. At this time, the UGW can also send the IP address to the CGW, so that the CGW knows the allocation of the IP address.
  • an IP address is allocated by the UGW joint server, and the IP address allocation in the network separated by the CU is realized.
  • FIG. 8 to FIG. 10 show a control plane gateway and a user plane gateway for assigning an IP address according to an embodiment of the present invention.
  • control plane gateway 800 of the embodiment of the present invention includes a receiving unit 810, a determining unit 820, an allocating unit 830, and a transmitting unit 840.
  • the receiving unit 810 is configured to receive a first request message sent by the user equipment UE.
  • the determining unit 820 is configured to determine, according to the first request message, whether the IP address is allocated by the control plane gateway.
  • the allocating unit 830 is configured to allocate an IP address when the determining unit 820 determines that the IP address is assigned by the control plane gateway.
  • the sending unit 840 is configured to send, to the user plane gateway, a message that triggers the user plane gateway to allocate an IP address and/or carries policy information indicating the user plane gateway assigning an IP address when the determining unit 820 determines that the IP address is not assigned by the control plane gateway.
  • the control plane gateway implemented by the present invention can allocate an IP address in a network separated by CUs.
  • the first request message may carry at least one of a service type requested by the UE, an APN corresponding to the UE, identity information of the UE, and authentication key information of the UE.
  • the determining unit 820 is specifically configured to determine, according to at least one of a service type, an APN, an identity information, and an authentication key information carried in the first request message, whether the IP address is allocated by the control plane gateway.
  • the determining unit 820 can also be determined based on the real-time status of its capabilities or capabilities.
  • the control plane gateway determines whether to assign an IP address by itself according to specific conditions, and can fully utilize network resources to improve the efficiency of allocating IP addresses.
  • the determining unit is specifically configured to determine, according to the type of the first request message, whether the IP address is allocated by the control plane gateway.
  • the allocating unit 830 may be specifically configured to locally allocate an IP address or allocate an IP address through a server.
  • the allocating unit 830 may be specifically configured to send, to the user plane gateway, a message for instructing the user plane gateway to send a second request message to the server, where the second request message is used to request the server to allocate an IP address; and the receiving server passes the user plane.
  • the IP address forwarded by the gateway may be specifically configured to send, to the user plane gateway, a message for instructing the user plane gateway to send a second request message to the server, where the second request message is used to request the server to allocate an IP address; and the receiving server passes the user plane.
  • the IP address forwarded by the gateway.
  • the allocating unit 830 may be specifically configured to send a message of the third request message to the server, where the third request message is used to request the server to allocate an IP address; and receive the IP address sent by the server.
  • the allocating unit 830 may be specifically configured to send a third request message to the server by using the user plane gateway; and receive an IP address forwarded by the server through the user plane gateway.
  • the server can be a DHCP server.
  • the allocating unit 830 is further configured to send, by using the user plane gateway, a request message for authenticating the UE to the server having the authentication function; and receiving the server with the authentication function through the user.
  • the authentication response message forwarded by the gateway; and according to The authentication response message determines that the server having the authentication function successfully authenticates the UE.
  • the server with the authentication function may be an AAA server, and the RADIUS authentication may be performed on the UE.
  • the receiving module unit 810 is further configured to receive a fourth request message sent by the user plane gateway, where the fourth request message is after the user plane gateway receives the message that the UE sends the request to allocate the IP address.
  • the sending unit 840 is further configured to send the IP address to the UE.
  • FIG. 9 is a schematic block diagram of a control plane gateway 900 according to an embodiment of the present invention.
  • the control plane gateway shown in FIG. 9 includes a receiver 910, a processor 920, a transmitter 930, a memory 940, and a system bus 950.
  • the processor 920, the memory 940, the receiver 910, and the transmitter 930 are connected by a bus system 950 for storing instructions for executing instructions stored by the memory 940 to control the receiver 910 to receive signals.
  • the transmitter 930 is controlled to send a signal.
  • the control plane gateway 900 may correspond to the control plane gateway in the method shown in FIGS. 2 and 3, or may correspond to the control plane gateway shown in FIG. Specifically, the receiver 910 corresponds to the receiving unit 810 in FIG. 8, the processor 920 corresponds to the determining unit 810 and the allocating unit 830 in FIG. 8, and the transmitter 930 corresponds to the transmitting unit 840 in FIG.
  • the above and other operations and/or functions of the various units in the control plane gateway 900 of the embodiment of the present invention implement respective flows of the respective methods of FIGS. 2 through 7, respectively. It should be understood that in the process of the control plane gateway 900 implementing the flow of any of the methods of FIG. 2 to FIG.
  • the processor 920 is configured to execute the instructions stored by the memory 940 to control the receiver 910 to receive the corresponding method flow.
  • the various messages or messages received by the ingress device, and the various messages or messages sent by the access point device in the corresponding method flow are sent by the sender 930.
  • the sender 930 For brevity, no further details are provided herein.
  • FIG. 10 is a schematic block diagram of a user plane gateway 1000 according to an embodiment of the present invention.
  • the user plane gateway 1000 shown in FIG. 10 includes a receiving unit 1010, a determining unit 1020, and an allocating unit 1030.
  • the receiving unit 1010 is configured to receive the first request message sent by the UE, receive a message sent by the control plane gateway to trigger the user plane gateway to allocate an IP address, or receive the first request message sent by the UE, and carry the control plane to send A message indicating policy information for assigning an IP address to the user plane gateway.
  • the determining unit 1020 is configured to: when the receiving unit receives the first request message sent by the UE, determine, according to the first request message, that the IP address is locally allocated by the user plane gateway or the IP address is allocated by the server; and is used by the receiving unit to receive the control plane gateway.
  • the allocating unit 1030 is configured to locally allocate an IP address when the determining unit 1020 determines that the IP address is locally allocated by the user plane gateway.
  • the allocating unit 1030 is further configured to allocate an IP address by the server when the determining unit 1020 determines that the IP address is allocated by the server.
  • the user plane gateway of the embodiment of the present invention may allocate an IP address in a network separated by CUs.
  • the determining unit 820 is specifically configured to determine, according to the type of the first request message, that the IP address is locally allocated by the user plane gateway or the IP address is allocated by the server; the determining unit 820 is further configured to use the type and policy information according to the first request message. Make sure that the IP address is assigned locally by the user plane gateway or by the server.
  • the type of the first request message indicates that the request message is a message requesting the user plane gateway to assign an IP address to the UE.
  • the allocating unit 1030 may be specifically configured to send a message of the second request message to the server, where the second request message is used to request the server to allocate an IP address; and receive the IP address sent by the server.
  • the server can be a DHCP server.
  • the allocating unit 1030 is further configured to send a request message for authenticating the UE to the server having the authentication function before receiving the IP address by using the DHCP server; and receiving the authentication function.
  • the server with the authentication function may be an AAA server, and the RADIUS authentication may be performed on the UE.
  • the user plane gateway may further include a sending unit, configured to send an IP address to the UE or send an IP address to the control plane gateway, so that the control plane gateway sends the IP address to the UE.
  • a sending unit configured to send an IP address to the UE or send an IP address to the control plane gateway, so that the control plane gateway sends the IP address to the UE.
  • FIG. 11 is a schematic block diagram of a user plane gateway 1100 according to an embodiment of the present invention.
  • the control plane gateway shown in FIG. 11 includes a receiver 1110, a processor 1120, a transmitter 1130, a memory 1140, and a system bus 1150.
  • the processor 1120, the memory 1140, the receiver 1110, and the transmitter 1130 are connected by a bus system 1150 for storing instructions, and the processor 1120 is configured to execute instructions stored by the memory 1140 to control the receiver 1110 to receive signals. And controlling the transmitter 1130 to send a signal.
  • the user plane gateway 1100 may correspond to the user plane gateway in the method shown in FIG. 2 and FIG. 3, and may also correspond to the user plane gateway shown in FIG. Specifically, the receiver 1110 corresponds to the receiving unit 1010 in FIG. 10, the processor 1120 corresponds to the determining unit 1010 and the allocating unit 1030 in FIG. 10, and the transmitter 1130 corresponds to the transmitting unit in FIG.
  • the above and other operations and/or functions of the various units in the user plane gateway 1100 of the embodiment of the present invention implement respective processes of the respective methods of FIGS. 2 through 7, respectively. It should be understood that, in the process that the user plane gateway 1100 implements the flow of any one of the methods of FIG. 2 to FIG.
  • the processor 1120 is configured to execute the instruction stored by the memory 1140 to control the receiver 1110 to receive the corresponding method flow.
  • the various messages or messages received by the ingress device and the various messages or messages sent by the access point device in the corresponding method flow are sent by the sender 1130.
  • the sender 1130 For brevity, no further details are provided herein.
  • the disclosed systems, devices, and methods may be implemented in other manners.
  • 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 mutual 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 in an electrical, mechanical or other form.
  • the units described as separate components may or may not be physically separated, 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 purpose 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 single unit. Yuanzhong.
  • 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 or contributes to the prior art, or a part of the technical solution, may be embodied in the form of a software product, which is 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 foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like. .

Landscapes

  • Data Exchanges In Wide-Area Networks (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本发明提供了一种分配IP地址的方法、控制面网关和用户面网关。分配IP地址的方法为：控制面网关接收用户设备UE发送的第一请求消息；控制面网关根据第一请求消息确定是否由控制面网关分配IP地址；控制面网关确定由控制面网关分配IP地址时，分配IP地址；控制面网关确定不由控制面网关分配IP地址时，向用户面网关发送触发用户面网关分配IP地址和/或携带指示用户面网关分配IP地址的策略信息的消息。本发明的技术方案方法可以实现在CU分离的网络中分配IP地址。

Description

分配互联网协议地址的方法、控制面网关和用户面网关 技术领域
本发明涉及通信领域，尤其涉及一种分配互联网协议(Internet Protocol，IP)地址的方法、控制面网关和用户面网关。
背景技术
在控制面与用户面分离(Control and User Plane Separation，CUPS)的网络架构中，控制面与用户面分离，即将一些或者全部兼具控制面和用户面的功能的网元，拆分成控制面网元和用户面网元两个实体。
CUPS也称为CU分离。CU分离的网络架构中，控制面网元具有控制面功能，主要包括与其他网元之间的信令连接、处理用户设备的移动性管理和会话管理请求、管理用户设备的上下文和建立传输数据的通道等。用户面网元具有用户面功能，主要包括发送用户设备的上下行数据报文、执行针对数据报文的服务质量(Quality of Service，QoS)的控制和流量统计等。
比如，将传统的公用数据网网关(Public Data Network GateWay，PGW)拆分成CGW(Control GateWay)和UGW(User GateWay)。UGW具备PGW的控制面功能，UGW具备PGW的用户面功能。
传统的演进型分组核心网(Evolved Packet Core，EPC)网络中，互联网协议(Internet Protocol，IP)地址的分配由PGW负责。以动态IP地址分配的机制分配IP地址的具体方法为：网络设备(如MME)根据用户设备(User Equipment，UE)请求的业务和UE的签约信息，判断需要为UE分配动态IP地址，并发送请求给PGW，要求PGW为UE分配地址。如果PGW具备了分配IP地址的能力(如配置有IP地址池)，则PGW直接返回分配的IP地址给UE；如果PGW不具备分配IP地址的能力，则需要向外部具备分配IP地址功能的服务器(如DHCP服务器)请求分配IP地址。当PGW收到外部服务器分配的地址后，再发送给UE。
而CU分离后，CU分离的网络中，引入了一个技术问题：PGW分离为UGW和CGW后，如何分配UE的IP地址。
发明内容
本发明提供了一种分配IP地址的方法、控制面网关和用户面网关，能够在CU分离的网络中为UE分配IP地址。
第一方面，本发明提供了一种分配IP地址的方法。首先控制面网关接收UE发送的第一请求消息；然后控制面网关根据所述第一请求消息确定是否由控制面网关分配IP地址；控制面网关确定由控制面网关分配IP地址时，分配IP地址；控制面网关确定不由控制面网关分配IP地址时，向用户面网关发送触发用户面网关分配IP地址和/或携带指示所述用户面网关分配IP地址的策略信息的消息的策略信息。
本发明的分配IP地址的方法，控制面网关接收到UE的IP地址请求消息后，先确定是否由自己分配IP地址。若控制面网关确定由自己分配IP地址，则继续分配IP地址；若控制面网关确定不由自己分配IP地址，则控制面网关向用户面网关发送消息，以便于用户面网关分配IP地址。本发明的技术方案使得在CU分离的网络中可以由控制面网关或用户面网关来为UE分配IP地址。
在一种可能的实现方式中，第一请求消息携带UE请求的业务类型、UE对应的接入点名称(Access Point Name，APN)、UE的身份信息和UE的鉴权密钥信息中的至少一种信息。此时，控制面网关可以根据第一请求携带的上述信息来确定是否由控制面网关分配IP地址。控制面网关还可以根据自己的能力或能力的实时状态来确定。控制面网关根据具体情况来确定是否由自己分配IP地址，可以充分利用网络资源，提高分配IP地址的效率。
在一种可能的实现方式中，控制面网关根据第一请求消息确定是否由控制面网关分配IP地址具体为：控制面网关根据第一请求消息的类型确定是否由控制面网关分配IP地址。即控制面网关在确定第一请求消息为请求控制面网关为UE分配IP地址的消息后，确定是否由控制面网关分配IP地址。
在一种可能的实现方式中，控制面网关分配IP地址的具体方式为：本地分配IP地址或通过服务器分配IP地址。
在一种可能的实现方式中，控制面网关通过服务器分配IP地址具体为：控制面网关向用户面网关发送用于指示用户面网关向服务器发送第二请求消息的消息，第二请求消息用于请求服务器分配IP地址；控制面网关接服务器通过用户面网关转发的IP地址。
在一种可能的实现方式中，控制面网关通过服务器分配IP地址具体为： 控制面网关向服务器发送第三请求消息，第三请求消息用于请求服务器分配IP地址；控制面网关接收服务器发送的IP地址。
在一种可能的实现方式中，控制面网关向服务器发送第三请求消息具体为：控制面网关通过用户面网关向服务器发送第三请求消息。控制面网关接收服务器发送的IP地址具体为：控制面网关接收服务器通过用户面网关转发的IP地址。
在一种可能的实现方式中，服务器为动态主机配置协议(Dynamic Host Configuration Protocol，DHCP)服务器。
在一种可能的实现方式中，当服务器为DHCP服务器时，在控制面网关通过DHCP服务器分配IP地址之前，控制面网关通过用户面网关向具有鉴权功能的服务器发送用于请求对UE进行鉴权的消息；控制面网关接收具有鉴权功能的服务器通过用户面网关转发的鉴权响应消息；控制面网关根据鉴权响应消息确定具有鉴权功能的服务器对UE鉴权成功。
在一种可能的实现方式中，控制面网关本地分配IP地址前，直接或通过用户面网关向具有鉴权功能的服务器发送用于请求对UE进行鉴权的消息，并直接或通过用户面网关接收具有鉴权功能的服务器发送的鉴权响应消息，然后根据鉴权响应消息确定对UE鉴权成功。
在上述可能的实现方式中，可以在对UE鉴权成功后才为UE分配IP地址。其中，具有鉴权功能的服务器可以是验证、授权和记账(Authentication、Authorization、Accounting，AAA)服务器，可以对UE进行远程访问拨号用户服务(Remote Authentication Dial In User Service，RADIUS)鉴权。
在一种可能的实现方式中，在控制面网关分配IP地址前，控制面网关接收用户面网关发送的第四请求消息，第四请求消息为用户面网关接收UE发送的请求分配IP地址的消息后生成的消息，或为UE向用户面网关发送的请求分配IP地址的消息。
在这种可能的实现方式中，控制面网关接收到UE的IP地址请求消息后，还需接收用户面网关上报的UE通过用户面发送的IP地址请求消息，才分配IP地址。
在第一种可能的实现方式中，控制面网关分配IP地址后，向UE发送IP地址。控制面网关可以直接向UE发送IP地址，也可以通过移动性管理网元或基站等网元向UE转发IP地址。
该实现方式使得UE在缺省承载建立的过程中分配IP地址。
第二方面，本发明提供了一种分配IP地址的方法。用户面网关接收用户设备UE发送的第一请求消息时，根据所述第一请求消息确定由所述用户面网关本地分配IP地址或通过服务器分配IP地址；和用户面网关接收控制面网关发送的用于触发用户面网关分配IP地址的消息时，确定由用户面网关本地分配IP地址或通过服务器分配IP地址；和用户面网关接收UE发送的第一请求消息和接收控制面网关发送的携带用于指示用户面网关分配IP地址的策略信息的消息时，根据第一请求消息和策略信息确定由用户面网关本地分配IP地址或通过服务器分配IP地址。用户面网关确定由用户面网关本地分配IP地址时，本地分配IP地址；用户面网关确定通过服务器分配IP地址时，通过服务器分配IP地址。
本发明的分配IP地址的方法，用户面网关接收到UE请求分配IP地址的消息或/和控制面网关发送的策略信息后，根据请求消息或/和策略信息确定由自己直接分配IP地址还是通过服务器分配IP地址，并执行相应的分配IP地址的流程。本发明的技术方案使得在CU分离的网络中可以由用户面网关或服务器来为UE分配IP地址。
在一种可能的实现方式中，根据第一请求消息确定由用户面网关本地分配IP地址或通过服务器分配IP地址的具体实现方式为：用户面网关根据第一请求消息的类型确定由用户面网关本地分配IP地址或通过服务器分配IP地址；根据第一请求消息和策略信息确定由用户面网关本地分配IP地址或通过服务器分配IP地址的具体实现方式为：用户面网关根据第一请求消息的类型和策略信息确定由用户面网关本地分配IP地址或通过服务器分配IP地址。第一请求消息的类型是指该请求消息为请求用户面网关为UE分配IP地址的消息。
在该实现方式中，用户面网关接收到UE请求分配IP地址的消息后，根据从控制面网关接收的策略消息来确定由自己还是通过服务器分配IP地址，从而使得在CU分离的网络中用户面网关根据控制面网关的决策来进行IP地址的分配。
在一种可能的实现方式中，用户面网关通过服务器分配IP地址具体为：用户面网关向服务器发送第二请求消息的消息，第二请求消息用于请求服务器分配IP地址；用户面网关接收服务器发送的IP地址。
在一种可能的实现方式中，服务器为DHCP服务器。
在一种可能的实现方式中，在用户面网关通过服务器分配IP地址之前，用户面网关向具有鉴权功能的服务器发送用于请求对UE进行鉴权的请求消息；用户面网关接收具有鉴权功能的服务器发送的鉴权响应消息；用户面网关根据鉴权响应消息确定具有鉴权功能的服务器对UE鉴权成功。
在一种可能的实现方式中，用户面网关直接分配IP地址前，向具有鉴权功能的服务器发送用于请求对UE进行鉴权的消息，并接收具有鉴权功能的服务器发送的鉴权响应消息，然后根据鉴权响应消息确定对UE鉴权成功。
在上述可能的实现方式中，可以在对UE鉴权成功后才为UE分配IP地址。其中，具有鉴权功能的服务器可以是AAA服务器，可以对UE进行RADIUS鉴权。
在一种可能的实现方式中，该方法还包括：用户面网关向UE发送IP地址，或向控制面网关发送IP地址，以便于控制面网关向UE发送IP地址。
第三方面，提供了一种控制面网关。该网关包括接收单元，用于接收用户设备UE发送的第一请求消息；确定单元，用于根据第一请求消息确定是否由控制面网关分配IP地址；分配单元，用于在确定单元确定由控制面网关分配IP地址时，分配IP地址；发送单元，用于在确定单元确定不由控制面网关分配IP地址时，向用户面网关发送触发所述用户面网关分配IP地址和/或携带指示用户面网关分配IP地址的策略信息的消息。
本发明的控制面网关，接收到UE的IP地址请求消息后，先确定是否由自己分配IP地址。若控制面网关确定由自己分配IP地址，则继续分配IP地址；若控制面网关确定不由自己分配IP地址，则控制面网关向用户面网关发送消息，以便于用户面网关分配IP地址。本发明的技术方案使得在CU分离的网络中可以由控制面网关或用户面网关来为UE分配IP地址。
在一种可能的实现方式中，第一请求消息携带UE请求的业务类型、UE对应的APN、UE的身份信息和UE的鉴权密钥信息中的至少一种信息。此时，确定单元可以根据第一请求携带的上述信息来确定是否由控制面网关分配IP地址。确定单元还可以根据自己的能力或能力的实时状态来确定。确定单元根据具体情况来确定是否由自己分配IP地址，可以充分利用网络资源，提高分配IP地址的效率。
在一种可能的实现方式中，确定单元具体用于根据第一请求消息的类型 确定是否由控制面网关分配IP地址。第一请求消息的类型是指该请求消息为请求控制面网关为UE分配IP地址的消息。
在一种可能的实现方式中，分配单元具体用于本地分配IP地址或通过服务器分配IP地址。
在一种可能的实现方式中，分配单元具体用于向用户面网关发送用于指示用户面网关向服务器发送第二IP地址请求消息的消息，第二IP地址请求消息用于请求服务器分配IP；并接收服务器通过用户面网关转发的IP地址。
在一种可能的实现方式中，分配单元具体用于：向服务器发送第三IP地址请求消息，第三IP地址请求消息用于请求服务器分配IP地址；接收服务器发送的IP地址。
在一种可能的实现方式中，分配单元具体用于通过用户面网关向服务器发送第三IP地址请求消息；并接收服务器通过用户面网关转发的IP地址。
在一种可能的实现方式中，服务器为DHCP服务器。
在一种可能的实现方式中，当服务器为DHCP服务器时，分配单元在通过DHCP服务器分配IP地址之前，还用于通过用户面网关向具有鉴权功能的服务器发送用于请求对UE进行鉴权的请求消息；并接收具有鉴权功能的服务器通过用户面网关转发的鉴权响应消息；然后根据鉴权响应消息确定具有鉴权功能的服务器对UE鉴权成功。
在一种可能的实现方式中，分配单元在本地分配IP地址前，还用于：直接或通过用户面网关向具有鉴权功能的服务器发送用于请求对UE进行鉴权的消息，并直接或通过用户面网关接收具有鉴权功能的服务器发送的鉴权响应消息，然后根据鉴权响应消息确定对UE鉴权成功。
在上述可能的实现方式中，可以在对UE鉴权成功后才为UE分配IP地址。其中，具有鉴权功能的服务器可以是AAA服务器，可以对UE进行RADIUS鉴权。
在一种可能的实现方式中，接收单元在分配单元分配IP地址前，还用于接收用户面网关发送的第四请求消息，第四请求消息为用户面网关接收UE发送的请求分配IP地址的消息后生成的消息，或为UE向用户面网关发送的请求分配IP地址的消息。
在一种可能的实现方式中，发送单元还用于向UE发送所述IP地址。
第四方面.提供了一种用户面网关。该用户名网关包括接收单元，用于 接收UE发送的第一请求消息、接收控制面网关发送的用于触发用户面网关分配IP地址的消息或接收UE发送的第一请求消息及控制面网关发送的携带用于指示用户面网关分配IP地址的策略信息的消息。确定单元，用于在接收单元接收UE发送的第一请求消息时根据第一请求消息确定由用户面网关本地分配IP地址或通过服务器分配IP地址；和用于在接收单元接收控制面网关发送的用于触发用户面网关分配IP地址的消息时，确定由用户面网关本地分配IP地址或通过服务器分配IP地址；和用于在接收单元接收UE发送的第一请求消息及控制面网关发送的携带用于指示用户面网关分配IP地址的策略信息的消息时，根据第一请求消息和策略信息确定由用户面网关本地分配IP地址或通过服务器分配IP地址；分配单元，用于在确定单元确定由用户面网关本地分配IP地址时，本地分配IP地址；分配单元还用于在确定单元确定通过服务器分配IP地址，通过服务器分配IP地址。
本发明的用户面网关，接收UE发送的请求分配IP地址的消息，并确定确定由自己还是通过服务器分配IP地址。本发明的技术方案使得在CU分离的网络中可以由用户面网关或服务器来为UE分配IP地址。
在一种可能的实现方式中，确定单元具体用于根据第一请求消息的类型确定由用户面网关本地分配IP地址或通过服务器分配IP地址；确定单元还具体用于根据第一请求消息的类型和策略信息确定由用户面网关本地分配IP地址或通过服务器分配IP地址。第一请求消息的类型是指该请求消息为请求用户面网关为UE分配IP地址的消息。
在一种可能的实现方式中，分配单元具体用于向服务器发送第二IP地址请求消息的消息，第二IP地址请求消息用于请求服务器分配IP地址；并接收服务器发送的IP地址。
在一种可能的实现方式中，分配单元在通过服务器分配IP地址之前，还用于向具有鉴权功能的服务器发送用于请求对UE进行鉴权的请求消息；并接收具有鉴权功能的服务器发送的鉴权响应消息；然后根据鉴权响应消息确定具有鉴权功能的服务器对UE鉴权成功。
在一种可能的实现方式中，分配单元本地分配IP地址前，还用于向具有鉴权功能的服务器发送用于请求对UE进行鉴权的消息，并接收具有鉴权功能的服务器发送的鉴权响应消息，然后根据鉴权响应消息确定对UE鉴权成功。
在上述可能的实现方式中，可以在对UE鉴权成功后才为UE分配IP地址。其中，具有鉴权功能的服务器可以是AAA服务器，可以对UE进行RADIUS鉴权。
在一种可能的实现方式中，该用户名网关还包括发送单元，用于向UE发送IP地址或向控制面网关发送IP地址，以便于控制面网关向UE发送IP地址。
第五方面.提供了一种控制面网关。该控制面网关包括接收器、发送器、存储器、处理器和总线***。接收器、发送器、存储器和处理器通过总线***相连，存储器用于存储指令，接收器和发送器分别用于接收和发送消息，处理器用于执行存储器存储的指令，并调用接收器和发送器执行第一方面或其任意一种可能的实现方式。
第六方面.提供了一种用户面网关。该用户名网关包括接收器、发送器、存储器、处理器和总线***。接收器、发送器、存储器和处理器通过总线***相连，存储器用于存储指令，接收器和发送器分别用于接收和发送消息，处理器用于执行存储器存储的指令，并调用接收器和发送器执行第二方面或其任意一种可能的实现方式。
附图说明
为了更清楚地说明本发明实施例的技术方案，下面将对本发明实施例中所需要使用的附图作简单地介绍，显而易见地，下面所描述的附图仅仅是本发明的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1是本发明的一种可能的网络架构示意图。
图2是本发明一个实施例的分配IP地址的方法的示意性流程图。
图3是本发明另一个实施例的分配IP地址的方法的示意性流程图。
图4是本发明又一个实施例的分配IP地址的方法的示意性流程图。
图5是本发明又一个实施例的分配IP地址的方法的示意性流程图。
图6是本发明又一个实施例的分配IP地址的方法的示意性流程图。
图7是本发明又一个实施例的分配IP地址的方法的示意性流程图。
图8是本发明一个实施例的控制面网元的示意性框架图。
图9是本发明另一个实施例的控制面网元的示意性框架图。
图10是本发明一个实施例的用户面网元的示意性框架图。
图11是本发明另一个实施例的用户面网元的示意性框架图。
具体实施方式
为使本发明实施例的目的、技术方案和优点更加清楚，下面将结合本发明实施例中的附图，对本发明实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例是本发明一部分实施例，而不是全部的实施例。基于本发明中的实施例，本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例，都属于本发明保护的范围。
图1示出了本发明实施例的一种CPUS网络架构示意图，其主要包括UE、演进型基站(Evolved Node B，eNB)、控制面网关、用户面网关和服务器(Server)。
图1中虚线表示通过控制面传输消息，实现表示通过用户面传输消息或报文。
UE可称为接入终端、终端设备、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、终端、无线通信设备、用户代理或用户装置。UE可以是蜂窝电话、无绳电话、会话启动协议(Session Initiation Protocol，SIP)电话、无线本地环路(Wireless Local Loop，WLL)站、个人数字处理(Personal Digital Assistant，PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备以及未来5G网络中的终端设备等。UE可以与控制面网通过信令消息通信，也可以与用户面网关收发数据报文。
eNB只是本发明适用的一种CP分离的网络架构中一种可能的组成部分，其也可以是移动性管理网元(Mobility Management Entity，MME)，或者是未来5G网络中的基站设备、小基站设备等。UE与控制面网关和用户面网关之间通过eNB通信，当然，UE与控制面网关和用户面网关之间也可以直接通信，即CP分离的网络架构种可以没有eNB，本发明对此并不限定。
控制面网关具有控制面的接口，主要用于与其他网元之间的进行信令连接，处理用户的移动性管理和会话管理请求，管理用户的上下文和建立传输数据的通道。控制面网关可以用于静态IP地址分配或动态IP地址分配时的网关自主分配。控制面网关可以是PGW分离后具有控制面功能的CGW。
用户面网关具有用户面的接口，主要用于发送用户的上下行数据报文、执行针对数据报文的QoS控制和流量统计等。用户面网关可以用于动态IP地址分配时的网关自主分配、动态IP地址分配时的外部网络分配。Server可以分配IP地址，与用户面网关相连可以收发数据报文。用户面网关可以是PGW分离后具有用户面功能的UGW。
下面结合图2，对本发明一个实施例提供的方案进行说明。
S201，控制面网关接收UE发送的第一请求消息。
第一请求消息可以携带UE请求的业务类型、UE对应的APN、UE的身份信息和UE的鉴权密钥信息等等信息。此时，控制面网关可以根据第一请求携带的上述信息来确定是否由控制面网关分配IP地址。控制面网关还可以根据自己的能力或能力的实时状态来确定。控制面网关根据具体情况来确定是否由自己分配IP地址，可以充分利用网络资源，提高分配IP地址的效率。
UE需要建立会话或建立承载时，会向控制面网关发送IP地址请求消息，该消息可以携带UE的信息和/或服务器的信息。
S202，控制面网关确定是否由控制面网关分配IP地址。
控制面网关接收到UE的IP地址请求消息后，确定是否需要由自己来分配IP地址。控制面网关确定是否由自己来分配IP地址的可能的实现方式如下：控制面网关可以根据UE请求的不同的业务类型(或者UE签约的业务类型)来确定。比如：若UE请求MBB业务、车联网业务或物联网业务等业务，则确定由控制面网关来获分配IP地址；若UE请求企业网业务、公共安全业务、私有云业务等的业务，则不由控制面网关分配IP地址。
控制面网关还可以根据UE请求的APN来确定。比如：当UE请求接入提供MBB业务、车联网业务或物联网业务等的APN时，确定由控制面网关分配IP地址，当请求接入提供企业网业务、公共安全业务、私有云业务等的APN时，确定不由控制面网关分配IP地址。
控制面网关还可以根据自己的能力来确定。比如控制面网关配置有本地IP地址池，则确定由控制面网关分配，如没有，则不由控制面网关分配。
控制面网关还可以根据自己的能力的实时状态来确定。比如：虽然控制面网关配置有本地IP地址池，但是地址池中的地址已经分配完了，这个时候就不能由控制面网关来分配IP地址。
控制面网关还可以根据第一请求消息的类型确定是否由控制面网关分配IP地址，即当控制面网关确定第一请求消息为请求控制面网关为UE分配IP地址的消息后，确定是否由控制面网关分配IP地址。
S203，控制面网关确定由控制面网关分配IP地址时，分配IP地址。
当控制面网关确定由自己分配IP地址时，其还可以进一步确定是通过DHCP机制分配IP地址，还是通过非DHCP机制分配IP地址。
DHCP机制是一种IP地址分配方式，通常有两个实体参与，一个是DHCP Client，另一个是DHCP Server。DHCP Client请求DHCP Server分配IP地址，DHCP Server为DHCP Client分配IP地址。IP地址可以是IPv4地址、IPv6完整地址或其他地址。
当控制面网关确定通过DHCP机制分配IP地址时，若其可以作为DHCP Server，则控制面网关直接从IP地址池中为UE分配IP地址，并向UE直接发送或是通过具有控制面功能的网元向UE发送该IP地址。
如果控制面网关确定通过DHCP机制分配IP地址，但其自己不能分配IP地址时，其可以作为DHCP Client请求DHCP Server分配IP地址。
控制面网关作为DHCP Client请求DHCP Server分配IP地址有两种实现方式，一种实现方式是控制面网关自己构建DHCP请求消息，发送给DHCP Server，但是因为与DHCP Server的接口在用户面网关(如PGW分离后的UGW)，所以该消息必须先要发给用户面网关，再由用户面网关转发给DHCP Server。DHCP Server分配IP地址后通过用户面网关发送给控制面网关，控制面网关再将IP地址发送给UE。另一种实现方式是控制面网关通知用户面网关发送DHCP请求消息给DHCP Server，由DHCP Server分配IP地址，然后再由用户面网关将IP地址转发给控制面网关，控制面网关再将IP地址发送给UE。可选的，控制面网关还可以将IP地址通知给用户面网关。
当控制面网关确定采用非DHCP机制分配IP地址时，一种实现方式为：控制面网关自己构建请求消息，发送给外部服务器，但是因为与外部服务器的接口在用户面网关，所以该消息必须先要发给用户面网关，再由用户面网关转发给外部服务器；外部服务器将分配的IP地址发送给控制面网关，然后控制面网关再发送给UE。可选的，控制面网关还可以将IP地址通知给用户面网关。
如当外部服务器为AAA Server时，用户面网关通过控制面网关发送的 消息中的指示信息或者自身的配置信息确定AAA Server的地址，并构建请求消息，将UE信息(包括鉴权信息)、业务信息发送给AAA Server。AAA Server分配IP地址后，将IP地址返回用户面网关。此时，AAA Server可能只鉴权不返回IP地址。如果AAA Server没有返回IP地址，用户面网关还需要重新通过DHCP的方式分配IP地址。
上述方式介绍的是在缺省承载建立过程中分配并向UE发送IP地址。控制面网关也可以在缺省承载建立过程后分配并向UE发送IP地址。此时，控制面网关接收UE发送的IP地址请求消息并判断由自己分配IP地址后，不会立即分配IP地址。而是在缺省承载建立过程之后，UE会向用户面网关发送用户面的IP地址请求消息，用户面网关向该消息上报给控制面网关。控制面网关接收到该消息后，才会使用上述的DHCP机制或非DHCP机制分配IP地址，并向UE发送该IP地址。
当控制面网关通过服务器分配IP地址时，服务器可能分配IP地址失败，此时，服务器向控制面网关返回的可以是一个通知控制面网关该服务器分配IP地址失败的响应消息。控制面网关接收到该响应消息后，可以通过其他方式分配IP地址。
S204，控制面网关确定不由控制面网关分配IP地址时，控制面网关向用户面网关发送触发用户面网关分配IP地址和/或携带指示所述用户面网关分配IP地址的策略信息的消息。
控制面网关向用户面网关发送IP地址请求消息中可以根据具体需求携带以下信息：UE信息、服务信息、承载标识、指示标识或外部服务器标识。
具体地，指示标识可以用于指示由用户面网关分配地址或由用户面网关联合外部服务器分配IP地址。若没有指示标识，用户面网关可以从消息名称中判断由用户面网关分配地址或指示用户面网关联合外部服务器分配IP地址。
如果控制面网关指示用户面网关联系外部服务器分配IP地址，指示标识可以用于指示外部服务器分配IP地址，请求消息中可以携带外部服务器的IP地址或标识。
这样，用户面网关接收到控制面网关发送的请求消息后，可以根据该请求消息中携带的各种信息来分配IP地址。
图3为本发明实施例提供的分配IP地址的方法的示意性流程图。
S301，用户面网关接收UE发送的第一请求消息时，根据第一请求消息确定由用户面网关本地分配IP地址或通过服务器分配IP地址；和用户面网关接收控制面网关发送的用于触发用户面网关分配IP地址的消息时，确定由用户面网关本地分配IP地址或通过服务器分配IP地址；和用户面网关接收UE发送的第一请求消息和接收控制面网关发送的携带用于指示用户面网关分配IP地址的策略信息的消息时，根据第一请求消息和策略信息确定由用户面网关本地分配IP地址或通过服务器分配IP地址。用户面网关可以是PGW分离后的UGW。
第一请求消息的类型是指该请求消息为请求用户面网关为UE分配IP地址的消息，此时，根据第一请求消息确定由用户面网关本地分配IP地址或通过服务器分配IP地址具体为：用户面网关在确定第一请求消息为请求用户面网关为UE分配IP地址的消息后，确定由用户面网关本地分配IP地址或通过服务器分配IP地址。根据第一请求消息和策略信息确定由用户面网关本地分配IP地址或通过服务器分配IP地址具体为：用户面网关在确定第一请求消息为请求用户面网关为UE分配IP地址的消息后，根据策略信息确定由用户面网关本地分配IP地址或通过服务器分配IP地址。
用户面网关接收的控制面网关发送的策略信息中可以根据具体需求携带以下信息：UE信息、服务信息、承载标识、指示标识或外部服务器标识。
具体地，指示标识可以用于指示由用户面网关分配地址。若没有指示标识，用户面网关可以从消息名称中确定由用户面网关分配地址。
指示标识还可以用于指示外部服务器的IP地址，或请求消息中可以携带外部服务器的IP地址或标识。
用户面网关可以在接收到控制面网关的策略信息后，根据策略信息确定由自己还是通过服务器在缺省承载建立的过程中为UE分配IP地址；也可以是在接收到UE的请求分配IP地址的请求消息后，根据请求消息确定由自己还是通过服务器在缺省建立过程后为UE分配IP地址。当然，用户面网关也可以是在既接收到控制面网关发送的策略信息，又接收到UE发送的请求分配IP地址的请求消息后，根据策略信息和请求消息确定由自己直接分配IP地址还是通过服务器分配IP地址。
S302，用户面网关确定由用户面网关本地分配IP地址时，本地分配IP地址。
当用户面网关根据控制面网关发送的IP地址请求消息的名称或该消息中携带的指示标识或其他信息确定由用户面网关确定分配IP地址后，还需进一步确定是否通过DHCP机制分配IP地址。
当用户面网关确定通过DHCP机制分配IP地址，并且其可以作为DHCP Server时，则用户面网关直接从IP地址池中为UE分配P地址，然后在缺省承载建立的过程中先向控制面网关发送该IP地址，再由控制面网关向UE发送该IP地址，或者在缺省承载建立过程后向UE直接发送IP地址。
S303，用户面网关确定通过服务器分配IP地址时，通过服务器分配IP地址。
当用户面网关确定通过DHCP机制分配IP地址时，用户面网关可以作为DHCP Client请求DHCP Server分配IP地址，具体实现方式是：用户面网关发送DHCP请求消息给DHCP Server，由DHCP Server分配IP地址，然后用户面网关接收到DHCP Server发送的IP地址后，再由用户面网关将IP地址在缺省承载建立过程中发送给控制面网关，由控制面网关将IP地址发送给UE，或用户面网关在缺省承载建立过程后将IP地址直接发送给UE。可选的，用户面网关还可以将IP地址通知给控制面网关。
当用户面网关确定采用非DHCP机制分配IP地址时，一种实现方式为：用户面网关构建请求消息，发送给外部服务器，请求外部服务器分配IP地址；然后用户面网关接收到外部服务器发送的IP地址后，再由用户面网关将IP地址在缺省承载建立过程中发送给控制面网关，由控制面网关将IP地址发送给UE，或用户面网关在缺省承载建立过程后将IP地址直接发送给UE。可选的，用户面网关还可以将IP地址通知给控制面网关。
如当外部服务器为AAA Server时，用户面网关通过控制面网关发送的消息中的指示信息或者自身的配置信息确定AAA Server的地址，并构建请求消息，将UE信息(包括鉴权信息)、业务信息发送给AAA Server。AAA Server分配IP地址后，将IP地址返回用户面网关。此时，AAA Server可能只鉴权不返回IP地址。如果AAA Server没有返回IP地址，用户面网关还需要重新通过DHCP的方式分配IP地址。
如果请求消息中携带外部服务器的IP地址，UGW可以直接联系到外部服务器；如果请求消息中携带外部服务器的标识，UGW需要用它关联到已经保存的外部服务器的IP地址，或者通过(Domain Name System，DNS) 服务器查询到该外部服务器的IP地址。
如果控制面网关向用户面网关发送的IP地址请求消息中携带有承载标识时，当用户面网关分配IP地址，或请求服务器处分配IP地址后，可以根据确定该IP地址与承载标识所对应的承载相关联。
上述描述的是用户面网关在接收到控制面网关发送的IP地址请求消息后，即分配分配IP地址的情况，用户面网关在接收到控制面网关发送的IP地址请求消息后，若该消息携带的是指示用户面网关为UE分配IP地址的策略信息，则用户面网关还需接收到缺省承载建立过程后UE发送的IP地址请求消息，才会分配IP地址。
此时，用户面网关接收UE发送的IP地址请求消息后，根据用户面网关发送的策略信息确定是否使用DHCP机制分配IP地址，才会使用上述的DHCP机制或非DHCP机制分配IP地址，并向UE发送该IP地址。
策略可以是一种报文格式匹配和转发方式，比如：如果收到UE发送的DHCP请求报文，就为它分配IP地址。如果收到UE发送的RADIS鉴权报文，就转发到AAA Server，由AAA Server鉴权和分配IP地址。进一步，如果AAA Server只鉴权但没有分配IP地址，则UGW继续采用DHCP机制分配IP地址。
当用户面网关通过服务器分配IP地址时，服务器可能分配IP地址失败，此时，服务器向用户面网关返回的可以是一个通知用户面网关该服务器分配IP地址失败的响应消息。用户面面网关接收到该响应消息后，可以通过其他方式分配IP地址。
图4为本发明一个实施例的分配IP地址的方法的示意性流程图。图4中的CGW为图2和图3所示的方法中的控制面网关的示例。
S401，UE向CGW发送请求消息，CGW接收UE发送的请求消息。
S402，CGW根据接收到的请求消息确定由自己分配IP地址。CGW可以根据自己的能力、能力的实时状态或UE的信息等确定由自己分配IP地址。CGW也可以根据请求消息中携带的信息或请求消息的名称来确定是否由自己分配IP地址。
S403，CGW确定由自己分配IP地址后，可以确定自己可以作为DHCP Server直接从IP地址池中分配IP，并从IP地址池中分配IP地址。
S404，CGW将分配的IP地址返回给UE。CGW可以直接将IP地址发 送给UE，也可以通过具有控制面功能的网元将IP地址转发给UE。
本发明实施例的分配IP地址的方法，由CGW来分配IP地址，实现了CU分离的网络中IP地址的分配。
图5为本发明另一个实施例的分配IP地址的方法的示意性流程图。图5中与图4中相同的标记表示相同的含义，此处不再赘述。
S501，CGW确定由自己分配IP地址，且需要通过DHCP机制分配IP地址后，进一步确定自己需要作为DHCP Client请求DHCP服务器分配IP地址。因此CGW向DHCP Server发送第二请求消息。此时，图5中的服务器为DHCP Server。
此时，CGW可以自己生成请求消息发送给DHCP Server。但由于CGW与DHCP Server的接口在UGW，所以该消息必须先要发给UGW，再由UGW转发给DHCP Server。CGW也可以向UGW发送通知消息，通知UGW发送DHCP请求消息给DHCP Server，请求DHCP Server分配IP地址。
另一种情况下，CGW确定由自己分配IP地址，且需要通过非DHCP机制分配IP地址后，CGW可以向如AAA Server发送请求消息。此时，图5中的服务器为AAA Server。这种情况下，CGW向UGW发送通知消息，通知UGW向AAA Server请求IP地址。此时，UGW通过CGW发送的消息中的指示信息或者自身的配置信息确定AAA Server的地址，并构建请求消息，将UE信息(包括鉴权信息)、业务信息发送给AAA Server。
S502，服务器接收到UGW发送的IP地址请求消息后，分配IP地址。若服务器为AAA服务器，还需要对UE进行鉴权。
S503，服务器将分配的IP地址发送给UGW。此时，若服务器为AAA Server，则可能AAA Server只鉴权，而没有返回IP地址。这种情形下，在AAA Server鉴权成功的情况下，UGW还需要通过DHCP机制分配IP地址。
本发明实施例的分配IP地址的方法，由CGW联合服务器来分配IP地址，实现了CU分离的网络中IP地址的分配。
图6为本发明另一个实施例的分配IP地址的方法的示意性流程图。图6中与图4中相同的标记表示相同的含义，此处不再赘述。
S601，CGW接收UE发送的IP地址请求消息后，确定不由自己分配IP地址，此时需要向UGW发送IP地址请求消息。UGW为图2和图3所示的方法中的用户面网元的一个示例。
S602，CGW向UGW发送用于指示UGW分配IP地址的策略信息，UGW接收CGW发送的用于指示UGW分配IP地址的策略信息。
S603，UGW接收CGW发送的用于指示UGW分配IP地址的策略信息后，确定UGW可以作为DHCP Server，则UGW直接IP地址池中分配IP地址。
S604，UGW将分配的IP地址发送给CGW，以便于CGW能够将IP地址发送给UE。当然，UGW也可以直接将IP地址发送给UE。
本发明实施例的分配IP地址的方法，由CGW判断不由自己分配IP地址后，向UGW发送消息，由UGW分配IP地址，实现了CU分离的网络中IP地址的分配。
图7为本发明另一个实施例的分配IP地址的方法的示意性流程图。图6中与图4和图6中相同的标记表示相同的含义，此处不再赘述。
S701，UGW确定采用DHCP机制分配IP地址，但自己不能作为DHCP Server分配地址时，需要作为DHCP Client请求DHCP Server分配地址，此时，UGW向DHCP Server发送第二请求消息。即此时，图7中的服务器为DHCP Server。
另外一种情形下，当UGW确定通过非DHCP机制分配IP地址时，UGW可以向如AAA Server发送请求消息。此时，图7中的服务器为AAA Server。这种情况下，UGW通过CGW发送的消息中的指示信息或者自身的配置信息确定AAA Server的地址，并构建请求消息，将UE信息(包括鉴权信息)、业务信息发送给AAA Server。
S702，服务器接收到UGW发送的IP地址请求消息后，分配IP地址。若服务器为AAA服务器，还需要对UE进行鉴权。
S703，服务器将分配的IP地址发送给UGW。此时，若服务器为AAA Server，则可能AAA Server只鉴权，而没有返回IP地址。这种情形下，在AAA Server鉴权成功的情况下，UGW还需要通过DHCP机制分配IP地址。
S704，UGW向分配的IP地址发送给UE。此时，UGW也可以将IP地址发送CGW，使得CGW了解IP地址的分配情况。
本发明实施例的分配IP地址的方法，由UGW联合服务器来分配IP地址，实现了CU分离的网络中IP地址的分配。
上面结合图2至图7介绍了本发明实施例分配IP地址的方法，下面结 合图8至图10介绍本发明实施例的分配IP地址的控制面网关和用户面网关。
如图8所示，本发明实施例的控制面网关800包括接收单元810、确定单元820、分配单元830和发送单元840。
接收单元810用于接收用户设备UE发送的第一请求消息。确定单元820用于根据第一请求消息确定是否由控制面网关分配IP地址。分配单元830用于在确定单元820确定由控制面网关分配IP地址时，分配IP地址。发送单元840用于在确定单元820确定不由控制面网关分配IP地址时，向用户面网关发送触发用户面网关分配IP地址和/或携带指示用户面网关分配IP地址的策略信息的消息。
本发明实施的控制面网关可以在CU分离的网络中分配IP地址。
可选地，第一请求消息可以携带UE请求的业务类型、UE对应的APN、UE的身份信息和UE的鉴权密钥信息中的至少一种。此时，确定单元820具体用于根据第一请求消息携带的业务类型、APN、身份信息和鉴权密钥信息中的至少一种确定是否由控制面网关分配IP地址。确定单元820还可以根据自己的能力或能力的实时状态来确定。控制面网关根据具体情况来确定是否由自己分配IP地址，可以充分利用网络资源，提高分配IP地址的效率。
可选地，确定单元具体用于根据第一请求消息的类型确定是否由控制面网关分配IP地址。
可选地，分配单元830可以具体用于本地分配IP地址或通过服务器分配IP地址。
可选地，分配单元830可以具体用于向用户面网关发送用于指示用户面网关向服务器发送第二请求消息的消息，第二请求消息用于请求服务器分配IP地址；并接收服务器通过用户面网关转发的IP地址。
可选地，分配单元830可以具体用于向服务器发送第三请求消息的消息，第三请求消息用于请求服务器分配IP地址；并接收服务器发送的IP地址。
可选地，分配单元830可以具体用于通过用户面网关向服务器发送第三请求消息；并接收服务器通过用户面网关转发的IP地址。
可选地，服务器可以是DHCP服务器。
可选地，分配单元830在通过DHCP服务器分配IP地址之前，还用于通过用户面网关向具有鉴权功能的服务器发送对UE进行鉴权的请求消息；并接收具有鉴权功能的服务器通过用户面网关转发的鉴权响应消息；并根据 鉴权响应消息确定具有鉴权功能的服务器对UE鉴权成功。
可选地，具有鉴权功能的服务器可以是AAA服务器，可以对UE进行RADIUS鉴权。
可选地，接收模单元810在分配单元830分配IP地址前，还用于接收用户面网关发送的第四请求消息，第四请求消息为用户面网关接收UE发送的请求分配IP地址的消息后生成的消息，或为UE向用户面网关发送的请求分配IP地址的消息。
可选地，发送单元840还用于向UE发送所述IP地址。
图9为本发明一个实施例的控制面网关900的示意性框图。图9所示的控制面网关包括接收器910、处理器920、发送器930、存储器940和***总线950。处理器920、存储器940、接收器910和发送器930通过总线***950相连，该存储器940用于存储指令，该处理器920用于执行该存储器940存储的指令，以控制接收器910接收信号，并控制发送器930发送信号。
控制面网关900可对应于图2和图3所示的方法中的控制面网关，也可以对应于图8所示的控制面网关。具体而言，接收器910对应图8中的接收单元810，处理器920对应图8中的确定单元810和分配单元830，发送器930对应图8中的发送单元840。本发明实施例的控制面网关900中的各个单元的上述和其它操作和/或功能分别实现图2至图7中的各个方法的相应流程。应理解，在控制面网关900实现图2至图7中任一方法的流程的过程中，该处理器920用于执行该存储器940存储的指令，以控制接收器910接收相应的方法流程中接入点设备接收的各种消息或报文，以及控制发送器930发送相应的方法流程中接入点设备发送的各种消息或报文，为了简洁，在此不再赘述。
图10为本发明一个实施例的用户面网关1000的示意性框图。图10所示的用户面网关1000包括接收单元1010、确定单元1020和分配单元1030。
接收单元1010用于用于接收UE发送的第一请求消息、接收控制面网关发送的用于触发用户面网关分配IP地址的消息或接收UE发送的第一请求消息及控制面网关发送的携带用于指示用户面网关分配IP地址的策略信息的消息。确定单元1020用于在接收单元接收UE发送的第一请求消息时根据第一请求消息确定由用户面网关本地分配IP地址或通过服务器分配IP地址；和用于在接收单元接收控制面网关发送的用于触发用户面网关分配IP 地址的消息时，确定由用户面网关本地分配IP地址或通过服务器分配IP地址；和用于在接收单元接收UE发送的第一请求消息及控制面网关发送的携带用于指示用户面网关分配IP地址的策略信息的消息时，根据第一请求消息和所述策略信息确定由用户面网关本地分配IP地址或通过服务器分配IP地址。分配单元1030用于在确定单元1020确定由用户面网关本地分配IP地址时，本地分配IP地址。分配单元1030还用于在确定单元1020确定通过服务器分配IP地址时，通过服务器分配IP地址。
本发明实施例的用户面网关，可以在CU分离的网络中分配IP地址。
可选地，确定单元820具体用于根据第一请求消息的类型确定由用户面网关本地分配IP地址或通过服务器分配IP地址；确定单元820还具体用于根据第一请求消息的类型和策略信息确定由用户面网关本地分配IP地址或通过服务器分配IP地址。第一请求消息的类型指示该请求消息为请求用户面网关为UE分配IP地址的消息。
可选地，分配单元1030可以具体用于向服务器发送第二请求消息的消息，第二请求消息用于请求服务器分配IP地址；并接收服务器发送的IP地址。
可选地，服务器可以是DHCP服务器。
可选地，当服务器为DHCP服务器时，分配单元1030在通过DHCP服务器分配IP地址之前，还用于向具有鉴权功能的服务器发送对UE进行鉴权的请求消息；并接收具有鉴权功能的服务器发送的鉴权响应消息；并根据鉴权响应消息确定具有鉴权功能的服务器对UE鉴权成功。
可选地，具有鉴权功能的服务器可以是AAA服务器，可以对UE进行RADIUS鉴权。
可选地，用户面网关还可以包括发送单元，用于向UE发送IP地址或向控制面网关发送IP地址，以便于控制面网关向UE发送所述IP地址。
图11为本发明一个实施例的用户面网关1100的示意性框图。图11所示的控制面网关包括接收器1110、处理器1120、发送器1130、存储器1140和***总线1150。处理器1120、存储器1140、接收器1110和发送器1130通过总线***1150相连，该存储器1140用于存储指令，该处理器1120用于执行该存储器1140存储的指令，以控制接收器1110接收信号，并控制发送器1130发送信号。
用户面网关1100可对应于图2和图3所示的方法中的用户面网关，也可以对应于图10所示的用户面网关。具体而言，接收器1110对应图10中的接收单元1010，处理器1120对应图10中的确定单元1010和分配单元1030，发送器1130对应图10中的发送单元。本发明实施例的用户面网关1100中的各个单元的上述和其它操作和/或功能分别实现图2至图7中的各个方法的相应流程。应理解，在用户面网关1100实现图2至图7中任一方法的流程的过程中，该处理器1120用于执行该存储器1140存储的指令，以控制接收器1110接收相应的方法流程中接入点设备接收的各种消息或报文，以及控制发送器1130发送相应的方法流程中接入点设备发送的各种消息或报文，为了简洁，在此不再赘述。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本发明的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的***、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的***、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个***，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本发明各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单 元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本发明的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本发明各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本发明的具体实施方式，但本发明的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本发明揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本发明的保护范围之内。因此，本发明的保护范围应以权利要求的保护范围为准。

Claims (30)

  1. 一种分配互联网协议IP地址的方法，其特征在于，包括：
    控制面网关接收用户设备UE发送的第一请求消息；
    所述控制面网关根据所述第一请求消息确定是否由所述控制面网关分配IP地址；
    所述控制面网关确定由所述控制面网关分配IP地址时，分配IP地址；
    所述控制面网关确定不由所述控制面网关分配IP地址时，向用户面网关发送触发所述用户面网关分配IP地址和/或携带指示所述用户面网关分配IP地址的策略信息的消息。
  2. 根据权利要求1所述的方法，其特征在于，所述控制面网关分配IP地址包括：
    所述控制面网关本地分配IP地址或通过服务器分配IP地址。
  3. 根据权利要求2所述的方法，其特征在于，所述控制面网关通过服务器分配IP地址，包括：
    所述控制面网关向用户面网关发送用于指示所述用户面网关向服务器发送第二请求消息的消息，所述第二请求消息用于请求所述服务器分配IP地址；
    所述控制面网关接收所述服务器通过所述用户面网关转发的IP地址。
  4. 根据权利要求2所述的方法，其特征在于，所述控制面网关通过服务器分配IP地址，包括：
    所述控制面网关向服务器发送第三请求消息，所述第三请求消息用于请求所述服务器分配IP地址；
    所述控制面网关接收所述服务器发送的IP地址。
  5. 根据权利要求4所述的方法，其特征在于，所述控制面网关向服务器发送第三请求消息，包括：
    所述控制面网关通过用户面网关向服务器发送第三请求消息；
    所述控制面网关接收所述服务器发送的IP地址，包括：
    所述控制面网关接收所述服务器通过所述用户面网关转发的IP地址。
  6. 根据权利要求3至5中任一项所述的方法，其特征在于，所述服务器为动态主机配置协议DHCP服务器。
  7. 根据权利要求6所述的方法，其特征在于，在所述控制面网关通过 所述DHCP服务器分配IP地址之前，所述方法还包括：
    所述控制面网关通过所述用户面网关向具有鉴权功能的服务器发送用于请求对所述UE进行鉴权的消息；
    所述控制面网关接收所述具有鉴权功能的服务器通过所述用户面网关转发的鉴权响应消息；
    所述控制面网关根据所述鉴权响应消息确定所述具有鉴权功能的服务器对所述UE鉴权成功。
  8. 根据权利要求1至7中任一项所述的方法，其特征在于，在所述控制面网关分配IP地址前，所述方法还包括：
    所述控制面网关接收用户面网关发送的第四请求消息，所述第四请求消息为所述用户面网关接收UE发送的请求分配IP地址的消息后生成的消息或为所述UE向所述用户面网关发送的请求分配IP地址的消息。
  9. 根据权利要求1至8中任一项所述的方法，其特征在于，所述第一请求消息携带所述UE请求的业务类型、所述UE对应的接入点名称APN、所述UE的身份信息和所述UE的鉴权密钥信息中的至少一种；
    其中，所述控制面网关根据所述第一请求消息确定是否由所述控制面网关分配IP地址，包括：
    所述控制面网关根据所述第一请求消息携带的所述业务类型、所述APN、所述身份信息和所述鉴权密钥信息中的至少一种确定是否由所述控制面网关分配IP地址。
  10. 根据权利要求1至8中任一项所述的方法，其特征在于，所述控制面网关根据所述第一请求消息确定是否由所述控制面网关分配IP地址，包括：
    所述控制面网关根据所述第一请求消息的类型确定是否由所述控制面网关分配IP地址。
  11. 一种分配互联网协议IP地址的方法，其特征在于，包括：
    用户面网关接收用户设备UE发送的第一请求消息时，根据所述第一请求消息确定由所述用户面网关本地分配IP地址或通过服务器分配IP地址；和
    用户面网关接收控制面网关发送的用于触发所述用户面网关分配IP地址的消息时，确定由所述用户面网关本地分配IP地址或通过服务器分配IP 地址；和
    所述用户面网关接收UE发送的第一请求消息和接收控制面网关发送的携带用于指示所述用户面网关分配IP地址的策略信息的消息时，根据所述第一请求消息和所述策略信息确定由所述用户面网关本地分配IP地址或通过服务器分配IP地址；
    所述用户面网关确定由所述用户面网关本地分配IP地址时，本地分配IP地址；
    所述用户面网关确定通过服务器分配IP地址时，通过所述服务器分配IP地址。
  12. 根据权利要求11所述的方法，其特征在于，所述用户面网关通过服务器分配IP地址，包括：
    所述用户面网关向服务器发送第二请求消息，所述第二请求消息用于请求所述服务器分配IP地址；
    所述用户面网关接收所述服务器发送的IP地址。
  13. 根据权利要求11或12所述的方法，其特征在于，所述服务器为动态主机配置协议DHCP服务器。
  14. 根据权利要求13所述的方法，其特征在于，在所述用户面网关向服务器发送第二请求消息之前，所述方法还包括：
    所述用户面网关向具有鉴权功能的服务器发送用于请求对所述UE进行鉴权的消息；
    所述用户面网关接收所述具有鉴权功能的服务器发送的鉴权响应消息；
    所述用户面网关根据所述鉴权响应消息确定所述具有鉴权功能的服务器对所述UE鉴权成功。
  15. 根据权利要求11至14中任一项所述的方法，其特征在于，所述根据所述第一请求消息确定由所述用户面网关本地分配IP地址或通过服务器分配IP地址，包括：
    所述用户面网关根据所述第一请求消息的类型确定由所述用户面网关本地分配IP地址或通过服务器分配IP地址；
    所述根据所述第一请求消息和所述策略信息确定由所述用户面网关本地分配IP地址或通过服务器分配IP地址，包括：
    所述用户面网关根据所述第一请求消息的类型和所述策略信息确定由 所述用户面网关本地分配IP地址或通过服务器分配IP地址。
  16. 一种控制面网关，其特征在于，包括：
    接收单元，用于接收用户设备UE发送的第一请求消息；
    确定单元，用于根据所述第一请求消息确定是否由所述控制面网关分配IP地址；
    分配单元，用于在所述确定单元确定由所述控制面网关分配IP地址时，分配IP地址；
    发送单元，用于在所述确定单元确定不由所述控制面网关分配IP地址时，向用户面网关发送触发所述用户面网关分配IP地址和/或携带指示所述用户面网关分配IP地址的策略信息的消息。
  17. 根据权利要求16所述的控制面网关，其特征在于，所述分配单元具体用于：
    本地分配IP地址或通过服务器分配IP地址。
  18. 根据权利要求17所述的控制面网关，其特征在于，所述分配单元具体用于：
    向用户面网关发送用于指示所述用户面网关向服务器发送第二请求消息的消息，所述第二请求消息用于请求所述服务器分配IP；
    接收所述服务器通过所述用户面网关转发的IP地址。
  19. 根据权利要求17所述的控制面网关，其特征在于，所述分配单元具体用于：
    向服务器发送第三请求消息，所述第三请求消息用于请求所述服务器分配IP地址；
    接收所述服务器发送的IP地址。
  20. 根据权利要求19所述的控制面网关，其特征在于，所述分配单元具体用于：
    通过用户面网关向服务器发送第三请求消息；
    接收所述服务器通过所述用户面网关转发的IP地址。
  21. 根据权利要求18至20中任一项所述的控制面网关，其特征在于，所述服务器为动态主机配置协议DHCP服务器。
  22. 根据权利要求21所述的控制面网关，其特征在于，所述分配单元在通过所述DHCP服务器分配IP地址之前，还用于：
    通过所述用户面网关向具有鉴权功能的服务器发送用于请求对所述UE进行鉴权的请求消息；
    接收所述具有鉴权功能的服务器通过所述用户面网关转发的鉴权响应消息；
    根据所述鉴权响应消息确定所述具有鉴权功能的服务器对所述UE鉴权成功。
  23. 根据权利要求16至22中任一项所述的控制面网关，其特征在于，所述接收单元在所述分配单元分配IP地址前，还用于接收用户面网关发送的第四请求消息，所述第四请求消息为所述用户面网关接收UE发送的请求分配IP地址的消息后生成的消息或为所述UE向所述用户面网关发送的请求分配IP地址的消息。
  24. 根据权利要求16至23中任一项所述的控制面网关，其特征在于，所述第一请求消息携带所述UE请求的业务类型、所述UE对应的接入点名称APN、所述UE的身份信息和所述UE的鉴权密钥信息中的至少一种。
    其中，所述确定单元具体用于根据所述第一请求消息携带的所述业务类型、所述APN、所述身份信息和所述鉴权密钥信息中的至少一种确定是否由所述控制面网关分配IP地址。
  25. 根据权利要求16至23中任一项所述的控制面网关，其特征在于，所述确定单元具体用于根据所述第一请求消息的类型确定是否由所述控制面网关分配IP地址。
  26. 一种用户面网关，其特征在于，包括：
    接收单元，用于接收用户设备UE发送的第一请求消息、接收控制面网关发送的用于触发所述用户面网关分配IP地址的消息或接收UE发送的第一请求消息及控制面网关发送的携带用于指示所述用户面网关分配IP地址的策略信息的消息；
    确定单元，用于在所述接收单元接收UE发送的第一请求消息时根据所述第一请求消息确定由所述用户面网关本地分配IP地址或通过服务器分配IP地址；和用于在所述接收单元接收控制面网关发送的用于触发所述用户面网关分配IP地址的消息时，确定由所述用户面网关本地分配IP地址或通过服务器分配IP地址；和用于在所述接收单元接收UE发送的第一请求消息及控制面网关发送的携带用于指示所述用户面网关分配IP地址的策略信息的 消息时，根据所述第一请求消息和所述策略信息确定由所述用户面网关本地分配IP地址或通过服务器分配IP地址；
    分配单元，用于在所述确定单元确定由所述用户面网关本地分配IP地址时，本地分配IP地址；
    所述分配单元还用于在所述确定单元确定通过服务器分配IP地址时，通过所述服务器分配IP地址。
  27. 根据权利要求26所述的用户面网关，其特征在于，所述分配单元具体用于：
    向服务器发送第二请求消息的消息，所述第二请求消息用于请求所述服务器分配IP地址；
    接收所述服务器发送的IP地址。
  28. 根据权利要求26或27所述的用户面网关，其特征在于，所述服务器为动态主机配置协议DHCP服务器。
  29. 根据权利要求28所述的用户面网关，其特征在于，所述分配单元在通过所述DHCP服务器分配IP地址之前，还用于：
    向具有鉴权功能的服务器发送用于请求对所述UE进行鉴权的请求消息；
    接收所述具有鉴权功能的服务器发送的鉴权响应消息；
    根据所述鉴权响应消息确定所述具有鉴权功能的服务器对所述UE鉴权成功。
  30. 根据权利要求26至29中任一项所述的用户面网关，其特征在于，所述确定单元具体用于根据所述第一请求消息的类型确定由所述用户面网关本地分配IP地址或通过服务器分配IP地址；
    所述确定单元还具体用于根据所述第一请求消息的类型和所述策略信息确定由所述用户面网关本地分配IP地址或通过服务器分配IP地址。
PCT/CN2016/071247 2016-01-18 2016-01-18 分配互联网协议地址的方法、控制面网关和用户面网关 WO2017124231A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2016/071247 WO2017124231A1 (zh) 2016-01-18 2016-01-18 分配互联网协议地址的方法、控制面网关和用户面网关

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2016/071247 WO2017124231A1 (zh) 2016-01-18 2016-01-18 分配互联网协议地址的方法、控制面网关和用户面网关

Publications (1)

Publication Number Publication Date
WO2017124231A1 true WO2017124231A1 (zh) 2017-07-27

Family

ID=59361234

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/071247 WO2017124231A1 (zh) 2016-01-18 2016-01-18 分配互联网协议地址的方法、控制面网关和用户面网关

Country Status (1)

Country Link
WO (1) WO2017124231A1 (zh)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109495593A (zh) * 2017-09-11 2019-03-19 中兴通讯股份有限公司 地址分配方法及***
US10873563B2 (en) * 2016-01-19 2020-12-22 Huawei Technologies Co., Ltd. IP address allocation method, and device
CN113328894A (zh) * 2017-08-31 2021-08-31 北京华为数字技术有限公司 基于cu分离的双机热备的方法及设备

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101188542A (zh) * 2006-11-17 2008-05-28 华为技术有限公司 建立ip隧道的方法及***及分发ip地址的装置
WO2014000286A1 (zh) * 2012-06-29 2014-01-03 华为技术有限公司 网关***、设备和通信方法
CN104185209A (zh) * 2013-05-24 2014-12-03 中兴通讯股份有限公司 一种小蜂窝基站接入***及其实现网络接入的方法
WO2015096005A1 (zh) * 2013-12-23 2015-07-02 华为技术有限公司 消息处理方法和网关

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101188542A (zh) * 2006-11-17 2008-05-28 华为技术有限公司 建立ip隧道的方法及***及分发ip地址的装置
WO2014000286A1 (zh) * 2012-06-29 2014-01-03 华为技术有限公司 网关***、设备和通信方法
CN104185209A (zh) * 2013-05-24 2014-12-03 中兴通讯股份有限公司 一种小蜂窝基站接入***及其实现网络接入的方法
WO2015096005A1 (zh) * 2013-12-23 2015-07-02 华为技术有限公司 消息处理方法和网关

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10873563B2 (en) * 2016-01-19 2020-12-22 Huawei Technologies Co., Ltd. IP address allocation method, and device
US11212252B2 (en) 2016-01-19 2021-12-28 Huawei Technologies Co., Ltd. IP address allocation method, and device
CN113328894A (zh) * 2017-08-31 2021-08-31 北京华为数字技术有限公司 基于cu分离的双机热备的方法及设备
CN113328894B (zh) * 2017-08-31 2022-06-28 华为技术有限公司 基于cu分离的双机热备的方法及设备
CN109495593A (zh) * 2017-09-11 2019-03-19 中兴通讯股份有限公司 地址分配方法及***
CN109495593B (zh) * 2017-09-11 2022-03-25 中兴通讯股份有限公司 地址分配方法及***

Similar Documents

Publication Publication Date Title
EP3518596B1 (en) Communication method and access network device
CN112153098B (zh) 一种应用迁移方法及装置
US20080153453A1 (en) Method for providing emergency service in WiMAX networks
CN107733808B (zh) 一种流量传输方法及装置
US20170244705A1 (en) Method of using converged core network service, universal control entity, and converged core network system
US9113436B2 (en) Method and system for information transmission
US11153207B2 (en) Data link layer-based communication method, device, and system
US20230232301A1 (en) Methods and apparatus for supporting quality of service in a system including a cable modem termination system and wireless communications link
US11083048B2 (en) Devices and methods for transforming user plane signaling from a remote sidelink control server into control plane signaling
CN108271433B (zh) 一种数据报文处理方法及控制面网元、用户面网元
US20190223013A1 (en) Method for establishing public data network connection and related device
CN111869310A (zh) 用于执行小数据快速路径通信的方法和***
JP5626547B2 (ja) ＷｉＭＡＸにおけるＩＰベースの緊急サービスの処理方法
US9516681B2 (en) Method, device and system for accessing core network by means of non-3GPP access
KR20180051621A (ko) 전기통신 네트워크와 적어도 하나의 사용자 장비 간의 적어도 하나의 통신 교환의 개선된 핸들링을 위한 방법, 전기통신 네트워크, 사용자 장비, 시스템, 프로그램 및 컴퓨터 프로그램 제품
WO2017124231A1 (zh) 分配互联网协议地址的方法、控制面网关和用户面网关
US11653395B2 (en) Method for establishing a connection of a mobile terminal to a mobile radio communication network and radio access network component
KR101481337B1 (ko) 소프트웨어 정의 네트워크 기반 이동통신 시스템 및 이의 단말 접속 처리 방법
WO2018054272A1 (zh) 数据的发送方法和装置、计算机存储介质
US20210315027A1 (en) Mapping Logical Network Resources to Transport Resources
WO2022007657A1 (zh) 一种域名***请求的发送方法及装置
CN115515091A (zh) 网络地址转换方法、中继设备、通信***以及存储介质
WO2013097614A1 (zh) 为ue分配ip地址的方法、***及tnan、ue
US20200137726A1 (en) Communications device and communication method
WO2015013883A1 (zh) 一种数据传输方法及设备

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 16885504

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 16885504

Country of ref document: EP

Kind code of ref document: A1