WO2023001010A1 - Procédé et dispositif de communication - Google Patents

Procédé et dispositif de communication Download PDF

Info

Publication number
WO2023001010A1
WO2023001010A1 PCT/CN2022/104908 CN2022104908W WO2023001010A1 WO 2023001010 A1 WO2023001010 A1 WO 2023001010A1 CN 2022104908 W CN2022104908 W CN 2022104908W WO 2023001010 A1 WO2023001010 A1 WO 2023001010A1
Authority
WO
WIPO (PCT)
Prior art keywords
access gateway
plane data
address
terminal
teid
Prior art date
Application number
PCT/CN2022/104908
Other languages
English (en)
Chinese (zh)
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
Priority claimed from CN202111094796.8A external-priority patent/CN115701089A/zh
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2023001010A1 publication Critical patent/WO2023001010A1/fr

Links

Images

Classifications

    • 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

Definitions

  • the present application relates to the technical field of communication, and in particular to a communication method and device.
  • the fifth generation core network (5th generation Core, 5GC) supports access to the third generation partnership project (3rd generation partnership project, 3GPP) network and non-3GPP (non-3GPP) network access.
  • the non-3GPP access technology includes trusted non-3GPP (trusted non-3GPP) access, untrusted non-3GPP (untrusted non-3GPP) access and wired access.
  • the terminal can access the core network by establishing a connection with the non-3GPP access gateway.
  • the access gateway can be a trusted non-3GPP access gateway function (trusted non-3GPP gateway function, TNGF); for untrusted non-3GPP access, the access gateway can be non -3GPP conversion function (non-3GPP interworking function, N3IWF); for wired access, the access gateway may be a wired access gateway function (wireline-access gateway function, W-AGF).
  • trusted non-3GPP gateway function trusted non-3GPP gateway function
  • TNGF trusted non-3GPP gateway function
  • N3IWF non-3GPP interworking function
  • W-AGF wired access gateway function
  • the access gateway receives uplink information from the terminal, and the uplink information may be control plane data or user plane data. If the uplink information is control plane data, the access gateway can send the uplink information to the access and mobility management function (AMF) network element; if the uplink information is user plane data, the access gateway The uplink information needs to be sent to a user plane function (user plane function, UPF) network element. How the access gateway distinguishes whether the uplink information from the terminal is control plane data or user plane data is a problem that needs to be solved.
  • AMF access and mobility management function
  • the purpose of the present application is to provide a communication method and device, the method is used to enable an access gateway to distinguish whether uplink information is control plane data or user plane data.
  • the present application provides a communication method, and the method may be executed by an access gateway or components of the access gateway.
  • the access gateway receives a first data packet from the terminal, the first data packet includes a first IP header, a first GTP-U header and a first payload, and the first IP header includes the access The IP address of the gateway, the first GTP-U header includes the TEID of the access gateway; and, the access gateway according to at least one of the IP address of the access gateway and the TEID of the access gateway , determining that the first payload is control plane data or user plane data.
  • the first payload is encapsulated with a first GTP-U header
  • the first GTP-U header is encapsulated with a first UDP header
  • the first UDP header is encapsulated with a first IP header.
  • control plane data may include control plane messages, such as NAS messages, or other control plane messages except the NAS messages.
  • User plane data may include remote control service data and the like.
  • the access gateway can distinguish the uplink load according to at least one of the TEID of the access gateway included in the GTP-U header encapsulated outside the uplink load and the IP address of the access gateway included in the IP header. It is control plane data or user plane data, and a GTP-U tunnel is established between the access gateway and the terminal. Compared with the IPsec tunnel, it can simplify the process for the terminal to access the core network.
  • the IPsec-based tunnel encapsulation method needs to encapsulate a double-layer IP header outside the user plane data
  • the GTP-U tunnel-based encapsulation method needs to encapsulate a layer of IP header outside the user plane data.
  • the packet header length of the U-tunnel encapsulation method is smaller than that based on the IPsec tunnel encapsulation method, which can reduce the waste of transmission resources, time extension, and high power consumption of equipment caused by too long packet headers.
  • the access gateway determines that the first load is control plane data or user plane data according to at least one of the access gateway's IP address and the access gateway's TEID , which can include one or more of the following:
  • the access gateway determines that the first payload is the control plane data.
  • the access gateway determines that the first payload is the user plane data.
  • the access gateway determines that the first payload is the control plane data.
  • the access gateway determines that the first payload is the user plane data.
  • the access gateway determines that the first load is the control plane data.
  • the access gateway determines that the first load is the user plane data.
  • the access gateway can perform this by combining the TEID in the GTP-U header encapsulated outside the payload with the TEID allocated by the access gateway for the transmission of control plane data and the TEID allocated for transmission of user plane data, and/or, Compare the IP address of the access gateway in the IP header with the IP address allocated by the access gateway for transmitting control plane data and the IP address allocated for transmitting user plane data, so as to flexibly determine whether the load is control plane data or user plane data data.
  • the first GTP-U packet header further includes a message type field
  • the first data packet further includes a first message
  • the first message includes the first payload; in the first When a payload is the control plane data, the message type field is used to indicate the message type of the first message.
  • the GTP-U header can be encapsulated outside the payload, and can also be used as a parameter of the first message, that is, the first message is encapsulated outside the payload, and the GTP-U header is then encapsulated outside the first message.
  • the method may further include: the access gateway sending a first request message to the terminal, the first request message including The TEID of the access gateway and the IP address of the access gateway, wherein the TEID of the access gateway is the TEID allocated by the access gateway for transmitting the control plane data; and, the access gateway Receive a first response message from the terminal, where the first response message includes the TEID of the terminal, where the TEID of the terminal is the TEID allocated by the terminal for transmitting the control plane data.
  • the IP address of the access gateway is an IP address allocated by the access gateway for transmitting the control plane data.
  • the interaction between the access gateway and the terminal can send the TEID and IP address allocated for the transmission control plane data to the terminal, so that it can be used later to identify whether the uplink load is control plane data, and to obtain the terminal as the transmission control data.
  • the TEID assigned to the plane data so that the control plane data can be sent to the terminal through the GTP-U tunnel later.
  • the method may further include: the access gateway sending a second request message to the terminal, the second request message including a protocol data unit (PDU) session identifier and the access The TEID of the gateway, wherein the TEID of the access gateway is the TEID allocated by the access gateway for the user plane data of the PDU session; the access gateway receives the second response message from the terminal, and the The second response message includes the TEID of the terminal, where the TEID of the terminal is the TEID allocated by the terminal to the user plane data of the PDU session.
  • PDU protocol data unit
  • the access gateway interacts with the terminal, and can send the TEID allocated for the user plane data of the transmission PDU session to the terminal, so that it can be subsequently used to identify whether the uplink load is the user plane data of the PDU session, and obtain the terminal
  • the second request message further includes the IP address of the access gateway, and the IP address of the access gateway is allocated by the access gateway for the user plane data of the PDU session IP address.
  • the IP address allocated by the access gateway to the user plane data of the PDU session may be the same as or different from the IP address allocated by the access gateway to the control plane data.
  • the access gateway can also allocate an IP address to the user plane data of the PDU session, so as to subsequently identify whether the uplink load is the user plane data of the PDU session.
  • the method may further include: the access gateway receiving an indication from an Access and Mobility Management Function (AMF) network element information, where the indication information is used to indicate that an Internet Security Protocol (IPsec) tunnel does not need to be established between the access gateway and the terminal.
  • AMF Access and Mobility Management Function
  • the access gateway can determine not to establish an IPsec tunnel with the terminal according to the instruction information of the AMF, so as to simplify the process for the terminal to access the core network.
  • the first IP packet header further includes the IP address of the terminal
  • the method may further include: the access gateway according to the IP address of the terminal and the IP address of the terminal The corresponding relationship with the identification information of the terminal determines the identification information of the terminal; the access gateway determines the context information of the terminal according to the identification information of the terminal.
  • the access gateway can determine which terminal the uplink load comes from according to the IP address, as well as the context information of the terminal, so as to determine the control plane network element that establishes the N2 connection with the terminal or the user that establishes the N3 connection with the terminal network element.
  • the method may further include: the access gateway receiving a second message from the access node, where the second message includes the difference between the IP address of the terminal and the identification information of the terminal. Correspondence between.
  • the method may further include: the access gateway sending a second data packet to the terminal, where the second data packet includes a second IP header, a second GTP-U header, and a second Two loads, the second IP header includes the IP address of the access gateway, and the second GTP-U header includes the TEID of the terminal; wherein, when the second load is the control plane data, The TEID of the terminal is the TEID allocated by the terminal for transmitting the control plane data, and/or the IP address of the access gateway is the IP address allocated by the access gateway for transmitting the control plane data; or , when the second load is the user plane data, the TEID of the terminal is the TEID allocated by the terminal for transmitting the user plane data, and/or the IP address of the access gateway is the IP address allocated by the ingress gateway for transmitting user plane data.
  • the method may further include: the access gateway sending a second data packet to the terminal, where the second data packet includes a second IP header, a second GTP-U header, and a second Two loads, the second IP header includes the IP address of the access gateway, and the second GTP-U header includes the TEID of the access gateway; wherein the second load is the control plane data,
  • the IP address of the access gateway is the IP address allocated by the access gateway for transmitting the control plane data
  • the TEID of the access gateway is the TEID allocated by the access gateway for transmitting the control plane data.
  • the access gateway can use the TEID allocated by itself for transmitting the control plane data to send the control plane data to the terminal. Further, the terminal can obtain the TEID allocated by the access gateway for transmitting control plane data, and can send the control plane data to the access gateway based on the TEID, so that the UE does not need to allocate the TEID for transmitting control plane data to the UE through an additional message, and can The signaling interaction between the access gateway and the UE is reduced, and the utilization rate of network resources is improved.
  • the present application provides a communication method, and the method may be executed by a terminal or by components of the terminal.
  • the method includes: the terminal receives a second data packet from the access gateway, the second data packet includes a second Internet Protocol (IP) packet header, a second General Packet Radio Service Tunneling Protocol-User Plane (GTP-U) A header and a second load, the second IP header includes the IP address of the access gateway, and the second GTP-U header includes the tunnel endpoint identifier (TEID) of the terminal; and, the terminal according to the At least one of the IP address of the access gateway and the TEID of the terminal determines whether the second load is control plane data or user plane data.
  • IP Internet Protocol
  • GTP-U General Packet Radio Service Tunneling Protocol-User Plane
  • TEID tunnel endpoint identifier
  • the terminal determines that the second load is control plane data or user plane data according to at least one of the IP address of the access gateway and the TEID of the terminal, which may include the following: one or more:
  • the terminal determines that the second payload is the control plane data.
  • the terminal determines that the second payload is the user plane data.
  • the terminal determines that the second payload is the control plane data.
  • the terminal determines that the second payload is the user plane data.
  • the terminal determines that the second payload is the control plane data.
  • the terminal determines that the second payload is the user plane data.
  • the second GTP-U packet header further includes a message type field
  • the second data packet further includes a third message
  • the third message includes the second payload; in the first
  • the message type field is used to indicate the message type of the third message.
  • the method before the terminal receives the second data packet from the access gateway, the method further includes: the terminal receives a first request message from the access gateway, and the first request message Including the TEID of the access gateway and the IP address of the access gateway, wherein the TEID of the access gateway is the TEID allocated by the access gateway for transmitting the control plane data; the terminal sends the The access gateway sends a first response message, where the first response message includes the TEID of the terminal, where the TEID of the terminal is the TEID allocated by the terminal for transmitting the control plane data.
  • the method may further include: the terminal receiving a second request message from the access gateway, where the second request message includes a protocol data unit (PDU) session identifier and the access The TEID of the ingress gateway, wherein the TEID of the access gateway is the TEID allocated by the access gateway for the user plane data of the PDU session; the terminal sends a second response message to the access gateway, and the The second response message includes the TEID of the terminal, where the TEID of the terminal is the TEID allocated by the terminal to the user plane data of the PDU session.
  • PDU protocol data unit
  • the second request message further includes the IP address of the access gateway, and the IP address of the access gateway is allocated by the access gateway for the user plane data of the PDU session IP address.
  • the method may further include: the terminal sending a first data packet to the access gateway, where the first data packet includes a first IP header, a first GTP-U header, and a second A payload, the first IP header includes the IP address of the access gateway, and the first GTP-U header includes the TEID of the access gateway; wherein, the first payload is the control plane data
  • the IP address of the access gateway is the IP address assigned by the access gateway for transmitting the control plane data
  • the TEID of the access gateway is the IP address allocated by the access gateway for transmitting the control plane data.
  • the IP address of the access gateway is the IP address allocated by the access gateway for transmitting the user plane data
  • the TEID of the access gateway is the TEID allocated by the access gateway for transmitting the user plane data.
  • the present application provides a communication method, and the method may be executed by a terminal or by components of the terminal.
  • the method includes: the terminal generates a first data packet, the first data packet includes a first Internet Protocol (IP) header, a first General Packet Radio Service Tunneling Protocol-User Plane (GTP-U) and a first load,
  • IP Internet Protocol
  • GTP-U General Packet Radio Service Tunneling Protocol-User Plane
  • the first IP header includes the IP address of the access gateway
  • the first GTP-U header includes the tunnel endpoint identifier (TEID) of the access gateway
  • the first load is control plane data
  • the The IP address of the access gateway is the IP address allocated by the access gateway for transmitting the control plane data
  • the TEID of the access gateway is the TEID allocated by the access gateway for transmitting the control plane data
  • the The first load is user plane data
  • the IP address of the access gateway is the IP address allocated by the access gateway for transmitting the user plane data
  • the method may further include: the terminal receiving a second data packet from the access gateway, where the second data packet includes a second IP header, a second GTP-U header, and The second payload, the second IP header includes the IP address of the access gateway, and the second GTP-U header includes the TEID of the access gateway.
  • the method may further include: determining, by the terminal, that the second payload is control plane data according to at least one of the IP address of the access gateway and the TEID of the access gateway. Or it is user plane data; or, the terminal determines that the second load is control plane data or user plane data by analyzing the second load.
  • the terminal determines, according to at least one of the IP address of the access gateway and the TEID of the access gateway, that the second load is control plane data or user plane data, and may Including one or more of the following:
  • the terminal determines that the second payload is the control plane data.
  • the terminal determines that the second payload is the control plane data.
  • the terminal determines that the second payload is the control plane data.
  • the IP address allocated by the access gateway for transmitting the control plane data is the same as the IP address allocated by the access gateway for transmitting the user plane data.
  • the present application provides a communication method, and the method may be executed by an access gateway or components of the access gateway.
  • the method includes: the access gateway receives a first data packet from the terminal, the first data packet includes a first Generic Routing Encapsulation (GRE) protocol header and a first load, and the first GRE protocol header includes a first GRE key word and the first protocol type field; and, the access gateway determines, according to at least one of the first GRE keyword and the first protocol type field, that the first payload is control plane data or user plane data.
  • GRE Generic Routing Encapsulation
  • the access gateway can distinguish whether the uplink payload is control plane data or user plane data according to at least one of the GRE keyword and the protocol type field included in the GRE protocol header encapsulated outside the uplink payload, and The GRE tunnel is established between the access gateway and the terminal. Compared with the IPsec tunnel, the process for the terminal to access the core network can be simplified.
  • the IPsec-based tunnel encapsulation method needs to encapsulate a double-layer IP header outside the user plane data
  • the GRE tunnel-based encapsulation method needs to encapsulate a layer of IP header outside the user plane data, obviously based on the GRE tunnel encapsulation method
  • the header length of the data packet is smaller than that based on the IPsec tunnel encapsulation method, which can reduce the waste of transmission resources, time extension, and high power consumption of the device caused by the excessive length of the packet header.
  • the access gateway determines, according to at least one of the first GRE keyword and the first protocol type field, that the first payload is control plane data or user plane data, Can include one or more of the following:
  • the access gateway determines that the first payload is the control plane data.
  • the access gateway determines that the first payload is the control plane data.
  • the access gateway determines that the first load is the control plane data.
  • the access gateway determines that the first payload is user plane data of the PDU session.
  • PDU protocol data unit
  • the access gateway can compare the GRE keyword in the GRE protocol header encapsulated outside the payload with the keyword and PDU session identifier allocated by the access gateway for the transmission control plane data, and/or analyze the GRE protocol header The protocol type field in , to flexibly determine whether the load is control plane data or user plane data.
  • the method before the access gateway receives the first data packet from the terminal, the method further includes: the access gateway sends a first request message to the terminal, and the first request message includes The Internet Protocol (IP) address of the access gateway and the key allocated by the access gateway for transmitting the control plane data.
  • IP Internet Protocol
  • the access gateway interacts with the terminal, and can send the key assigned for the transmission control plane data to the terminal, so as to be used later to identify whether the uplink load is control plane data.
  • the method before the access gateway receives the first data packet from the terminal, the method further includes: the access gateway receiving indication information from an Access and Mobility Management Function (AMF) network element , the indication information is used to indicate that an Internet Security Protocol (IPsec) tunnel does not need to be established between the access gateway and the terminal.
  • AMF Access and Mobility Management Function
  • IPsec Internet Security Protocol
  • the first data packet further includes a first IP header
  • the first IP header includes the IP address of the terminal
  • the method further includes: the access gateway according to the terminal The IP address of the terminal, and the corresponding relationship between the IP address of the terminal and the identification information of the terminal, determine the identification information of the terminal; the access gateway determines the context of the terminal according to the identification information of the terminal information.
  • the method further includes: the access gateway receiving a second message from the access node, where the second message includes the information between the IP address of the terminal and the identification information of the terminal. corresponding relationship.
  • the method further includes: the access gateway sending a second data packet to the terminal, the second data packet includes a second GRE protocol packet header and a second payload, and the second The GRE protocol packet header includes a second GRE keyword and a second protocol type field; wherein, when the second payload is the control message, the second GRE keyword is for the access gateway to transmit the control plane A keyword for data allocation, and/or the second protocol type field is used to indicate that the second load is the control plane data; or, when the second load is user plane data of a PDU session, the The second GRE key includes the PDU session identifier.
  • the present application provides a communication method, and the method may be executed by a terminal or by components of the terminal.
  • the method includes: the terminal receives a second data packet from the access gateway, the second data packet includes a second Generic Routing Encapsulation (GRE) protocol header and a second load, and the second GRE protocol header includes a second GRE key word and a second protocol type field; and, the terminal determines, according to at least one of the second GRE keyword and the second protocol type field, that the second payload is control plane data or user plane data.
  • GRE Generic Routing Encapsulation
  • the terminal determines that the second payload is control plane data or user plane data according to at least one of the second GRE keyword and the second protocol type field, including the following One or more:
  • the terminal determines that the second payload is the control plane data.
  • the terminal determines that the second payload is the control plane data.
  • the terminal determines that the second payload is the control plane data.
  • the terminal determines that the second payload is user plane data of the PDU session.
  • PDU protocol data unit
  • the method before the terminal receives the second data packet from the access gateway, the method further includes: the terminal receives a first request message from the access gateway, and the first request message including the Internet Protocol (IP) address of the access gateway and the second GRE keyword, wherein the second GRE keyword is a keyword allocated by the access gateway for transmitting the control plane data .
  • IP Internet Protocol
  • the method further includes: the terminal sends a first data packet to the access gateway, the first data packet includes a first GRE protocol header and a first payload, and the first The GRE protocol packet header includes a first GRE keyword and a first protocol type field; wherein, when the first load is the control message, the first GRE keyword is for the access gateway to transmit the control plane A keyword for data allocation, and/or the first protocol type field is used to indicate that the first load is the control plane data; or, when the first load is user plane data of a PDU session, the The first GRE key includes the PDU session identifier.
  • the present application provides a communication method, and the method may be executed by an access gateway, or by components of the access gateway.
  • the method includes: the access gateway receives a first payload from a terminal, wherein the first payload is encapsulated with a first Transmission Control Protocol (TCP) header, or the first payload is encapsulated with a first general routing encapsulation ( GRE) protocol header; the access gateway determines whether the first payload is control plane data or user plane data according to the encapsulation mode of the first payload.
  • TCP Transmission Control Protocol
  • GRE general routing encapsulation
  • different encapsulation methods are used for the control plane data and user plane data, so that the access gateway can distinguish whether the uplink load is control plane data or user plane data according to the encapsulation mode of the received load. data.
  • the access gateway can distinguish whether the uplink load is control plane data or user plane data according to the encapsulation mode of the received load. data.
  • the IPsec-based tunnel encapsulation method needs to encapsulate a double-layer IP header outside the user plane data
  • the GRE tunnel-based encapsulation method (or TCP encapsulation method) needs to encapsulate a layer of IP header outside the user plane data.
  • the header length of the data packet based on the GRE tunnel encapsulation method is smaller than that based on the IPsec tunnel encapsulation method, which can reduce the waste of transmission resources, time extension, and high power consumption of the device caused by the overly long header of the data packet. question.
  • the first TCP header includes the port number allocated by the access gateway for transmitting the control plane data
  • the GRE keyword in the first GRE protocol header includes a protocol data unit (PDU ) session ID.
  • the access gateway determines that the first payload is control plane data or user plane data according to the encapsulation mode of the first payload, which may include one or more of the following:
  • the access gateway determines that the first payload is the control plane data.
  • the access gateway determines that the first payload is user plane data of a PDU session.
  • the access gateway can distinguish whether the load is user plane data or control plane data through the encapsulation mode of the load.
  • the first payload is encapsulated with the first TCP header, which may be: the first payload is encapsulated with a third GRE protocol header, and the third GRE protocol header is encapsulated There is the first TCP packet header.
  • the third GRE protocol packet header includes a third GRE keyword
  • the third GRE keyword is a keyword allocated by an access node to the terminal
  • the method further includes: the The access gateway determines the identification information of the terminal according to the third GRE keyword and the corresponding relationship between the third GRE keyword and the identification information of the terminal; the access gateway determines the identification information of the terminal according to the The identification information of the terminal determines the context information of the terminal.
  • the access gateway can determine which terminal the uplink load comes from and the context information of the terminal according to the GRE keyword in the GRE protocol header encapsulated outside the load, so as to determine the control plane network element that establishes an N2 connection with the terminal Or determine the user plane network element that establishes the N3 connection with the terminal.
  • the method further includes: the access gateway receiving a second message from the access node, the second message including the third GRE keyword and the identification information of the terminal Correspondence between.
  • the access gateway can obtain the GRE key assigned by the access node to the terminal, so as to subsequently use it to determine which terminal the uplink load comes from.
  • the first TCP header is encapsulated with a first Internet Protocol (IP) header
  • the first GRE protocol header is encapsulated with a first IP header
  • the first IP header is including the IP address of the terminal
  • the method further includes: determining, by the access gateway, the Identification information of the terminal; the access gateway determines the context information of the terminal according to the identification information of the terminal.
  • IP Internet Protocol
  • the method further includes: the access gateway receiving a second message from the access node, where the second message includes the information between the IP address of the terminal and the identification information of the terminal. corresponding relationship.
  • the method before the access gateway receives the first load from the terminal, the method further includes: the access gateway sends a first request message to the terminal, the first request message includes the The port number of the access gateway and the IP address of the access gateway, wherein the port number of the access gateway is the port number allocated by the access gateway for transmitting the control plane data, and the access gateway The IP address of is the IP address allocated by the access gateway for transmitting the control plane data.
  • the first request message includes the IP address allocated by the access gateway for transmitting user plane data.
  • the method before the access gateway receives the first load from the terminal, the method further includes: the access gateway receives indication information from an Access and Mobility Management Function (AMF) network element, The indication information is used to indicate that there is no need to establish an Internet Security Protocol (IPsec) tunnel between the access gateway and the terminal.
  • AMF Access and Mobility Management Function
  • the method further includes: the access gateway sending a second payload to the terminal, where the second payload is encapsulated with a second TCP header, or the second payload is encapsulated with A second GRE protocol header; wherein, when the second load is the control plane data, the second load is encapsulated with the second TCP header, and the second TCP header includes the terminal for transmission
  • the port number assigned to the control plane data or, when the second load is the user plane data of the PDU, the second load is encapsulated with a second GRE protocol header, and the GRE in the second GRE protocol header Keyword includes the PDU session identifier.
  • the second payload is encapsulated with the second TCP header, which may be: the second payload is encapsulated with a fourth GRE protocol header, and the fourth GRE protocol header is encapsulated with The second TCP header, wherein the GRE keyword in the fourth GRE protocol header is a keyword assigned by the access node to the terminal.
  • the present application provides a communication method, which may be performed by a terminal or by a component of the terminal, and the method includes: the terminal receives a second payload from an access gateway, wherein the second payload is encapsulated with The second Transmission Control Protocol (TCP) header, or the second load is encapsulated with a second Generic Routing Encapsulation (GRE) protocol header; the terminal determines that the second load is according to the encapsulation mode of the second load Control plane data or user plane data.
  • TCP Transmission Control Protocol
  • GRE Generic Routing Encapsulation
  • the second TCP header includes the port number allocated by the terminal for transmitting the control plane data
  • the GRE keyword in the second GRE protocol header includes a protocol data unit (PDU) session logo.
  • the terminal determines that the second payload is control plane data or user plane data according to the encapsulation manner of the second payload, which may include one or more of the following:
  • the terminal determines that the second payload is the control plane data.
  • the terminal determines that the first payload is user plane data of a PDU session.
  • the second payload is encapsulated with the second TCP header, including: the second payload is encapsulated with a fourth GRE protocol header, and the fourth GRE protocol header is encapsulated with The second TCP header, wherein the GRE keyword in the fourth GRE protocol header is a keyword assigned by the access node to the terminal.
  • the method before the terminal receives the second load from the access gateway, the method further includes: the terminal receives a first request message from the access gateway, and the first request message includes The port number of the access gateway and the IP address of the access gateway, wherein the port number of the access gateway is the port number allocated by the access gateway for transmitting the control plane data, and the access The IP address of the gateway is the IP address allocated by the access gateway for transmitting the control plane data.
  • the first request message further includes an IP address allocated by the access gateway for transmitting user plane data.
  • the method further includes: the terminal sending a first payload to the access gateway, where the first payload is encapsulated with a first TCP header, or the first payload is encapsulated with A first GRE protocol header; wherein, when the first load is the control plane data, the first load is encapsulated with the first TCP header, and the first TCP header includes the access gateway as The port number assigned to transmit the control plane data; or, when the first load is user plane data of a PDU, the first load is encapsulated with a first GRE protocol header, and the first GRE protocol header contains The GRE keyword includes the PDU Session Identifier.
  • the first payload is encapsulated with the first TCP header, which may be: the first payload is encapsulated with a third GRE protocol header, and the third GRE protocol header is encapsulated with The first TCP header, wherein the GRE keyword in the third GRE protocol header is a keyword assigned by the access node to the terminal.
  • the present application provides a communication method, and the method may be executed by an access node or by a component of the access node.
  • the method includes: the access node receives a first payload from a terminal, the first payload is encapsulated with a first transmission control protocol (TCP) header; the access node sends the first payload to an access gateway, wherein The first payload is encapsulated with a third Generic Routing Encapsulation (GRE) protocol header, and the third GRE protocol header is encapsulated with the third TCP header.
  • TCP transmission control protocol
  • GRE Generic Routing Encapsulation
  • the third GRE protocol packet header includes a third GRE keyword
  • the third GRE keyword is a keyword allocated by the access node to the terminal
  • the third GRE keyword is used to determine the Identification information of the terminal.
  • the TCP connection between the UE and the TNGF is disconnected at the access node, that is, a TCP connection is established between the UE and the access node, and the access node then establishes a TCP connection with the TNGF.
  • the access node After the access node receives the first payload from the terminal, it encapsulates the GRE protocol header outside the first payload, and fills in the GRE keyword in the GRE protocol header as the keyword assigned by the access node to the terminal, and then encapsulates the The first payload of is sent to the TNGF to identify which terminal the first payload comes from.
  • the TNGF can determine the identification information of the terminal sending the first payload according to the GRE keyword in the GRE protocol header, and determine the control plane network element that establishes an N2 connection with the terminal based on the identification information of the terminal, or determine the The user plane network element on which the terminal establishes an N3 connection.
  • the method may further include: the access node assigning a third GRE keyword to the terminal; the access node sending a second message to the access gateway, the first The second message includes the correspondence between the third GRE keyword and the identification information of the terminal.
  • the method may further include: the access node sending a second message to the access gateway, where the second message includes the Internet Protocol (IP) address and The correspondence between the identification information of the terminals.
  • IP Internet Protocol
  • the first TCP header is encapsulated with a first IP header, the source address in the first IP header is the IP address of the terminal, and the destination address in the first IP header is is the IP address of the access node;
  • the third TCP header is encapsulated with a third IP header, the source address in the third IP header is the IP address of the access node, and the first IP header The destination address in is the IP address of the access gateway.
  • the present application provides a communication method, and the method may be executed by an access and mobility management function network element, or by components of the access and mobility management function network element.
  • the method includes: the access and mobility management function (AMF) network element, according to at least one of the type of the terminal and the service type of the terminal, determines that there is no need to establish an Internet security protocol (IPsec) between the terminal and the access gateway. ) tunnel; the AMF network element sends indication information to the access gateway, where the indication information is used to indicate that the IPsec tunnel does not need to be established between the terminal and the access gateway.
  • IPsec Internet security protocol
  • the type of the terminal is, for example, a terminal of a smart factory (such as a robot arm, a mobile truck, etc.), an IoT device, or a low-power device.
  • the service type of the terminal is, for example, a remote control service.
  • the AMF determines, according to at least one of the type of the terminal and the service type of the terminal, that there is no need to establish an IPsec tunnel between the terminal and the access gateway, that is, a simplified 5G core network access process can be performed, and the The ingress gateway sends indication information to indicate that the access gateway does not need to establish an IPsec tunnel with the terminal, thereby simplifying the process for the terminal to access the 5G core network, and reducing the waste of transmission resources and time spent due to the IPsec encapsulation method during user plane data transmission.
  • the present application provides a communication device, including a memory, and one or more processors, the memory is coupled to the one or more processors; the memory is used to store computer programs or instructions, when the When the computer program or instruction is executed by the one or more processors, the communication device executes the method described in the above-mentioned first aspect or any design of the first aspect, or causes the communication device to execute the above-mentioned The method described in the fourth aspect or any design of the fourth aspect, or causing the communication device to execute the method described in the sixth aspect or any design of the sixth aspect.
  • the present application provides a communication device, including a memory, and one or more processors, the memory is coupled to the one or more processors; the memory is used to store computer programs or instructions, when When the computer program or instructions are executed by the one or more processors, the communication device executes the method described in the above-mentioned second aspect or any design of the second aspect, or causes the communication device to execute The method described in the above third aspect or any design of the third aspect, or make the communication device execute the method described in the above fifth aspect or any design of the fifth aspect, or make the communication The device executes the method described in the seventh aspect or any one of the designs of the seventh aspect.
  • the present application provides a communication device, including a memory, and one or more processors, the memory is coupled to the one or more processors; the memory is used to store computer programs or instructions, when When the computer program or instructions are executed by the one or more processors, the communication device is made to execute the method described in the eighth aspect or any one of the designs of the eighth aspect.
  • the present application provides a communication device, including a memory, and one or more processors, the memory is coupled to the one or more processors; the memory is used to store computer programs or instructions, when The computer program or instruction, when executed by the one or more processors, causes the communication device to perform the method described in the ninth aspect above.
  • the present application provides a communication device, including a communication unit and a processing unit, and these units or modules can perform the corresponding functions performed by the access gateway in the first aspect or any design example of the first aspect, Or perform the corresponding functions performed by the access gateway in the fourth aspect or any design example of the fourth aspect, or perform the corresponding functions performed by the access gateway in the sixth aspect or any design example of the sixth aspect Features.
  • the present application provides a communication device, including a communication unit and a processing unit. These units or modules can perform the corresponding functions performed by the terminal in any design example of the second aspect or the second aspect, or perform The corresponding function performed by the terminal in the above third aspect or any design example of the third aspect, or perform the corresponding function performed by the terminal in the above fifth aspect or any design example of the fifth aspect, or perform the above first The corresponding functions performed by the terminal in the seventh aspect or any design example of the seventh aspect.
  • the present application provides a communication device, including a communication unit and a processing unit, and these units or modules can perform the corresponding functions performed by the access node in the eighth aspect or any design example of the eighth aspect.
  • the present application provides a communication device, including a communication unit and a processing unit, and these units or modules can perform corresponding functions performed by the access and mobility management functional network element in the ninth aspect.
  • the present application provides a communication system, including the communication device in the tenth aspect and/or the communication device in the eleventh aspect; or including the communication device in the fourteenth aspect and/or the fifteenth aspect in the communication device.
  • the present application provides a communication system, including the communication device in the tenth aspect and/or the communication device in the twelfth aspect; or including the communication device in the fourteenth aspect and/or the sixteenth aspect in the communication device.
  • the present application provides a communication system, including the communication device in the tenth aspect and/or the communication device in the thirteenth aspect; or including the communication device in the fourteenth aspect and/or the seventeenth aspect in the communication device.
  • the present application provides a computer-readable storage medium, in which computer programs or instructions are stored, and when the computer programs or instructions are executed, any one of the above-mentioned first aspect or the first aspect can be realized
  • the present application provides a computer-readable storage medium, in which computer programs or instructions are stored, and when the computer programs or instructions are executed, any one of the above-mentioned second aspect or the second aspect can be realized
  • the present application provides a computer-readable storage medium, in which computer programs or instructions are stored.
  • the computer programs or instructions are executed, any one of the above-mentioned eighth aspect or the eighth aspect can be realized. method described in the project design.
  • the present application provides a computer-readable storage medium, in which a computer program or instruction is stored, and when the computer program or instruction is executed, the method described in the above-mentioned ninth aspect can be realized.
  • the present application provides a terminal device, which can implement the method described in the above-mentioned first aspect or any one of the designs of the first aspect, or implement the above-mentioned fourth aspect or any of the fourth aspects The method described in one design, or implement the method described in the sixth aspect or any design of the sixth aspect.
  • Figure 1a is a schematic diagram of a 5G network architecture based on a service architecture in an embodiment of the present application
  • Figure 1b is a schematic diagram of a 5G network architecture based on a point-to-point interface in an embodiment of the present application
  • Figure 1c is another schematic diagram of the 5G network architecture based on the point-to-point interface in the embodiment of the present application;
  • FIG. 2 is a schematic flow diagram of a communication method provided in an embodiment of the present application.
  • FIG. 3 is a schematic flowchart of a method for obtaining an IP address and a TEID for transmitting control plane data provided by an embodiment of the present application;
  • FIG. 4 is a schematic flowchart of a method for obtaining an IP address and a TEID for transmitting user plane data provided by an embodiment of the present application;
  • FIG. 5 is another schematic flowchart of a method for obtaining an IP address and a TEID for transmitting user plane data provided by an embodiment of the present application;
  • FIG. 6 is another schematic flowchart of a communication method provided in an embodiment of the present application.
  • Fig. 7 is a schematic diagram of the GRE protocol header provided by the embodiment of the present application.
  • Fig. 8 is a schematic diagram of the GRE key in the GRE protocol header provided by the embodiment of the present application.
  • FIG. 9 is a schematic flow diagram of a method for obtaining a GRE key used to transmit control plane data provided by an embodiment of the present application.
  • FIG. 10 is another schematic flowchart of the communication method provided by the embodiment of the present application.
  • FIG. 11 is a schematic flow diagram of a method for obtaining a TCP port number for transmitting control plane data provided by an embodiment of the present application
  • FIG. 12 is a schematic structural diagram of a communication device provided by an embodiment of the present application.
  • FIG. 13 is another schematic structural diagram of a communication device provided by an embodiment of the present application.
  • FIG. 14 is another schematic flowchart of the communication method provided by the embodiment of the present application.
  • “Multiple” means two or more, and in view of this, “multiple” can also be understood as “at least two” in the embodiments of the present application.
  • “At least one” can be understood as one or more, such as one, two or more. For example, including at least one means including one, two or more, and does not limit which ones are included. For example, where at least one of A, B, and C is included, then A, B, C, A and B, A and C, B and C, or A and B and C may be included. Similarly, the understanding of descriptions such as “at least one" is similar.
  • At least one of the following or similar expressions refer to any combination of these items, including any combination of single or plural items.
  • at least one of A, B and C includes A, B, C, AB, AC, BC or ABC.
  • And/or describes the association relationship of associated objects, indicating that there may be three types of relationships, for example, A and/or B may indicate: A exists alone, A and B exist simultaneously, and B exists independently.
  • the character "/”, unless otherwise specified, generally indicates that the associated objects before and after are in an "or” relationship.
  • ordinal numerals such as “first”, “second”, “third”, and “fourth” mentioned in the embodiments of this application are used to distinguish multiple objects, and are not used to limit the order of multiple objects , timing, priority or degree of importance, and the descriptions of “first”, “second”, “third”, and “fourth” do not limit that the objects must be different.
  • FIG. 1a it is a schematic diagram of a fifth generation (5th generation, 5G) network architecture based on a service architecture.
  • the 5G network architecture shown in Figure 1a may include three parts, namely a terminal part, a data network (data network, DN) and an operator network part.
  • the functions of some of the network elements are briefly introduced and described below.
  • the operator network may include but not limited to one or more of the following network elements: network slice selection function (network slice selection function, NSSF) network element, authentication server function (authentication server function, AUSF) network element, Network exposure function (NEF) network element, network repository function (NRF) network element, access and mobility management function (access and mobility management function, AMF) network element, policy control function (policy control function (PCF) network element, unified data management (unified data management, UDM) network element, session management function (session management function, SMF) network element, access network (AN) or wireless access network (radioaccess) network, RAN), and user plane function (user plane function, UPF) network elements, etc.
  • the part other than the radio access network part may be referred to as the core network part.
  • the operator network also includes an application function (application function, AF) network element.
  • Terminal device which can be referred to as a terminal for short, is a device with wireless transceiver function, which can be deployed on land, including indoor or outdoor, handheld or vehicle-mounted; it can also be deployed on water (such as ships, etc.); Can be deployed in the air (such as aircraft, balloons and satellites, etc.).
  • the terminal device may be a tablet computer (pad), a computer with a wireless transceiver function, a virtual reality (virtual reality, VR) terminal, an augmented reality (augmented reality, AR) terminal, a wireless terminal in industrial control (industrial control), Wireless terminals in self driving, wireless terminals in remote medical, wireless terminals in smart grid, wireless terminals in transportation safety, smart city ), wireless terminals in smart home (smart home), user equipment (user equipment, UE), terminal equipment adapted to the Internet of Things (Internet of Things, IoT) (such as terminal equipment in smart factories, smart manufacturing industry terminal equipment, etc.), terminal equipment supporting sparklink short-distance communication technology, etc.
  • IoT Internet of Things
  • the above-mentioned terminal can establish a connection with the operator network through an interface provided by the operator network (for example, N1, etc.), and use services such as data and/or voice provided by the operator network.
  • the terminal can also access the DN through the operator network, and use operator services deployed on the DN, and/or services provided by a third party.
  • the above-mentioned third party may be a service party other than the operator's network and the terminal device, and may provide other services such as data and/or voice for the terminal device.
  • the specific form of expression of the above-mentioned third party can be determined according to the actual application scenario, and is not limited here.
  • the RAN is a sub-network of the operator's network and an implementation system between service nodes and terminal equipment in the operator's network.
  • the terminal equipment To access the operator's network, the terminal equipment first passes through the RAN, and then can be connected to the service node of the operator's network through the RAN.
  • a RAN device is a device that provides a wireless communication function for a terminal device, and the RAN device is also called an access network device.
  • RAN equipment includes but is not limited to: next-generation base station (g nodeB, gNB), evolved node B (evolved node B, eNB), radio network controller (radio network controller, RNC), node B (node B, NB), base station controller (base station controller, BSC), base transceiver station (base transceiver station, BTS), home base station (for example, home evolved nodeB, or home node B, HNB), baseband unit (baseBand unit, BBU) , transmission point (transmitting and receiving point, TRP), transmission point (transmitting point, TP), mobile switching center, etc.
  • next-generation base station g nodeB, gNB
  • evolved node B evolved node B
  • eNB evolved node B
  • RNC radio network controller
  • node B node B
  • base station controller base station controller
  • BTS base transceiver station
  • home base station for example, home evolved nodeB, or home node B, HNB
  • the AMF network element mainly performs functions such as mobility management and access authentication/authorization. In addition, it is also responsible for transferring user policies between UE and PCF.
  • the SMF network element mainly performs functions such as session management, execution of control policies issued by the PCF, selection of UPF, and allocation of UE Internet Protocol (internet protocol, IP) addresses.
  • the UPF network element as an interface with the data network, completes functions such as user plane data forwarding, session/flow-based charging statistics, and bandwidth limitation.
  • the UDM network element is mainly responsible for managing subscription data, user access authorization and other functions.
  • the NSSF network element is mainly responsible for managing information related to network slicing.
  • NEF network elements are mainly used to support the opening of capabilities and events.
  • the AF network element mainly transmits the requirements from the application side to the network side, for example, Quality of Service (QoS) requirements or user status event subscription.
  • QoS Quality of Service
  • the AF may be a third-party functional entity, or an application service deployed by an operator, such as an IP Multimedia Subsystem (IP Multimedia Subsystem, IMS) voice call service.
  • IP Multimedia Subsystem IP Multimedia Subsystem, IMS
  • the PCF network element is mainly responsible for policy control functions such as charging for sessions and service data flow levels, QoS bandwidth guarantee, mobility management, and UE policy decision-making.
  • the PCFs connected to AMF and SMF correspond to AM PCF (PCF for Access and Mobility Control) and SM PCF (PCF for Session Management), respectively, which may not be the same PCF entity in the actual deployment scenario.
  • the NRF network element can be used to provide a network element discovery function, and provide network element information corresponding to the network element type based on the request of other network elements.
  • NRF also provides network element management services, such as network element registration, update, de-registration, network element status subscription and push, etc.
  • AUSF network element It is mainly responsible for authenticating users to determine whether users or devices are allowed to access the network.
  • DN is a network outside the operator's network.
  • the operator's network can access multiple DNs, and various services can be deployed on the DN, which can provide data and/or voice services for terminal equipment.
  • DN is a private network of a smart factory.
  • the sensors installed in the workshop of the smart factory can be terminal devices.
  • the control server of the sensor is deployed in the DN, and the control server can provide services for the sensor.
  • the sensor can communicate with the control server, obtain instructions from the control server, and transmit the collected sensor data to the control server according to the instructions.
  • DN is a company's internal office network, and the mobile phone or computer of the company's employees can be a terminal device, and the employee's mobile phone or computer can access information and data resources on the company's internal office network.
  • Nnssf, Nausf, Nnef, Nnrf, Namf, Npcf, Nsmf, Nudm, Naf, N1, N2, N3, N4, and N6 are interface serial numbers.
  • interface serial numbers refer to the meanings defined in the 3GPP standard protocol, and there is no limitation here.
  • the 5G network architecture based on point-to-point interfaces is shown in Figure 1b.
  • the access network includes a 3GPP access network and an untrusted non-3GPP access network.
  • Access devices in the 3GPP access network may be called radio access network (radioaccess network, RAN) devices.
  • An access device in an untrusted non-3GPP access network may be called a non-3GPP interworking function (non-3GPP interworking function, N3IWF) device.
  • the N3IWF equipment may include routers and the like, for example.
  • FIG. 1b it is a schematic diagram of a 5G network architecture based on a point-to-point interface, and the introduction of the functions of the network elements can refer to the introduction of the functions of the corresponding network elements in Figure 1a, and will not be repeated here.
  • the main difference between FIG. 1b and FIG. 1a is that the interfaces between network elements in FIG. 1b are point-to-point interfaces, while the interfaces between network elements in FIG. 1a are service interfaces.
  • N1, N2, N3, N4, N6, N11, NWu, Y1, and Y2 in FIG. 1b are interface serial numbers.
  • interface serial numbers refer to the meanings defined in the 3GPP standard protocol, and there is no limitation here.
  • the 5G core network When the 5G core network supports trusted non-3GPP access, or supports wired network access, or supports trusted non-3GPP and wired network access, its 5G network architecture is similar to Figure 1b.
  • the non-trusted non-3GPP access in Figure 1b may be replaced by a trusted non-3GPP access, and the N3IWF may be replaced by a trusted non-3GPP access gateway (trusted non-3GPP gateway function, TNGF); or, Replace the untrusted non-3GPP access in Figure 1b with wired network access, and replace N3IWF with a wired network access gateway function (W-AGF).
  • TNGF trusted non-3GPP gateway function
  • W-AGF wired network access gateway function
  • FIG. 1c it is a schematic diagram of a 5G network architecture based on a point-to-point interface, and the introduction of the functions of the network elements can refer to the introduction of the corresponding network element functions in Figure 1a, and will not be repeated here.
  • the main difference between FIG. 1c and FIG. 1a is that the interfaces between network elements in FIG. 1c are point-to-point interfaces, while the interfaces between network elements in FIG. 1a are service interfaces.
  • N1, N2, N3, N4, N6, N11, NWu, and Uu in Fig. 1c are interface serial numbers.
  • interface serial numbers refer to the meaning defined in the 3GPP standard agreement, and there is no limitation here.
  • the above-mentioned network element or function may be a network element in a hardware device, or a software function running on dedicated hardware, or a virtualization function instantiated on a platform (for example, a cloud platform).
  • a platform for example, a cloud platform.
  • the foregoing network element or function may be implemented by one device, or jointly implemented by multiple devices, or may be a functional module in one device, which is not specifically limited in this embodiment of the present application.
  • the embodiment of the present application provides a communication method, which can be applied to the non-3GPP access scenario shown in FIG. 1b or FIG. 1c.
  • the access gateway is N3IWF or next generation access gateway (next generation packet data Gateway, ngPDG).
  • the access gateway is TNGF.
  • the access gateway is W-AGF.
  • the access node (also called an access device) between the terminal and the access gateway can be a wireless local area networks access point (WLAN AP), a fixed access network (fixed access network, FAN ) devices, G-nodes (G-nodes), wifi APs, Bluetooth access nodes, switches, or routers that support Starlight short-distance communication.
  • WLAN AP wireless local area networks access point
  • FAN fixed access network
  • G-nodes G-nodes
  • wifi APs G-nodes
  • Bluetooth access nodes switches, or routers that support Starlight short-distance communication.
  • the embodiment of the present application takes a trusted non-3GPP access scenario, that is, the access gateway is TNGF as an example for description.
  • the access and mobility management network elements, unified data management, and user plane network elements in this embodiment of the application can be AMF, UDM, and UPF in Figure 1a, Figure 1b, or Figure 1c, respectively, or they can be future communications such as In the sixth generation (6th generation, 6G) network, the network element having the functions of the above-mentioned AMF, UDM, and UPF is not limited in this embodiment of the present application.
  • 6G sixth generation
  • the embodiments of the present application are described by taking the above-mentioned AMF, UDM, and UPF as an example for the network elements of access and mobility management, unified data management, and user plane, respectively.
  • the terminal is UE as an example for illustration.
  • FIG. 2 shows a schematic flowchart of a communication method provided by an embodiment of the present application. As shown in FIG. 2 , this embodiment introduces the communication method provided by this embodiment from the uplink direction and the downlink direction respectively.
  • tunnel endpoint identifier tunnel endpoint identifier (tunnel endpoint identifier, TEID) allocated by TNGF for the transmission of control plane data is denoted as TNGF TEID_1, and the TEID allocated by TNGF for transmission of user plane data is denoted as TNGF TEID_2,
  • IP Internet protocol
  • the Internet protocol (internet protocol, IP) address allocated by TNGF for transmission control plane data is recorded as TNGF IP address 1
  • the IP address allocated by TNGF for transmission of user plane data is recorded as TNGF IP address 2
  • the UE is designated as transmission control plane data.
  • the TEID allocated for the plane data is denoted as UE TEID_1
  • the TEID allocated by the UE for transmitting user plane data is denoted as UE TEID_2.
  • the payload is encapsulated with a general packet radio service tunnel protocol-user plane (GTP-U) packet header
  • GTP-U packet header is encapsulated with a User Datagram Protocol (User Datagram Protocol) packet header.
  • Datagram Protocol, UDP Datagram Protocol
  • UDP User Datagram Protocol
  • the encapsulation method of the IP packet header encapsulated outside the UDP packet header is denoted as GTP-U/UDP/IP.
  • the first message (or the third message) is encapsulated with a GTP-U header
  • the GTP-U header is encapsulated with a UDP header
  • the UDP header is encapsulated with an IP header as message/GTP- U/UDP/IP.
  • S201 The UE sends a first data packet to the TNGF.
  • the TNGF receives the first data packet.
  • the UE may send the first data packet to the TNGF through the GTP-U tunnel.
  • the first data packet includes a first IP header, a first GTP-U header and a first payload.
  • the first payload is encapsulated with a first GTP-U header
  • the first GTP-U header is encapsulated with a first UDP header
  • the first UDP header is encapsulated with a first IP header.
  • the UE may encapsulate the first GTP-U header outside the first payload, encapsulate the first UDP header outside the first GTP-header, and encapsulate the first IP header outside the first UDP header, to obtain the first data packet , and send the first data packet to the TNGF through the GTP-U tunnel.
  • the load may be control plane data
  • the control plane data includes control plane messages, such as non access stratum (non access stratum, NAS) messages, or other control plane data other than NAS messages exchanged between the UE and the TNGF; It can also be user plane data, such as remote control service data.
  • the first IP packet header includes a destination IP address and a source IP address, and the destination IP address and the source IP address are respectively the IP address of the TNGF and the IP address of the UE.
  • the first GTP-U header includes the TEID of the TNGF.
  • the IP address of TNGF can be the IP address allocated by TNGF for transmitting control plane data (denoted as TNGF IP address 1), or the IP address allocated by TNGF for transmitting user plane data (denoted as TNGF IP address 2).
  • the TEID of the TNGF can be the TEID allocated by the TNGF for the transmission of control plane data (denoted as TNGF TEID_1), or the TEID allocated by the TNGF for the transmission of user plane data (denoted as TNGF TEID_2). At least one of the IP address of the TNGF or the TEID of the TNGF may be used to identify whether the first load is control plane data or user plane data.
  • the TEID of the TNGF is the TEID allocated by the TNGF for transmitting the control plane data.
  • the UE may encapsulate the first payload according to the GTP-U/UDP/IP encapsulation manner, and fill in the TEID in the GTP-U header as TNGF TEID_1 to indicate that the first payload is control plane data.
  • the IP address of the TNGF is an IP address allocated by the TNGF for transmitting the control plane data.
  • the UE may encapsulate the first payload in a GTP-U/UDP/IP encapsulation manner, and fill in the destination IP address in the IP header as TNGF IP address 1, to indicate that the first payload is control plane data.
  • the TEID of TNGF is the TEID allocated by TNGF for transmission of control plane data
  • the IP address of TNGF is the IP address allocated by TNGF for transmission of control plane data.
  • the UE can encapsulate the first payload according to the GTP-U/UDP/IP encapsulation method, fill in the TEID in the GTP-U header as TNGF TEID_1, and fill in the destination IP address in the IP header as TNGF IP Address 1, to indicate that the first payload is control plane data.
  • the TEID of the TNGF is the TEID allocated by the TNGF for transmitting user plane data.
  • the UE may encapsulate the first payload according to the GTP-U/UDP/IP encapsulation manner, and fill in the TEID in the GTP-U packet header as TNGF TEID_2 to indicate that the first payload is user plane data.
  • the IP address of the TNGF is an IP address allocated by the TNGF for transmitting user plane data.
  • the UE may encapsulate the first payload according to the GTP-U/UDP/IP encapsulation method, and fill in the destination IP address in the IP header as TNGF as TNGF IP address 2, to indicate that the first payload is the user plane data.
  • the TEID of TNGF is the TEID allocated by TNGF for transmitting user plane data
  • the IP address of TNGF is the IP address allocated by TNGF for transmitting user plane data.
  • the UE can encapsulate the first payload according to the GTP-U/UDP/IP encapsulation method, fill in the TEID in the GTP-U header as TNGF TEID_2, and fill in the destination IP address in the IP header as TNGF IP Address 2, to indicate that the first payload is user plane data.
  • the IP address allocated by TNGF for transmitting control plane data and the IP address allocated by TNGF for transmitting user plane data can be the same or different, that is, TNGF IP address 1 and TNGF IP address 2 can be the same or different, This embodiment of the present application does not limit it.
  • TNGF assigns the same IP address for transmitting control plane data and user plane data.
  • TNGF allocates an IP address for transmitting control plane data, but does not allocate an IP address for transmitting user plane data.
  • the IP address used for transmitting user plane data is the same as the IP address used for transmitting control plane data.
  • the UE can fill in the destination IP address of the IP header as the IP address allocated by TNGF for the transmission of control plane data or the IP address allocated by TNGF for the transmission of user plane data, and/or, the TEID in the GTP-U header Fill in the TEID allocated by TNGF for transmission of control plane data or the TEID allocated by TNGF for transmission of user plane data to indicate that the first load is control plane data or user plane data.
  • the UE can negotiate with TNGF to obtain the IP address and TEID allocated by TNGF for transmitting control plane data, and the IP address and TEID allocated by TNGF for transmitting user plane data; correspondingly, TNGF can also By negotiating with the UE, the TEID allocated by the UE for transmitting control plane data and the TEID allocated by the UE for transmitting user plane data are acquired.
  • the UE may receive a first request message from the TNGF, where the first request message includes the TEID allocated by the TNGF for transmission of control plane data and the IP address allocated by the TNGF for transmission of control plane data.
  • the UE may send a first response message to the TNGF, where the first response message includes the TEID allocated by the UE for transmitting control plane data.
  • the first request message and the first response message may be an extended authentication protocol (extensible authentication protocol, EAP) message or a 5G notification (5G-notification) message.
  • EAP-request extended authentication request
  • EAP-response extended authentication response
  • both the first request message and the first response message are 5G notification messages.
  • the first request message may also include a differentiated services code point (differentiated services code point, DSCP) used for transmitting control plane data.
  • DSCP differentiated services code point
  • the UE may receive a second request message from the TNGF, where the second request message includes a protocol data unit (protocol data unit, PDU) session identifier and a TEID allocated by the TNGF for transmitting user plane data of the PDU session.
  • the UE may send a second response message to the TNGF, where the second response message includes the TEID allocated by the UE for transmitting the user plane data of the PDU session.
  • PDU protocol data unit
  • Fig. 3 shows a flow chart of a method for acquiring an IP address and a TEID for transmitting control plane data provided by an embodiment of the present application. As shown in Fig. 3, the method may include the following steps.
  • S301 Establish a layer (layer, L)2 connection between the UE and the access node.
  • the UE may establish an L2 connection with the access node through bluetooth, wifi, radio frequency identification (radio frequency identification, RFID) technology, or Xinghuo short-distance communication technology.
  • the access node can be a G-node (G-node), a wifi AP, or a Bluetooth access point that supports Starlight short-distance communication technology.
  • S302 The access node sends an extended authentication request message to the UE.
  • the UE receives the extended authentication request message.
  • the access node may send an extended authentication request message or an identity (identity) message to the UE.
  • the extended authentication request message or the identity message is used to request the identification information of the UE.
  • the identification information of the UE includes at least a network access identifier (network access identifier, NAI) of the UE.
  • NAI network access identifier
  • the NAI includes the UE's device identifier and public land mobile network (public land mobile network, PLMN) information, or includes the UE's device identifier and service provider information, or includes the UE's device identifier, PLMN information and service provider information.
  • the device ID of the UE is recorded as device ID
  • the PLMN information is recorded as PLMN
  • the service provider information is recorded as Service provider name
  • the service provider information can be identified by the Star Alliance.
  • S303 The UE sends an extended authentication response message to the access node.
  • the access node receives the extended authentication response message.
  • the extended authentication response message includes the identification information of the UE.
  • the access node sends the identification information of the UE to the TNGF.
  • the TNGF receives the identification information of the UE.
  • the access node may select the TNGF for the UE according to the UE's identification information. For example, the access node may select the TNGF according to the PLMN information or service provider information included in the NAI, and send the UE's identification information to the TNGF. For example, the access node may send the identification information of the UE to the TNGF through an authentication authorization accounting (authentication authorization accounting, AAA) message.
  • AAA authentication authorization accounting
  • the TNGF sends a 5G start (5G-Start) message to the UE.
  • the UE receives the 5G start message.
  • TNGF can determine that the UE needs to access the 5G core network based on the UE's identification information. For example, if the UE's NAI includes 5G PLMN information, the TNGF determines that the UE needs to access the 5G core network, and sends the extended authentication to the UE.
  • a request message or a 5G start message ( Figure 3 takes the 5G start message as an example).
  • the extended authentication request message or the 5G start message may be used to instruct the UE to start accessing the 5G core network.
  • S306 The UE sends a registration request message (registration request message) to the AMF.
  • the AMF receives the registration request message.
  • the UE initiates a registration process for accessing the 5G core network, for example, the UE sends a registration request message to the AMF through the access node and the TNGF.
  • the registration request message may be a NAS message.
  • the registration request message includes UE type indication information and service type indication information.
  • the UE type indication information can be used to indicate the type of UE, such as indicating that the UE is a UE of a smart factory (such as a robot arm, a mobile truck, etc.); or indicating that the UE is an IoT device; or indicating that the UE is a low-power device, etc.
  • the type of UE is not limited to this.
  • the service type indication information may be used to indicate the service type of the UE, such as indicating that the service type of the UE is a remote control service, etc., and the embodiment of the present application does not limit the service type of the UE to this.
  • the UE sends the registration request message to the AMF through the access node and the TNGF can be understood as: the UE sends the registration request message to the access node, and the access node forwards the registration request message to the TNGF after receiving the registration request message, And forwarded to the AMF by the TNGF, that is, the registration request message is transparently transmitted at the access node and the TNGF.
  • the AMF sends an authentication message to the UDM.
  • the UDM receives the authentication message.
  • the authentication and authentication message is used to perform an authentication and authentication procedure for the UE.
  • S308 An authentication process is performed between the UE and the UDM.
  • the UDM sends the subscription data to the AMF.
  • the AMF receives the subscription data.
  • the UDM can send the subscription data related to the UE to the AMF.
  • the subscription data may include at least one of UE type indication information and service type indication information.
  • the AMF sends indication information to the TNGF.
  • the TNGF receives the indication information.
  • the indication information is used to indicate that there is no need to establish an IPsec tunnel between the UE and the TNGF.
  • the AMF may determine that the UE performs a simplified 5G core network access procedure according to at least one of the UE type indication information and the service type indication information. For example, if the UE is a UE of a smart factory, or an IoT device, or a low-power device, the AMF may determine that the UE performs a simplified 5G core network access process. For another example, if the service type of the UE is a remote control service, the AMF may determine that the UE performs a simplified 5G core network access procedure.
  • the simplified 5G core network access process means that there is no need to establish an IPsec tunnel between the UE and the TNGF.
  • an unencrypted IPsec tunnel is established between UE and TNGF; for an untrusted non-3GPP access scenario, an encrypted IPsec tunnel is established between UE and N3IWF. That is, regardless of the trusted non-3GPP access scenario or the untrusted non-3GPP access scenario, an IPsec tunnel can be established between the UE and its corresponding access gateway.
  • an IPsec tunnel can be established between the UE and its corresponding access gateway.
  • multiple signaling interactions between multiple network elements are required, and the complexity is high.
  • the encapsulation method based on the IPsec tunnel needs to encapsulate a double-layer IP header outside the user plane data, resulting in a longer length of the header of the encapsulated data packet, which consumes more transmission resources, and will Increase the delay required for device encapsulation or decapsulation, thereby increasing the power consumption of the device.
  • the AMF determines that the UE can perform a simplified 5G core network access process according to at least one of the UE type and the UE service type, that is, the IPsec tunnel process does not need to be established, and sends indication information to the TNGF to indicate TNGF does not need to establish an IPsec tunnel with the UE, which can simplify the process of UE accessing the 5G core network, and can reduce the problems of waste of transmission resources, time extension, and high power consumption of equipment caused by IPsec encapsulation in the process of user plane data transmission.
  • the AMF may send an N2 message to the TNGF, where the N2 message includes the indication information, to indicate that the TNGF does not need to establish an IPsec tunnel with the UE.
  • the N2 message may also include information such as a security key.
  • S311 The TNGF sends a first request message to the UE.
  • the UE receives the first request message.
  • the first request message may be an extended authentication request message or a 5G notification message.
  • the first request message includes TNGF IP address 1, TNGF TEID_1 and DSCP.
  • the TNGF determines that there is no need to establish an IPsec tunnel with the UE. Further, the TNGF may determine to establish a GTP-U tunnel with the UE. Specifically, the TNGF allocates the IP address of the TNGF and the TEID of the TNGF to the UE, and carries the IP address of the TNGF and the TEID of the TNGF in an extended authentication request message or a 5G notification message and sends it to the UE.
  • the IP address of TNGF is the IP address (i.e.
  • TNGF IP address 1 that is subsequently used to transmit control plane data
  • the TEID of TNGF is the TEID (i.e. TNGF TEID_1) that is subsequently used to transmit control plane data.
  • the TNGF may also determine the DSCP used for subsequent transmission of control plane data, and carry the DSCP in the extended authentication request message or 5G notification message and send it to the UE.
  • the UE After receiving the extended authentication request message or 5G notification message, the UE stores TNGF IP address 1, TNGF TEID_1 and DSCP, so as to send control plane data to TNGF through the GTP-U tunnel.
  • S312 The UE sends a first response message to the TNGF.
  • the TNGF receives the first response message.
  • the first response message may be an extended authentication response message or a 5G notification message.
  • the first response message includes UE TEID_1.
  • the UE determines to establish a GTP-U tunnel with the TNGF. Specifically, the UE assigns the TEID of the UE to the TNGF, and carries the TEID of the UE in an extended authentication response message or a 5G notification message and sends it to the TNGF.
  • the TEID of the UE is the TEID (that is, UE TEID_1) used for subsequent transmission of control plane data.
  • TNGF stores UE TEID_1, so as to send control plane data to UE through GTP-U tunnel.
  • a GTP-U tunnel can be established between the UE and the TNGF, and information for subsequent control plane data transmission, such as TNGF IP address 1, TNGF TEID_1, UE TEID_1, and DSCP, can be negotiated.
  • the GTP-U tunnel establishment process requires less interactive signaling, which can reduce the complexity of UE access to the 5G core network, and the length of the header of the data packet encapsulated based on the GTP-U encapsulation method is smaller than that based on the Psec encapsulation method, thereby reducing Due to the IPsec encapsulation method, there are problems such as waste of transmission resources, time extension, and high power consumption of equipment.
  • the first response message sent by the UE to the TNGF includes UE TEID_1.
  • UE TEID_1 may not be included in the first response message.
  • the UE TEID_1 may be a pre-configured fixed value. That is, the UE TEID_1 may or may not be included in the first response message, which is not limited in this embodiment of the present application.
  • S313 Perform a dynamic host configuration protocol (dynamic host configuration protocol, DHCP) process between the UE and the access node.
  • DHCP dynamic host configuration protocol
  • the UE sends a configuration request message to the access node, where the configuration request message is used to request the IP address of the UE.
  • the access node configures an IP address for the UE, and sends a configuration response message to the UE, where the configuration response message includes the IP address of the UE.
  • the IP address of the UE may include the IP address obtained by the UE for transmitting control plane data (denoted as UE IP address 1), and the IP address obtained by the UE for transmitting user plane data (denoted as UE IP address 2).
  • the UE may respectively obtain the IP address used for transmitting control plane data and the IP address used for transmitting user plane data through step 313 .
  • the UE IP address 1 and the UE IP address 2 may be the same or different, which is not limited in this embodiment of the present application. For ease of understanding, this embodiment of the present application is described by taking UE IP address 1 and UE IP address 2 being the same as an example.
  • S314 The access node sends a second message to the TNGF.
  • the TNGF receives the second message.
  • the second message includes the correspondence between the IP address of the UE and the identification information of the UE.
  • the second message may be an AAA message.
  • the access node may include the correspondence between the IP address of the UE and the identification information of the UE in the AAA message and send it to the TNGF.
  • the TNGF stores the correspondence between the IP address of the UE and the identification information of the UE. In this way, after the TNGF subsequently receives the uplink information (control plane data or user plane data), it can determine the sender of the uplink information.
  • UE identification information Table 1 shows an example of the correspondence between the IP address of the UE and the identification information of the UE maintained by the TNGF.
  • TNGF establishes connections with three UEs, wherein the identification information of the UE corresponding to IP address 1 is identification information 1, the identification information of the UE corresponding to IP address 2 is identification information 2, and the identification information of the UE corresponding to IP address 3 is The identification information of is identification information 3.
  • Table 1 is used as an example and does not limit the specific realization of the corresponding relationship between the IP address of the UE and the identification information of the UE maintained by the TNGF.
  • step S314 is an optional step, which is indicated by a dotted line in FIG. 3 .
  • the TNGF may also acquire the correspondence between the IP address of the UE and the identification information of the UE in other ways, which is not limited in this embodiment of the present application.
  • S315 The TNGF and the AMF send an N2 connection establishment request message.
  • the AMF receives the N2 connection establishment request message.
  • the N2 connection establishment request message is used to establish the N2 connection between the TNGF and the AMF for the UE.
  • S316 The AMF sends an N2 connection establishment response message to the TNGF.
  • the TNGF receives the N2 connection establishment response message.
  • the N2 connection establishment response message is used to indicate that the establishment of the N2 connection established for the UE is completed.
  • the N2 connection establishment response message may include a registration completed NAS message.
  • the registration completed NAS message is used to indicate that the UE has successfully registered.
  • S317 The TNGF sends a third data packet to the UE.
  • the UE receives the third data packet.
  • TNGF decapsulates the N2 message to obtain the registered NAS message, encapsulates the registered NAS message according to the GTP-U/UDP/IP encapsulation method, obtains the third data packet, and sends the Three data packets are sent to the UE.
  • TNGF encapsulates the GTP-U header outside the registered NAS message, fills the TEID in the GTP-U header as UE TEID_1; encapsulates the UDP header outside the GTP-U header; and encapsulates the IP header outside the UDP header, and Fill in the source IP address and the destination IP address in the IP packet header as the TNGF IP address 1 and the IP address of the UE respectively, to obtain the third data packet.
  • FIG. 4 shows a flow chart of a method for acquiring an IP address and a TEID for transmitting user plane data provided by an embodiment of the present application. As shown in Fig. 4, the method may include the following steps.
  • S401 The UE sends a session establishment request message to the TNGF.
  • the TNGF receives the PDU session establishment request message.
  • the UE initiates a PDU session establishment process, and sends a PDU session establishment request message (PDU session establishment request) to TNGF.
  • PDU session establishment request For example, the UE sends a PDU session establishment request message to the TNGF through the GTP-U tunnel.
  • the PDU session establishment request message is control plane data, and the UE can encapsulate the PDU session establishment request message according to the GTP-U/UDP/IP encapsulation method, obtain the encapsulated data packet, and send the encapsulated data packet to TNGF.
  • the UE encapsulates the GTP-U packet header outside the PDU session establishment request message, fills the TEID in the GTP-U with the TNGF TEID_1 obtained in the aforementioned step S311, encapsulates the PDU packet header outside the GTP-U packet header, and wraps the PDU packet header outside the PDU packet header.
  • the TNGF decapsulates it to obtain a PDU session establishment request message, and sends the PDU session establishment request message to the AMF, that is, executes the content shown in step S402.
  • the UE sends a PDU session establishment request message to the TNGF through the GTP-U tunnel.
  • the PDU session establishment request message is control plane data, and the UE can encapsulate the PDU session establishment request message according to the message/GTP-U/UDP/IP encapsulation method, obtain the encapsulated data packet, and send the encapsulated data packet Send to TNGF.
  • the UE takes the PDU session establishment request message as a parameter of the first message; encapsulates the GTP-U header outside the first message, fills the TEID in the GTP-U with the TNGF TEID_1 obtained in the aforementioned step S311, and uses the GTP-U
  • the message type field in the U header indicates the message type of the first message; then encapsulate the PDU header outside the GTP-U header, and encapsulate the IP header outside the PDU header, and fill in the source IP address and the destination IP address in the IP header respectively Obtain the encapsulated data packet for the IP address of the UE and the TNGF IP address 1 obtained in the aforementioned step S311. Further, after receiving the encapsulated data packet, the TNGF decapsulates it to obtain a PDU session establishment request message, and sends the PDU session establishment request message to the AMF, that is, executes the content shown in step S402.
  • the TNGF sends a PDU session establishment request message to the AMF.
  • the AMF receives the PDU session establishment request message.
  • the AMF network element performs a process of establishing a PDU session.
  • the AMF After the AMF receives the PDU session establishment request message, it can interact with other control plane network elements (such as AMF) and user plane network elements (UPF) to perform the PDU session establishment process.
  • AMF control plane network elements
  • UPF user plane network elements
  • S404 The AMF sends an N2 PDU session establishment request message to the TNGF.
  • TNGF receives the N2 PDU session establishment request message.
  • the N2 PDU session establishment request message includes a PDU session identification (PDU session ID).
  • the N2 PDU session establishment request message may also include a quality of service (quality of service, QoS) parameter related to the PDU session, a NAS message that the PDU session is successfully established, and the like.
  • QoS quality of service
  • S405 The TNGF sends a second request message to the UE.
  • the UE receives the second request message.
  • the second request message includes the PDU session identifier and TNGF TEID_2.
  • the second request message may also include TNGF IP address_2.
  • the TNGF may allocate a TEID of the TNGF to the UE according to the PDU session identifier, and carry the TEID of the TNGF in the second request message and send it to the UE.
  • the TNGF may also assign an IP address of the TNGF to the UE according to the PDU session identifier, and send the IP address of the TNGF to the UE in the second request message.
  • the TEID of TNGF is the TEID (i.e.
  • the UE After receiving the second request message, the UE stores the TNGF TEID_2 and the TNGF IP address 2, so as to subsequently send the user plane data of the PDU session to the TNGF through the GTP-U tunnel.
  • S406 The UE sends a second response message to the TNGF.
  • the TNGF receives the second response message.
  • the second response message includes UE TEID_2.
  • the UE may allocate the TEID of the UE to the TNGF, and carry the TEID of the UE in the second response message and send it to the UE.
  • the TEID of the UE is the TEID (that is, UE TEID_2) that is subsequently used to transmit the user plane data of the PDU session.
  • the TNGF stores the UE TEID_2, so as to subsequently send the user plane data of the PDU session to the UE through the GTP-U tunnel.
  • the second response message may also include the IP address of the UE, and the IP address may be the IP address obtained by the UE in the aforementioned step S313, or the IP address obtained by the UE in other ways. This is not limited.
  • a GTP-U tunnel can be established between the UE and the TNGF, and information for subsequently transmitting user plane data of the PDU session, such as TNGF IP address 2, TNGF TEID_2, and UE TEID_2, can be negotiated.
  • the length of the header of the data packet encapsulated based on the GTP-U encapsulation mode is shorter than that based on the Psec encapsulation mode, which can reduce the problems of waste of transmission resources, time extension, and high power consumption of equipment caused by the IPsec encapsulation mode.
  • the second response message sent by the UE to the TNGF includes UE TEID_2.
  • the second response message may not include UE TEID_2.
  • the UE TEID_2 may be a pre-configured fixed value. That is, the UE TEID_2 may or may not be included in the second response message, which is not limited in this embodiment of the present application.
  • UE TEID_1 and UE TEID_2 may be the same or different, which is not limited in this embodiment of the present application.
  • the TNGF sends a NAS message indicating that the PDU session is established successfully to the UE.
  • the UE receives the NAS message indicating that the PDU session is established successfully.
  • the NAS message that the PDU session is successfully established is control plane data
  • TNGF encapsulates the NAS message that the PDU session is successfully established according to the encapsulation method of GTP-U/UDP/IP, obtains the encapsulated data packet, and converts the encapsulated The data packet is sent to UE.
  • step S407 reference may be made to the description of the aforementioned step S317, which will not be repeated here.
  • the TNGF sends an N2 PDU session establishment response message to the AMF.
  • the AMF receives the N2 PDU session establishment response message.
  • step S408 the AMF interacts with other network elements to continue the process of establishing the PDU session until the establishment of the PDU session is completed, and the implementation process will not be repeated here.
  • one or more PDU sessions can be established between TNGF and UE.
  • the TNGF may allocate multiple TNGF TEID_2 to the multiple PDUs, and the UE may allocate multiple UE TEID_2 to the multiple PDUs.
  • each TNGF TEID_2 in a plurality of TNGF TEID_2 is different, namely TNGF can allocate different TEIDs for different PDU sessions.
  • Multiple UE TEID_2 can be the same or different, that is, the UE can allocate the same TEID or different TEIDs for different PDU sessions.
  • the following description will be made by taking the establishment of a PDU session between the TNGF and the UE as an example.
  • the UE encapsulates the GTP-U header outside the payload.
  • the UE may encapsulate the GTP-U header outside the first message, and the payload is a parameter of the first message (that is, the first message includes the payload).
  • the GTE-U header may also include the first message and a message type (message type) field.
  • the message type field may be used to indicate the message type of the first message. For example, when the load is control plane data, the value of the message type field is the first value; when the load is user plane data, the value of the message type field is the second value, and the message type field can be used to indicate the first value
  • the message type of a message when the load is control plane data, the value of the message type field is the first value; when the load is user plane data, the value of the message type field is the second value, and the message type field can be used to indicate the first value
  • the message type of a message when the load is control plane data, the value of the message type field is the first
  • the message type field is used to indicate that the payload encapsulated in the GTP header is user plane data or control plane data, that is, regardless of the payload encapsulated in the GTP header Whether it is user plane data or control plane data, the message type field remains unchanged.
  • the message type field is used to indicate the message type of the first message encapsulated in the GTP header, the first message includes control plane data, and the control plane data is NAS message and other information on the access side at least one of parameters etc.
  • the message type field ie, the second value
  • the message type field may be used to indicate the message type of the first message.
  • the second value is 256
  • the message type of the first message can be a GTP-U message (GTP-U message); or, the second value is 257, and the message type of the first message can be a GTP-U request message (GTP-U request message); or, the second value is 258, and the message type of the first message may be a GTP-U response message (GTP-U response message), etc.
  • the embodiment of the present application is not limited thereto.
  • the parameters and control plane data between TNGF and UE can be encapsulated in a GTP-U packet header for interaction, which can reduce the number of signaling interactions between TNGF and UE and improve the utilization of network resources.
  • FIG. 5 shows another schematic flow diagram for obtaining an IP address and a TEID for transmitting user plane data.
  • steps 502, S503, S504, and S507 in FIG. 5 are respectively the same as steps S402, S403, S404, and S408 in FIG. 4, the difference is that:
  • S501 The UE sends a GTP-U message to the TNGF.
  • the TNGF receives the GTP-U message.
  • the GTP-U message includes a PDU session establishment request message.
  • the UE initiates the PDU session establishment process, and the UE can encapsulate the PDU session establishment request message according to the encapsulation method in step S401, that is, the PDU session establishment request message is encapsulated in the GTP-U packet header, the GTP-U packet header is encapsulated in the UDP packet header, and the UDP packet header Encapsulated in the IP header.
  • the message type field in the GTP-U header can be 255.
  • the UE may also use the PDU session establishment request message as a parameter of the first message, and encapsulate the first message in a message/GTP-U/UDP/IP encapsulation manner.
  • the first message may be a GTP-U message.
  • the UE encapsulates the PDU session establishment request message in the GTP-U message; encapsulates the GTP-U header outside the GTP-U message, and fills the message type field in the GTP-U header with 256; and then in the GTP-U header Encapsulate the UDP header and encapsulate the IP header outside the UDP header.
  • the message type field in the GTP-U header can be 256.
  • the TEID in the GTP-U header is TNGF TEID_1
  • the destination IP address in the IP header is TNGF IP address 1.
  • the TNGF may determine that the received uplink information is control plane data according to at least one of the TEID in the GTP-U header and the destination IP address in the IP header. Further, when the message type field is 255, TNGF can determine that the content carried by the GTP-U header is control plane data; when the message type field is 256, TNGF can determine that the content carried by the GTP-U header is a GTP-U message , and then the TNGF continues to parse the GTP-U message to obtain control plane data (ie, the PDU session establishment request message).
  • control plane data ie, the PDU session establishment request message
  • S505 The TNGF sends a GTP-U request message to the UE.
  • the UE receives the GTP-U request message.
  • the GTP-U request message includes the NAS message that the PDU session is established successfully, and the TNGF IP address 2 and TNGF TEID_2 used to transmit the user plane data of the PDU.
  • the TNGF may use the NAS message that the PDU session is established successfully as a parameter of the third message, and encapsulate the third message according to the message/GTP-U/UDP/IP encapsulation manner.
  • the third message may be a GTP-U request message.
  • TNGF can encapsulate the NAS message of successful PDU session establishment, TNGF IP address 2 and TNGF TEID_2 in the GTP-U request message; encapsulate the GTP-U packet header outside the GTP-U request message, and wrap the GTP-U packet header in the GTP-U packet header Fill in the message type field as 257; then encapsulate the UDP header outside the GTP-U header, and encapsulate the IP header outside the UDP header.
  • the TEID in the GTP-U header is UE TEID_1
  • the destination IP address in the IP header is TNGF IP address 1.
  • the UE may determine that the received downlink information is control plane data according to at least one of the TEID in the GTP-U header and the source IP address in the IP header.
  • the message type field is 257, and the UE can determine that the content carried by the GTP-U header is a GTP-U request message, and then the UE continues to parse the GTP-U request message to obtain the control plane data (that is, the NAS message that the PDU session is successfully established) and parameters (i.e. TNGF IP address 2 and TNGF TEID_2).
  • S506 The UE sends a GTP-U response message to the TNGF.
  • the TNGF receives the GTP-U response message.
  • the GTP-U response message includes UE TEID_2.
  • the UE may also encapsulate UE TEID_2 in a GTP-U response message, encapsulate the GTP-U response message in a GTP-U header, encapsulate the GTP-U header in a UDP header, and encapsulate the UDP header in an IP header.
  • the message type field in the GTP-U header can be 258.
  • the TEID in the GTP-U header is TNGF TEID_1
  • the destination IP address in the IP header is TNGF IP address 1.
  • the TNGF may determine that the received uplink information is control plane data according to at least one of the TEID in the GTP-U header and the destination IP address in the IP header.
  • the message type field is 258, and TNGF can determine that the content carried by the GTP-U header is a GTP-U response message, and then TNGF continues to parse the GTP-U response message to obtain parameters (ie, UE TEID_2).
  • the UE sends the first data packet to the TNGF through the GTP-U tunnel.
  • the TNGF may execute the contents shown in step S202 to step S204.
  • the TNGF determines whether the first load is control plane data or user plane data according to at least one of the IP address of the TNGF and the TEID of the TNGF. If the TNGF determines that the first payload is user plane data, the TNGF executes the content shown in step S203; if the TNGF determines that the first payload is control plane data, the TNGF executes the content shown in step S204.
  • the TNGF After receiving the first data packet, the TNGF parses it to obtain the IP address of the TNGF, the TEID of the TNGF and the first payload in the first data packet. Further, the TNGF may determine whether the first load is control plane data or user plane data according to at least one of the IP address of the TNGF and the TEID of the TNGF.
  • TNGF can compare the IP address of TNGF in the first data packet with the TNGF IP address 1 in the aforementioned step S311 and the TNGF IP address 2 in the aforementioned step S405, or compare the TNGF in the first data packet
  • the TEID is compared with the TNGF TEID_1 in the aforementioned step S311 and the TNGF TEID_2 in the aforementioned step S405 to determine whether the first load is control plane data or user plane data.
  • TNGF can determine that the first load is control plane data; or, the IP address of TNGF is TNGF IP address 1, then TNGF can determine that the first load is control plane data; or, the TEID of TNGF is TNGF TEID_1, and the IP address of TNGF is TNGF IP address 1, then TNGF can determine that the first load is control plane data.
  • TNGF can determine that the first load is user plane data; or, if the IP address of TNGF is TNGF IP address 2, then TNGF can determine that the first load is user plane data; or, TNGF's TEID is TNGF TEID_2, and the IP address of TNGF is TNGF IP address 2, then TNGF can determine that the first load is user plane data.
  • the first IP packet header includes the IP address of the UE
  • the TNGF can determine the identification information of the UE according to the IP address of the UE and the correspondence between the IP address of the UE and the identification information of the UE, and Determine the context information of the UE according to the identification information of the UE.
  • the UE context information includes UE identification information, UE N2 interface identification, N2 interface information, N3 interface information, and the like.
  • the N2 interface information can be used to determine the control plane network element that establishes the N2 connection for the UE
  • the N3 interface information can be used to determine the user plane network element that establishes the N3 connection for the UE.
  • the first load is control plane data
  • the TNGF can determine the control plane network element that establishes the N2 connection for the UE according to the context information of the UE, and then send the first load to the control plane network element through the N2 connection
  • the TNGF may determine the user plane network element that establishes the N3 connection for the UE according to the context information of the UE, and then send the first load to the user plane network element through the N3 connection
  • Fig. The user plane network element is UPF as an example).
  • S203 The TNGF sends the first payload to the UPF.
  • the UPF receives the first load.
  • the TNGF may send the first payload to the UPF through the N3 connection.
  • the TNGF sends the first payload to the AMF.
  • the AMF receives the first load.
  • the TNGF may send the first payload to the AMF through the N2 connection.
  • Steps S201 to S204 described above describe a specific implementation process for the TNGF to distinguish whether uplink information is control plane data or user plane data in the uplink direction.
  • Steps S205a to S208 a specific implementation process for the UE to distinguish whether downlink information is control plane data or user plane data in the downlink direction is introduced.
  • S205a The UPF sends the second payload to the TNGF.
  • S205b The AMF sends the second payload to the TNGF.
  • the TNGF receives the second load.
  • the second payload may be user plane data or control plane data.
  • the TNGF may receive the second load from the UPF through the N3 connection, as shown in step S205a.
  • the second load is control plane data
  • the TNGF may receive the second load from the control plane network element (the AMF is taken as an example in FIG. 2 ) through the N2 connection, as shown in step S205b.
  • step S205b is an optional step, which is indicated by a dotted line in FIG. 2 .
  • the second load may be control plane data received by the TNGF from other control plane network elements, or may be generated by the TNGF itself.
  • S206 The TNGF generates a second data packet according to the second payload.
  • the second data packet includes a second IP header, a second GTP-U header and a second payload.
  • the second payload is encapsulated with a second GTP-U header
  • the second GTP-U header is encapsulated with a second UDP header
  • the second UDP header is encapsulated with a second IP header.
  • the TNGF may encapsulate the second GTP-U header outside the second payload, encapsulate the second UDP header outside the second GTP- header, and encapsulate the second IP header outside the second UDP header, to obtain the second data packet.
  • the second IP packet header includes a destination IP address and a source IP address, and the destination IP address and the source IP address are respectively the IP address of the UE and the IP address of the TNGF.
  • the second GTP-U header includes the TEID of the UE.
  • the IP address of TNGF can be the IP address allocated by TNGF for transmitting control plane data (denoted as TNGF IP address 1), or the IP address allocated by TNGF for transmitting user plane data (denoted as TNGF IP address 2).
  • the TEID of the UE may be the TEID allocated by the UE for transmission of control plane data (denoted as UE TEID_1), or the TEID allocated by the UE for transmission of user plane data (denoted as UE TEID_2). At least one of the IP address of the TNGF and the TEID of the UE may be used to identify whether the second load is control plane data or user plane data.
  • the TEID of the UE is the TEID allocated by the UE for transmitting the control plane data.
  • the TNGF may encapsulate the second payload according to the GTP-U/UDP/IP encapsulation manner, and fill in the TEID in the GTP-U header as UE TEID_1 to indicate that the second payload is control plane data.
  • the IP address of the TNGF is an IP address allocated by the TNGF for transmitting the control plane data.
  • TNGF can encapsulate the second payload according to the GTP-U/UDP/IP encapsulation method, and fill in the source IP address in the IP packet header as TNGF IP address 1 to indicate that the second payload is control plane data.
  • the TEID of the UE is the TEID allocated by the UE for transmission of the control plane data
  • the IP address of the TNGF is the IP address allocated by the TNGF for transmission of the control plane data.
  • TNGF can encapsulate the second payload according to the GTP-U/UDP/IP encapsulation method, fill in the TEID in the GTP-U header as UE TEID_1, and fill in the source IP address in the IP header as TNGF IP Address 1, to indicate that the second payload is control plane data.
  • the TEID of the UE is the TEID allocated by the UE for transmitting user plane data.
  • the TNGF may encapsulate the second payload according to the GTP-U/UDP/IP encapsulation manner, and fill in the TEID in the GTP-U header as UE TEID_2 to indicate that the second payload is user plane data.
  • the IP address of the TNGF is an IP address allocated by the TNGF for transmitting user plane data.
  • TNGF can encapsulate the second payload according to the encapsulation method of GTP-U/UDP/IP, and fill in the source IP address in the IP packet header as TNGF is TNGF IP address 2, to indicate that the second payload is the user plane data.
  • the TEID of the UE is the TEID allocated by the UE for transmitting user plane data
  • the IP address of the TNGF is the IP address allocated by the TNGF for transmitting user plane data.
  • TNGF can encapsulate the second payload according to the GTP-U/UDP/IP encapsulation method, fill in the TEID in the GTP-U header as UE TEID_2, and fill in the source IP address in the IP header as TNGF IP Address 2, to indicate that the second payload is user plane data.
  • S207 The TNGF sends the second data packet to the UE.
  • the UE receives the second data packet.
  • the TNGF sends the second data packet to the UE through the GTP-U tunnel.
  • the UE determines according to at least one of the IP address of the TNGF and the TEID of the UE that the second load is control plane data or user plane data.
  • the UE After receiving the second data packet, the UE parses it to obtain the IP address of the TNGF, the TEID of the UE, and the second payload in the second data packet. Further, the UE may determine whether the second load is control plane data or user plane data according to at least one of the IP address of the TNGF and the TEID of the UE.
  • the UE can compare the IP address of the TNGF in the second data packet with the TNGF IP address 1 in the aforementioned step S311 and the TNGF IP address 2 in the aforementioned step S405, or compare the IP address of the UE in the second data packet
  • the TEID is compared with the UE TEID_1 in the aforementioned step S312 and the UE TEID_2 in the aforementioned step S406 to determine whether the second load is control plane data or user plane data.
  • the UE can determine that the second load is control plane data; or, the IP address of the TNGF is TNGF IP address 1, then the UE can determine that the second load is control plane data; or, the TEID of the UE is UE TEID_1, and the IP address of TNGF is TNGF IP address 1, then the UE can determine that the second load is control plane data.
  • the UE may determine that the second load is user plane data; or, the IP address of the TNGF is TNGF IP address 2, then the UE may determine that the second load is user plane data; or, the UE's TEID is UE TEID_2, and the IP address of TNGF is TNGF IP address 2, then the UE can determine that the second load is user plane data.
  • FIG. 14 shows a schematic flowchart of a communication method provided by an embodiment of the present application.
  • both the first load and the second load are control plane data.
  • this embodiment introduces the communication method provided by this embodiment from the downlink direction and the uplink direction respectively.
  • the TEID allocated by TNGF for transmission control plane data is recorded as TNGF TEID_1
  • the IP address allocated by TNGF for transmission control plane data is recorded as TNGF IP address 1.
  • the encapsulation method in which the GTP-U header is encapsulated outside the payload, the UDP header is encapsulated outside the GTP-U header, and the IP header is encapsulated outside the UDP header is denoted as GTP-U/UDP/IP.
  • steps S1401-S1410 and S1411-S1414 in this embodiment are respectively the same as steps S301-S310 and S313-S316 in FIG. 3 , the difference is that:
  • S1415 The TNGF generates a second data packet.
  • the second data packet includes a second IP header, a second GTP-U header and a second payload.
  • the second payload is a registration completed NAS message.
  • the registered NAS message is encapsulated with a second GTP-U header
  • the second GTP-U header is encapsulated with a second UDP header
  • the second UDP header is encapsulated with a second IP header.
  • the TNGF decapsulates it to obtain a registered NAS message, and encapsulates the registered NAS message according to the GTP-U/UDP/IP encapsulation mode to obtain a second data packet.
  • TNGF encapsulates the second GTP-U header outside the registered NAS message, encapsulates the second UDP header outside the second GTP-header, and encapsulates the second IP header outside the second UDP header to obtain the second data packet .
  • the second IP packet header includes a destination IP address and a source IP address, and the destination IP address and the source IP address are respectively the IP address of the UE and the IP address of the TNGF.
  • the second GTP-U header includes the TEID of the TNGF.
  • the second payload is a registration completed NAS message, that is, the second payload is control plane data.
  • the IP address of the TNGF is TNGF IP address 1.
  • the TEID of TNGF is TNGF TEID_1.
  • the TNGF parses it to obtain a registration completed NAS message; and, according to the indication information received in step S1410, determines to establish a GTP-U tunnel with the UE, and determines to pass the GTP -
  • the U tunnel sends a NAS message of registration completion to the UE.
  • the TNGF can assign the IP address of the TNGF and the TEID of the TNGF to the UE, fill the IP address of the TNGF and the TEID of the TNGF into the second IP header and the second GTP-U header respectively, and follow the GTP-U/UDP/
  • the IP encapsulation method encapsulates the registered NAS message to obtain the second data packet.
  • the IP address of TNGF allocated by TNGF to UE is the IP address (i.e. TNGF IP address 1) for subsequent transmission of control plane data; TEID (i.e. TNGF TEID_1).
  • the TNGF may also determine the DSCP used for subsequent transmission of control plane data, and carry the DSCP in the second data packet and send it to the UE.
  • the IP address of the UE may include an IP address used to transmit control plane data (denoted as UE IP address 1) and an IP address used to transmit user plane data (denoted as UE IP address 2).
  • UE IP address 1 and the UE IP address 2 may be the same or different, which is not limited in this embodiment of the present application.
  • the IP address of the TNGF may include an IP address used to transmit control plane data (denoted as TNGF IP address 1) and an IP address used to transmit user plane data (denoted as TNGF IP address 2).
  • TNGF IP address 1 and the TNGF IP address 2 may be the same or different, which is not limited in this embodiment of the present application.
  • S1416 The TNGF sends the second data packet to the UE.
  • the UE receives the second data packet.
  • the TNGF sends the second data packet to the UE through the GTP-U tunnel.
  • S1417 The UE stores the TNGF IP address 1 and the TNGF TEID_1.
  • the UE may determine that TNGF IP address 1 is the IP address used to transmit control plane data, and determine that TNGF TEID_1 is the TEID used to transmit control plane data, and store the TNGF IP address 1 and the TNGF TEID_1. For example, after receiving the second data packet, the UE decapsulates it to obtain TNGF IP address 1, TNGF TEID_1 and the second payload. In this embodiment, the second payload is a registration completed NAS message.
  • the UE may determine that TNGF IP address 1 is the IP address used to transmit control plane data according to the NAS message of the registration completion, and determine that TNGF TEID_1 is the TEID used to transmit control plane data, and store the TNGF IP address 1 and the TNGF TEID_1, so that the UE can send control plane data to TNGF through the GTP-U tunnel based on TNGF IP address 1 and TNGF TEID_1.
  • the UE may obtain the DSCP by parsing the second data packet, and store the DSCP, so that the subsequent UE may send control plane data to the TNGF through the GTP-U tunnel based on the DSCP.
  • the TNGF may send a fourth data packet to the UE based on the TNGF IP address 1 and the TNGF TEID_1, where the fourth payload included in the fourth data packet is control plane data.
  • TNGF fills TNGF IP address 1 and TNGF TEID_1 into the IP header and GTP-U header respectively, and encapsulates the fourth load according to the GTP-U/UDP/IP encapsulation method to obtain the fourth data packet, and GTP-U The U tunnel sends the fourth data packet to the TNGF.
  • the UE parses it, and obtains the IP address of the TNGF, the TEID of the TNGF, and the fourth payload in the fourth data packet.
  • the UE may determine whether the fourth load is control plane data or user plane data according to at least one of the IP address of the TNGF and the TEID of the TNGF.
  • the IP address of the TNGF is TNGF IP address 1
  • the TEID of the TNGF is TNGF TEID_1.
  • the UE may determine that the fourth load is control plane data according to TNGF IP address 1, or according to TNGF TEID_1, or according to TNGF IP address 1 and TNGF TEID_1.
  • the UE may also determine whether the fourth payload is control plane data or user plane data by analyzing the fourth payload. That is, for the UE side, the UE can determine whether the fourth load is control plane data or user plane data through at least one of the IP address of the TNGF and the TEID of the TNGF, and can also determine whether the fourth load is control plane data or user plane data by analyzing the fourth load.
  • the user plane data is not limited in this embodiment of the application.
  • the TNGF sends the TNGF IP address 1 and TNGF TEID_1 to the UE through the registered NAS message, so that the UE can obtain the IP address and TEID allocated by the TNGF for the transmission control plane data.
  • TNGF does not need to assign TNGF IP address 1 and TNGF TEID_1 to UE through other messages (such as the extended authentication request message or 5G notification message in step S311), which can reduce the signaling interaction between TNGF and UE, and improve network resources. utilization rate.
  • TNGF can send control plane data to UE through GTP-U tunnel based on TNGF IP address 1 and TNGF TEID_1.
  • the UE sends control plane data to the TNGF through the GTP-U tunnel based on the TNGF IP address 1 and TNGF TEID_1.
  • S1418 The UE sends the first data packet to the TNGF.
  • the TNGF receives the first data packet.
  • the UE may send the first data packet to the TNGF through the GTP-U tunnel.
  • the first data packet includes a first IP header, a first GTP-U header and a first payload.
  • the first payload is control plane data, such as NAS messages (such as a PDU session establishment request, etc.).
  • the first payload is encapsulated with a first GTP-U header
  • the first GTP-U header is encapsulated with a first UDP header
  • the first UDP header is encapsulated with a first IP header.
  • the UE may encapsulate the first GTP-U header outside the first payload, encapsulate the first UDP header outside the first GTP-header, and encapsulate the first IP header outside the first UDP header, to obtain the first data packet , and send the first data packet to the TNGF through the GTP-U tunnel.
  • the first IP packet header includes a destination IP address and a source IP address, and the destination IP address and the source IP address are respectively the IP address of the TNGF and the IP address of the UE.
  • the first GTP-U header includes the TEID of the TNGF.
  • the IP address of TNGF is the IP address (denoted as TNGF IP address 1) that TNGF distributes for transmission control plane data; ). For example, the UE determines that the first payload sent to the TNGF is control plane data.
  • the UE may respectively fill in the first IP header and the first GTP-U header according to the TNGF IP address 1 and TNGF TEID_1 obtained in step S1417, and encapsulate the first load according to the GTP-U/UDP/IP encapsulation method , obtain the first data packet, and send the first data packet to the TNGF.
  • the TNGF determines according to at least one of the TNGF IP address 1 and the TNGF TEID_1 that the first payload is control plane data.
  • the TNGF After receiving the first data packet, the TNGF parses it to obtain the IP address of the TNGF, the TEID of the TNGF and the first load in the first data packet, and determines the first load according to at least one of the IP address of the TNGF and the TEID of the TNGF. Whether the load is control plane data or user plane data.
  • the IP address of the TNGF is TNGF IP address 1
  • the TEID of the TNGF is TNGF TEID_1.
  • the TNGF may determine that the first payload is control plane data according to TNGF IP address 1, or according to TNGF TEID_1, or according to TNGF IP address 1 and TNGF TEID_1.
  • S1420 The TNGF sends the first payload to the AMF.
  • the AMF receives the first load.
  • the TNGF may send the first payload to the AMF through the N2 connection.
  • FIG. 6 shows a schematic flowchart of a communication method provided by an embodiment of the present application. As shown in FIG. 6 , this embodiment introduces the communication method provided by the embodiment of the present application from the uplink direction and the downlink direction respectively.
  • GRE general routing encapsulation
  • S601 The UE sends a first data packet to the TNGF.
  • the TNGF receives the first data packet.
  • the UE may send the first data packet to the TNGF through the GRE tunnel.
  • the first data packet includes a first GRE protocol header and a first payload.
  • a GRE protocol header is encapsulated outside the first payload
  • a first IP header is encapsulated outside the first GRE protocol header.
  • the UE may encapsulate the first GRE protocol header outside the first payload, and encapsulate the first IP header outside the first GRE protocol header to obtain the first data packet, and send the first data packet to the TNGF through the GRE tunnel.
  • the first IP packet header includes a destination IP address and a source IP address, and the destination IP address and the source IP address are respectively the IP address of the TNGF and the IP address of the UE.
  • the first GRE protocol header includes a first GRE key (GRE key) and a first protocol type (protocol type) field.
  • Fig. 7 shows an example diagram of a GRE protocol packet header. As shown in FIG. 7 , the GRE protocol header includes 8 octets.
  • octet 1 of the GRE protocol header includes a check bit, a keyword (key) bit, and a sequence number (sequence number); octet 2 of the GRE protocol header includes a version number (version); octet 3-4 of the GRE protocol header is the protocol Type field; octet 5-8 of the GRE protocol header is the GRE key.
  • the check digit is used to indicate whether the checksum field is inserted into the GRE protocol header. If the check digit value is 0, it means that the GRE protocol header does not have a checksum field; if the check digit value is 1, Indicates that the checksum field is inserted into the header of the GRE protocol.
  • the keyword bit is used to indicate whether a GRE key is inserted in the GRE protocol header. If the keyword bit is 0, it means that the GRE protocol header has no GRE key; if the keyword bit is 1, it means that the GRE protocol header is inserted. Got the GRE key.
  • the first GRE key may be a keyword allocated by TNGF for transmitting control plane data, or the first GRE key includes a PDU session identifier.
  • the first protocol type field may be used to indicate that the first payload is control plane data. At least one of the first GRE key and the first protocol type field may be used to identify whether the first payload is control plane data or user plane data.
  • the first payload is control plane data
  • the first GRE key is a key assigned by TNGF for transmitting control plane data.
  • the UE can encapsulate the first payload according to the GRE/IP encapsulation method, and fill in the GRE key in the GRE protocol packet header as the keyword allocated by TNGF for the transmission control plane data, so as to indicate that the first payload is the control plane data.
  • the first payload is control plane data
  • the first protocol type field is used to indicate that the first payload is control plane data.
  • the UE may encapsulate the first payload in a GRE/IP encapsulation manner, and use the protocol type field in the GRE protocol packet header to indicate that the first payload is control plane data.
  • the protocol type field may be pre-defined, or pre-negotiated between the UE and the TNGF, etc., which is not limited in this embodiment of the present application.
  • the first load is control plane data
  • the first GRE key is a key allocated by TNGF for transmitting control plane data
  • the first protocol type field is used to indicate that the first load is control plane data.
  • the UE can encapsulate the first payload according to the GRE/IP encapsulation method, fill in the GRE key in the GRE protocol header as the keyword allocated by TNGF for the transmission control plane data, and use the protocol type field in the GRE protocol header Indicates that the first payload is control plane data.
  • the first payload is user plane data of a PDU session
  • the first GRE key includes the PDU session identifier.
  • the UE may encapsulate the first payload according to the GRE/IP encapsulation method, and fill in the GRE key in the GRE protocol header as the PDU session identifier, so as to indicate that the first payload is user plane data of the PDU session.
  • Figure 8 shows an example diagram of a GRE key. As shown in Figure 8, the UE can fill in the octet 6 of the GRE key as the PDU session identifier.
  • octet 5 of GRE key includes QoS flow ID (QoS flow ID, QFI), which is used to identify the QoS flow in the PDU session;
  • octet 8 of GRE key includes reflective QoS indicator (reflective QoS indicator, RQI), which is used for data QoS control of packets.
  • the UE can identify whether the first payload is control plane data or user plane data through the GRE key field or the protocol type field in the GRE protocol header.
  • the UE may negotiate with the TNGF to obtain the key allocated by the TNGF for transmitting control plane data.
  • the UE may receive a first request message from the TNGF, where the first request message includes a key allocated by the TNGF for transmitting control plane data.
  • FIG. 9 shows a flow chart of a method for acquiring keywords used for transmitting control plane data provided by an embodiment of the present application. Wherein, steps S901 to S910, S913 to S916 in FIG. 9 are respectively the same as steps S301 to S310, S313 to S316 in FIG. 3, the difference is that:
  • S911 The TNGF sends a first request message to the UE.
  • the UE receives the first request message.
  • the first request message may be an extended authentication request message or a 5G notification message.
  • the first request message includes TNGF IP address 1, GRE key and DSCP for transmitting control plane data.
  • the TNGF determines that there is no need to establish an IPsec tunnel with the UE. Further, the TNGF may determine to establish a GRE tunnel with the UE. Specifically, TNGF allocates TNGF IP address 1, GRE key and DSCP for the UE to transmit control plane data, and carries TNGF IP address 1, GRE key and DSCP in the extended authentication request message (or 5G notification message) sent to the UE.
  • the UE After receiving the extended authentication request message (or 5G notification message), the UE stores TNGF IP address 1, GRE key and DSCP, so as to send control plane data to TNGF through the GRE tunnel.
  • the first request message may also include the TNGF IP address 2 used to transmit user plane data.
  • TNGF can allocate TNGF IP address 2 for transmitting user plane data to UE during the registration process, such as carrying TNGF IP address 2 in the first request message and sending it to UE; or, TNGF can also establish PDU session TNGF IP address 2 for transmitting user plane data is allocated to the UE, as shown in the aforementioned step S405.
  • S912 The UE sends a first response message to the TNGF.
  • the TNGF receives the first response message.
  • the first response message may be an extended authentication response message or a 5G notification message.
  • the UE may send the first response message to the TNGF.
  • S917 The TNGF sends the third data packet to the UE.
  • the UE receives the third data packet.
  • TNGF decapsulates it to obtain the registered NAS message, encapsulates the registered NAS message according to the GRE/IP encapsulation method, obtains the third data packet, and sends the third data packet to UE.
  • TNGF encapsulates the GRE protocol header outside the registered NAS message, and fills in the GRE key in the GRE protocol header as the keyword allocated by TNGF for the transmission control plane data (and/or, using the protocol type field of the GRE protocol header to indicate The GRE protocol header includes control plane data); and encapsulate the IP header outside the GRE protocol header, and fill in the source IP address and the destination IP address in the IP header as TNGF IP address 1 and the IP address of the UE respectively, to obtain the third data Bag.
  • the UE sends the first data packet to the TNGF through the GRE tunnel.
  • the TNGF may execute the contents shown in step S602 to step S604.
  • the TNGF determines whether the first payload is control plane data or user plane data according to at least one of the first GRE key and the first protocol type field. If the TNGF determines that the first payload is user plane data, the TNGF executes the content shown in step S603; if the TNGF determines that the first payload is control plane data, the TNGF executes the content shown in step S604.
  • the TNGF After receiving the first data packet, the TNGF parses it to obtain the first GRE key, the first protocol type field and the first load in the first data packet. Further, the TNGF may determine whether the first payload is control plane data or user plane data according to at least one of the first GRE key and the first protocol type field. For example, the TNGF can determine whether the first load is control plane data by comparing the first GRE key with the GRE key acquired in the aforementioned step S911.
  • TNGF can determine that the first load is control plane data; or, the first protocol type field is used to indicate that the first load is control plane data, then TNGF can determine The first load is control plane data; or, the first GRE key is the GRE key obtained in the aforementioned step S911, and the first protocol type field is used to indicate that the first load is control plane data, then the TNGF can determine that the first load is control plane data. surface data.
  • the first GRE key includes a PDU session identifier, then the TNGF may determine that the first load is user plane data of the PDU session.
  • the first IP packet header includes the IP address of the UE
  • the TNGF can determine the identification information of the UE according to the IP address of the UE and the correspondence between the IP address of the UE and the identification information of the UE, and The context information of the UE is determined according to the identification information of the UE.
  • the description corresponding to the aforementioned step S202 which will not be repeated here.
  • S603 The TNGF sends the first payload to the UPF.
  • the UPF receives the first load.
  • the TNGF may send the first payload to the UPF through the N3 connection.
  • the TNGF sends the first payload to the AMF.
  • the AMF receives the first load.
  • the TNGF may send the first payload to the AMF through the N2 connection.
  • Steps S601 to S604 described above describe the specific implementation process of TNGF distinguishing whether uplink information is control plane data or user plane data in the uplink direction.
  • steps S605a to S608 the specific implementation process of UE distinguishing whether downlink information is control plane data or user plane data in the downlink direction is introduced.
  • S605a The UPF sends the second payload to the TNGF.
  • S605b The AMF sends the second payload to the TNGF.
  • the TNGF receives the second load.
  • step S605a and step S605b for the specific implementation process of step S605a and step S605b, reference may be made to the corresponding descriptions of the foregoing steps S205a and S205b, which will not be repeated here.
  • S606 The TNGF generates a second data packet.
  • the second data packet includes a second GRE protocol header and a second payload.
  • the second payload is encapsulated with a second GRE protocol header
  • the second GRE protocol header is encapsulated with a second IP header.
  • the TNGF may encapsulate the second GRE protocol header outside the second payload, and encapsulate the second IP header outside the second GRE protocol header to obtain the second data packet, and send the second data packet to the UE through the GRE tunnel.
  • the second IP packet header includes a destination IP address and a source IP address, and the destination IP address and the source IP address are respectively the IP address of the UE and the IP address of the TNGF.
  • the second GRE protocol packet header includes a second GRE key and a second protocol type field.
  • the second GRE key may be a keyword allocated by TNGF for transmitting control plane data, or the second GRE key includes a PDU session identifier.
  • the second protocol type field may be used to indicate that the second payload is control plane data. At least one of the second GRE key and the second protocol type field may be used to identify whether the second payload is control plane data or user plane data.
  • the second GRE key is a key allocated by TNGF for transmitting control plane data.
  • TNGF can encapsulate the second payload according to the GRE/IP encapsulation method, and fill in the GRE key in the GRE protocol header as the keyword allocated by TNGF for the transmission control plane data, so as to indicate that the second payload is the control plane data.
  • the second protocol type field is used to indicate that the second payload is control plane data.
  • the TNGF may encapsulate the second payload in a GRE/IP encapsulation manner, and use the protocol type field in the GRE protocol packet header to indicate that the second payload is control plane data.
  • the second GRE key is a key allocated by TNGF for transmitting control plane data
  • the second protocol type field is used to indicate that the second load is control plane data.
  • TNGF can encapsulate the second payload according to the GRE/IP encapsulation method, fill in the GRE key in the GRE protocol header as the keyword allocated by TNGF for the transmission control plane data, and use the protocol type field in the GRE protocol header Indicates that the second payload is control plane data.
  • the second GRE key when the second payload is user plane data of a PDU session, the second GRE key includes the PDU session identifier.
  • the TNGF can encapsulate the second payload according to the GRE/IP encapsulation method, and fill in the GRE key in the GRE protocol header as the PDU session identifier, so as to indicate that the second payload is the user plane data of the PDU session.
  • the TNGF sends the second data packet to the UE.
  • the UE receives the second data packet.
  • the TNGF sends the second data packet to the UE through the GRE tunnel.
  • the UE determines, according to at least one of the second GRE key and the second protocol type field, whether the second payload is control plane data or user plane data.
  • the UE After receiving the second data packet, the UE parses it to obtain the second GRE key, the second protocol type field and the second payload in the second data packet. Further, the UE may determine whether the second payload is control plane data or user plane data according to at least one of the second GRE key and the second protocol type field. For example, the UE may determine whether the first load is control plane data by comparing the second GRE key with the GRE key obtained in the aforementioned step S911.
  • the UE may determine that the second load is control plane data; or, the second protocol type field is used to indicate that the second load is control plane data, then the UE may determine The second load is control plane data; or, the second GRE key is the GRE key obtained in the aforementioned step S911, and the second protocol type field is used to indicate that the second load is control plane data, then the UE may determine that the second load is control plane data. surface data.
  • the second GRE key includes the PDU session identifier, the UE may determine that the second payload is user plane data of the PDU session.
  • FIG. 10 shows a schematic flowchart of a communication method provided by an embodiment of the present application. As shown in FIG. 10 , this embodiment introduces the communication method provided by the embodiment of the present application from the uplink direction and the downlink direction respectively.
  • the payload is encapsulated in the GRE protocol header, and the encapsulation method in which the GRE protocol header is encapsulated in the IP header is denoted as GRE/IP; the payload is encapsulated in the TCP header, and the TCP header is encapsulated in the IP header.
  • the method is recorded as TCP/IP; and the encapsulation method of encapsulating the payload in the GRE protocol header, the GRE protocol header in the TCP header, and the TCP header in the IP header is recorded as GRE/TCP/IP.
  • S1001 The UE sends a first payload to the TNGF.
  • the TNGF receives the first load.
  • the first payload is encapsulated with a first TCP header
  • the first TCP header is encapsulated with a first IP address.
  • the UE may encapsulate the first TCP header outside the first payload, and encapsulate the first IP header outside the first TCP header to obtain the encapsulated first payload, and send the encapsulated first payload to TNGF through the PCT connection. load.
  • the first TCP packet header includes a source port number and a destination port number, and the source port number and the destination port number are respectively the TCP port number of the UE and the TCP port number of the TNGF.
  • the TCP port number of the UE is a port number allocated by the UE for transmitting control plane data.
  • the TCP port number of the TNGF is a port number allocated by the TNGF for transmitting control plane data.
  • the first payload is encapsulated with a first GRE protocol header
  • the first GRE protocol header is encapsulated with a first IP address.
  • the UE may encapsulate the first GRE protocol header outside the first payload, and encapsulate the first IP header outside the first GRE protocol header, obtain the encapsulated first payload, and send the encapsulated first payload to the TNGF through the GRE tunnel.
  • the GRE keyword in the header of the first GRE protocol includes the PDU session identifier.
  • the encapsulation manner of the first payload includes encapsulating the first payload in the first TCP header, or encapsulating the first payload in the first GRE protocol header.
  • the encapsulation manner of the first payload may be used to identify whether the first payload is control plane data or user plane data. For example, when the first payload is control plane data, the first payload is encapsulated with a first TCP header.
  • the UE can encapsulate the first payload according to the TCP ⁇ IP encapsulation method, and fill in the source port number and the destination port number in the TCP packet header as the TCP port number of the UE and the TCP port number of the TNGF respectively, so as to identify the first payload.
  • One load is control plane data.
  • the first payload when the first payload is user plane data, the first payload is encapsulated with a first GRE protocol header.
  • the UE may encapsulate the first payload according to the GRE/IP encapsulation method, and fill in the GRE key in the GRE protocol header as the PDU session identifier, so as to identify that the first payload is the user plane data of the PDU session.
  • a GRE tunnel may be established between the UE and the TNGF, and the GRE tunnel is used to transmit user plane data.
  • the first payload is user plane data of the PDU session, and the UE may send the first data packet to the TNGF through the GRE tunnel.
  • the first payload is encapsulated with a first GRE protocol header, and the GRE key of the first GRE protocol header includes a PDU session identifier.
  • a TCP connection may be established between the UE and the TNGF, and the TCP connection is used to transmit control plane data.
  • the first payload is control plane data
  • the UE may send the first data packet to the TNGF through a TCP connection.
  • the TCP connection can be established between the UE and the TNGF in the following two ways.
  • TCP connection 1 an end-to-end TCP connection is established between the UE and the TNGF, which is denoted as TCP connection 1.
  • the IP address included in the IP header of the data packet transmitted on the TCP connection 1 is the IP address of the UE and the IP address of the TNGF.
  • UE may send a first data packet to TNGF through TCP connection 1, and the source IP address and destination IP address of the first IP header of the first data packet are the IP address of UE and the IP address of TNGF respectively.
  • mode 1 the data packets between the UE and the TNGF are transparently transmitted at the access node.
  • the UE In mode 2, the UE first establishes a TCP connection with the access node, denoted as TCP connection 2; the access node then establishes a TCP connection with the TNGF, denoted as TCP connection 3.
  • the IP address included in the IP header of the data packet transmitted on the TCP connection 2 is the IP address of the UE and the IP address of the access node.
  • the IP address included in the IP header of the data packet transmitted on the TCP connection 3 is the IP address of the access node and the IP address of the TNGF.
  • the UE may send the first payload to the TNGF through TCP connection 2 and TCP connection 3 .
  • the UE encapsulates the TCP header outside the first payload, encapsulates the IP header outside the TCP header, and fills in the source IP address and the destination IP address of the IP header as the IP address of the UE and the IP address of the access node respectively, to obtain the encapsulated
  • the access node receives the encapsulated first payload 1, and analyzes it to obtain the first payload
  • the access node Encapsulate the GRE protocol packet header outside the first load, encapsulate the GRE protocol packet header in the TCP packet header, encapsulate the IP packet header outside the TCP packet header, and fill in the source IP address and the destination IP address of the IP packet header as the IP address of the access node, respectively.
  • the IP address of the TNGF is used to obtain the encapsulated first payload 2 , and the encapsulated first payload 2 is sent to the TNGF through the TCP connection 3 .
  • the GRE key in the header of the GRE protocol is a key assigned by the access node to the UE.
  • the UE When the above method 2 is used to establish a TCP connection between the UE and the TNGF, in the uplink direction, the UE first encapsulates the control plane data according to the TCP/IP encapsulation method, and sends the encapsulated control plane data to the Access node: After receiving the control plane data, the access node encapsulates the control plane data according to the encapsulation method of GRE/TCP/IP, and sends the encapsulated control plane data to TNGF through TCP connection 3 .
  • TNGF In the downlink direction, TNGF first encapsulates the control plane data according to the GRE/TCP/IP encapsulation method, and sends the encapsulated control plane data to the access node through TCP connection 3; after the access node receives the control plane data, The control plane data is encapsulated according to the TCP/IP encapsulation method, and the encapsulated control plane data is sent to the UE through the TCP connection 2.
  • the specific implementation process is similar to that in the uplink direction, and will not be repeated here.
  • the first payload is encapsulated with the first TCP header, which may be: the first payload is encapsulated with the third GRE protocol header, and the third GRE protocol header is encapsulated with the first TCP header. That is, the access node encapsulates the third GRE protocol header outside the first payload, encapsulates the first TCP header outside the third GRE protocol header, and encapsulates the first IP header outside the first TCP header.
  • the GRE key in the third GRE protocol packet header is a keyword allocated by the access node to the UE, and is recorded as the third GRE key.
  • the UE may negotiate with the TNGF to obtain a port number allocated for transmitting control plane data. For example, the UE may receive a first request message from the TNGF, where the first request message includes a port number allocated by the TNGF for transmitting control plane data.
  • FIG. 11 shows a flowchart of a method for acquiring a port number used for transmitting control plane data provided by an embodiment of the present application. Wherein, steps S1101 to S1110, S1113, S1116, and S1117 in FIG. 11 are respectively the same as steps S301 to S310, S313, S315, and S316 in FIG. 3 , the difference is that:
  • S1111 The TNGF sends a first request message to the UE.
  • the UE receives the first request message.
  • the first request message may be an extended authentication request message or a 5G notification message.
  • the first request message includes the TNGF IP address 1 for transmitting control plane data and the TCP port number of the TNGF.
  • the TNGF determines that there is no need to establish an IPsec tunnel with the UE. Further, the TNGF may determine to establish a TCP connection with the UE. Specifically, the TNGF allocates the TNGF IP address 1 and the TCP port number of the TNGF for the UE to transmit control plane data, and carries the TNGF IP address 1 and the TCP port number of the TNGF in the extended authentication request message (or 5G notification message ) to the UE. After receiving the extended authentication request message (or 5G notification message), the UE stores the TNGF IP address 1 and the TCP port number of the TNGF, so as to send control plane data to the TNGF through the TCP connection subsequently.
  • the first request message may also include the TNGF IP address 2 used to transmit user plane data.
  • TNGF can allocate TNGF IP address 2 for transmitting user plane data to UE during the registration process, such as carrying TNGF IP address 2 in the first request message and sending it to UE; or, TNGF can also establish PDU session TNGF IP address 2 for transmitting user plane data is allocated to the UE, as shown in the aforementioned step S405.
  • S1112 The UE sends a first response message to the TNGF.
  • the TNGF receives the first response message.
  • the first response message may be an extended authentication response message or a 5G notification message.
  • the UE may send the first response message to the TNGF.
  • the first response message may include the TCP port number of the UE.
  • S1114 The access node sends a second message to the TNGF.
  • the TNGF receives the second message.
  • the second message includes the correspondence between the IP address of the UE and the identification information of the UE, or the correspondence between the third GRE key and the identification information of the UE, or the correspondence between the IP address of the UE and the identification information of the UE and the corresponding relationship between the third GRE key and the identification information of the UE.
  • the second message may be an AAA message.
  • the access node may assign a GRE key to the UE, record it as the third GRE key, and send the corresponding relationship between the third GRE key and the identification information of the UE to the TNGF in the AAA message. After the TNGF receives the second message, it stores the correspondence between the third GRE key and the identification information of the UE.
  • the corresponding relationship with the identification information of the UE determines the identification information of the UE that sends the uplink information.
  • Table 2 shows an example of the corresponding relationship between the GRE key maintained by the TNGF and the identification information of the UE.
  • TNGF establishes connections with three UEs.
  • the identification information of the UE corresponding to GRE key 1 is identification information 1
  • the identification information of the UE corresponding to GRE key 2 is identification information 2
  • the identification information of the UE corresponding to GRE key 3 is The identification information of is identification information 3.
  • Table 2 is used as an example and does not limit the specific implementation of the corresponding relationship between the GRE key maintained by the TNGF and the identification information of the UE.
  • GRE keys UE's identification information GRE key 1 Identification information 1
  • step S1114 is an optional step, which is indicated by a dotted line in FIG. 11 .
  • the TNGF may also obtain the correspondence between the GRE key and the identification information of the UE in other ways, which is not limited in this embodiment of the present application.
  • the correspondence between the IP address of the UE and the identification information of the UE reported by the access node to the TNGF reference may be made to the content corresponding to the aforementioned step S314, which will not be repeated here.
  • S1115 Establish a TCP connection between the UE and the TNGF.
  • the UE initiates a TCP connection to the TNGF, and a TCP connection is established between the UE and the TNGF, and the TCP connection is used to transmit control plane data.
  • the TCP connection can be established between the UE and the TNGF through the aforementioned two methods, which will not be repeated here.
  • S1118 The UE sends the third payload to the TNGF.
  • the TNGF receives the third load.
  • the UE may send the third payload to the TNGF through the GRE tunnel.
  • the UE may send the third load to the TNGF through TCP connection 1 (or TCP connection 2 and TCP connection 3).
  • the UE may send the third load to the TNGF through TCP connection 1 (or TCP connection 2 and TCP connection 3).
  • TCP connection 1 or TCP connection 2 and TCP connection 3
  • the UE may send the third load to the TNGF through TCP connection 1 (or TCP connection 2 and TCP connection 3).
  • TCP connection 1 or TCP connection 2 and TCP connection 3
  • the third package when the third payload is control plane data, the third package is encapsulated with a TCP header, and the source port number and destination port number of the TCP header are respectively the TCP port number of the UE and the TNGF port number. TCP port number.
  • the TNGF After receiving the encapsulated third payload, the TNGF parses it, obtains the TCP port number of the UE and stores it, so as to send control plane data to the UE through the TCP connection later.
  • the UE sends the first payload to the TNGF.
  • the TNGF may execute the contents shown in step S1102 to step S1104.
  • the TNGF determines whether the first payload is control plane data or user plane data according to the encapsulation manner of the first payload. If the TNGF determines that the first payload is user plane data, then the TNGF executes the content shown in step S1003; if the TNGF determines that the first payload is control plane data, then the TNGF executes the content shown in step S1004.
  • the TNGF After receiving the first data packet, the TNGF parses it to obtain the encapsulation mode of the first payload. Further, the TNGF may determine whether the first payload is control plane data or user plane data according to the encapsulation manner of the first payload. For example, if the first payload is encapsulated with a first TCP header, then TNGF can determine that the first payload is control plane data; or, the first payload is encapsulated with a third GRE protocol header, and the third GRE protocol header is encapsulated in the first TCP header , the TNGF can determine that the first payload is control plane data, wherein the GRE key in the third GRE protocol packet header includes the third GRE key.
  • the TNGF can determine that the first payload is user plane data of the PDU session.
  • the first IP packet header includes the IP address of the UE
  • the TNGF can determine the identification information of the UE according to the IP address of the UE and the correspondence between the IP address of the UE and the identification information of the UE, and The context information of the UE is determined according to the identification information of the UE.
  • the description corresponding to the aforementioned step S202 which will not be repeated here.
  • the first payload is control plane data
  • the first payload is encapsulated in the third GRE protocol header
  • the TNGF receives the first payload of the UE through TCP connection 1 and TCP connection 2
  • the TNGF can According to the GRE key of the third GRE protocol header and the corresponding relationship between the GRE key and the identification information of the UE, the identification information of the UE is determined, and the context information of the UE is determined according to the identification information of the UE.
  • the context information of the UE includes the identification information of the UE, the identification of the N2 interface of the UE, the information of the N2 interface and the information of the N3 interface.
  • the N2 interface information can be used to determine the control plane network element that establishes the N2 connection for the UE.
  • the TNGF can determine the control plane network element that establishes the N2 connection for the UE according to the context information of the UE, and then send the first load to the control plane network element through the N2 connection (Figure 2 takes the control plane network element as an example of AMF) .
  • S1003 The TNGF sends the first payload to the UPF.
  • the UPF receives the first load.
  • the TNGF may send the first payload to the UPF through the N3 connection.
  • the TNGF sends the first payload to the AMF.
  • the AMF receives the first load.
  • the TNGF may send the first payload to the AMF through the N2 connection.
  • steps S1001 to S1004 describe the specific implementation process of TNGF distinguishing uplink information as control plane data or user plane data in the uplink direction.
  • steps S605a to S608 the specific implementation process of UE distinguishing whether downlink information is control plane data or user plane data in the downlink direction is introduced.
  • S1005a The UPF sends the second payload to the TNGF.
  • S1005b The AMF sends the second payload to the TNGF.
  • the TNGF receives the second load.
  • step S1005a and step S1005b for the specific implementation process of step S1005a and step S1005b, reference may be made to the corresponding descriptions of the aforementioned steps S205a and S205b, which will not be repeated here.
  • the TNGF sends the second payload to the UE.
  • the UE receives the second payload.
  • the second payload is encapsulated with a second TCP header.
  • the TNGF can encapsulate the second TCP header outside the second payload, and encapsulate the second IP header outside the second TCP header to obtain the encapsulated second payload, and send the encapsulated second payload to the UE.
  • the second TCP packet header includes a source port number and a destination port number, and the source port number and the destination port number are respectively the TCP port number of the TNGF and the TCP port number of the UE.
  • the second IP packet header includes a source IP address and a destination IP address, and the source address and the destination IP address are respectively the TNGF IP address 1 and the IP address of the UE.
  • the second payload is control plane data
  • the second payload is encapsulated with the fourth GRE protocol header
  • the second payload is encapsulated with the second TCP header.
  • the TNGF may encapsulate the fourth GRE protocol header outside the second payload, encapsulate the second TCP header outside the fourth GRE protocol header, and encapsulate the second IP header outside the second TCP header to obtain the encapsulated second payload , and then send the encapsulated second payload to the access node through the TCP connection 3, and the access node forwards the second payload to the UE.
  • the GRE key of the fourth GRE protocol header includes the third GRE key.
  • the second TCP packet header includes a source port number and a destination port number, and the source port number and the destination port number are respectively the TCP port number of the TNGF and the TCP port number of the UE.
  • the second IP packet header includes a source IP address and a destination IP address, and the source address and the destination IP address are respectively the TNGF IP address 1 and the IP address of the UE.
  • the second payload is encapsulated with a second GRE protocol header.
  • the TNGF may encapsulate the second GRE protocol header outside the second payload, and encapsulate the second IP header outside the second GRE protocol header to obtain the encapsulated second payload, and transmit the encapsulated second payload through the GRE tunnel. sent to the UE.
  • the GRE key in the second GRE protocol header includes the PDU session identifier.
  • the second IP packet header includes a source IP address and a destination IP address, and the source address and the destination IP address are respectively the TNGF IP address 1 and the IP address of the UE.
  • S1007 The UE determines whether the second payload is control plane data or user plane data according to the encapsulation manner of the second payload.
  • the UE After receiving the encapsulated second payload, the UE analyzes it to obtain the encapsulation mode of the second payload. Further, the UE may determine whether the second payload is control plane data or user plane data according to the encapsulation manner of the second payload. For example, if the second payload is encapsulated with the second TCP header, the UE may determine that the second payload is control plane data. For another example, if the second payload is encapsulated with a second GRE protocol header, the UE may determine that the second payload is user plane data.
  • each of the above devices includes a corresponding hardware structure and/or software module for performing each function.
  • the present invention can be realized in the form of hardware or a combination of hardware and computer software in combination with the units and algorithm steps of each example described in the embodiments disclosed herein. Whether a certain function is executed by hardware or computer software drives hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art may use different methods to implement the described functions for each specific application, but such implementation should not be regarded as exceeding the scope of the present invention.
  • FIG. 12 is a schematic block diagram of a communication device 1200 provided by an embodiment of the present application, including a communication unit 1201 and a processing unit 1202 .
  • the communication unit 1201 is used for communicating with the outside, and may also be called a communication interface, a transceiver unit, or an input or output interface.
  • the processing unit 1202 may read data or instructions in the storage unit, so that the communication device 1200 implements the methods in the foregoing embodiments.
  • the communication device 1200 may be an access gateway or a chip in the access gateway.
  • the communication unit 1201 is configured to receive a first data packet from a terminal, the first data packet includes a first IP header, a first GTP-U header and a first payload, and the first IP header includes the access IP address of the gateway, the first GTP-U packet header includes the TEID of the access gateway.
  • the processing unit 1202 is configured to determine, according to at least one of the IP address of the access gateway and the TEID of the access gateway, whether the first payload is control plane data or user plane data.
  • the processing unit 1202 is configured to perform one or more of the following:
  • the TEID of the access gateway is the TEID allocated by the access gateway for transmitting the control plane data, it is determined that the first payload is the control plane data.
  • the TEID of the access gateway is the TEID allocated by the access gateway for transmitting the user plane data, it is determined that the first payload is the user plane data.
  • the IP address of the access gateway is the IP address allocated by the access gateway for transmitting the control plane data
  • the IP address of the access gateway is the IP address allocated by the access gateway for transmitting the user plane data
  • the TEID of the access gateway is the TEID allocated by the access gateway for transmitting the control plane data
  • the IP address of the access network is the TEID assigned by the access gateway for transmitting the control plane data
  • the assigned IP address determines that the first payload is the control plane data.
  • the TEID of the access gateway is the TEID allocated by the access gateway for transmitting the user plane data
  • the IP address of the access network is the TEID allocated by the access gateway for transmitting the user plane data
  • the assigned IP address is used to determine that the first load is the user plane data.
  • the first GTP-U packet header further includes a message type field
  • the first data packet further includes a first message
  • the first message includes the first payload; in the When the first payload is the control plane data, the message type field is used to indicate the message type of the first message.
  • the communication unit 1201 before the access gateway receives the first data packet from the terminal, the communication unit 1201 is configured to send a first request message to the terminal, where the first request message includes the TEID of the access gateway and the IP address of the access gateway, wherein the TEID of the access gateway is the TEID allocated by the access gateway for transmitting the control plane data.
  • the communication unit 1201 may also be configured to receive a first response message from the terminal, where the first response message includes the TEID of the terminal, and the TEID of the terminal is used by the terminal to transmit the control plane TEID for data allocation.
  • the method may further include: the communication unit 1201 is configured to send a second request message to the terminal, where the second request message includes a protocol data unit (PDU) session identifier and the connection The TEID of the ingress gateway, wherein the TEID of the access gateway is the TEID allocated by the access gateway for the user plane data of the PDU session.
  • the communication unit 1201 may also be configured to receive a second response message from the terminal, where the second response message includes the TEID of the terminal, and the TEID of the terminal is TEID allocated for user plane data.
  • the second request message further includes the IP address of the access gateway, where the IP address of the access gateway is allocated by the access gateway for the user plane data of the PDU session. IP address.
  • the communication unit 1201 before the access gateway receives the first data packet from the terminal, the communication unit 1201 is configured to receive indication information from an access and mobility management functional network element, where the indication information is used to indicate There is no need to establish an Internet security protocol tunnel between the access gateway and the terminal.
  • the first IP packet header further includes the IP address of the terminal
  • the processing unit 1202 is configured to The corresponding relationship between the information determines the identification information of the terminal; and determines the context information of the terminal according to the identification information of the terminal.
  • the communication unit 1201 is configured to receive a second message from the access node, where the second message includes a correspondence between the IP address of the terminal and the identification information of the terminal.
  • the communication unit 1201 is configured to send a second data packet to the terminal, where the second data packet includes a second IP header, a second GTP-U header, and a second payload, and the first The second IP header includes the IP address of the access gateway, and the second GTP-U header includes the TEID of the terminal; wherein, when the second load is the control plane data, the TEID of the terminal is The TEID allocated by the terminal for transmitting the control plane data, and/or the IP address of the access gateway is the IP address allocated by the access gateway for transmitting the control plane data; or, in the second When the load is the user plane data, the TEID of the terminal is the TEID allocated by the terminal for transmitting the user plane data, and/or the IP address of the access gateway is the IP address of the access gateway for transmitting the user plane data.
  • the IP address to which the data is assigned.
  • the communication unit 1201 is further configured to send a second data packet to the terminal, where the second data packet includes a second IP header, a second GTP-U header, and a second payload, and the The second IP header includes the IP address of the access gateway, and the second GTP-U header includes the TEID of the access gateway; wherein, the second load is the control plane data, and the access gateway The IP address of the access gateway is the IP address allocated by the access gateway for transmitting the control plane data, and the TEID of the access gateway is the TEID allocated by the access gateway for transmitting the control plane data.
  • the communication unit 1201 is configured to receive a first data packet from a terminal, the first data packet includes a first Generic Routing Encapsulation (GRE) protocol header and a first payload, and the first GRE protocol header includes a first GRE Keyword and first protocol type fields.
  • the processing unit 1202 is configured to determine, according to at least one of the first GRE keyword and the first protocol type field, whether the first payload is control plane data or user plane data.
  • GRE Generic Routing Encapsulation
  • the processing unit 1202 is configured to perform one or more of the following:
  • the access gateway When the first GRE key is a key allocated by the access gateway for transmitting the control plane data, determine that the first payload is the control plane data.
  • the first protocol type field when used to indicate that the first payload is the control plane data, determine that the first payload is the control plane data.
  • the first GRE keyword is a keyword allocated by the access gateway for transmitting the control plane data
  • the first protocol type field is used to indicate that the first payload is the control plane data
  • it is determined that the first load is the control plane data.
  • the first GRE keyword includes a protocol data unit (PDU) session identifier
  • PDU protocol data unit
  • the communication unit 1201 before the access gateway receives the first data packet from the terminal, the communication unit 1201 is configured to send a first request message to the terminal, where the first request message includes the The IP address of the Internet Protocol and the keyword allocated by the access gateway for transmitting the control plane data.
  • the communication unit 1201 before the access gateway receives the first data packet from the terminal, the communication unit 1201 is configured to receive indication information from an access and mobility management functional network element, where the indication information is used to indicate There is no need to establish an Internet security protocol tunnel between the access gateway and the terminal.
  • the first data packet further includes a first IP header
  • the first IP header includes the IP address of the terminal
  • the processing unit 1202 is configured to, according to the IP address of the terminal, and determining the identification information of the terminal according to the correspondence between the IP address of the terminal and the identification information of the terminal; and determining the context information of the terminal according to the identification information of the terminal.
  • the communication unit 1201 is configured to receive a second message from the access node, where the second message includes a correspondence between the IP address of the terminal and the identification information of the terminal.
  • the communication unit 1201 is configured to send a second data packet to the terminal, the second data packet includes a second GRE protocol header and a second payload, and the second GRE protocol header includes a first Two GRE keywords and a second protocol type field; wherein, when the second load is the control message, the second GRE keyword is a keyword allocated by the access gateway for transmitting the control plane data , and/or the second protocol type field is used to indicate that the second load is the control plane data; or, when the second load is user plane data of a PDU session, the second GRE keyword Include the PDU session identifier.
  • the communication unit 1201 is configured to receive the first payload from the terminal, where the first payload is encapsulated with a first Transmission Control Protocol (TCP) header, or the first payload is encapsulated with a first general routing encapsulation (GRE) protocol header.
  • the processing unit 1202 is configured to determine whether the first payload is control plane data or user plane data according to the encapsulation manner of the first payload.
  • the first TCP header includes the port number allocated by the access gateway for transmitting the control plane data
  • the GRE keyword in the first GRE protocol header includes a protocol data unit ( PDU) session identifier.
  • the processing unit 1202 is configured to perform one or more of the following:
  • the first payload is encapsulated with the first TCP header, it is determined that the first payload is the control plane data.
  • the first payload is encapsulated with the first GRE protocol header, it is determined that the first payload is user plane data of a PDU session.
  • the first TCP header is encapsulated outside the first payload, which may be: a third GRE protocol header is encapsulated outside the first payload, and a third GRE protocol header is encapsulated outside the third GRE protocol header. encapsulated in the first TCP header.
  • the third GRE protocol packet header includes a third GRE keyword
  • the third GRE keyword is a keyword allocated by the access node to the terminal
  • the processing unit 1202 is configured to The third GRE keyword, and the corresponding relationship between the third GRE keyword and the identification information of the terminal, determine the identification information of the terminal; and determine the identification information of the terminal according to the identification information of the terminal contextual information.
  • the communication unit 1201 is configured to receive a second message from the access node, where the second message includes a correspondence between the third GRE keyword and the identification information of the terminal.
  • the first TCP header is encapsulated with a first Internet Protocol header
  • the first GRE protocol header is encapsulated with a first IP header
  • the first IP header includes the The IP address of the terminal
  • the processing unit 1202 is configured to determine the identification information of the terminal according to the IP address of the terminal and the correspondence between the IP address of the terminal and the identification information of the terminal; and, according to The identification information of the terminal determines the context information of the terminal.
  • the communication unit 1201 is configured to receive a second message from the access node, where the second message includes a correspondence between the IP address of the terminal and the identification information of the terminal.
  • the communication unit 1201 before the access gateway receives the first load from the terminal, the communication unit 1201 is configured to send a first request message to the terminal, where the first request message includes the port number and the IP address of the access gateway, wherein the port number of the access gateway is the port number allocated by the access gateway for transmitting the control plane data, and the IP address of the access gateway is the The IP address allocated by the access gateway for transmitting the control plane data.
  • the first request message includes the IP address allocated by the access gateway for transmitting user plane data.
  • the communication unit 1201 before the access gateway receives the first load from the terminal, the communication unit 1201 is configured to receive indication information from an access and mobility management functional network element, where the indication information is used to indicate the There is no need to establish an Internet security protocol tunnel between the access gateway and the terminal.
  • the communication unit 1201 is configured to send a second payload to the terminal, where the second payload is encapsulated with a second TCP header, or the second payload is encapsulated with a second GRE protocol header ;
  • the second load is the control plane data
  • the second load is encapsulated with the second TCP header
  • the second TCP header includes the allocation of the terminal for transmitting the control plane data or
  • the second payload is user plane data of a PDU
  • the second payload is encapsulated with a second GRE protocol header
  • the GRE keyword in the second GRE protocol header includes the PDU session identifier.
  • the second payload is encapsulated with the second TCP header, which may be: the second payload is encapsulated with a fourth GRE protocol header, and the fourth GRE protocol header is encapsulated There is the second TCP packet header, wherein the GRE keyword in the fourth GRE protocol packet header is a keyword allocated by the access node to the terminal.
  • the communication device 1200 may be a terminal or a chip in the terminal.
  • the communication unit 1201 is used for the second data packet from the access gateway, the second data packet includes a second Internet Protocol (IP) packet header, a second General Packet Radio Service Tunneling Protocol-User Plane (GTP-U ) packet header and a second load, the second IP packet header includes the IP address of the access gateway, and the second GTP-U packet header includes the tunnel endpoint identifier (TEID) of the terminal or includes the access gateway's Tunnel Endpoint Identifier (TEID).
  • the processing unit 1202 is configured to determine the The second load is control plane data or user plane data.
  • the processing unit 1202 is configured to perform one or more of the following:
  • the TEID of the terminal is the TEID allocated by the terminal for transmitting the control plane data, determine that the second payload is the control plane data.
  • the TEID of the terminal is the TEID allocated by the terminal for transmitting the user plane data, determine that the second payload is the user plane data.
  • the second payload is the control plane data.
  • the second payload is the user plane data.
  • the TEID of the terminal is the TEID allocated by the terminal for transmitting the control plane data
  • the IP address of the access network is the IP address allocated by the access gateway for transmitting the control plane data
  • the TEID of the terminal is the TEID allocated by the terminal for transmitting the user plane data
  • the IP address of the access network is the IP address allocated by the access gateway for transmitting the user plane data
  • the second GTP-U packet header further includes a message type field
  • the second data packet further includes a third message
  • the third message includes the second payload; in the When the second payload is the control plane data, the message type field is used to indicate the message type of the third message.
  • the communication unit 1201 before the terminal receives the second data packet from the access gateway, the communication unit 1201 is configured to receive a first request message from the access gateway, where the first request message includes the The TEID of the access gateway and the IP address of the access gateway, wherein the TEID of the access gateway is the TEID allocated by the access gateway for transmitting the control plane data.
  • the communication unit 1201 may also be configured to send a first response message to the access gateway, where the first response message includes the TEID of the terminal, and the TEID of the terminal is used by the terminal to transmit the control The TEID assigned to the surface data.
  • the communication unit 1201 is configured to receive a second request message from the access gateway, where the second request message includes a protocol data unit (PDU) session identifier and the TEID of the access gateway , wherein the TEID of the access gateway is the TEID allocated by the access gateway for the user plane data of the PDU session.
  • the communication unit 1201 may also be configured to send a second response message to the access gateway, where the second response message includes the TEID of the terminal, and the TEID of the terminal is The TEID assigned to the user plane data.
  • PDU protocol data unit
  • the second request message further includes the IP address of the access gateway, where the IP address of the access gateway is allocated by the access gateway for the user plane data of the PDU session. IP address.
  • the communication unit 1201 is configured to send a first data packet to the access gateway, where the first data packet includes a first IP header, a first GTP-U header, and a first payload, so The first IP header includes the IP address of the access gateway, and the first GTP-U header includes the TEID of the access gateway; wherein, when the first load is the control plane data, the The IP address of the access gateway is the IP address allocated by the access gateway for transmitting the control plane data, and/or the TEID of the access gateway is the TEID allocated by the access gateway for transmitting the control plane data ; or, when the first load is the user plane data, the IP address of the access gateway is the IP address allocated by the access gateway for transmitting the user plane data, and/or the access gateway The TEID of the gateway is the TEID allocated by the access gateway for transmitting the user plane data.
  • the processing unit 1202 is configured to perform one or more of the following:
  • the TEID of the access gateway is the TEID allocated by the access gateway for transmitting the control plane data, it is determined that the second payload is the control plane data.
  • the second payload is the control plane data.
  • the TEID of the access gateway is the TEID allocated by the access gateway for transmitting the control plane data
  • the IP address of the access gateway is the TEID allocated by the access gateway for transmitting the control plane data
  • the communication unit 1201 is configured to receive a second data packet from the access gateway, the second data packet includes a second Generic Routing Encapsulation (GRE) protocol header and a second payload, and the second GRE protocol header includes the first Two GRE keywords and a second protocol type field.
  • the processing unit 1202 is configured to determine, according to at least one of the second GRE keyword and the second protocol type field, whether the second payload is control plane data or user plane data.
  • GRE Generic Routing Encapsulation
  • the processing unit 1202 is configured to perform one or more of the following:
  • the second GRE key is a key allocated by the access gateway for transmitting the control plane data
  • the second GRE key is a key allocated by the access gateway for transmitting the control plane data
  • the second protocol type field is used to indicate that the first load is the control plane data
  • the second GRE keyword includes a protocol data unit (PDU) session identifier
  • PDU protocol data unit
  • the communication unit 1201 before the terminal receives the second data packet from the access gateway, the communication unit 1201 is configured to receive a first request message from the access gateway, where the first request message includes the An Internet Protocol (IP) address of the access gateway and the second GRE key, wherein the second GRE key is a key allocated by the access gateway for transmitting the control plane data.
  • IP Internet Protocol
  • the communication unit 1201 is configured to send a first data packet to the access gateway, the first data packet includes a first GRE protocol header and a first payload, and the first GRE protocol header Including a first GRE keyword and a first protocol type field; wherein, when the first payload is the control message, the first GRE keyword is allocated by the access gateway for transmitting the control plane data A keyword, and/or the first protocol type field is used to indicate that the first load is the control plane data; or, when the first load is user plane data of a PDU session, the first GRE Keyword includes the PDU session identifier.
  • the communication unit 1201 is configured to receive the second payload from the access gateway, where the second payload is encapsulated with a second Transmission Control Protocol (TCP) header, or the second payload is encapsulated with a second common Routing Encapsulation (GRE) protocol header.
  • the processing unit 1202 is configured to determine whether the second payload is control plane data or user plane data according to the encapsulation manner of the second payload.
  • the second TCP header includes the port number allocated by the terminal for transmitting the control plane data
  • the GRE keyword in the second GRE protocol header includes a protocol data unit (PDU) Session ID.
  • PDU protocol data unit
  • the processing unit 1202 is configured to perform one or more of the following:
  • the second payload is encapsulated with the second TCP header, it is determined that the second payload is the control plane data.
  • the second payload is encapsulated with the second GRE protocol header, it is determined that the first payload is user plane data of a PDU session.
  • the second payload is encapsulated with the second TCP header, including: the second payload is encapsulated with a fourth GRE protocol header, and the fourth GRE protocol header is encapsulated with The second TCP header, wherein the GRE keyword in the fourth GRE protocol header is a keyword assigned by the access node to the terminal.
  • the communication unit 1201 is configured to receive a first request message from the access gateway, where the first request message includes the The port number of the access gateway and the IP address of the access gateway, wherein the port number of the access gateway is the port number allocated by the access gateway for transmitting the control plane data, and the IP address of the access gateway The address is an IP address allocated by the access gateway for transmitting the control plane data.
  • the first request message further includes an IP address allocated by the access gateway for transmitting user plane data.
  • the communication unit 1201 is configured to send a first payload to the access gateway, where the first payload is encapsulated with a first TCP header, or the first payload is encapsulated with a first GRE A protocol header; wherein, when the first payload is the control plane data, the first payload is encapsulated with the first TCP header, and the first TCP header includes the information for the access gateway to transmit the The port number assigned to the control plane data; or, when the first payload is user plane data of a PDU, the first payload is encapsulated with a first GRE protocol header, and the GRE key in the first GRE protocol header word includes the PDU Session Identifier.
  • the first payload is encapsulated with the first TCP header, which may be: the first payload is encapsulated with a third GRE protocol header, and the third GRE protocol header is encapsulated There is the first TCP header, wherein the GRE key in the third GRE protocol header is a key allocated by the access node to the terminal.
  • the communication device 1200 may also be an access node or a chip in the access node.
  • the communication unit 1201 is configured to receive a first payload from a terminal, the first payload is encapsulated with a first TCP header; and, send the first payload to the access gateway, wherein the first payload is encapsulated with a A third GRE protocol header, where the third TCP header is encapsulated outside the third GRE protocol header.
  • the third GRE protocol packet header includes a third GRE keyword
  • the third GRE keyword is a keyword allocated by the access node to the terminal
  • the third GRE The keyword is used to determine the identification information of the terminal.
  • the processing unit 1202 is configured to assign a third GRE keyword to the terminal; the communication unit 1201 is configured to send a second message to the access gateway, where the second message includes the first Correspondence between the three GRE keywords and the identification information of the terminal.
  • the communication unit 1201 is further configured to send a second message to the access gateway, where the second message includes a correspondence between the IP address of the terminal and the identification information of the terminal .
  • the first TCP header is encapsulated with a first IP header
  • the source address in the first IP header is the IP address of the terminal
  • the destination address in the first IP header is The address is the IP address of the access node
  • the third TCP header is encapsulated with a third IP header, the source address in the third IP header is the IP address of the access node, and the first IP The destination address in the packet header is the IP address of the access gateway.
  • the communication device 1200 may also be an access and mobility management network element or a chip in the access and mobility management network element.
  • the processing unit 1202 is configured to determine that an IPsec tunnel does not need to be established between the terminal and the access gateway according to at least one of the type of the terminal and the service type of the terminal.
  • the communication unit 1201 is configured to send indication information to the access gateway, where the indication information is used to indicate that the IPsec tunnel does not need to be established between the terminal and the access gateway.
  • each unit in the device can be implemented in the form of software called by the processing element; they can also be implemented in the form of hardware; some units can also be implemented in the form of software called by the processing element, and some units can be implemented in the form of hardware.
  • each unit can be a separate processing element, or it can be integrated in a certain chip of the device.
  • it can also be stored in the memory in the form of a program, which is called and executed by a certain processing element of the device.
  • all or part of these units can be integrated together, or implemented independently.
  • the processing element mentioned here may also be a processor, which may be an integrated circuit with signal processing capability.
  • each step of the above method or each unit above may be implemented by an integrated logic circuit of hardware in the processor element or implemented in the form of software called by the processing element.
  • the units in any of the above devices may be one or more integrated circuits configured to implement the above method, for example: one or more specific integrated circuits (application specific integrated circuit, ASIC), or, one or Multiple microprocessors (digital signal processor, DSP), or, one or more field programmable gate arrays (field programmable gate array, FPGA), or a combination of at least two of these integrated circuit forms.
  • ASIC application specific integrated circuit
  • DSP digital signal processor
  • FPGA field programmable gate array
  • the units in the device can be implemented in the form of a processing element scheduler
  • the processing element can be a general-purpose processor, such as a central processing unit (central processing unit, CPU) or other processors that can call programs.
  • CPU central processing unit
  • these units can be integrated together and implemented in the form of a system-on-a-chip (SOC).
  • SOC system-on-a-chip
  • the above communication unit 1201 is an interface circuit of the device for receiving signals from other devices or transmitting signals to other devices.
  • the communication unit 1201 is an interface circuit for the chip to receive signals from other chips or devices, or to send signals to other chips or devices.
  • FIG. 13 it is a schematic diagram of a communication device 1300 provided by an embodiment of the present application, where the communication device 1300 includes a processor 1310 and an interface 1330 .
  • the communication device 1300 may further include a memory 1320 .
  • the interface 1330 is used to communicate with other devices.
  • the interface 1330 may also be a communication module, a transceiver unit, a transceiver, a transceiver module, or a communication circuit.
  • the methods performed by the terminal, the access gateway, or the access node in the above embodiments may be implemented by the processor 1310 calling a program stored in the memory. That is, the terminal, access gateway, or access node may include a processor 1310, and the processor 1310 executes the method performed by the terminal, access gateway, or access node in the foregoing method embodiments by invoking a program in the memory.
  • the processor 1310 here may be an integrated circuit with a signal processing capability, such as a CPU.
  • a terminal, an access gateway, or an access node may be realized by one or more integrated circuits configured to implement the above method. For example, one or more ASICs, or one or more microprocessors DSP, or one or more FPGAs, etc., or a combination of at least two of these integrated circuit forms.
  • the functions/implementation process of the communication unit 1201 and the processing unit 1202 in FIG. 12 can be realized by calling the computer-executable instructions stored in the memory 1320 by the processor 1310 in the communication device 1300 shown in FIG. 13 .
  • the function/implementation process of the processing unit 1202 in FIG. 12 can be realized by the processor 1310 in the communication device 1300 shown in FIG.
  • the function/implementation process can be realized through the interface 1330 in the communication device 1300 shown in FIG. 13 .
  • sequence numbers of the above-mentioned processes do not mean the order of execution, and the order of execution of the processes should be determined by their functions and internal logic, rather than by the embodiments of the present invention.
  • the implementation process constitutes any limitation.
  • the present application also provides a computer-readable storage medium, on which a computer program is stored.
  • a computer program When the computer program is executed by a computer, the functions implemented by the UE, TNGF, access node, or AMF in the foregoing embodiments can be realized.
  • the present application also provides a computer program product, which can implement the functions implemented by the UE, TNGF, access node, or AMF in the foregoing embodiments when the computer program product is executed by a computer.
  • the present application also provides a chip system, the chip system includes at least one processor and an interface circuit, the processor is used to execute instructions and/or data interaction through the interface circuit, so that the device where the chip system is located realizes Functions implemented by UE, TNGF, access node, or AMF in the foregoing embodiments.
  • the system-on-a-chip may consist of chips, or may include chips and other discrete devices.
  • all or part of them may be implemented by software, hardware, firmware or any combination thereof.
  • software When implemented using software, it may be implemented in whole or in part in the form of a computer program product.
  • the computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on the computer, the processes or functions according to the embodiments of the present application will be generated in whole or in part.
  • the computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable devices.
  • the computer instructions may be stored in or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from a website, computer, server or data center Transmission to another website site, computer, server, or data center by wired (eg, coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (eg, infrared, wireless, microwave, etc.).
  • the computer-readable storage medium may be any available medium that can be accessed by a computer, or a data storage device including a server, a data center, and the like integrated with one or more available media.
  • the available medium may be a magnetic medium (such as a floppy disk, a hard disk, or a magnetic tape), an optical medium (such as a DVD), or a semiconductor medium (such as a solid state disk (solid state disk, SSD)), etc.
  • the various illustrative logic units and circuits described in the embodiments of the present application can be implemented by a general-purpose processor, a digital signal processor, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic devices, Discrete gate or transistor logic, discrete hardware components, or any combination of the above designed to implement or operate the described functions.
  • the general-purpose processor may be a microprocessor, and optionally, the general-purpose processor may also be any conventional processor, controller, microcontroller or state machine.
  • a processor may also be implemented by a combination of computing devices, such as a digital signal processor and a microprocessor, multiple microprocessors, one or more microprocessors combined with a digital signal processor core, or any other similar configuration to accomplish.
  • the steps of the method or algorithm described in the embodiments of the present application may be directly embedded in hardware, a software unit executed by a processor, or a combination of both.
  • the software unit can be stored in random access memory (random access memory, RAM), flash memory, read-only memory (read-only memory, ROM), EPROM memory, EEPROM memory, registers, hard disk, removable disk, CD-ROM or notebook In any other form of storage media in the field.
  • the storage medium can be connected to the processor, so that the processor can read information from the storage medium, and can write information to the storage medium.
  • the storage medium can also be integrated into the processor.
  • the processor and storage medium can be provided in an ASIC.
  • the above functions described in this application may be implemented in hardware, software, firmware or any combination of the three. If implemented in software, the functions can be stored on or transmitted over as one or more instructions or code on a computer-readable medium.
  • Computer-readable media includes computer storage media and communication media that facilitate transfer of a computer program from one place to another. Storage media may be any available media that can be accessed by a general purpose or special computer.
  • Such computer-readable media may include, but are not limited to, RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other device that can be used to carry or store instructions or data structures and Other medium of program code in a form readable by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor.
  • any connection is properly defined as a computer-readable medium, for example, if the software is transmitted from a web site, server, or other remote source via a coaxial cable, fiber optic computer, twisted pair, digital subscriber line (DSL) Or transmitted by wireless means such as infrared, wireless and microwave are also included in the definition of computer readable media.
  • DSL digital subscriber line
  • the disk (disk) and disk (disc) include compact disk, laser disk, optical disc, digital versatile disc (digital versatile disc, DVD), floppy disk and Blu-ray disc. Disks usually reproduce data magnetically, while discs usually use Lasers make optical copies of data. Combinations of the above can also be contained on a computer readable medium.
  • Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another.
  • a storage media may be any available media that can be accessed by a general purpose or special purpose computer.

Landscapes

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

Abstract

L'invention concerne un procédé et un dispositif de communication, ledit procédé comprenant les étapes suivantes : une passerelle d'accès reçoit un premier paquet de données d'un terminal, le premier paquet de données comprenant un premier en-tête de paquet IP, un premier en-tête de paquets GTP-U et une première charge, le premier en-tête de paquet IP comprenant une adresse IP de la passerelle d'accès, et le premier en-tête de paquet GTP-U comprenant un TEID de la passerelle d'accès ; et la passerelle d'accès détermine si la première charge est constituée de données de plan de commande ou de données de plan utilisateur selon l'adresse IP de la passerelle d'accès et/ou le TEID de la passerelle d'accès. Selon la présente demande, la passerelle d'accès peut distinguer si un signal de liaison montante est constitué de données de plan de commande ou de données de plan utilisateur.
PCT/CN2022/104908 2021-07-22 2022-07-11 Procédé et dispositif de communication WO2023001010A1 (fr)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
CN202110831818.8 2021-07-22
CN202110831818 2021-07-22
CN202111094796.8A CN115701089A (zh) 2021-07-22 2021-09-17 一种通信方法以及装置
CN202111094796.8 2021-09-17

Publications (1)

Publication Number Publication Date
WO2023001010A1 true WO2023001010A1 (fr) 2023-01-26

Family

ID=84978872

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/104908 WO2023001010A1 (fr) 2021-07-22 2022-07-11 Procédé et dispositif de communication

Country Status (1)

Country Link
WO (1) WO2023001010A1 (fr)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101686578A (zh) * 2008-09-28 2010-03-31 中兴通讯股份有限公司 家庭演进基站系统及无线设备的接入方法
US20170126618A1 (en) * 2015-11-02 2017-05-04 Cisco Technology, Inc. System and method for providing a change in user equipment packet data network internet protocol address in a split control and user plane evolved packet core architecture
CN106900081A (zh) * 2016-08-23 2017-06-27 中国移动通信有限公司研究院 接入网节点粒度的用户面数据隧道传输的方法及装置
US20190075046A1 (en) * 2016-04-08 2019-03-07 Intel Corporation User-plane path selection for the edge service
CN113132322A (zh) * 2019-12-31 2021-07-16 华为技术有限公司 一种通信的方法及装置

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101686578A (zh) * 2008-09-28 2010-03-31 中兴通讯股份有限公司 家庭演进基站系统及无线设备的接入方法
US20170126618A1 (en) * 2015-11-02 2017-05-04 Cisco Technology, Inc. System and method for providing a change in user equipment packet data network internet protocol address in a split control and user plane evolved packet core architecture
US20190075046A1 (en) * 2016-04-08 2019-03-07 Intel Corporation User-plane path selection for the edge service
CN106900081A (zh) * 2016-08-23 2017-06-27 中国移动通信有限公司研究院 接入网节点粒度的用户面数据隧道传输的方法及装置
CN113132322A (zh) * 2019-12-31 2021-07-16 华为技术有限公司 一种通信的方法及装置

Similar Documents

Publication Publication Date Title
US20210250767A1 (en) Systems and methods for accessing a network
US20220360634A1 (en) User plane model for non-3gpp access to fifth generation core network
US20230308853A1 (en) Computing workload management in next generation cellular networks
US9264972B2 (en) Home networking with integrated cellular communication
US11102689B2 (en) Packet data connections in a wireless communication system using a wireless local area network
US20230319556A1 (en) Key obtaining method and communication apparatus
WO2020029922A1 (fr) Procédé et appareil de transmission de message
US20230171672A1 (en) Route configuration method and apparatus
WO2019242525A1 (fr) Procédé de transmission de données, dispositif et système associés
US20240015630A1 (en) Routing Between Networks Based on Identifiers
WO2021204277A1 (fr) Procédé, appareil et système de communication
WO2023185880A9 (fr) Procédé de détermination de dispositif de réseau d'accès
WO2023001010A1 (fr) Procédé et dispositif de communication
WO2021169683A1 (fr) Procédé et dispositif de communication
KR102439422B1 (ko) 네트워크 액세스 방법 및 장치
WO2012110004A1 (fr) Procédé et dispositif de transfert de messages sur la base de lte-lan
CN115701089A (zh) 一种通信方法以及装置
WO2023246649A1 (fr) Procédé de communication, appareil de communication et système de communication
WO2023066207A1 (fr) Procédé et appareil de communication
WO2022068336A1 (fr) Procédé de mise à jour d'informations de routage, appareil de communication et support de stockage
TWI820874B (zh) 一種應用於通道直接鏈路建立的傳輸方法及裝置
WO2022022639A1 (fr) Procédé et dispositif de communication
WO2023197737A1 (fr) Procédé d'envoi de message, procédé de gestion de pin, appareil de communication et système de communication
WO2024012230A1 (fr) Procédé et appareil de communication
WO2023216932A1 (fr) Procédé et appareil de communication

Legal Events

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

Ref document number: 22845175

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE