WO2019104858A1 - 报文转发的方法、控制面网关和用户面网关 - Google Patents

报文转发的方法、控制面网关和用户面网关 Download PDF

Info

Publication number
WO2019104858A1
WO2019104858A1 PCT/CN2018/074027 CN2018074027W WO2019104858A1 WO 2019104858 A1 WO2019104858 A1 WO 2019104858A1 CN 2018074027 W CN2018074027 W CN 2018074027W WO 2019104858 A1 WO2019104858 A1 WO 2019104858A1
Authority
WO
WIPO (PCT)
Prior art keywords
plane gateway
user plane
gateway
routing table
forwarding
Prior art date
Application number
PCT/CN2018/074027
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 JP2018548203A priority Critical patent/JP7065034B2/ja
Publication of WO2019104858A1 publication Critical patent/WO2019104858A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/74—Address processing for routing
    • H04L45/745—Address table lookup; Address filtering
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46—Interconnection of networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46—Interconnection of networks
    • H04L12/4633—Interconnection of networks using encapsulation techniques, e.g. tunneling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/66—Arrangements for connecting between networks having differing types of switching systems, e.g. gateways
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/74—Address processing for routing

Definitions

  • the present application relates to the field of communications, and more particularly to a method for message forwarding, a control plane gateway, and a user plane gateway.
  • the gateway is typically sunk, ie more gateways are deployed close to the vehicle user. In this way, car-to-car communication may occur in a scenario across the sinking gateway.
  • the present application provides a method for packet forwarding, a control plane gateway, and a user plane gateway, which can effectively optimize a forwarding path to meet the requirements of low latency services.
  • a method for packet forwarding including:
  • the control plane gateway acquires registration information of the first user equipment UE and registration information of the second user equipment UE, where the registration information of the first UE includes a UE identifier that communicates with the first UE, and the registration of the second UE
  • the information includes a UE identity that is in communication with the second UE;
  • the control plane gateway generates a forwarding routing table of the first UE and the second UE according to the registration information of the first UE and the registration information of the second UE, where the forwarding routing table includes the Information required by a UE and the second UE to perform a message transmission path;
  • the control plane gateway sends the forwarding routing table to the first user plane gateway and the second user plane gateway, where the forwarding routing table is used by the user plane gateway to determine between the first UE and the second UE.
  • the packet forwarding path where the first user plane gateway is a gateway where the first UE is located, and the second user plane gateway is a gateway where the second UE is located.
  • control plane gateway determines the forwarding routing table and sends a forwarding routing table to the first user plane gateway, so that the first user plane gateway determines the report between the first UE and the second UE according to the forwarding routing table.
  • the forwarding path can optimize the packet forwarding path to meet the requirements of low-latency services.
  • the first UE and the second UE may be in the same user plane gateway or may be a cross-user plane gateway. That is to say, the first user plane gateway may be the same as or different from the second user plane gateway.
  • the first user plane gateway is the same as the second user plane gateway, where
  • Generating a forwarding routing table of the first UE and the second UE including:
  • the control plane gateway generates the forwarding routing table according to the registration information and the identifier of the first user plane gateway, where the forwarding routing table includes a route that the first user plane gateway reaches the first UE, And the routing of the first user plane gateway to the second UE, where the packet forwarding of the first UE and the second UE is directly sent by the first user plane gateway.
  • the packet forwarding of the first UE and the second UE can be directly forwarded by the first user plane gateway, and does not need to be forwarded from the first user plane gateway through the transmission network and the central gateway, thereby optimizing the forwarding path and reducing forwarding.
  • Delay able to meet the needs of low-latency services.
  • the first user plane gateway and the second user plane gateway are different user plane gateways, where
  • Generating a forwarding routing table of the first UE and the second UE including:
  • the control plane gateway generates the forwarding routing table according to the registration information, the identifier of the first user plane gateway, and the identifier of the second user plane gateway, where the forwarding routing table includes the first user plane And the route that the gateway reaches the second UE by using the second user plane gateway, and the route that the second user plane gateway reaches the first UE by using the first user plane gateway.
  • the first user plane gateway and the second user plane gateway are different user plane gateways under the same central gateway.
  • the packet forwarding of the first UE and the second UE may be directly forwarded through the tunnel between the first user plane gateway and the second user plane gateway, without forwarding from the user plane gateway through the transmission network and the central gateway.
  • the forwarding path is optimized, and the forwarding delay is reduced, which can meet the requirements of low-latency services.
  • the IP address of the first UE and the IP address of the second UE are allocated by the central gateway. Since the central gateway remains unchanged, even if the UE switches from the local UP1 to the local UPF2, the IP address of the UE does not change, thereby ensuring The continuity of the upper layer application avoids the business interruption caused by the reconnection of the gateway.
  • the method before the generating the forwarding routing table, the method further includes:
  • the control plane gateway updates the registration information to obtain the updated registration information
  • the control plane gateway updates the forwarding routing table according to the updated registration information.
  • control plane gateway when the control plane gateway performs the update, it can update only the entries of the UE whose user plane gateway changes, and does not need to update the entries of all the registered UEs, thereby reducing the update range and saving the overhead. .
  • the method before the control plane gateway sends the forwarding routing table to the first user plane gateway and the second user plane gateway, the method further includes:
  • the control plane gateway sends a create tunnel request to the first user plane gateway and the second user plane gateway, where the create tunnel request is used to request to create the first user plane gateway and the second user plane gateway. Between the tunnels;
  • the control plane gateway receives a second create tunnel request response sent by the second user plane gateway, and the second create tunnel request response is used by the second user plane gateway to respond to the create tunnel request.
  • control plane gateway may request a tunnel connection between the first user plane gateway and the second user plane gateway, so as to implement communication between the user plane gateways, thereby optimizing the forwarding path.
  • a method for packet forwarding including:
  • the first user plane gateway receives a forwarding routing table sent by the control plane gateway, where the forwarding routing table includes information required by the first user equipment UE and the second UE to perform a path for packet transmission;
  • the first user plane gateway Determining, by the first user plane gateway, a packet forwarding path between the first UE and the second UE according to the forwarding routing table, where the first user plane gateway is where the first UE is located The gateway, the second user plane gateway is a gateway where the second UE is located.
  • the first user plane gateway receives the forwarding routing table sent by the control plane gateway, and determines a packet forwarding path between the first UE and the second UE according to the forwarding routing table, and can optimize the packet forwarding path. Thereby meeting the needs of low latency services.
  • the first UE and the second UE may be in the same user plane gateway or may be a cross-user plane gateway. That is to say, the first user plane gateway may be the same as or different from the second user plane gateway.
  • the first user plane gateway is the same as the second user plane gateway, where the forwarding routing table includes a route that the first user plane gateway reaches the first UE, and Routing of the first user plane gateway to the second UE;
  • Determining, by the first user plane gateway, the packet forwarding path of the first UE and the second UE according to the forwarding routing table including:
  • the first user plane gateway determines that the packet forwarding of the first UE and the second UE is directly sent by the first user plane gateway according to the forwarding routing table.
  • the packet forwarding of the first UE and the second UE can be directly forwarded by the first user plane gateway, and does not need to be forwarded from the first user plane gateway through the transmission network and the central gateway, thereby optimizing the forwarding path and reducing forwarding.
  • Delay able to meet the needs of low-latency services.
  • the first user plane gateway and the second user plane gateway are different user plane gateways
  • the forwarding routing table includes the first user plane gateway passing the second user plane. a route that the gateway reaches the second UE, and a route that the second user plane gateway reaches the first UE by using the first user plane gateway;
  • the first user plane gateway determines, according to the forwarding routing table, a packet forwarding path of the first UE and the second UE, including:
  • the first user plane gateway determines, according to the forwarding routing table, that the packet of the first UE and the second UE is forwarded through a tunnel between the first user plane gateway and the second user plane gateway. send.
  • the first user plane gateway and the second user plane gateway are different user plane gateways under the same central gateway.
  • the packet forwarding of the first UE and the second UE may be directly forwarded through the tunnel between the first user plane gateway and the second user plane gateway, without forwarding from the user plane gateway through the transmission network and the central gateway.
  • the forwarding path is optimized, and the forwarding delay is reduced, which can meet the requirements of low-latency services.
  • the IP address of the first UE and the IP address of the second UE are allocated by the central gateway. Since the central gateway remains unchanged, even if the UE switches from the local UP1 to the local UPF2, the IP address of the UE does not change, thereby ensuring The continuity of the upper layer application avoids the business interruption caused by the reconnection of the gateway.
  • the method further includes:
  • the first user plane gateway receives a tunnel creation request sent by the control plane gateway, where the first creation tunnel request is used to request to create a tunnel between the first user plane gateway and the second user plane gateway;
  • the first user plane gateway sends a first create tunnel request response to the control plane gateway, where the first create tunnel request response is used by the first user plane gateway to respond to the create tunnel request.
  • the first user plane gateway may respond to the tunnel creation request of the control plane gateway and establish a tunnel connection with the second user plane gateway, so as to implement communication between the user plane gateways, thereby optimizing the forwarding path.
  • control plane gateway for performing the method of any of the above first aspect or any of the possible implementations of the first aspect.
  • control plane gateway comprises means for performing the method of any of the first aspect or the first aspect of the first aspect described above.
  • a user plane gateway for performing the method of any of the foregoing second aspect or any of the possible implementations of the second aspect.
  • the user plane gateway comprises means for performing the method of any of the above-described second aspect or any of the possible implementations of the second aspect.
  • a control plane gateway including a processor, a memory, and a transceiver.
  • the processor is coupled to the memory and the transceiver.
  • the memory is for storing instructions for the processor to execute, and the transceiver is for communicating with other network elements under the control of the processor.
  • the processor executes the instructions stored by the memory, the execution causes the processor to perform the method of the first aspect or any of the possible implementations of the first aspect.
  • a user plane gateway comprising a processor, a memory, and a transceiver.
  • the processor is coupled to the memory and the transceiver.
  • the memory is for storing instructions for the processor to execute, and the transceiver is for communicating with other network elements under the control of the processor.
  • the processor executes the instructions stored by the memory, the execution causes the processor to perform the method of any of the possible implementations of the second aspect or the second aspect.
  • a seventh aspect a computer readable storage medium storing a program causing a control plane gateway to perform the above-described first aspect, and forwarding of any of the various implementations thereof Methods.
  • a computer readable storage medium storing a program that causes a user plane gateway to perform the above second aspect, and any of the various implementations of the message forwarding Methods.
  • a communication chip in which instructions are stored which, when run on a control plane gateway, cause the communication chip to perform the method of any of the first aspect or the first aspect of the first aspect.
  • a communication chip in which instructions are stored which, when run on a user plane gateway, cause the communication chip to perform the method of any of the second aspect or the second aspect of the second aspect.
  • a computer program product comprising instructions, which when executed on a computer, cause the computer to perform the method of the first aspect or any of its possible implementations, or the second aspect or any of its possible The method in the implementation.
  • Figure 1 is a network diagram of a CUPS network with a control plane and a user plane separated.
  • FIG. 2 is a schematic diagram of a scenario in which an embodiment of the present application is applied.
  • FIG. 3 is a structural block diagram of a control plane gateway according to an embodiment of the present application.
  • FIG. 4 is a structural block diagram of a user plane gateway according to an embodiment of the present application.
  • FIG. 5 is a schematic interaction diagram of a method for message forwarding according to an embodiment of the present application.
  • Figure 6 is a schematic diagram of an example of application of an embodiment of the present application.
  • FIG. 7 is a schematic diagram of another example in accordance with an embodiment of the present application.
  • FIG. 8 is an interaction diagram of a specific process according to an embodiment of the present application.
  • FIG. 9 is a schematic block diagram of a control plane gateway in accordance with an embodiment of the present application.
  • FIG. 10 is a schematic block diagram of a user plane gateway according to an embodiment of the present application.
  • FIG. 11 is a schematic block diagram of a user plane gateway in accordance with an embodiment of the present application.
  • GSM Global System of Mobile communication
  • CDMA Code Division Multiple Access
  • WCDMA Wideband Code Division Multiple Access
  • GPRS General Packet Radio Service
  • LTE Long Term Evolution
  • FDD Frequency Division Duplex
  • TDD Time Division Duplex
  • UMTS Universal Mobile Telecommunication System
  • WiMAX Worldwide Interoperability for Microwave Access
  • the technical solution of the embodiment of the present application can be applied to a 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 having both the control plane and the user plane function are split into two individuals: a control plane network element and a user plane network element.
  • CUPS is also known as CU 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. Channel.
  • 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.
  • the channel may also be referred to as a tunnel, such as a General Packet Radio Service (GPRS) Tunneling Protocol (GTP) tunnel.
  • GPRS General Packet Radio Service
  • GTP General Packet Radio Service Tunneling Protocol
  • Figure 1 shows a CUPS network architecture diagram.
  • the network architecture mainly includes a UE, a base station, a control plane gateway, and a server.
  • the dotted line in Figure 1 indicates that the message is transmitted through the control plane, and the solid line indicates that the message or data message is transmitted through the user plane.
  • a UE may refer to a terminal device, an access terminal, 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 terminal device may also be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), with wireless communication.
  • SIP Session Initiation Protocol
  • WLL Wireless Local Loop
  • PDA Personal Digital Assistant
  • the terminal device the vehicle to X (V2X) device, the vehicle to vehicle (V2V) device, and the like are not limited in this embodiment of the present application.
  • the UE may communicate with the control plane gateway through signaling messages, or may transmit data packets with the user plane gateway.
  • the base station is a possible component of a CP-separated network architecture used in the embodiment of the present application, and may be a base station device g-NB, a small base station device, an eNB, or a cloud wireless access network in a future 5G network.
  • the wireless controller in the (Cloud Radio Access Network, CRAN) scenario, or the Mobility Management Entity (MME), or the base station can be a relay station, an access point, an in-vehicle device, a wearable device, and a future 5G.
  • the network device in the network or the network device in the PLMN network in the future is not limited in this embodiment.
  • the UE communicates with the control plane gateway and the user plane gateway through the base station. Of course, 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 have no base station. Not limited.
  • the core network (CN) in the 5G network includes the network function (NF) of the control plane and the network function of the user plane.
  • the core network is connected to a 5G access network (RAN).
  • RAN 5G access network
  • Control Plane (CP) Gateway has a control plane interface, mainly used for signaling connection with other network elements, handling user mobility management and session management requests, managing user context and establishment. The channel through which data is transmitted.
  • 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 control gateway (Control GateWay, CGW) having a control plane function after the Public Data Network GateWay (PGW) is separated.
  • the network function of the control plane may be a Session Management Function (SMF), an Access and Mobility Management Function (AMF).
  • SMF Session Management Function
  • AMF Access and Mobility Management Function
  • the user plane (User Plane, UP) 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 allocate an IP address and connect to the user plane gateway to send and receive data packets.
  • the user plane gateway may be a user plane gateway (UGW) having a user plane function after the PGW is separated.
  • UGW user plane gateway
  • the user plane gateway may be separated into a central gateway (for example, an Anchor Plan User Plane Function (UPF)) and an edge gateway (for example, a local Local UPF), where Anchor UPF acts as a user plane anchor.
  • UPF Anchor Plan User Plane Function
  • An Anchor UPF can correspond to multiple Local UPFs. As the UE moves, a scenario across the Local UPF occurs.
  • FIG. 2 is a schematic diagram of a scenario in which an embodiment of the present application is applied.
  • the network architecture mainly includes a control plane gateway, a transmission network, a user plane gateway, and a vehicle (including the vehicle 1 and the vehicle 2).
  • the user plane gateway is separated into an Anchor UPF and a Local UPF (including Local UPF1 and Local UPF2).
  • the vehicle 1 and the vehicle 2 may communicate under the same Local UPF (such as the vehicle 1 and the vehicle 2 shown in the lane T1 in FIG. 2), and may also cross the Local UPF (as shown in the lane T2 in FIG. 2).
  • the vehicle 1 communicates with the vehicle 2).
  • the embodiment of the present application proposes a new solution, which optimizes the path to meet the requirements of low-latency services.
  • FIG. 3 shows a block diagram of a control plane gateway 300 in accordance with an embodiment of the present application.
  • the illustrated control plane gateway 300 includes a processor 301, a memory 302, and a transceiver 303.
  • the processor 301, the memory 302, and the transceiver 303 communicate with one another via internal interconnect paths to communicate control and/or data signals.
  • processor 301, memory 302, and transceiver 303 can be implemented by a chip.
  • the memory 302 can store program code, and the processor 301 calls the program code stored in the memory 302 to implement the corresponding functions of the control plane gateway.
  • the processor 301 is configured to:
  • the registration information of the first UE includes a UE identifier that communicates with the first UE, and the registration information of the second UE Including a UE identifier that communicates with the second UE;
  • the control plane gateway generates a forwarding routing table of the first UE and the second UE according to the registration information of the first UE and the registration information of the second UE, where the forwarding routing table includes the Information required by a UE and the second UE to perform a message transmission path;
  • the forwarding routing table is sent by the transceiver 303 to the first user plane gateway and the second user plane gateway, where the forwarding routing table is used by the user plane gateway to determine the first UE and the second UE. And a packet forwarding path, where the first user plane gateway is a gateway where the first UE is located, and the second user plane gateway is a gateway where the second UE is located.
  • control plane gateway 300 may also include other devices such as input devices, output devices, batteries, and the like.
  • the memory 302 may store instructions for performing the method performed by the control plane gateway in the method for message forwarding of the embodiments of the present application.
  • the processor 301 can execute the instructions stored in the memory 302 in combination with other hardware (for example, the transceiver 303) to complete the steps performed by the control plane gateway in the following method.
  • other hardware for example, the transceiver 303
  • FIG. 4 shows a block diagram of a structure of a user plane gateway 400 in accordance with an embodiment of the present application.
  • the illustrated user plane gateway 400 includes a processor 401, a memory 402, and a transceiver 403.
  • the processor 401, the memory 402, and the transceiver 403 communicate with one another via internal connection paths to communicate control and/or data signals.
  • processor 401, memory 402, and transceiver 403 can be implemented by a chip.
  • the memory 402 can store program code, and the processor 401 calls the program code stored in the memory 402 to implement the corresponding functions of the user plane gateway.
  • the processor 401 is configured to:
  • a forwarding routing table sent by the control plane gateway, where the forwarding routing table includes information required by the first user equipment UE and the second UE to perform a path for packet transmission;
  • the user plane gateway 400 may also include other devices such as input devices, output devices, batteries, and the like.
  • the memory 402 can store instructions for performing the method performed by the user plane gateway in the method for message forwarding of embodiments of the present application.
  • the processor 401 can execute the instructions stored in the memory 402 in combination with other hardware (for example, the transceiver 403) to complete the steps performed by the user plane gateway (the first user plane gateway or the second user plane gateway) in the following method, the specific working process and the beneficial effects. See the description in the method embodiments below.
  • the method disclosed in the embodiments of the present application may be applied to a processor or implemented by a processor.
  • the processor may be an integrated circuit chip with signal processing capabilities.
  • each step of the following method may be completed by an integrated logic circuit of hardware in the processor or an instruction in the form of software.
  • the above processor may be a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or the like.
  • Programming logic device discrete gate or transistor logic device, discrete hardware component, system chip (SoC), central processor unit (CPU), or network processor (network) Processor, NP
  • SoC system chip
  • CPU central processor unit
  • NP network processor
  • DSP digital signal processor
  • MCU microcontroller
  • PLD programmable logic device
  • the methods, steps, and logical block diagrams disclosed in the embodiments of the present application can be implemented or executed.
  • the general purpose processor may be a microprocessor or the processor or any conventional processor or the like.
  • the steps of the method disclosed in the embodiments of the present application may be directly implemented by the hardware decoding processor, or may be performed by a combination of hardware and software modules in the decoding processor.
  • the software module can be located in a random access memory (RAM), a flash memory, a read-only memory (ROM), a programmable read only memory or an electrically erasable programmable memory, a register, etc.
  • RAM random access memory
  • ROM read-only memory
  • programmable read only memory or an electrically erasable programmable memory
  • register etc.
  • the storage medium is located in the memory, and the processor reads the instructions in the memory and performs the steps of the following methods in combination with the hardware thereof.
  • FIG. 5 shows a schematic interaction diagram of a method 500 for message forwarding in accordance with an embodiment of the present application. As shown in FIG. 5, the method 500 includes:
  • the control plane gateway acquires registration information of the first user equipment UE and registration information of the second UE, where the registration information of the first UE includes a UE identifier that communicates with the first UE, and the second UE is registered.
  • the information includes a UE identity that is in communication with the second UE.
  • control plane gateway may be an AMF/SMF node or a device, or may be an MME, which is not limited thereto.
  • the registration information of the first UE may include a user entry of the first UE and a UE identifier that communicates with the first UE.
  • the registration information of the second UE may include a user entry of the second UE and a UE identity that communicates with the second UE.
  • control plane gateway can learn the packet forwarding relationship between the first UE and the second UE according to the foregoing registration information.
  • both the first UE and the second UE register with the V2X server and join a formation group. Then, the control plane gateway can obtain the foregoing registration information through the V2X controller, so that the first UE and the second UE are a communication group, and then the forwarding routing table is delivered.
  • the foregoing registration information may be obtained by the control plane gateway through a server (for example, a V2X server), or may be sent by the server to the control plane gateway through a Network Exposure Function (NEF). It may be pre-configured to the control plane gateway, which is not limited in this embodiment of the present application.
  • a server for example, a V2X server
  • NEF Network Exposure Function
  • the control plane gateway can obtain registration information of multiple UEs with communication requirements, which is not limited in this embodiment of the present application.
  • the control plane gateway generates a forwarding routing table of the first UE and the second UE according to the registration information of the first UE and the registration information of the second UE, where the forwarding routing table includes the foregoing Information required by a UE and the second UE to perform a path for message transmission.
  • control plane gateway associates with the user context according to the registration information of the first UE and the registration information of the second UE, and generates a forwarding routing table on the forwarding plane.
  • the control plane gateway may maintain a forwarding routing table, where the forwarding routing table may include information required for a communication path between the first UE and the second UE.
  • the forwarding routing table may include an Internet Protocol (IP) address of the first UE, an IP address of the second UE, and an identifier (ID) of the user plane gateway where the first UE and the second UE are located, Information such as the address of the next hop device of the UE, the address of the next hop device of the second UE, and the like.
  • IP Internet Protocol
  • ID identifier
  • the path that the first UE and the second UE perform packet forwarding may be the communication from the first UE to the second UE, or may be the communication from the second UE to the first UE, which is not specifically limited.
  • the forwarding routing table may include routing information of the unidirectional path when the first UE communicates with the second UE, and may also include routing information of the bidirectional path, which is not limited.
  • the control plane gateway sends the forwarding routing table to the first user plane gateway and the second user plane gateway, where the forwarding routing table is used by the user plane gateway to determine a packet forwarding path between the first UE and the second UE.
  • the first user plane gateway or the second user plane gateway is a Local UPF.
  • the control plane gateway sends the forwarding routing table to the first user plane gateway.
  • the first user plane gateway receives the forwarding routing table delivered by the control plane gateway.
  • the first user plane gateway determines, according to the forwarding routing table, a packet forwarding path between the first UE and the second UE.
  • the second user plane gateway receives the forwarding routing table delivered by the control plane gateway.
  • the second user plane gateway determines, according to the forwarding routing table, a packet forwarding path between the first UE and the second UE.
  • the forwarding message of the UE has an IP address for communication between the two parties, and the UE may query the forwarding routing table based on the IP address.
  • step S505 may not be performed, wherein the control plane gateway may only send the forwarding routing table to the first user plane gateway in step S503.
  • control plane gateway determines the forwarding routing table and sends a forwarding routing table to the first user plane gateway, so that the first user plane gateway determines the report between the first UE and the second UE according to the forwarding routing table.
  • the text forwarding path can optimize the packet forwarding path to meet the requirements of low-latency services.
  • the foregoing first UE and the second UE may be in the same user plane gateway or may be a cross-user plane gateway. That is to say, the first user plane gateway may be the same as or different from the second user plane gateway.
  • the technical solutions of the embodiments of the present application are applicable. These situations will be described in detail below.
  • the first user plane gateway is the same as the second UE user plane gateway, where the forwarding routing table of the first UE and the second UE is generated, including:
  • the control plane gateway generates the forwarding routing table according to the registration information and the identifier of the first user plane gateway, where the forwarding routing table includes a route that the first user plane gateway reaches the first UE, And the routing of the first user plane gateway to the second UE, where the packet forwarding of the first UE and the second UE is directly sent by the first user plane gateway.
  • the control plane gateway may be based on the registration information of the first UE and the second UE, and the first user plane gateway.
  • the identifier is generated, and the forwarding routing table is generated, and the forwarding routing table is sent to the first user plane gateway.
  • the forwarding routing table includes a route that the first user plane gateway reaches the first UE, and a route that the first user plane gateway reaches the second UE. That is to say, the packet forwarding of the first UE and the second UE is locally forwarded by the first user plane gateway.
  • the first user plane gateway determines that the packet forwarding of the first UE and the second UE is directly sent by the first user plane gateway according to the forwarding routing table.
  • the packet forwarding of the first UE and the second UE can be directly forwarded through the first user plane gateway (such as UPF1 in FIG. 2) without passing through the transmission network and the central gateway from the first user plane gateway (for example, The anchor point UPF in 2 forwards and forwards, optimizes the forwarding path, reduces the forwarding delay, and can meet the requirements of low-latency services.
  • the first user plane gateway such as UPF1 in FIG. 2
  • the anchor point UPF in 2 forwards and forwards, optimizes the forwarding path, reduces the forwarding delay, and can meet the requirements of low-latency services.
  • the first user plane gateway and the second user plane gateway are different user plane gateways, where
  • the generating a forwarding routing table of the first UE and the second UE includes:
  • the control plane gateway generates the forwarding routing table according to the registration information, the identifier of the first user plane gateway, and the identifier of the second user plane gateway, where the forwarding routing table includes the first user plane And the route that the gateway reaches the second UE by using the second user plane gateway, and the route that the second user plane gateway reaches the first UE by using the first user plane gateway.
  • the first user plane gateway and the second user plane gateway are different user plane gateways under the same central gateway.
  • the control plane gateway may be based on the registration information of the first UE and the second UE, the identifier of the first user plane gateway, and the second user plane gateway.
  • the identifier is generated, and the forwarding routing table is generated, and the forwarding routing table is sent to the first user plane gateway and the second user plane gateway.
  • the forwarding routing table includes a route that the first user plane gateway reaches the first UE by using the second user plane gateway, and a route that the second user plane gateway reaches the second UE by using the first user plane gateway.
  • the packet forwarding of the first UE and the second UE may be forwarded through a tunnel between the first user plane gateway and the second user plane gateway.
  • the first user plane gateway determines that the packet forwarding of the first UE and the second UE is sent through a tunnel between the first user plane gateway and the second user plane gateway according to the forwarding routing table.
  • the packet forwarding of the first UE and the second UE may be directly forwarded through a tunnel between the first user plane gateway and the second user plane gateway (such as the local UPF1 and the local UPF2 tunnel in FIG. 2), instead of It needs to be forwarded from the user plane gateway through the transmission network and the central gateway (such as the anchor Anchor UPF in Figure 2), optimizes the forwarding path, reduces the forwarding delay, and can meet the requirements of low latency services.
  • the IP address of the first UE and the IP address of the second UE are allocated by the central gateway. Since the central gateway remains unchanged, even if the UE switches from the local UP1 to the local UPF2, the IP address of the UE does not change, thereby ensuring The continuity of the upper layer application avoids the business interruption caused by the reconnection of the gateway.
  • first UE and the second UE may use the tunnel between the first user plane gateway and the second user plane gateway to perform packet forwarding. How to open a tunnel between the first user plane gateway and the second user plane gateway will be described below.
  • the method before the control plane gateway sends the forwarding routing table to the first user plane gateway and the second user plane gateway, the method further includes:
  • the control plane gateway sends a create tunnel request to the first user plane gateway and the second user plane gateway, where the create tunnel request is used to request to create the first user plane gateway and the second user plane gateway. Between the tunnels.
  • the first user plane gateway receives the create tunnel request; and the second user plane gateway receives the create tunnel request.
  • the first user plane gateway After the first user plane gateway establishes a tunnel with the second user plane gateway, the first user plane gateway sends a first create tunnel request response to the control plane gateway, where the first create tunnel request response is used by the first user.
  • the face gateway responds to the create tunnel request.
  • control plane gateway receives the first created tunnel request response sent by the first user plane gateway.
  • the second user plane gateway After the first user plane gateway establishes a tunnel with the second user plane gateway, the second user plane gateway sends a second create tunnel request response to the control plane gateway, where the second create tunnel request response is used for the second user.
  • the face gateway responds to the create tunnel request.
  • control plane gateway receives the second created tunnel request response sent by the second user plane gateway.
  • control plane gateway can request a tunnel connection between the first user plane gateway and the second user plane gateway, so as to implement communication between the user plane gateways, thereby optimizing the forwarding path.
  • FIG. 6 shows a schematic diagram of an example of application of an embodiment of the present application.
  • both the vehicle 1 and the vehicle 2 are connected to the local UPF 1
  • the vehicle 3 is connected to the local UPF 2.
  • the local UPF1 and the local UPF2 correspond to the same anchor UPF (that is, the local UPF1).
  • the vehicle 2 may also move to the local UPF2.
  • the vehicle (car) can be regarded as a UE.
  • the control plane gateway sends the forwarding routing table to the local UPF1, so that the vehicle 1 and the vehicle 2 can use the path 1' to forward the packet, so that the forwarding is completed directly in the local UPF1,
  • the packet needs to be forwarded to the anchor UPF through the transport network, which optimizes the forwarding path and reduces the forwarding delay.
  • the control plane gateway sends a forwarding routing table to the local UPF1 and the local UPF2 to establish a tunnel between the UPF1 and the UPF2, so that the vehicle 2 and the vehicle 3 can report using the path 2'.
  • the packet is forwarded, and the packet is forwarded through the tunnel between the UPF1 and the UPF2.
  • the packet is not forwarded to the anchor UPF through the transport network.
  • the forwarding path is optimized and the forwarding delay is reduced.
  • the method 500 further includes:
  • the control plane gateway updates the registration information to obtain the updated registration information
  • the control plane gateway updates the forwarding routing table according to the updated registration information.
  • the control plane gateway can update the registration information of the UE.
  • the control plane gateway may update the forwarding routing table based on the updated registration information.
  • the control plane gateway performs the update, it can update only the entries of the UE whose user plane gateway changes, and does not need to update the entries of all the registered UEs, thereby reducing the update range and saving the overhead.
  • the UEs that need to communicate may be dynamically added in the initial scheduled or late stage, which is not limited.
  • a registration mechanism is introduced, and two or more parties that need to communicate are managed or maintained through an application layer.
  • FIG. 7 shows a schematic diagram of another example in accordance with an embodiment of the present application.
  • the vehicle 1, the vehicle 2, and the vehicle 3 are a moving vehicle formation, and the vehicles in the moving vehicle formation need to maintain continuous business communication.
  • the server such as the V2X server.
  • the server organizes the vehicle 1, the vehicle 2, and the vehicle 3 according to the received formation communication request.
  • the server transmits the formation vehicle information (ie, the above registration information) to the control plane gateway (such as AMF/SMF in FIG. 7) through the NEF.
  • the control plane gateway generates a forwarding routing table according to the formation vehicle information, and sends it to the user plane gateway (including local UPF1 and local UPF2).
  • No formation is required between the scattered vehicles, and no formation requests are sent to the server.
  • the control plane gateway needs to update the route of the local UPF1 to the vehicle 2, and the route of the local UPF2 to the vehicle 1, ensuring the vehicle 1 and the vehicle 2 Communication occurs through the tunnel between the local UPF1 and the local UPF2 without routing updates to the scattered vehicles.
  • control plane gateway only updates the user entries for the formation vehicle, thereby reducing the number of updated user entries, reducing network turbulence and helping to improve network performance.
  • FIG. 8 shows an interaction diagram of a specific flow in accordance with an embodiment of the present application.
  • the solid line in FIG. 8 indicates the interaction step between the respective devices, and the broken line indicates the packet forwarding path between UE1 and UE2.
  • the process includes:
  • the UE1 establishes a Packet Data Network (PDN) to connect to the anchor UPF, and the edge user plane is established in the local UPF1.
  • PDN Packet Data Network
  • UE2 establishes a PDN connection to the anchor UPF, and the edge user plane is established at the local UPF1.
  • UE1 registers with the V2X server (or controller controller) and joins the formation.
  • UE2 registers with the V2X server (or controller controller) and joins the formation.
  • UE1 and UE2 are registered to an Application Server (AS). Among them, UE1 and UE2 are a fleeted vehicle. Packet forwarding needs to be performed between UE1 and UE2.
  • AS Application Server
  • the V2X server can obtain the formation information of UE1 and UE2.
  • the V2X server sends the formation information (or registration information) of UE1 and UE2 to the SMF.
  • the formation information may also be pre-configured to the SMF.
  • the SMF acquires the formation information of UE1 and UE2. Further, the SMF generates a forwarding routing table according to the formation information of UE1 and UE2.
  • the SMF sends a user-level forwarding routing table to the local UPF1.
  • the local UPF1 can determine the packet forwarding path of the UE1 and the UE2 according to the forwarding routing table.
  • the packet forwarding path of UE1 to UE2 is: UE1-RAN1-local UPF1-RAN1-UE2.
  • UE2 switches. UE2 switches from RAN1 to RAN2, and the corresponding UPF switches from local UPF1 to local UPF2.
  • the packet forwarding of UE1 and UE2 can be forwarded through the following paths: (1) original link: UE1-RAN1-local UPF1-RAN1-UE2; (2) new link : UE1-RAN1-local UPF1-RAN2-UE2.
  • the new link here refers to the link that has not been optimized after the handover of UE2.
  • the message between the UE1 and the UE2 may be a V2V packet.
  • the RAN2 sends a path switch request to the AMF.
  • the AMF initiates a create session request to the SMF.
  • the create session request in step 810 is sent by the AMF to the SMF.
  • the SMF may send a create session request to the local UPF2 according to an algorithm.
  • the create session request in step 811 is sent by the SMF to the local UPF2.
  • the local UPF2 replies to the SMF to create a session response (create session response).
  • the "Create Session Response” herein corresponds to "Create Session Request” in step 811.
  • the SMF sends a GTP tunnel create request to the local UPF1.
  • the request for creating an inter-UPF tunnel in step 813 is used to request to create a tunnel between the local UPF1 and the local UPF2, such as a GTP tunnel.
  • the local UPF1 replies to the SMF to create an inter-UPF tunnel response.
  • the SMF sends an inter-UPF tunnel request to the local UPF2.
  • the request to create an inter-UPF tunnel in step 815 is the same as the method of creating a tunnel between the local UPF1 and the local UPF2, such as a GTP tunnel.
  • the local UPF2 replies to the SMF to create an inter-UPF tunnel response.
  • the SMF sends a session modify request to the anchor UPF.
  • the session modification request in step 817 is sent by the SMF to the anchor UPF.
  • the anchor UPF replies to the SMF with a session modify response.
  • the "session modification response” herein corresponds to the "session modification request” in step 817.
  • the SMF needs to update the forwarding routing table, and sends the updated forwarding routing table to the local UPF1 and the local UPF2.
  • the SMF sends an update user-level forwarding routing request to the local UPF2.
  • the local UPF2 replies to the SMF with a user-level forwarding route response.
  • the user-level forwarding route response in step 820 is for the local UPF2 response to update the user-level forwarding routing request in step 819.
  • the SMF sends an update user-level forwarding routing request to the local UPF1.
  • the local UPF1 replies to the SMF with a user-level forwarding route response.
  • the user-level forwarding route response in step 822 is used by the UPF1 response to update the user-level forwarding routing request in step 821.
  • the local UPF1 may determine the forwarding path of the UE1 and the UE2 according to the updated forwarding routing table.
  • the packet forwarding path is: UE1-RAN1-local UPF1-local UPF2-RAN2-UE2.
  • the packet forwarding path is not unified with the path of UE1 to UE2, and the packet forwarding path of UE2 to UE1 is: UE2-RAN2-local UPF1-RAN1-UE1.
  • the SMF replies to the AMF to create a session response (create session response).
  • create session response The create session response in step 823 is used to respond to the create session request in step 810.
  • the AMF returns a path switch request response to the RAN2.
  • the packet forwarding path of the UE2 to the UE1 is updated to: UE2-RAN2-local UPF2-local UPF1-RAN1-UE1, and the uplink and downlink paths are unified, that is, the packet forwarding path of UE2 to UE1 and the report of UE1 to UE2 are implemented.
  • the text forwarding path is unified.
  • the RAN2 sends a link release request to the RAN1, or a release resource request.
  • the SMF sends a release resource request to the UPF1, or deletes a session request.
  • the technical solution of the embodiment of the present application implements path optimization, effectively reduces packet forwarding delay, and can meet the requirements of low-latency services.
  • each term in FIG. 8 may correspond to a corresponding sending and/or receiving subject.
  • the names of the terms used in the respective steps do not limit the steps to be performed.
  • the nomenclature of the terms may be replaced with other nomenclature.
  • FIG. 6 to FIG. 8 are only for facilitating the understanding of the embodiments of the present application, and the embodiments of the present application are not limited to the specific scenarios illustrated. It is apparent to those skilled in the art that various modifications and changes can be made in the embodiments of the present invention in accordance with the examples of FIG. 6 to FIG. 8. Such modifications or variations are also within the scope of the embodiments of the present invention.
  • FIG. 9 shows a schematic block diagram of a control plane gateway 900 in accordance with an embodiment of the present application.
  • the control plane gateway 900 is configured to execute a method or a step corresponding to the foregoing control plane gateway.
  • each module in the control plane gateway 900 can be implemented by software.
  • the control plane gateway 900 can be installed in a general purpose computer device. As shown in FIG. 9, the control plane gateway 900 includes:
  • the obtaining module 910 is configured to acquire registration information of the first user equipment UE and registration information of the second user equipment UE, where the registration information of the first UE includes a UE identifier that communicates with the first UE, and the second The registration information of the UE includes a UE identifier that communicates with the second UE;
  • the processing module 920 is configured to generate, according to the registration information of the first UE and the registration information of the second UE, a forwarding routing table of the first UE and the second UE, where the forwarding routing table includes the Information required by the first UE and the second UE to perform a path for packet transmission;
  • the transceiver module 930 is configured to send the forwarding routing table to the first user plane gateway and the second user plane gateway, where the forwarding routing table is used by the user plane gateway to determine the first UE and the second UE. And a message forwarding path, where the first user plane gateway is a gateway where the first UE is located, and the second user plane gateway is a gateway where the second UE is located.
  • the first user plane gateway is the same as the second user plane gateway, where
  • the processing module 920 is specifically configured to:
  • the forwarding routing table includes a route that the first user plane gateway reaches the first UE, and the first The user plane gateway arrives at the route of the second UE, where the packet forwarding of the first UE and the second UE is directly sent by the first user plane gateway.
  • the first user plane gateway and the second user plane gateway are different user plane gateways, where
  • the processing module 920 is specifically configured to:
  • the control plane gateway generates the forwarding routing table according to the registration information, the identifier of the first user plane gateway, and the identifier of the second user plane gateway, where the forwarding routing table includes the first user plane And the route that the gateway reaches the second UE by using the second user plane gateway, and the route that the second user plane gateway reaches the first UE by using the first user plane gateway.
  • the processing module 920 is further configured to: update the registration information to obtain the updated registration information; and be configured to update the forwarding routing table according to the updated registration information.
  • the transceiver module 930 is further configured to:
  • control plane gateway 900 may correspond to the control plane gateway in the message forwarding of the foregoing method embodiment, and the foregoing and other management operations and/or functions of the respective modules in the control plane gateway 900 respectively
  • beneficial effects in the foregoing method embodiments may also be implemented.
  • no further details are provided herein.
  • processing module 920 in the embodiment of the present application may be implemented by a processor, and the transceiver module 930 and the obtaining module 910 may be implemented by a transceiver.
  • FIG. 10 shows a schematic block diagram of a user plane gateway 1000 in accordance with an embodiment of the present application.
  • the user plane gateway 1000 is configured to perform the foregoing method or step corresponding to the first user plane gateway.
  • each module in the user plane gateway 1000 can be implemented by using software.
  • the user plane gateway 1000 can be installed in a general purpose computer device. As shown in FIG. 10, the user plane gateway 1000 includes:
  • the transceiver module 1010 is configured to receive a forwarding routing table sent by the control plane gateway, where the forwarding routing table includes information required by the first user equipment UE and the second user equipment UE to perform a packet transmission path;
  • the processing module 1020 is configured to determine, according to the forwarding routing table, a packet forwarding path between the first UE and the second UE, where the first user plane gateway is a gateway where the first UE is located The second user plane gateway is a gateway where the second UE is located.
  • the first user plane gateway is the same as the second user plane gateway, where the forwarding routing table includes a route that the first user plane gateway reaches the first UE, and the first a route that the user plane gateway reaches the second UE;
  • the processing module 1020 is specifically configured to:
  • the first user plane gateway and the second user plane gateway are different user plane gateways
  • the forwarding routing table includes the first user plane gateway reaching the a route of the second UE, and a route that the second user plane gateway reaches the first UE by using the first user plane gateway;
  • the processing module 1020 is specifically configured to:
  • the transceiver module 1010 is further configured to:
  • the user plane gateway 1000 may correspond to the first user plane gateway in the message forwarding of the foregoing method embodiment, and the above and other management operations and/or other management operations of the respective modules in the user plane gateway 1000.
  • the functions of the foregoing method are respectively implemented in order to implement the corresponding steps of the foregoing methods. For the sake of brevity, details are not described herein again.
  • processing module 1020 in the embodiment of the present application may be implemented by a processor, and the transceiver module 1010 may be implemented by a transceiver.
  • FIG. 11 shows a schematic block diagram of a user plane gateway 1100 in accordance with an embodiment of the present application.
  • the user plane gateway 1100 is configured to perform the foregoing method or step corresponding to the second user plane gateway.
  • each module in the user plane gateway 1100 can be implemented by software.
  • the user plane gateway 1100 can be installed in a general purpose computer device. As shown in FIG. 11, the user plane gateway 1100 includes:
  • the transceiver module 1110 is configured to receive a forwarding routing table sent by the control plane gateway, where the forwarding routing table includes a route that the first user plane gateway reaches the second user equipment UE by using the second user plane gateway, and the second user
  • the first gateway of the gateway is the user plane gateway where the first UE is located
  • the second user plane gateway is the second The user plane gateway where the UE is located, the first user plane gateway and the second user plane gateway are different user plane gateways;
  • the processing module 1120 is configured to determine, according to the forwarding routing table, a packet forwarding path between the first UE and the second UE.
  • the transceiver module 1110 is further configured to:
  • the user plane gateway 1100 may correspond to the second user plane gateway in the message forwarding of the foregoing method embodiment, and the above and other management operations and/or other management operations of the respective modules in the user plane gateway 1100.
  • the functions of the foregoing method are respectively implemented in order to implement the corresponding steps of the foregoing methods. For the sake of brevity, details are not described herein again.
  • processing module 1120 in the embodiment of the present application may be implemented by a processor, and the transceiver module 1110 may be implemented by a transceiver.
  • 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 application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the functions may be stored in a computer readable storage medium if implemented in the form of a software functional unit and sold or used as a standalone product.
  • the technical solution of the present application 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 application.
  • 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, which can store program codes.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本申请提供了一种用于报文转发的方法、控制面网关和用户面网关，该方法包括：控制面网关获取第一用户设备UE的注册信息和第二用户设备UE的注册信息，该第一UE的注册信息包括与该第一UE进行通信的UE标识，该第二UE的注册信息包括与该第二UE进行通信的UE标识；根据该注册信息，生成第一UE和第二UE的转发路由表，该转发路由表包括第一UE和第二UE进行报文传输的路径所需的信息；将该转发路由表下发给第一用户面网关和第二用户面网关，该转发路由表用于用户面网关确定第一UE和第二UE之间的报文转发路径。本申请实施例的用于报文转发的方法、控制面网关和用户面网关，能够有效地优化转发路径，以满足低时延业务的需求。

Description

报文转发的方法、控制面网关和用户面网关
本申请要求于2017年11月28日提交中国专利局、申请号为201711219039.2、发明名称为“报文转发的方法、控制面网关和用户面网关”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信领域，并且更具体地，涉及一种报文转发的方法、控制面网关和用户面网关。
背景技术
在车到车通讯中，由于车辆的移动性，需要尽可能的兼顾业务的连续性和低时延。业务的连续性的表现之一就是车辆用户通讯的端点信息(比如用户通讯IP地址)保持不变，这样使得通讯双方可以快速联系上对方而不需要通过其他技术换取对方变化后的端点信息。为了获得更低的时延，通常会将网关下沉，即在离车辆用户近的位置部署更多的网关。这样，车到车通讯可能会在跨下沉网关的场景中进行。
在用户面网关下沉后，若仍然采用现有技术的报文转发方案，将会导致路径迂回，增大转发时延。因此，需要找到一种方案，可以有效地优化转发路径，以满足低时延业务的需求。
发明内容
本申请提供一种用于报文转发的方法、控制面网关和用户面网关，能够有效地优化转发路径，以满足低时延业务的需求。
第一方面，提供了一种用于报文转发的方法，包括：
控制面网关获取第一用户设备UE的注册信息和第二用户设备UE的注册信息，所述第一UE的注册信息包括与所述第一UE进行通信的UE标识，所述第二UE的注册信息包括与所述第二UE进行通信的UE标识；
所述控制面网关根据所述第一UE的注册信息和所述第二UE的注册信息，生成所述第一UE和所述第二UE的转发路由表，所述转发路由表包括所述第一UE和所述第二UE进行报文传输的路径所需的信息；
所述控制面网关将所述转发路由表下发给第一用户面网关和第二用户面网关，所述转发路由表用于用户面网关确定所述第一UE和所述第二UE之间的报文转发路径，其中，所述第一用户面网关是第一UE所在的网关，所述第二用户面网关是所述第二UE所在的网关。
在本申请实施例中，控制面网关通过确定转发路由表并向第一用户面网关下发转发路由表，使得第一用户面网关根据转发路由表确定第一UE和第二UE之间的报文转发路径，能够优化报文转发路径，从而满足低时延业务的需求。
在本申请实施例中，上述第一UE和第二UE可能同在一个用户面网关下，也可能是跨用户面网关。也就是说，第一用户面网关与第二用户面网关可能相同，也可能不相同。
在一些可能的实现方式中，所述第一用户面网关与所述第二用户面网关相同，其中，
生成所述第一UE和所述第二UE的转发路由表，包括：
所述控制面网关根据所述注册信息和所述第一用户面网关的标识，生成所述转发路由表，所述转发路由表包括所述第一用户面网关到达所述第一UE的路由，以及所述第一用户面网关到达所述第二UE的路由，其中，所述第一UE和所述第二UE的报文转发是通过所述第一用户面网关直接发送的。
这样，第一UE和第二UE的报文转发可以通过第一用户面网关直接进行转发，而不需要从第一用户面网关经过传输网络以及中心网关迂回转发，优化了转发路径，降低了转发时延，能够满足低时延业务的需求。
在一些可能的实现方式中，所述第一用户面网关与所述第二用户面网关是不同的用户面网关，其中，
生成所述第一UE和所述第二UE的转发路由表，包括：
所述控制面网关根据所述注册信息、所述第一用户面网关的标识和所述第二用户面网关的标识，生成所述转发路由表，所述转发路由表包括所述第一用户面网关经过所述第二用户面网关到达所述第二UE的路由，以及所述第二用户面网关经过所述第一用户面网关到达所述第一UE的路由。
可选地，所述第一用户面网关与所述第二用户面网关是同一中心网关下的不同用户面网关。
这里，第一UE和第二UE的报文转发可以通过第一用户面网关和第二用户面网关之间的隧道直接进行转发，而不需要从用户面网关经过传输网络以及中心网关迂回转发，优化了转发路径，降低了转发时延，能够满足低时延业务的需求。并且，第一UE的IP地址与第二UE的IP地址是中心网关分配的，由于中心网关保持不变，即使UE从本地UP1切换到本地UPF2，UE的IP地址也未发生变化，从而保证了上层应用的连续性，避免了网关重连带来的业务中断。
在一些可能的实现方式中，在生成所述转发路由表前，所述方法还包括：
所述控制面网关对所述注册信息进行更新，得到所述更新后的注册信息；
所述控制面网关根据所述更新后的注册信息，更新所述转发路由表。
这里，控制面网关在进行更新时，可以只针对用户面网关发生变化的UE的表项进行更新，而不需要对所有注册过的UE的表项进行更新，从而减少了更新范围，节省了开销。
在一些可能的实现方式中，在所述控制面网关向所述第一用户面网关和所述第二用户面网关下发所述转发路由表前，所述方法还包括：
所述控制面网关向所述第一用户面网关和所述第二用户面网关发送创建隧道请求，所述创建隧道请求用于请求创建所述第一用户面网关和所述第二用户面网关之间的隧道；
所述控制面网关接收所述第一用户面网关发送的第一创建隧道请求响应，所述第一创建隧道请求响应用于所述第一用户面网关响应所述创建隧道请求；
所述控制面网关接收所述第二用户面网关发送的第二创建隧道请求响应，所述第二创建隧道请求响应用于所述第二用户面网关响应所述创建隧道请求。
这里，控制面网关可以请求第一用户面网关和第二用户面网关之间建立隧道连接，以便于实现跨用户面网关之间的通信，从而优化转发路径。
第二方面，提供了一种用于报文转发的方法，包括：
第一用户面网关接收控制面网关发送的转发路由表，所述转发路由表包括第一用户设备UE和第二UE进行报文传输的路径所需的信息；
所述第一用户面网关根据所述转发路由表确定所述第一UE和所述第二UE之间的报文转发路径，其中，所述第一用户面网关是所述第一UE所在的网关，第二用户面网关是所述第二UE所在的网关。
在本申请实施例中，第一用户面网关接收控制面网关发送的转发路由表，并根据转发路由表确定第一UE和第二UE之间的报文转发路径，能够优化报文转发路径，从而满足低时延业务的需求。
在本申请实施例中，上述第一UE和第二UE可能同在一个用户面网关下，也可能是跨用户面网关。也就是说，第一用户面网关与第二用户面网关可能相同，也可能不相同。
在一些可能的实现方式中，所述第一用户面网关与所述第二用户面网关相同，其中，所述转发路由表包括所述第一用户面网关到达所述第一UE的路由，以及所述第一用户面网关到达所述第二UE的路由；
所述第一用户面网关根据所述转发路由表确定所述第一UE和所述第二UE的报文转发路径，包括：
所述第一用户面网关根据所述转发路由表，确定所述第一UE和所述第二UE的报文转发通过所述第一用户面网关直接发送。
这样，第一UE和第二UE的报文转发可以通过第一用户面网关直接进行转发，而不需要从第一用户面网关经过传输网络以及中心网关迂回转发，优化了转发路径，降低了转发时延，能够满足低时延业务的需求。
在一些可能的实现方式中，所述第一用户面网关与所述第二用户面网关是不同的用户面网关，所述转发路由表包括所述第一用户面网关经过所述第二用户面网关到达所述第二UE的路由，以及所述第二用户面网关经过所述第一用户面网关到达所述第一UE的路由；
其中，所述第一用户面网关根据所述转发路由表确定所述第一UE和所述第二UE的报文转发路径，包括：
所述第一用户面网关根据所述转发路由表，确定所述第一UE和所述第二UE的报文转发通过所述第一用户面网关和所述第二用户面网关之间的隧道发送。
可选地，所述第一用户面网关与所述第二用户面网关是同一中心网关下的不同用户面网关。
这里，第一UE和第二UE的报文转发可以通过第一用户面网关和第二用户面网关之间的隧道直接进行转发，而不需要从用户面网关经过传输网络以及中心网关迂回转发，优化了转发路径，降低了转发时延，能够满足低时延业务的需求。并且，第一UE的IP地址与第二UE的IP地址是中心网关分配的，由于中心网关保持不变，即使UE从本地UP1切换到本地UPF2，UE的IP地址也未发生变化，从而保证了上层应用的连续性，避免了网关重连带来的业务中断。
在一些可能的实现方式中，所述方法还包括：
所述第一用户面网关接收所述控制面网关发送的创建隧道请求，所述第一创建隧道请求用于请求创建所述第一用户面网关和所述第二用户面网关之间的隧道；
所述第一用户面网关向所述控制面网关发送第一创建隧道请求响应，所述第一创建隧道 请求响应用于所述第一用户面网关响应所述创建隧道请求。
这里，第一用户面网关可以响应控制面网关的创建隧道请求，并与第二用户面网关建立隧道连接，以便于实现跨用户面网关之间的通信，从而优化转发路径。
第三方面，提供了一种控制面网关，用于执行上述第一方面或第一方面的任意可能的实现方式中的方法。具体地，该控制面网关包括用于执行上述第一方面或第一方面的任意可能的实现方式中的方法的模块。
第四方面，提供了一种用户面网关，用于执行上述第二方面或第二方面的任意可能的实现方式中的方法。具体地，该用户面网关包括用于执行上述第二方面或第二方面的任意可能的实现方式中的方法的模块。
第五方面，提供了一种控制面网关，该控制面网关包括处理器、存储器和收发器。处理器与存储器和收发器连接。存储器用于存储指令，处理器用于执行该指令，收发器用于在处理器的控制下与其他网元进行通信。该处理器执行该存储器存储的指令时，该执行使得该处理器执行第一方面或第一方面的任意可能的实现方式中的方法。
第六方面，提供了一种用户面网关，该用户面网关包括处理器、存储器和收发器。处理器与存储器和收发器连接。存储器用于存储指令，处理器用于执行该指令，收发器用于在处理器的控制下与其他网元进行通信。该处理器执行该存储器存储的指令时，该执行使得该处理器执行第二方面或第二方面的任意可能的实现方式中的方法。
第七方面，提供了一种计算机可读存储介质，该计算机可读存储介质存储有程序，该程序使得控制面网关执行上述第一方面，及其各种实现方式中的任一种报文转发的方法。
第八方面，提供了一种计算机可读存储介质，该计算机可读存储介质存储有程序，该程序使得用户面网关执行上述第二方面，及其各种实现方式中的任一种报文转发的方法。
第九方面，提供了一种通信芯片，其中存储有指令，当其在控制面网关上运行时，使得所述通信芯片执行上述第一方面或第一方面的任意可能的实现方式中的方法。
第十方面，提供了一种通信芯片，其中存储有指令，当其在用户面网关上运行时，使得所述通信芯片执行上述第二方面或第二方面的任意可能的实现方式中的方法。
第十一方面，提供了一种包含指令的计算机程序产品，其在计算机上运行时，使得计算机执行上述第一方面或其任意可能的实现方式中的方法，或者第二方面或其任意可能的实现方式中的方法。
附图说明
图1是一种控制面与用户面分离CUPS网络架构图。
图2是应用本申请实施例的一个场景示意图。
图3是根据本申请实施例的控制面网关的结构框图。
图4是根据本申请实施例的用户面网关的结构框图。
图5是根据本申请实施例的用于报文转发的方法的示意性交互图。
图6是应用本申请实施例的一个例子的示意图。
图7是根据本申请实施例的另一个例子的示意图。
图8是根据本申请实施例的一个具体流程的交互图。
图9是根据本申请实施例的控制面网关的示意性框图。
图10是根据本申请实施例的用户面网关的示意性框图。
图11是根据本申请实施例的用户面网关的示意性框图。
具体实施方式
下面将结合附图，对本申请中的技术方案进行描述。
本申请实施例的技术方案可以应用于各种通信系统，例如：全球移动通讯(Global System of Mobile communication，GSM)系统、码分多址(Code Division Multiple Access，CDMA)系统、宽带码分多址(Wideband Code Division Multiple Access，WCDMA)系统、通用分组无线业务(General Packet Radio Service，GPRS)、长期演进(Long Term Evolution，LTE)系统、LTE频分双工(Frequency Division Duplex，FDD)系统、LTE时分双工(Time Division Duplex，TDD)、通用移动通信系统(Universal Mobile Telecommunication System，UMTS)、全球互联微波接入(Worldwide Interoperability for Microwave Access，WiMAX)通信系统、未来的第五代(5th Generation，5G)系统或新无线(New Radio，NR)等。
本申请实施例的技术方案可以应用于控制面与用户面分离(Control and User Plane Separation，CUPS)的网络架构中。控制面与用户面分离，即将一些或者全部兼具控制面和用户面的功能的网元，拆分成控制面网元和用户面网元两个个体。CUPS也称为CU分离。CU分离的网络架构中，控制面网元具有控制面功能，主要包括与其他网元之间的信令连接、处理用户设备的移动性管理和会话管理请求、管理用户设备的上下文和建立传输数据的通道。用户面网元具有用户面功能，主要包括发送用户设备的上下行数据报文、执行针对数据报文的服务质量(Quality of Service，QoS)的控制和流量统计等。其中，通道也可称作隧道(tunnel)，比如通用分组无线服务技术(General Packet Radio Service，GPRS)隧道协议(GPRS Tunnelling Protocol，GTP)tunnel等。
图1示出了一种CUPS网络架构图。如图1所示，该网络架构主要包括UE、基站、控制面网关和服务器。图1中虚线表示通过控制面传输消息，实线表示通过用户面传输消息或数据报文。
UE可以指终端设备、接入终端、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、终端、无线通信设备、用户代理或用户装置。终端设备还可以是蜂窝电话、无绳电话、会话启动协议(Session Initiation Protocol，SIP)电话、无线本地环路(Wireless Local Loop，WLL)站、个人数字处理(Personal Digital Assistant，PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备，未来5G网络中的终端设备或者未来演进的公用陆地移动通信网络(Public Land Mobile Network，PLMN)中的终端设备、车到一切(Vehicle to X，V2X)设备、车到车(Vehicle to Vehicle，V2V)设备等，本申请实施例对此并不限定。UE可以与控制面网关通过信令消息通信，也可以与用户面网关进行数据报文的传输。
基站是本申请实施例使用的一种CP分离的网络架构中一种可能的组成部分，可以是未来5G网络中的基站设备g-NB、小基站设备、eNB，还可以是云无线接入网络(Cloud Radio Access Network，CRAN)场景下的无线控制器，或者是移动性管理网元(Mobility Management Entity，MME)或者，该基站可以为中继站、接入点、车载设备、可穿戴设备以及未来5G网络中的网络设备或者未来演进的PLMN网络中的网络设备等，本申请实施例并不限定。UE 与控制面网关和用户面网关之间通过基站通信，当然，UE与控制面网关和用户面网关之间也可以直接通信，即CP分离的网络架构种可以没有基站，本申请实施例对此并不限定。
5G网络中的核心网(Core Network，CN)包括控制面的网络功能(Network Function，NF)以及用户面的网络功能。核心网与5G接入网络(Radio Access Network，RAN)连接。
控制面(Control Plane，CP)网关(Gateway)具有控制面的接口，主要用于与其他网元之间的进行信令连接，处理用户的移动性管理和会话管理请求，管理用户的上下文和建立传输数据的通道。控制面网关可以用于静态IP地址分配或动态IP地址分配时的网关自主分配。控制面网关可以是公用数据网网关(Public Data Network GateWay，PGW)分离后具有控制面功能的控制网关(Control GateWay，CGW)。
可选地，控制面的网络功能可以是会话管理功能(Session Management Function，SMF)，接入和移动性管理功能(Access and Mobility Management Function，AMF)。
用户面(User Plane，UP)网关Gateway具有用户面的接口，主要用于发送用户的上下行数据报文、执行针对数据报文的QoS控制和流量统计等。用户面网关可以用于动态IP地址分配时的网关自主分配、动态IP地址分配时的外部网络分配。服务器(Server)可以分配IP地址，与用户面网关相连可以收发数据报文。用户面网关可以是PGW分离后具有用户面功能的用户面网关(User GateWay，UGW)。
进一步地，对于用户面网关下沉的场景，用户面网关可以分离成中心网关(比如，锚点Anchor用户面功能(User Plane Function，UPF))和边缘网关(比如，本地Local UPF)，其中，Anchor UPF作为用户面锚点，Local UPF将用户面拉远，为低时延业务提供就近转发。一个Anchor UPF可以对应多个Local UPF。随着UE的移动，会出现跨Local UPF的场景。
图2是应用本申请实施例的一个场景示意图。如图2所示，该网络架构主要包括控制面网关，传输网络，用户面网关和车辆(包括车辆1和车辆2)。其中，用户面网关分离为锚点(Anchor)UPF和本地(Local)UPF(包括Local UPF1和Local UPF2)。可选地，车辆1与车辆2可能在同一Local UPF下(如图2中车道T1中所示的车辆1与车辆2)进行通信，也可能跨Local UPF(如图2中车道T2中所示的车辆1与车辆2)进行通信。
应理解，上述只是以图2中的场景为例进行描述，并不对本申请实施例的保护范围构成限定。
在现有的方案中，若车辆1与车辆2均在Local UPF1，车辆1与车辆2通过路径1进行报文转发；若车辆2移动到Local UPF2下，车辆1与车辆2通过路径2进行报文转发。但不论是路径1还是路径2，都会拉长车辆1与车辆2进行报文转发的路径，时延较大，不能满足低时延业务的需求。
基于此，本申请实施例拟提出一种新的解决方案，通过对路径进行优化，以满足低时延业务的需求。
图3示出了根据本申请实施例的控制面网关300的结构框图。如图3所示，所示的控制面网关300包括：处理器301、存储器302和收发器303。
处理器301、存储器302和收发器303之间通过内部连接通路互相通信，传递控制和/或数据信号。在一个可能的设计中，处理器301、存储器302和收发器303可以通过芯片实现。该存储器302可以存储程序代码，处理器301调用存储器302存储的程序代码，以实现该控制面网关的相应功能。
所述处理器301用于：
通过所述收发器303获取第一UE的注册信息和第二UE的注册信息，所述第一UE的注册信息包括与所述第一UE进行通信的UE标识，所述第二UE的注册信息包括与所述第二UE进行通信的UE标识；
所述控制面网关根据所述第一UE的注册信息和所述第二UE的注册信息，生成所述第一UE和所述第二UE的转发路由表，所述转发路由表包括所述第一UE和所述第二UE进行报文传输的路径所需的信息；
通过所述收发器303将所述转发路由表下发给第一用户面网关和第二用户面网关，所述转发路由表用于用户面网关确定所述第一UE和所述第二UE之间的报文转发路径，其中，所述第一用户面网关是第一UE所在的网关，所述第二用户面网关是所述第二UE所在的网关。
可以理解的是，尽管并未示出，控制面网关300还可以包括其他装置，例如输入装置、输出装置、电池等。
在一个可能的设计中，存储器302可以存储用于执行本申请实施例的用于报文转发的方法中控制面网关执行的方法的指令。处理器301可以执行存储器302中存储的指令结合其他硬件(例如收发器303)完成下文方法中控制面网关执行的步骤，具体工作过程和有益效果可以参见下文方法实施例中的描述。
图4示出了根据本申请实施例的用户面网关400的结构框图。如图4所示，所示的用户面网关400包括：处理器401、存储器402和收发器403。
处理器401、存储器402和收发器403之间通过内部连接通路互相通信，传递控制和/或数据信号。在一个可能的设计中，处理器401、存储器402和收发器403可以通过芯片实现。该存储器402可以存储程序代码，处理器401调用存储器402存储的程序代码，以实现该用户面网关的相应功能。
所述处理器401用于：
通过所述收发器403接收控制面网关发送的转发路由表，所述转发路由表包括第一用户设备UE和第二UE进行报文传输的路径所需的信息；
根据所述转发路由表确定所述第一UE和所述第二UE之间的报文转发路径。
可以理解的是，尽管并未示出，用户面网关400还可以包括其他装置，例如输入装置、输出装置、电池等。
在一个可能的设计中，存储器402可以存储用于执行本申请实施例的用于报文转发的方法中用户面网关执行的方法的指令。处理器401可以执行存储器402中存储的指令结合其他硬件(例如收发器403)完成下文方法中用户面网关(第一用户面网关或第二用户面网关)执行的步骤，具体工作过程和有益效果可以参见下文方法实施例中的描述。
本申请实施例揭示的方法可以应用于处理器中，或者由处理器实现。处理器可能是一种集成电路芯片，具有信号的处理能力。在实现过程中，下文方法的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器可以是通用处理器、数字信号处理器(digital signal processor，DSP)，专用集成电路(application specific integrated circuit，ASIC)，现场可编程门阵列(field programmable gate array，FPGA)或者其他可编程逻辑器件，分立门或者晶体管逻辑器件，分立硬件组件，还可以是系统芯片(system on chip，SoC)，还 可以是中央处理器(central processor unit，CPU)，还可以是网络处理器(network processor，NP)，还可以是数字信号处理电路(digital signal processor，DSP)，还可以是微控制器(micro controller unit，MCU)，还可以是可编程控制器(programmable logic device，PLD)或其他集成芯片。可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存取存储器(random access memory，RAM)、闪存、只读存储器(read-only memory，ROM)、可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器，处理器读取存储器中的指令，结合其硬件完成下述方法的步骤。
图5示出了根据本申请实施例的用于报文转发的方法500的示意性交互图。如图5所示，所述方法500包括：
S501，控制面网关获取第一用户设备UE的注册信息和第二UE的注册信息，所述第一UE的注册信息包括与所述第一UE进行通信的UE标识，所述第二UE的注册信息包括与所述第二UE进行通信的UE标识。
可选地，所述控制面网关可以是AMF/SMF节点或设备，也可以是MME，对此不作限定。
可选地，所述第一UE的注册信息可以包括第一UE的用户表项以及与第一UE进行通信的UE标识。所述第二UE的注册信息可以包括第二UE的用户表项以及与第二UE进行通信的UE标识。
可选地，控制面网关根据上述注册信息可以获知第一UE与第二UE之间的报文转发关系。
具体地，第一UE和第二UE都向V2X服务器进行注册，并加入一个编队组。然后，控制面网关可以通过V2X控制器获取上述注册信息，从而获知第一UE与第二UE是一个通信组，进而下发转发路由表。
可选地，在具体实现时，上述注册信息可以是控制面网关通过服务器(比如，V2X服务器)主动获取的，也可以是服务器通过网络开放功能(Network Exposure Function，NEF)发送给控制面网关的，也可以是预先配置给所述控制面网关的，本申请实施例对此不作限定。
应理解，这里是以第一UE和第二UE为例说明。可选地，控制面网关可以获取多个有通信需求的UE的注册信息，本申请实施例对此不作限定。
S502，控制面网关根据所述第一UE的注册信息和所述第二UE的注册信息，生成所述第一UE和所述第二UE的转发路由表，所述转发路由表包括所述第一UE和所述第二UE进行报文传输的路径所需的信息。
具体地，控制面网关根据第一UE的注册信息和第二UE的注册信息，关联到用户上下文，并在转发面上生成转发路由表。
可选地，控制面网关可以维护转发路由表，该转发路由表中可以包括第一UE与第二UE之间的通信路径所需的信息。比如，该转发路由表可以包括第一UE的互联网协议(Internet Protocol，IP)地址，第二UE的IP地址，第一UE与第二UE所在的用户面网关的标识(Identifier，ID)，第一UE的下一跳设备的地址，第二UE的下一跳设备的地址等信息。
应理解，第一UE与第二UE进行报文转发的路径可以是第一UE到第二UE的通信，也 可以是第二UE到第一UE的通信，对此不作具体限定。对应地，转发路由表可以包括第一UE与第二UE进行通信时的单向路径的路由信息，也可以包括双向路径的路由信息，对此不作限定。
S503，控制面网关将转发路由表下发给第一用户面网关和第二用户面网关，所述转发路由表用于用户面网关确定第一UE和第二UE之间的报文转发路径。
可选地，所述第一用户面网关或第二用户面网关是Local UPF。可选地，如果第一UE和第二UE在同一用户面网关(比如第一用户面网关)下，则控制面网关向第一用户面网关下发所述转发路由表。
对应地，第一用户面网关接收控制面网关下发的所述转发路由表。
S504，第一用户面网关根据所述转发路由表确定第一UE和第二UE之间的报文转发路径。
对应地，第二用户面网关接收控制面网关下发的所述转发路由表。
S505，第二用户面网关根据所述转发路由表确定第一UE和第二UE之间的报文转发路径。
可选地，UE的转发报文中有双方通信的IP地址，UE可以基于IP地址查询转发路由表。
应理解，如果上述第一用户面网关与第二用户面网关相同，则可以不执行步骤S505，其中，在步骤S503中控制面网关可以只向第一用户面网关发送上述转发路由表。
在本申请实施例中，控制面网关通过确定转发路由表并向第一用户面网关下发转发路由表，使得第一用户面网关根据转发路由表确定第一UE和第二UE之间的报文转达路径，能够优化报文转发路径，从而满足低时延业务的需求。
需要说明的是，在本申请实施例中，上述第一UE和第二UE可能同在一个用户面网关下，也可能是跨用户面网关。也就是说，第一用户面网关与第二用户面网关可能相同，也可能不相同。当然，不论是哪种情形，本申请实施例的技术方案都是适用的。下面将对这些情形进行详细描述。
可选地，第一用户面网关和第二UE用户面网关相同，其中，生成第一UE和第二UE的转发路由表，包括：
所述控制面网关根据所述注册信息和所述第一用户面网关的标识，生成所述转发路由表，所述转发路由表包括所述第一用户面网关到达所述第一UE的路由，以及所述第一用户面网关到达所述第二UE的路由，其中，所述第一UE和所述第二UE的报文转发是通过所述第一用户面网关直接发送的。
具体而言，如果第一UE和第二UE在同一用户面网关(比如第一用户面网关)下，那么控制面网关可以基于第一UE和第二UE的注册信息，以及第一用户面网关的标识，生成所述转发路由表，并将转发路由表下发给第一用户面网关。其中，所述转发路由表包括第一用户面网关到达第一UE的路由，以及第一用户面网关到达第二UE的路由。也就是说，第一UE和第二UE的报文转发是通过第一用户面网关进行本地转发的。
对应地，第一用户面网关根据所述转发路由表，确定第一UE和第二UE的报文转发通过所述第一用户面网关直接发送。
这样，第一UE和第二UE的报文转发可以通过第一用户面网关(比如图2中的UPF1)直接进行转发，而不需要从第一用户面网关经过传输网络以及中心网关(比如图2中的锚点 UPF)迂回转发，优化了转发路径，降低了转发时延，能够满足低时延业务的需求。
可选地，所述第一用户面网关与所述第二用户面网关是不同的用户面网关，其中，
所述生成所述第一UE和所述第二UE的转发路由表，包括：
所述控制面网关根据所述注册信息、所述第一用户面网关的标识和所述第二用户面网关的标识，生成所述转发路由表，所述转发路由表包括所述第一用户面网关经过所述第二用户面网关到达所述第二UE的路由，以及所述第二用户面网关经过所述第一用户面网关到达所述第一UE的路由。
可选地，所述第一用户面网关与所述第二用户面网关是同一中心网关下的不同用户面网关。
具体而言，如果第一UE和第二UE不在同一用户面网关下，那么控制面网关可以基于第一UE和第二UE的注册信息，第一用户面网关的标识以及第二用户面网关的标识，生成所述转发路由表，并将转发路由表下发给第一用户面网关和第二用户面网关。其中，所述转发路由表包括第一用户面网关经过第二用户面网关到达第一UE的路由，以及第二用户面网关经过第一用户面网关到达第二UE的路由。第一UE和第二UE的报文转发可以通过第一用户面网关和第二用户面网关之间的隧道进行转发。
对应地，第一用户面网关根据所述转发路由表，确定第一UE和第二UE的报文转发通过所述第一用户面网关和所述第二用户面网关之间的隧道发送。
这里，第一UE和第二UE的报文转发可以通过第一用户面网关和第二用户面网关之间的隧道(比如图2中的本地UPF1和本地UPF2的隧道)直接进行转发，而不需要从用户面网关经过传输网络以及中心网关(比如图2中的锚点Anchor UPF)迂回转发，优化了转发路径，降低了转发时延，能够满足低时延业务的需求。并且，第一UE的IP地址与第二UE的IP地址是中心网关分配的，由于中心网关保持不变，即使UE从本地UP1切换到本地UPF2，UE的IP地址也未发生变化，从而保证了上层应用的连续性，避免了网关重连带来的业务中断。
上面描述了第一UE和第二UE可以使用第一用户面网关和第二用户面网关之间的隧道进行报文转发。下面将描述如何打通第一用户面网关和第二用户面网关之间的隧道。
可选地，在控制面网关向所述第一用户面网关和所述第二用户面网关下发所述转发路由表前，所述方法还包括：
所述控制面网关向所述第一用户面网关和所述第二用户面网关发送创建隧道请求，所述创建隧道请求用于请求创建所述第一用户面网关和所述第二用户面网关之间的隧道。
对应地，第一用户面网关接收所述创建隧道请求；第二用户面网关接收所述创建隧道请求。
在第一用户面网关与第二用户面网关建立隧道后，第一用户面网关向所述控制面网关发送第一创建隧道请求响应，所述第一创建隧道请求响应用于所述第一用户面网关响应所述创建隧道请求。
对应地，所述控制面网关接收所述第一用户面网关发送的第一创建隧道请求响应。
在第一用户面网关与第二用户面网关建立隧道后，第二用户面网关向所述控制面网关发送第二创建隧道请求响应，所述第二创建隧道请求响应用于所述第二用户面网关响应所述创建隧道请求。
对应地，所述控制面网关接收所述第二用户面网关发送的第二创建隧道请求响应。
也就是说，控制面网关可以请求第一用户面网关和第二用户面网关之间建立隧道连接，以便于实现跨用户面网关之间的通信，从而优化转发路径。
为了便于本领域的技术人员更清楚得理解本申请实施例的技术方案，下面将结合图6进行描述。图6示出了应用本申请实施例的一个例子的示意图。如图6所示，车辆1与车辆2均接入到本地UPF1，车辆3接入到本地UPF2。其中，本地UPF1和本地UPF2对应同一个锚点UPF(即本地UPF1)。可选地，车辆2也可能移动到本地UPF2下。其中，车辆(car)可以看作UE。
如果车辆1与车辆2需要进行通信，若采用现有技术的方案，车辆1与车辆2会使用路径1进行报文转发。而应用本申请实施例的技术方案后，控制面网关通过将转发路由表下发给本地UPF1，使得车辆1与车辆2能够使用路径1'进行报文转发，从而直接在本地UPF1完成转发，不需要通过传输网络将报文转发到锚点UPF处，优化了转发路径，降低了转发时延。
如果车辆2与车辆3需要进行通信，若采用现有技术的方案，车辆2与车辆3会使用路径2进行报文转发。而应用本申请实施例的技术方案后，控制面网关通过将转发路由表下发给本地UPF1和本地UPF2，建立UPF1和UPF2之间的隧道，使得车辆2与车辆3能够使用路径2'进行报文转发，从而通过UPF1和UPF2之间的隧道完成报文转发，不需要通过传输网络将报文转发到锚点UPF处，优化了转发路径，降低了转发时延。
应理解，在图6中，如果车辆2移动到本地UPF2下，也可以通过UPF1和UPF2之间的隧道实现与车辆1的通信，为了简洁，这里不作赘述。
综上所述，从图6中可以得知：应用本申请实施例的技术方案后得到的转发路径，显然要优于现有技术的转发路径，能够实现快速转发。
可选地，作为一个实施例，所述方法500还包括：
控制面网关对所述注册信息进行更新，得到所述更新后的注册信息；
所述控制面网关根据所述更新后的注册信息，更新所述转发路由表。
具体而言，如果UE移动或切换到不同的用户面网关，那么控制面网关可以对UE的注册信息进行更新。控制面网关可以基于更新后的注册信息，更新上述转发路由表。这里，控制面网关在进行更新时，可以只针对用户面网关发生变化的UE的表项进行更新，而不需要对所有注册过的UE的表项进行更新，从而减少了更新范围，节省了开销。
需要说明的，本申请实施例中，需要通信的UE双方可以在初始预定好或后期动态加入，对此不作限定。本申请实施例中引入注册机制，通过应用层来管理或维护需要通信的双方或多方。
为了便于本领域技术人员理解本申请实施例，下面将结合图7中的例子进行描述。
图7示出了根据本申请实施例的另一个例子的示意图。如图7所示，车辆1、车辆2和车辆3是一个移动车辆编队，该移动车辆编队中的车辆需要保持持续的业务通信。编队车辆在建立承载后，会先后向服务器(比如V2X server)发送编队通信请求。服务器根据收到的编队通信请求将车辆1、车辆2和车辆3进行编队。服务器通过NEF向控制面网关(比如图7中的AMF/SMF)发送编队车辆信息(即上述注册信息)。控制面网关根据编队车辆信息生成转发路由表，并下发给用户面网关(包括本地UPF1和本地UPF2)。零散车辆之间不需要进行编队，也不会向服务器发送编队请求。示例性地，在图7中，当车辆2从本地UPF1移 动到本地UPF2，控制面网关需要更新本地UPF1到车辆2上的路由，以及本地UPF2到车辆1上的路由，保证车辆1与车辆2通过本地UPF1和本地UPF2之间的隧道进行通信，而不需要对零散车辆进行路由更新。
因此，如果编队车辆中的某个车辆发生跨UPF移动，那么控制面网关仅针对编队车辆进行用户表项更新，从而降低了更新用户表项的数量，减少了网络动荡，有助于提高网络性能。
图8示出了根据本申请实施例的一个具体流程的交互图。图8中的实线表示各个设备间的交互步骤，虚线表示UE1与UE2之间的报文转发路径。如图8所示，该流程包括：
801，UE1建立分组数据网络(Packet Data Network，PDN)连接到锚点UPF，边缘用户面建立在本地UPF1。
802，UE2建立PDN连接到锚点UPF，边缘用户面建立在本地UPF1。
803，UE1注册到V2X服务器(或控制器controller)，加入编队。
804，UE2注册到V2X服务器(或控制器controller)，加入编队。
这里，UE1和UE2注册到应用服务器(Application Server，AS)。其中，UE1和UE2是一个编队的车辆。UE1与UE2之间需要进行报文转发。
对应地，V2X服务器可获取到UE1与UE2的编队信息。
805，V2X服务器将UE1和UE2的编队信息(或注册信息)发送给SMF。
可选地，该编队信息也可以预先配置给SMF。
对应地，SMF获取到UE1和UE2的编队信息。进一步地，SMF根据UE1和UE2的编队信息生成转发路由表。
806，SMF向本地UPF1下发用户级的转发路由表。
对应地，本地UPF1可以根据该转发路由表确定UE1和UE2的报文转发路径。
807，UE1到UE2的报文转发路径为：UE1-RAN1-本地UPF1-RAN1-UE2。
808，UE2发生切换。UE2从RAN1切换到RAN2，对应的UPF从本地UPF1切换到本地UPF2。
此时，如果系统支持双链路场景，则UE1与UE2的报文转发可以通过以下路径实现转发：(1)原链路：UE1-RAN1-本地UPF1-RAN1-UE2；(2)新链路：UE1-RAN1-本地UPF1-RAN2-UE2。这里的新链路是指UE2发生切换后还未优化的链路。可选地，UE1与UE2之间的报文可以是V2V报文。
809，RAN2向AMF发送路径切换请求(path switch request)。
810，AMF向SMF发起创建会话请求(create session request)。其中，步骤810中的创建会话请求是AMF发送给SMF的。
811，SMF可以根据算法向本地UPF2发送创建会话请求。其中，步骤811中的创建会话请求是SMF发送给本地UPF2的。
812，本地UPF2向SMF回复创建会话响应(create session response)。这里的“创建会话响应”对应于步骤811中的“创建会话请求”。
813，SMF向本地UPF1发送创建UPF间隧道请求(GTP tunnel create request)。
其中，步骤813中的创建UPF间隧道请求用于请求创建本地UPF1与本地UPF2之间的隧道，比如GTP tunnel。
814，本地UPF1向SMF回复创建UPF间隧道响应。
815，SMF向本地UPF2发送创建UPF间隧道请求。其中，步骤815中的创建UPF间隧道请求与步骤813中的“创建UPF间隧道请求”作用相同，都是用于请求创建本地UPF1与本地UPF2之间的隧道，比如GTP tunnel。
816，本地UPF2向SMF回复创建UPF间隧道响应。
这里，通过上述步骤813-816，建立了本地UPF1与本地UPF2之间的隧道。
817，SMF向锚点UPF发送会话修改请求(session modify request)。其中，步骤817中的会话修改请求是SMF发送给锚点UPF的。
818，锚点UPF向SMF回复会话修改响应(session modify response)。这里的“会话修改响应”对应于步骤817中的“会话修改请求”。
这里，当UE2发生切换后，SMF需要对转发路由表进行更新，并将更新后的转发路由表下发给本地UPF1和本地UPF2。
819，SMF向本地UPF2发送更新用户级转发路由请求(forward routing request)。
820，本地UPF2向SMF回复用户级转发路由响应。步骤820中的用户级转发路由响应用于本地UPF2响应步骤819中的更新用户级转发路由请求。
821，SMF向本地UPF1发送更新用户级转发路由请求(forward routing request)。
822，本地UPF1向SMF回复用户级转发路由响应。步骤822中的用户级转发路由响应用于UPF1响应步骤821中的更新用户级转发路由请求。
这里，本地UPF1可以根据更新后的转发路由表确定出UE1与UE2的转发路径。对于UE1到UE2，报文转发路径为：UE1-RAN1-本地UPF1-本地UPF2-RAN2-UE2。这里，对于UE2到UE1，报文转发路径还未与UE1到UE2的路径统一，UE2到UE1的报文转发路径为：UE2-RAN2-本地UPF1-RAN1-UE1。
823，SMF向AMF回复创建会话响应(create session response)。其中，步骤823中的创建会话响应用于响应步骤810中的创建会话请求。
824，AMF向RAN2回复路径切换请求响应。
此时，UE2到UE1的报文转发路径更新为：UE2-RAN2-本地UPF2-本地UPF1-RAN1-UE1，实现了上下行路径统一，即UE2到UE1的报文转发路径与UE1到UE2的报文转发路径是统一的。
825，RAN2向RAN1发送链路释放(path release)请求，或者，释放资源(release resource)请求。
826，SMF向UPF1发送释放会话资源(release resource)请求，或者，删除会话请求(delete session request)。
综上所述，本申请实施例的技术方案实现了路径优化，有效地降低了报文转发时延，能够满足低时延业务的需求。
需要说明的是，图8中各个术语(比如创建会话请求，创建会话响应)的含义、解释或作用可以对应于相应的发送和/或接收主体。其中，各个步骤中采用术语的名称并不对执行的步骤构成限定。可选地，术语的命名可以采用其他命名代替。
应理解，图6至图8中的例子仅仅是为了便于本领域技术人员理解本申请实施例，并非要将本申请实施例限于例示的具体场景。本领域技术人员根据图6至图8的例子，显然可以进行各种等价的修改或变化，这样的修改或变化也落入本发明实施例的范围内。
上文中结合图1至图8，详细描述了根据本申请实施例的报文转发的方法，下面将结合图9和图10，详细描述根据本申请实施例的控制面网关和用户面网关。
图9示出了根据本申请实施例的控制面网关900的示意性框图。所述控制面网关900用于执行前述控制面网关对应的方法或步骤。可选地，所述控制面网关900中各个模块可以通过软件来实现。所述控制面网关900可以安装在通用计算机设备中。如图9所示，所述控制面网关900包括：
获取模块910，用于获取第一用户设备UE的注册信息和第二用户设备UE的注册信息，所述第一UE的注册信息包括与所述第一UE进行通信的UE标识，所述第二UE的注册信息包括与所述第二UE进行通信的UE标识；
处理模块920，用于根据所述第一UE的注册信息和所述第二UE的注册信息，生成所述第一UE和所述第二UE的转发路由表，所述转发路由表包括所述第一UE和所述第二UE进行报文传输的路径所需的信息；
收发模块930，用于将所述转发路由表下发给第一用户面网关和第二用户面网关，所述转发路由表用于用户面网关确定所述第一UE和所述第二UE之间的报文转发路径，其中，所述第一用户面网关是所述第一UE所在的网关，所述第二用户面网关是所述第二UE所在的网关。
可选地，所述第一用户面网关与所述第二用户面网关相同，其中，
所述处理模块920具体用于：
根据所述注册信息和所述第一用户面网关的标识，生成所述转发路由表，所述转发路由表包括所述第一用户面网关到达所述第一UE的路由，以及所述第一用户面网关到达所述第二UE的路由，其中，所述第一UE和所述第二UE的报文转发是通过所述第一用户面网关直接发送的。
可选地，所述第一用户面网关与所述第二用户面网关是不同的用户面网关，其中，
所述处理模块920具体用于：
所述控制面网关根据所述注册信息、所述第一用户面网关的标识和所述第二用户面网关的标识，生成所述转发路由表，所述转发路由表包括所述第一用户面网关经过所述第二用户面网关到达所述第二UE的路由，以及所述第二用户面网关经过所述第一用户面网关到达所述第一UE的路由。
可选地，所述处理模块920还用于：对所述注册信息进行更新，得到所述更新后的注册信息；以及用于根据所述更新后的注册信息，更新所述转发路由表。
可选地，所述收发模块930还用于：
向所述第一用户面网关和所述第二用户面网关发送创建隧道请求，所述创建隧道请求用于请求创建所述第一用户面网关和所述第二用户面网关之间的隧道；
以及，接收所述第一用户面网关发送的第一创建隧道请求响应，所述第一创建隧道请求响应用于所述第一用户面网关响应所述创建隧道请求；
以及，接收所述第二用户面网关发送的第二创建隧道请求响应，所述第二创建隧道请求响应用于所述第二用户面网关响应所述创建隧道请求。
应理解，根据本申请实施例的控制面网关900可对应于前述方法实施例的报文转发中的控制面网关，并且控制面网关900中的各个模块的上述和其它管理操作和/或功能分别为了实 现前述各个方法的相应步骤，因此也可以实现前述方法实施例中的有益效果，为了简洁，在此不再赘述。
还应理解，本申请实施例中的处理模块920可以由处理器实现，收发模块930和获取模块910可以由收发器实现。
图10示出了根据本申请实施例的用户面网关1000的示意性框图。所述用户面网关1000用于执行前述第一用户面网关对应的方法或步骤。可选地，所述用户面网关1000中各个模块可以通过软件来实现。所述用户面网关1000可以安装在通用计算机设备中。如图10所示，所述用户面网关1000包括：
收发模块1010，用于接收控制面网关发送的转发路由表，所述转发路由表包括第一用户设备UE和第二用户设备UE进行报文传输的路径所需的信息；
处理模块1020，用于根据所述转发路由表确定所述第一UE和所述第二UE之间的报文转发路径，其中，所述第一用户面网关是所述第一UE所在的网关，第二用户面网关是所述第二UE所在的网关。
可选地，所述第一用户面网关与所述第二用户面网关相同，其中，所述转发路由表包括所述第一用户面网关到达所述第一UE的路由，以及所述第一用户面网关到达所述第二UE的路由；
所述处理模块1020具体用于：
根据所述转发路由表，确定所述第一UE和所述第二UE的报文转发通过所述第一用户面网关直接发送。
可选地，所述第一用户面网关与所述第二用户面网关是不同的用户面网关，所述转发路由表包括所述第一用户面网关经过所述第二用户面网关到达所述第二UE的路由，以及所述第二用户面网关经过所述第一用户面网关到达所述第一UE的路由；
其中，所述处理模块1020具体用于：
根据所述转发路由表，确定所述第一UE和所述第二UE的报文转发通过所述第一用户面网关和所述第二用户面网关之间的隧道发送。
可选地，所述收发模块1010还用于：
接收所述控制面网关发送的创建隧道请求，所述第一创建隧道请求用于请求创建所述第一用户面网关和所述第二用户面网关的隧道；
以及，向所述控制面网关发送第一创建隧道请求响应，所述第一创建隧道请求响应用于所述第一用户面网关响应所述创建隧道请求。
应理解，根据本申请实施例的用户面网关1000可对应于前述方法实施例的报文转发中的第一用户面网关，并且用户面网关1000中的各个模块的上述和其它管理操作和/或功能分别为了实现前述各个方法的相应步骤，因此也可以实现前述方法实施例中的有益效果，为了简洁，在此不再赘述。
还应理解，本申请实施例中的处理模块1020可以由处理器实现，收发模块1010可以由收发器实现。
图11示出了根据本申请实施例的用户面网关1100的示意性框图。所述用户面网关1100用于执行前述第二用户面网关对应的方法或步骤。可选地，所述用户面网关1100中各个模块可以通过软件来实现。所述用户面网关1100可以安装在通用计算机设备中。如图11所示， 所述用户面网关1100包括：
收发模块1110，用于接收控制面网关发送的转发路由表，所述转发路由表包括第一用户面网关经过所述第二用户面网关到达第二用户设备UE的路由，以及所述第二用户面网关经过所述第一用户面网关到达第一UE的路由，其中，所述第一用户面网关是所述第一UE所在的用户面网关，所述第二用户面网关是所述第二UE所在的用户面网关，所述第一用户面网关与所述第二用户面网关是不同的用户面网关；
处理模块1120，用于根据所述转发路由表确定所述第一UE和所述第二UE之间的报文转发路径。
可选地，所述收发模块1110还用于：
接收所述控制面网关发送的创建隧道请求，所述创建隧道请求用于请求创建所述第一用户面网关和所述第二用户面网关之间的隧道；
以及，向所述控制面网关发送第二创建隧道请求响应，所述第二创建隧道请求响应用于所述第二用户面网关响应所述创建隧道请求。
应理解，根据本申请实施例的用户面网关1100可对应于前述方法实施例的报文转发中的第二用户面网关，并且用户面网关1100中的各个模块的上述和其它管理操作和/或功能分别为了实现前述各个方法的相应步骤，因此也可以实现前述方法实施例中的有益效果，为了简洁，在此不再赘述。
还应理解，本申请实施例中的处理模块1120可以由处理器实现，收发模块1110可以由收发器实现。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技 术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器ROM、随机存取存储器RAM、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (19)

  1. 一种用于报文转发的方法，其特征在于，包括：
    控制面网关获取第一用户设备UE的注册信息和第二用户设备UE的注册信息，所述第一UE的注册信息包括与所述第一UE进行通信的UE标识，所述第二UE的注册信息包括与所述第二UE进行通信的UE标识；
    所述控制面网关根据所述第一UE的注册信息和所述第二UE的注册信息，生成所述第一UE和所述第二UE的转发路由表，所述转发路由表包括所述第一UE和所述第二UE进行报文传输的路径所需的信息；
    所述控制面网关将所述转发路由表下发给第一用户面网关和第二用户面网关，所述转发路由表用于用户面网关确定所述第一UE和所述第二UE之间的报文转发路径，其中，所述第一用户面网关是所述第一UE所在的网关，所述第二用户面网关是所述第二UE所在的网关。
  2. 根据权利要求1所述的方法，其特征在于，所述第一用户面网关与所述第二用户面网关相同，其中，
    所述生成所述第一UE和所述第二UE的转发路由表，包括：
    所述控制面网关根据所述注册信息和所述第一用户面网关的标识，生成所述转发路由表，所述转发路由表包括所述第一用户面网关到达所述第一UE的路由，以及所述第一用户面网关到达所述第二UE的路由，其中，所述第一UE和所述第二UE的报文转发是通过所述第一用户面网关直接发送的。
  3. 根据权利要求1所述的方法，其特征在于，所述第一用户面网关与所述第二用户面网关是不同的用户面网关，其中，
    所述生成所述第一UE和所述第二UE的转发路由表，包括：
    所述控制面网关根据所述注册信息、所述第一用户面网关的标识和所述第二用户面网关的标识，生成所述转发路由表，所述转发路由表包括所述第一用户面网关经过所述第二用户面网关到达所述第二UE的路由，以及所述第二用户面网关经过所述第一用户面网关到达所述第一UE的路由。
  4. 根据权利要求3所述的方法，其特征在于，所述方法还包括：
    所述控制面网关对所述注册信息进行更新，得到所述更新后的注册信息；
    所述控制面网关根据所述更新后的注册信息，更新所述转发路由表。
  5. 根据权利要求3或4所述的方法，其特征在于，在所述控制面网关向所述第一用户面网关和所述第二用户面网关下发所述转发路由表前，所述方法还包括：
    所述控制面网关向所述第一用户面网关和所述第二用户面网关发送创建隧道请求，所述创建隧道请求用于请求创建所述第一用户面网关和所述第二用户面网关之间的隧道；
    所述控制面网关接收所述第一用户面网关发送的第一创建隧道请求响应，所述第一创建隧道请求响应用于所述第一用户面网关响应所述创建隧道请求；
    所述控制面网关接收所述第二用户面网关发送的第二创建隧道请求响应，所述第二创建隧道请求响应用于所述第二用户面网关响应所述创建隧道请求。
  6. 一种用于报文转发的方法，其特征在于，包括：
    第一用户面网关接收控制面网关发送的转发路由表，所述转发路由表包括第一用户设备UE和第二UE进行报文传输的路径所需的信息；
    所述第一用户面网关根据所述转发路由表确定所述第一UE和所述第二UE之间的报文转发路径，其中，所述第一用户面网关是所述第一UE所在的网关，第二用户面网关是所述第二UE所在的网关。
  7. 根据权利要求6所述的方法，其特征在于，所述第一用户面网关与所述第二用户面网关相同，其中，所述转发路由表包括所述第一用户面网关到达所述第一UE的路由，以及所述第一用户面网关到达所述第二UE的路由；
    所述第一用户面网关根据所述转发路由表确定所述第一UE和所述第二UE的报文转发路径，包括：
    所述第一用户面网关根据所述转发路由表，确定所述第一UE和所述第二UE的报文转发通过所述第一用户面网关直接发送。
  8. 根据权利要求6所述的方法，其特征在于，所述第一用户面网关与所述第二用户面网关是不同用户面网关，所述转发路由表包括所述第一用户面网关经过所述第二用户面网关到达所述第二UE的路由，以及所述第二用户面网关经过所述第一用户面网关到达所述第一UE的路由；
    其中，所述第一用户面网关根据所述转发路由表确定所述第一UE和所述第二UE的报文转发路径，包括：
    所述第一用户面网关根据所述转发路由表，确定所述第一UE和所述第二UE的报文转发通过所述第一用户面网关和所述第二用户面网关之间的隧道发送。
  9. 根据权利要求8所述的方法，其特征在于，所述方法还包括：
    所述第一用户面网关接收所述控制面网关发送的创建隧道请求，所述第一创建隧道请求用于请求创建所述第一用户面网关和所述第二用户面网关的隧道；
    所述第一用户面网关向所述控制面网关发送第一创建隧道请求响应，所述第一创建隧道请求响应用于所述第一用户面网关响应所述创建隧道请求。
  10. 一种控制面网关，其特征在于，包括：
    获取模块，用于获取第一用户设备UE的注册信息和第二用户设备UE的注册信息，所述第一UE的注册信息包括与所述第一UE进行通信的UE标识，所述第二UE的注册信息包括与所述第二UE进行通信的UE标识；
    处理模块，用于根据所述第一UE的注册信息和所述第二UE的注册信息，生成所述第一UE和所述第二UE的转发路由表，所述转发路由表包括所述第一UE和所述第二UE进行报文传输的路径所需的信息；
    收发模块，用于将所述转发路由表下发给第一用户面网关和第二用户面网关，所述转发路由表用于用户面网关确定所述第一UE和所述第二UE之间的报文转发路径，其中，所述第一用户面网关是第一UE所在的网关，所述第二用户面网关是所述第二UE所在的网关。
  11. 根据权利要求10所述的控制面网关，其特征在于，所述第一用户面网关与所述第二用户面网关相同，其中，
    所述处理模块具体用于：
    根据所述注册信息和所述第一用户面网关的标识，生成所述转发路由表，所述转发路由表包括所述第一用户面网关到达所述第一UE的路由，以及所述第一用户面网关到达所述第二UE的路由，其中，所述第一UE和所述第二UE的报文转发是通过所述第一用户面网关直接发送的。
  12. 根据权利要求10所述的控制面网关，其特征在于，所述第一用户面网关与所述第二用户面网关是不同的用户面网关，其中，
    所述处理模块具体用于：
    所述控制面网关根据所述注册信息、所述第一用户面网关的标识和所述第二用户面网关的标识，生成所述转发路由表，所述转发路由表包括所述第一用户面网关经过所述第二用户面网关到达所述第二UE的路由，以及所述第二用户面网关经过所述第一用户面网关到达所述第一UE的路由。
  13. 根据权利要求12所述的控制面网关，其特征在于，所述处理模块还用于：对所述注册信息进行更新，得到所述更新后的注册信息；以及用于根据所述更新后的注册信息，更新所述转发路由表。
  14. 根据权利要求12或13所述的控制面网关，其特征在于，所述收发模块还用于：
    向所述第一用户面网关和所述第二用户面网关发送创建隧道请求，所述创建隧道请求用于请求创建所述第一用户面网关和所述第二用户面网关之间的隧道；
    以及，接收所述第一用户面网关发送的第一创建隧道请求响应，所述第一创建隧道请求响应用于所述第一用户面网关响应所述创建隧道请求；
    以及，接收所述第二用户面网关发送的第二创建隧道请求响应，所述第二创建隧道请求响应用于所述第二用户面网关响应所述创建隧道请求。
  15. 一种用户面网关，其特征在于，所述用户面网关为第一用户面网关，所述用户面网关包括：
    收发模块，用于接收控制面网关发送的转发路由表，所述转发路由表包括第一用户设备UE和第二用户设备UE进行报文传输的路径所需的信息；
    处理模块，用于根据所述转发路由表确定所述第一UE和所述第二UE之间的报文转发路径，其中，所述第一用户面网关是所述第一UE所在的网关，第二用户面网关是所述第二UE所在的网关。
  16. 根据权利要求15所述的用户面网关，其特征在于，所述第一用户面网关与所述第二用户面网关相同，其中，所述转发路由表包括所述第一用户面网关到达所述第一UE的路由，以及所述第一用户面网关到达所述第二UE的路由；
    所述处理模块具体用于：
    根据所述转发路由表，确定所述第一UE和所述第二UE的报文转发通过所述第一用户面网关直接发送。
  17. 根据权利要求15所述的用户面网关，其特征在于，所述第一用户面网关与所述第二用户面网关是不同的用户面网关，所述转发路由表包括所述第一用户面网关经过所述第二用户面网关到达所述第二UE的路由，以及所述第二用户面网关经过所述第一用户面网关到达所述第一UE的路由；
    其中，所述处理模块具体用于：
    根据所述转发路由表，确定所述第一UE和所述第二UE的报文转发通过所述第一用户面网关和所述第二用户面网关之间的隧道发送。
  18. 根据权利要求17所述的用户面网关，其特征在于，所述收发模块还用于：
    接收所述控制面网关发送的创建隧道请求，所述第一创建隧道请求用于请求创建所述第一用户面网关和所述第二用户面网关之间的隧道；
    以及，向所述控制面网关发送第一创建隧道请求响应，所述第一创建隧道请求响应用于所述第一用户面网关响应所述创建隧道请求。
  19. 一种计算机可读存储介质，包括计算机程序，当其在计算机上运行时，使得所述计算机执行如权利要求1至9中任一项所述的方法。
PCT/CN2018/074027 2017-11-28 2018-01-24 报文转发的方法、控制面网关和用户面网关 WO2019104858A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
JP2018548203A JP7065034B2 (ja) 2017-11-28 2018-01-24 メッセージ転送方法、制御プレーンゲートウェイおよびユーザプレーンゲートウェイ

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201711219039.2A CN109842558B (zh) 2017-11-28 2017-11-28 报文转发的方法、控制面网关和用户面网关
CN201711219039.2 2017-11-28

Publications (1)

Publication Number Publication Date
WO2019104858A1 true WO2019104858A1 (zh) 2019-06-06

Family

ID=66664271

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/074027 WO2019104858A1 (zh) 2017-11-28 2018-01-24 报文转发的方法、控制面网关和用户面网关

Country Status (3)

Country Link
JP (1) JP7065034B2 (zh)
CN (3) CN112187643B (zh)
WO (1) WO2019104858A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022033461A1 (zh) * 2020-08-14 2022-02-17 华为技术有限公司 一种通信方法及相关设备
CN114765591A (zh) * 2020-12-31 2022-07-19 大唐移动通信设备有限公司 一种数据传输方法、装置及存储介质

Families Citing this family (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114884612A (zh) 2019-06-24 2022-08-09 华为技术有限公司 用于传输业务报文的方法和装置
CN112423340B (zh) * 2019-08-21 2022-08-09 华为技术有限公司 一种用户面信息上报方法及装置
CN111432439B (zh) * 2020-03-27 2021-08-17 广州爱浦路网络技术有限公司 一种upf数据面扩展及其系统
EP4274174A1 (en) * 2021-01-29 2023-11-08 Huawei Technologies Co., Ltd. Communication method, system, apparatus, device and computer readable storage medium
CN113316098B (zh) * 2021-04-20 2022-10-21 新华三技术有限公司 一种建立业务通道、公网对讲的方法和公网对讲设备
CN113873502B (zh) * 2021-09-29 2024-02-23 中国电信股份有限公司 Ip地址管理方法、nef实体和通信系统
CN115002016B (zh) * 2022-05-17 2023-08-22 阿里云计算有限公司 报文处理系统、方法、设备和存储介质
CN115022936B (zh) * 2022-05-30 2023-09-08 中国电信股份有限公司 一种数据转发方法及相关设备
CN117955813A (zh) * 2022-10-31 2024-04-30 华为技术有限公司 一种报文传输方法、装置和系统
CN116192223B (zh) * 2023-04-25 2023-09-22 阿里巴巴达摩院(杭州)科技有限公司 专网信息的转发方法、车辆控制方法、装置及设备

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103139075A (zh) * 2013-03-13 2013-06-05 杭州华三通信技术有限公司 一种报文传输方法和设备
CN105704042A (zh) * 2015-12-31 2016-06-22 华为技术有限公司 报文处理方法、bng及bng集群系统

Family Cites Families (25)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2003069609A (ja) * 2001-08-23 2003-03-07 Fujitsu Ltd 仮想私設網サービスを提供するシステム
CN1996913A (zh) * 2005-12-31 2007-07-11 华为技术有限公司 一种控制与承载分离的网络互连系统及方法
CN101159905B (zh) * 2007-11-07 2010-04-21 华为技术有限公司 基站控制器内实现本地交换方法、核心网设备及网络系统
CN101540992B (zh) * 2009-05-04 2011-04-20 华为技术有限公司 报文转发的方法、基站和系统
CN101998666B (zh) * 2009-08-12 2014-09-10 中兴通讯股份有限公司 一种本地呼叫本地交换的实现方法
CN101778356A (zh) * 2009-12-30 2010-07-14 华为技术有限公司 短信发送方法、短信业务装置和基站子系统
ES2706416T3 (es) * 2011-01-13 2019-03-28 Nec Corp Sistema de red y método de enrutamiento
CN103477665B (zh) * 2011-04-12 2018-06-29 瑞典爱立信有限公司 在移动通信网络中发送用户面业务的方法和装置
CN102869116B (zh) * 2011-07-05 2015-07-08 华为终端有限公司 一种本地网络和实现本地网关和家庭基站建立连接的方法
CN102355655A (zh) * 2011-07-14 2012-02-15 中国联合网络通信集团有限公司 业务数据处理方法、无线网络控制器和接入网系统
PT2854475T (pt) * 2012-06-29 2019-02-04 Huawei Tech Co Ltd Sistema de gateway, dispositivo e método de comunicação
US9210615B2 (en) * 2012-09-17 2015-12-08 Brocade Communications Systems, Inc. Method and system for elastic and resilient 3G/4G mobile packet networking for subscriber data flow using virtualized switching and forwarding
US20150304215A1 (en) * 2012-12-28 2015-10-22 Hitachi, Ltd. Packet relay apparatus, packet transfer method, and communication system
CN104137603B (zh) * 2012-12-28 2018-01-19 华为技术有限公司 协作通信方法、装置及基站
CN105122888B (zh) * 2013-10-21 2019-05-24 华为技术有限公司 基站间的路由方法、服务网关和基站
CN105009521B (zh) * 2013-12-23 2018-10-19 华为技术有限公司 消息处理方法和网关
CN104869659B (zh) * 2014-02-20 2018-07-03 电信科学技术研究院 一种路径建立方法、设备及系统、核心网设备
CN105490945A (zh) * 2014-09-15 2016-04-13 上海贝尔股份有限公司 一种用于在控制面中控制转发数据的方法和装置
WO2016126238A1 (en) * 2015-02-03 2016-08-11 Nokia Solutions And Networks Oy Improvements in dual connectivity for different access networks
EP3337105B1 (en) * 2015-09-30 2021-04-07 Huawei Technologies Co., Ltd. Processing method and apparatus for service flow processing policy
WO2017054178A1 (zh) * 2015-09-30 2017-04-06 华为技术有限公司 保持业务连续性的方法、控制面网关和移动管理网元
CN111953514A (zh) * 2015-10-30 2020-11-17 华为技术有限公司 一种网关配置方法和网关设备
CN107211271B (zh) * 2015-12-31 2020-02-14 华为技术有限公司 用户设备接入网络的方法、核心网实体、基站及第一ue
US10172044B2 (en) * 2016-03-24 2019-01-01 Motorola Mobility Llc Method and device for data communication over a peer-to-peer connection in a mobile communication network
CN106101008B (zh) * 2016-05-31 2019-08-06 新华三技术有限公司 一种报文的传输方法和装置

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103139075A (zh) * 2013-03-13 2013-06-05 杭州华三通信技术有限公司 一种报文传输方法和设备
CN105704042A (zh) * 2015-12-31 2016-06-22 华为技术有限公司 报文处理方法、bng及bng集群系统

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022033461A1 (zh) * 2020-08-14 2022-02-17 华为技术有限公司 一种通信方法及相关设备
CN114765591A (zh) * 2020-12-31 2022-07-19 大唐移动通信设备有限公司 一种数据传输方法、装置及存储介质
CN114765591B (zh) * 2020-12-31 2023-07-18 大唐移动通信设备有限公司 一种数据传输方法、装置及存储介质

Also Published As

Publication number Publication date
JP7065034B2 (ja) 2022-05-11
CN112187650A (zh) 2021-01-05
CN112187643B (zh) 2021-12-10
JP2021504983A (ja) 2021-02-15
CN109842558A (zh) 2019-06-04
CN112187643A (zh) 2021-01-05
CN109842558B (zh) 2020-09-11

Similar Documents

Publication Publication Date Title
WO2019104858A1 (zh) 报文转发的方法、控制面网关和用户面网关
EP3611904B1 (en) Data session management
JP5204310B2 (ja) Ｌｔｅにおけるセルフバックホール
WO2019214729A1 (zh) 数据处理的方法和设备
TW201735716A (zh) 數據傳輸的方法、基站及終端設備
WO2019105378A1 (zh) 通信方法和通信装置
US10813036B2 (en) Anchor gateway switching method, apparatus, and system
WO2021018073A1 (zh) 传输数据的方法、通信装置和通信系统
WO2021031022A1 (zh) 链路切换的方法和通信设备
WO2018127018A1 (zh) 多链接通信方法、设备和终端
WO2017166139A1 (zh) 中继传输的方法和装置
WO2020015727A1 (zh) 路径选择的方法、终端设备和网络设备
US20190223061A1 (en) Bearer establishment method and apparatus
WO2018170747A1 (zh) 一种通信方法及装置
WO2018068216A1 (zh) 会话管理方法及网元
WO2021062727A1 (zh) 一种重定向方法及装置、终端设备、网络设备
TW202013936A (zh) 無線通訊方法和通訊設備
WO2020223907A1 (zh) 一种信息传输方法及装置、网络设备
WO2020252795A1 (zh) 无线通信的方法、终端设备，接入网设备和核心网设备
WO2022082690A1 (zh) 群组切换的方法、装置和系统
CN112291845B (zh) 一种寻呼方法及通信装置
WO2020199215A1 (zh) 传输数据的方法、终端设备和核心网设备
WO2022126412A1 (zh) 一种重置配置方法及装置、终端设备
WO2021208817A1 (zh) 网络资源控制的方法及设备
WO2022222748A1 (zh) 中继通信方法和装置

Legal Events

Date Code Title Description
ENP Entry into the national phase

Ref document number: 2018548203

Country of ref document: JP

Kind code of ref document: A

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

Ref document number: 18884810

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

Country of ref document: EP

Kind code of ref document: A1