Communication method and device

Abstract

A communication method and apparatus, the method comprising: an access gateway receiving a first data packet from a terminal, the first data packet including a first IP header, a first GTP-U header, and a first payload, the first IP header including the IP address of the access gateway, and the first GTP-U header including the TEID of the access gateway; and the access gateway determining, based on 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. Through the present application, the access gateway can distinguish whether an uplink signal is control plane data or user plane data.

Description

[0001] This application claims priority to the Chinese patent application filed with the China Patent Office on July 22, 2021, with application number 202110831818.8 and application name “A Communication Method and Device”, the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of communication technology, and in particular to a communication method and device. Background Art

[0003] The fifth generation core network (5GC) supports access to the 3rd Generation Partnership Project (3GPP) network and access to non-3GPP (non-3GPP) networks. Non-3GPP access technologies include trusted non-3GPP access, untrusted non-3GPP access, and wired access. A terminal can access the core network by establishing a connection with a non-3GPP access gateway. For trusted non-3GPP access, the access gateway can be a trusted non-3GPP access gateway function (TNGF); for untrusted non-3GPP access, the access gateway can be a non-3GPP interworking function (N3IWF); for wired access, the access gateway can be a wireline-access gateway function (W-AGF).

[0004] In non-3GPP access scenarios, an access gateway receives uplink information from a terminal. This uplink information can be either control plane data or user plane data. If the uplink information is control plane data, the access gateway can send it to the access and mobility management function (AMF) network element. If the uplink information is user plane data, the access gateway needs to send it to the 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. Summary of the Invention

[0005] The purpose of the present application is to provide a communication method and apparatus, which are used to enable an access gateway to distinguish whether uplink information is control plane data or user plane data.

[0006] In a first aspect, the present application provides a communication method, which can be executed by an access gateway or by a component of an access gateway. In this method, the access gateway receives a first data packet from a terminal, the first data packet including a first IP header, a first GTP-U header, and a first payload, the first IP header including the IP address of the access gateway, the first GTP-U header including the TEID of the access gateway; and the access gateway determines whether the first payload is control plane data or user plane data based on at least one of the IP address of the access gateway and the TEID of the access gateway. The first payload is encapsulated with a first GTP-U header, the first GTP-U header is encapsulated with a first UDP header, and the first UDP header is encapsulated with a first IP header.

[0007] Optionally, the control plane data may include a control plane message, such as a NAS message, or other control plane messages other than a NAS message. The user plane data may include remote control service data, etc.

[0008] In the above embodiment, the access gateway can distinguish whether the uplink load is control plane data or user plane data based on at least one of the access gateway's TEID included in the GTP-U header encapsulated outside the uplink load and the access gateway's IP address included in the IP header. Furthermore, a GTP-U tunnel is established between the access gateway and the terminal, which can simplify the process of the terminal accessing the core network compared to an IPsec tunnel. Furthermore, when transmitting user plane data, the IPsec tunnel encapsulation method requires encapsulating a double-layer IP header outside the user plane data, while the GTP-U tunnel encapsulation method requires encapsulating a single IP header outside the user plane data. Obviously, the header length of the data packet based on the GTP-U tunnel encapsulation method is shorter than that based on the IPsec tunnel encapsulation method, which can reduce problems such as waste of transmission resources, extended latency, and high device power consumption caused by excessively long data packet headers.

[0009] In one possible design, determining, by the access gateway, based on at least one of the IP address of the access gateway and the TEID of the access gateway, that the first load is control plane data or user plane data may include one or more of the following:

[0010] When the TEID of the access gateway is a TEID allocated by the access gateway for transmitting the control plane data, the access gateway determines that the first payload is the control plane data.

[0011] Alternatively, when the TEID of the access gateway is a TEID allocated by the access gateway for transmitting the user plane data, the access gateway determines that the first load is the user plane data.

[0012] Alternatively, when the IP address of the access gateway is an IP address allocated by the access gateway for transmitting the control plane data, the access gateway determines that the first load is the control plane data.

[0013] Alternatively, when the IP address of the access gateway is an IP address allocated by the access gateway for transmitting the user plane data, the access gateway determines that the first load is the user plane data.

[0014] Alternatively, when the TEID of the access gateway is the TEID allocated by the access gateway for transmitting the control plane data, and the IP address of the access network is the IP address allocated by the access gateway for transmitting the control plane data, the access gateway determines that the first load is the control plane data.

[0015] Alternatively, when the TEID of the access gateway is the TEID allocated by the access gateway for transmitting the user plane data, and the IP address of the access network is the IP address allocated by the access gateway for transmitting the user plane data, the access gateway determines that the first load is the user plane data.

[0016] Through the above design, the access gateway can flexibly determine whether the load is control plane data or user plane data by comparing the TEID in the GTP-U packet header encapsulated outside the load with the TEID allocated by the access gateway for transmitting control plane data and the TEID allocated for transmitting user plane data, and / or comparing the IP address of the access gateway in the IP packet header with the IP address allocated by the access gateway for transmitting control plane data and the IP address allocated by the access gateway for transmitting user plane data.

[0017] In one possible design, the first GTP-U packet header also includes a message type field, the first data packet also includes a first message, and the first message includes the first payload; when the first payload is the control plane data, the message type field is used to indicate the message type of the first message.

[0018] Through the above design, 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 then the GTP-U header is encapsulated outside the first message.

[0019] In one possible design, before the access gateway receives the first data packet from the terminal, 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 receiving a first response message from the terminal, the first response message including the TEID of the terminal, and the TEID of the terminal is the TEID allocated by the terminal for transmitting the control plane data. Optionally, the IP address of the access gateway is the IP address allocated by the access gateway for transmitting the control plane data.

[0020] Through the above design, the access gateway and the terminal interact with each other, and the TEID and IP address allocated for the transmission of control plane data can be sent to the terminal, so as to be used subsequently to identify whether the uplink load is control plane data, and to obtain the TEID allocated by the terminal for the transmission of control plane data, so as to subsequently send the control plane data to the terminal through the GTP-U tunnel.

[0021] In one possible design, the method may also include: the access gateway sends a second request message to the terminal, 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 assigned by the access gateway to the user plane data of the PDU session; the access gateway receives a second response message from the terminal, the second response message includes the TEID of the terminal, and the TEID of the terminal is the TEID assigned by the terminal to the user plane data of the PDU session.

[0022] Through the above design, the access gateway and the terminal interact with each other, and the TEID allocated for transmitting the user plane data of the PDU session can be sent to the terminal, so as to be used subsequently to identify whether the uplink load is the user plane data of the PDU session, and to obtain the TEID allocated by the terminal for transmitting the user plane data of the PDU session, so as to subsequently send the user plane data of the PDU session to the terminal through the GTP-U tunnel.

[0023] In one possible design, the second request message also includes the IP address of the access gateway, where the IP address of the access gateway is the IP address allocated by the access gateway for the user plane data of the PDU session. Optionally, the IP address allocated by the access gateway for the user plane data of the PDU session may be the same as or different from the IP address allocated by the access gateway for the control plane data.

[0024] Through the above design, the access gateway can also allocate an IP address to the user plane data of the PDU session, so as to be used to subsequently identify whether the uplink load is the user plane data of the PDU session.

[0025] In one possible design, before the access gateway receives the first data packet from the terminal, the method may further include: the access gateway receives indication information from an access and mobility management function (AMF) network element, wherein the indication information is used to indicate that an Internetwork Security Protocol (IPsec) tunnel does not need to be established between the access gateway and the terminal.

[0026] Through the above design, the access gateway can determine not to establish an IPsec tunnel with the terminal based on the instruction information of AMF, so as to simplify the process of terminal accessing the core network.

[0027] In one possible design, the first IP packet header also includes the IP address of the terminal, and the method may further include: the access gateway determines the identification information of the terminal based on the IP address of the terminal and the correspondence between the IP address of the terminal and the identification information of the terminal; the access gateway determines the context information of the terminal based on the identification information of the terminal.

[0028] Through the above design, the access gateway can determine which terminal the uplink load comes from and the context information of the terminal based on the IP address, so as to determine the control plane network element to establish an N2 connection with the terminal or determine the user plane network element to establish an N3 connection with the terminal.

[0029] In one possible design, the method may further include: the access gateway receiving a second message from the access node, the second message including a correspondence between the IP address of the terminal and the identification information of the terminal.

[0030] In one possible design, the method may further include: the access gateway sends a second data packet to the terminal, the second data packet including a second IP header, a second GTP-U header and a second load, the second IP header including the IP address of the access gateway, and the second GTP-U header including 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 access gateway for transmitting the user plane data.

[0031] In one possible design, the method may also include: the access gateway sends a second data packet to the terminal, the second data packet includes a second IP header, a second GTP-U header and a 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; wherein, the second payload 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, and the TEID of the access gateway is the TEID allocated by the access gateway for transmitting the control plane data.

[0032] With the above design, the access gateway can use the TEID it allocates for control plane data transmission to send control plane data to the terminal. Furthermore, the terminal can obtain the TEID allocated by the access gateway for control plane data transmission and send control plane data to the access gateway based on the TEID. This eliminates the need to allocate a TEID for control plane data transmission to the UE through additional messages, reduces signaling interactions between the access gateway and the UE, and improves network resource utilization.

[0033] In a second aspect, the present application provides a communication method, which can be executed by a terminal or by a component of the terminal. The method includes: the terminal receives a second data packet from an access gateway, the second data packet includes a second Internet Protocol (IP) header, a second General Packet Radio Service Tunneling Protocol-User Plane (GTP-U) header, and a second payload, 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 determines whether the second payload is control plane data or user plane data based on at least one of the IP address of the access gateway and the TEID of the terminal.

[0034] In one possible design, determining, by the terminal, based on at least one of the IP address of the access gateway and the TEID of the terminal, that the second load is control plane data or user plane data may include one or more of the following:

[0035] When the TEID of the terminal is a TEID allocated by the terminal for transmitting the control plane data, the terminal determines that the second payload is the control plane data.

[0036] Alternatively, when the TEID of the terminal is a TEID allocated by the terminal for transmitting the user plane data, the terminal determines that the second load is the user plane data.

[0037] Alternatively, when the IP address of the access gateway is an IP address allocated by the access gateway for transmitting the control plane data, the terminal determines that the second load is the control plane data.

[0038] Alternatively, when the IP address of the access gateway is an IP address allocated by the access gateway for transmitting the user plane data, the terminal determines that the second load is the user plane data.

[0039] Alternatively, when the TEID of the terminal is the TEID allocated by the terminal for transmitting the control plane data, and the IP address of the access network is the IP address allocated by the access gateway for transmitting the control plane data, the terminal determines that the second load is the control plane data.

[0040] Alternatively, when the TEID of the terminal is the TEID allocated by the terminal for transmitting the user plane data, and the IP address of the access network is the IP address allocated by the access gateway for transmitting the user plane data, the terminal determines that the second load is the user plane data.

[0041] In one possible design, the second GTP-U packet header also includes a message type field, the second data packet also includes a third message, and the third message includes the second load; when the second load is the control plane data, the message type field is used to indicate the message type of the third message.

[0042] In one possible design, before the terminal receives the second data packet from the access gateway, the method also includes: the terminal receives a first request message from the access gateway, 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 terminal sends a first response message to the access gateway, the first response message includes the TEID of the terminal, and the TEID of the terminal is the TEID allocated by the terminal for transmitting the control plane data.

[0043] In one possible design, the method may also include: the terminal receives a second request message from the access gateway, 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 assigned by the access gateway to the user plane data of the PDU session; the terminal sends a second response message to the access gateway, the second response message includes the TEID of the terminal, and the TEID of the terminal is the TEID assigned by the terminal to the user plane data of the PDU session.

[0044] In one possible design, the second request message also includes the IP address of the access gateway, where the IP address of the access gateway is the IP address allocated by the access gateway for the user plane data of the PDU session.

[0045] In one possible design, the method may also include: the terminal sends a first data packet to the access gateway, the first data packet includes a first IP header, a first GTP-U header and a first load, 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 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 TEID of the access gateway is the TEID allocated by the access gateway for transmitting the user plane data.

[0046] In a third aspect, the present application provides a communication method, which can be executed by a terminal or by a component 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 payload, the first IP header includes the IP address of the access gateway, and the first GTP-U header includes the tunnel endpoint identifier (TEID) of the access gateway; wherein the first payload is 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, and the TEID of the access gateway is the TEID allocated by the access gateway for transmitting the control plane data; or, the first payload 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, and the TEID of the access gateway is the TEID allocated by the access gateway for transmitting the user plane data; and, the terminal sends the first data packet to the access gateway.

[0047] In one possible design, the method may also include: the terminal receives a second data packet from the access gateway, the second data packet includes a second IP header, a second GTP-U 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 TEID of the access gateway.

[0048] In one possible design, the method may also include: the terminal determining whether the second load is control plane data or user plane data based on at least one of the IP address of the access gateway and the TEID of the access gateway; or, the terminal determining whether the second load is control plane data or user plane data by parsing the second load.

[0049] In one possible design, the terminal determines, based on 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, which may include one or more of the following:

[0050] When the TEID of the access gateway is a TEID allocated by the access gateway for transmitting the control plane data, the terminal determines that the second payload is the control plane data.

[0051] Alternatively, when the IP address of the access gateway is an IP address allocated by the access gateway for transmitting the control plane data, the terminal determines that the second load is the control plane data.

[0052] Alternatively, when the TEID of the access gateway is the TEID allocated by the access gateway for transmitting the control plane data, and the IP address of the access gateway is the IP address allocated by the access gateway for transmitting the control plane data, the terminal determines that the second load is the control plane data.

[0053] In one possible design, 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.

[0054] In a fourth aspect, the present application provides a communication method, which can be performed by an access gateway or by a component of the access gateway. The method includes: the access gateway receiving a first data packet from a terminal, the first data packet including a first Generic Routing Encapsulation (GRE) protocol header and a first payload, the first GRE protocol header including a first GRE keyword and a first protocol type field; and the access gateway determining, based on 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.

[0055] In the above embodiment, the access gateway can distinguish whether the uplink load is control plane data or user plane data based on at least one of the GRE keyword and protocol type fields included in the GRE protocol header encapsulated outside the uplink load. Furthermore, a GRE tunnel is established between the access gateway and the terminal, which can simplify the process of terminal access to the core network compared to an IPsec tunnel. Furthermore, when transmitting user plane data, the IPsec tunnel encapsulation method requires encapsulating a double-layer IP header outside the user plane data, while the GRE tunnel encapsulation method requires encapsulating a single IP header outside the user plane data. Obviously, the header length of the data packet based on the GRE tunnel encapsulation method is shorter than that based on the IPsec tunnel encapsulation method, which can reduce problems such as wasted transmission resources, extended latency, and high device power consumption caused by excessively long data packet headers.

[0056] In one possible design, the access gateway determines, based on 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, which may include one or more of the following:

[0057] When the first GRE keyword is a keyword assigned by the access gateway for transmitting the control plane data, the access gateway determines that the first payload is the control plane data.

[0058] Alternatively, when the first protocol type field is used to indicate that the first payload is the control plane data, the access gateway determines that the first payload is the control plane data.

[0059] Alternatively, when the first GRE keyword is a keyword assigned by the access gateway for transmitting the control plane data, and the first protocol type field is used to indicate that the first load is the control plane data, the access gateway determines that the first load is the control plane data.

[0060] Alternatively, when the first GRE keyword includes a protocol data unit (PDU) session identifier, the access gateway determines that the first payload is user plane data of the PDU session.

[0061] Through the above design, the access gateway can flexibly determine whether the load is control plane data or user plane data by comparing the GRE keyword in the GRE protocol packet header encapsulated outside the load with the keyword and PDU session identifier assigned by the access gateway for transmitting control plane data, and / or parsing the protocol type field in the GRE protocol packet header.

[0062] In one possible design, before the access gateway receives the first data packet from the terminal, the method also includes: the access gateway sends a first request message to the terminal, the first request message including the Internet Protocol (IP) address of the access gateway and a keyword assigned by the access gateway for transmitting the control plane data.

[0063] Through the above design, the access gateway and the terminal interact with each other and can send the keyword allocated for transmitting control plane data to the terminal for subsequent use in identifying whether the uplink load is control plane data.

[0064] In one possible design, before the access gateway receives the first data packet from the terminal, the method further includes: the access gateway receives indication information from an access and mobility management function (AMF) network element, wherein the indication information is used to indicate that an Internetwork Security Protocol (IPsec) tunnel does not need to be established between the access gateway and the terminal.

[0065] In one possible design, the first data packet also includes a first IP packet header, the first IP packet header includes the IP address of the terminal, and the method also includes: the access gateway determines the identification information of the terminal based on the IP address of the terminal and the correspondence between the IP address of the terminal and the identification information of the terminal; the access gateway determines the context information of the terminal based on the identification information of the terminal.

[0066] In one possible design, the method further includes: the access gateway receiving a second message from the access node, the second message including a correspondence between the IP address of the terminal and identification information of the terminal.

[0067] In one possible design, the method also includes: the access gateway sends a second data packet to the terminal, the second data packet includes a second GRE protocol header and a second payload, the second GRE protocol 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 a keyword assigned by the access gateway for transmitting the control plane data, and / or the second protocol type field is used to indicate that the second payload is the control plane data; or, when the second payload is user plane data of a PDU session, the second GRE keyword includes the PDU session identifier.

[0068] In a fifth aspect, the present application provides a communication method, which can be performed by a terminal or by a component of the terminal. The method includes: the terminal receiving a second data packet from an access gateway, the second data packet including a second Generic Routing Encapsulation (GRE) protocol header and a second payload, the second GRE protocol header including a second GRE keyword and a second protocol type field; and the terminal determining, based on 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.

[0069] In one possible design, the terminal determines, based on 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, including one or more of the following:

[0070] When the second GRE keyword is a keyword allocated by the access gateway for transmitting the control plane data, the terminal determines that the second payload is the control plane data.

[0071] Alternatively, when the second protocol type field is used to indicate that the first payload is the control plane data, the terminal determines that the second payload is the control plane data.

[0072] Alternatively, when the second GRE keyword is a keyword assigned by the access gateway for transmitting the control plane data, and the second protocol type field is used to indicate that the first load is the control plane data, the terminal determines that the second load is the control plane data.

[0073] Alternatively, when the second GRE keyword includes a protocol data unit (PDU) session identifier, the terminal determines that the second payload is user plane data of the PDU session.

[0074] In one possible design, before the terminal receives the second data packet from the access gateway, the method also includes: the terminal receives a first request message from the access gateway, 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 assigned by the access gateway for transmitting the control plane data.

[0075] In one possible design, the method also 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, the first GRE protocol header includes a first GRE keyword and a first protocol type field; wherein, when the first payload is the control message, the first GRE keyword is a keyword assigned by the access gateway for transmitting the control plane data, and / or the first protocol type field is used to indicate that the first payload is the control plane data; or, when the first payload is user plane data of a PDU session, the first GRE keyword includes the PDU session identifier.

[0076] In a sixth aspect, the present application provides a communication method, which can be performed by an access gateway or by a component of the access gateway. The method includes: the access gateway receiving a first payload from a terminal, wherein the first payload is encapsulated with a first Transmission Control Protocol (TCP) packet header or a first Generic Routing Encapsulation (GRE) protocol packet header; and the access gateway determining, based on the encapsulation method of the first payload, whether the first payload is control plane data or user plane data.

[0077] In the above embodiment, different encapsulation methods are used for control plane data and user plane data. This allows the access gateway to distinguish whether the uplink payload is control plane data or user plane data based on the encapsulation method of the received payload. Whether a TCP connection or a GRE tunnel is established between the terminal and the access gateway, the process of terminal accessing the core network can be simplified compared to an IPsec tunnel, and a TCP connection can improve the reliability of data transmission. Furthermore, when transmitting user plane data, the IPsec tunnel encapsulation method requires encapsulating a double-layer IP header outside the user plane data, while the GRE tunnel encapsulation method (or TCP encapsulation method) requires encapsulating a single IP header outside the user plane data. Obviously, the header length of the data packet based on the GRE tunnel encapsulation method (or TCP encapsulation method) is smaller than that based on the IPsec tunnel encapsulation method, which can reduce the problems of wasted transmission resources, extended time, and high device power consumption caused by excessively long data packet headers.

[0078] In one possible design, the first TCP packet header includes a port number allocated by the access gateway for transmitting the control plane data, and the GRE keyword in the first GRE protocol packet header includes a protocol data unit (PDU) session identifier.

[0079] In one possible design, the access gateway determines, based on an encapsulation mode of the first payload, whether the first payload is control plane data or user plane data, which may include one or more of the following:

[0080] When the first payload is encapsulated with the first TCP packet header, the access gateway determines that the first payload is the control plane data.

[0081] Alternatively, when the first payload is encapsulated with the first GRE protocol header, the access gateway determines that the first payload is user plane data of the PDU session.

[0082] Through the above design, the access gateway can distinguish whether the payload is user plane data or control plane data based on the payload encapsulation method.

[0083] In a possible design, the first payload is encapsulated in the first TCP packet header, which may be: the first payload is encapsulated in the third GRE protocol packet header, and the third GRE protocol packet header is encapsulated in the first TCP packet header.

[0084] In one possible design, the third GRE protocol packet header includes a third GRE keyword, which is a keyword assigned by the access node to the terminal. The method also includes: the access gateway determines the identification information of the terminal based on the third GRE keyword and the correspondence between the third GRE keyword and the identification information of the terminal; the access gateway determines the context information of the terminal based on the identification information of the terminal.

[0085] Through the above design, the access gateway can determine which terminal the uplink load comes from and the context information of the terminal based on the GRE keyword in the GRE protocol packet header encapsulated outside the load, so as to determine the control plane network element to establish an N2 connection with the terminal or determine the user plane network element to establish an N3 connection with the terminal.

[0086] In one possible design, the method further includes: the access gateway receiving a second message from the access node, the second message including a correspondence between the third GRE keyword and the identification information of the terminal.

[0087] Through the above design, the access gateway can obtain the GRE keyword allocated by the access node to the terminal, so as to subsequently use it to determine which terminal the uplink load comes from.

[0088] In one possible design, the first TCP packet header is encapsulated with a first Internet Protocol (IP) packet header, or the first GRE protocol packet header is encapsulated with a first IP packet header, and the first IP packet header includes the IP address of the terminal. The method also includes: the access gateway determines the identification information of the terminal based on the IP address of the terminal and the correspondence between the IP address of the terminal and the identification information of the terminal; the access gateway determines the context information of the terminal based on the identification information of the terminal.

[0089] In one possible design, the method further includes: the access gateway receiving a second message from the access node, the second message including a correspondence between the IP address of the terminal and identification information of the terminal.

[0090] In one possible design, before the access gateway receives the first load from the terminal, the method also includes: the access gateway sends a first request message to the terminal, the first request message including 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 is the IP address allocated by the access gateway for transmitting the control plane data.

[0091] In one possible design, the first request message includes an IP address allocated by the access gateway for transmitting user plane data.

[0092] In one possible design, before the access gateway receives the first load from the terminal, the method also includes: the access gateway receives indication information from an access and mobility management function (AMF) network element, wherein the indication information is used to indicate that an Internetwork Security Protocol (IPsec) tunnel does not need to be established between the access gateway and the terminal.

[0093] In one possible design, the method also includes: the access gateway sends a second payload to the terminal, the second payload is encapsulated with a second TCP packet header, or the second payload is encapsulated with a second GRE protocol packet header; wherein, when the second payload is the control plane data, the second payload is encapsulated with the second TCP packet header, and the second TCP packet header includes the port number allocated by the terminal for transmitting the control plane data; or, when the second payload is the user plane data of the PDU, the second payload is encapsulated with a second GRE protocol packet header, and the GRE keyword in the second GRE protocol packet header includes the PDU session identifier.

[0094] In one possible design, 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 the keyword assigned by the access node to the terminal.

[0095] In the seventh aspect, the present application provides a communication method, which can be executed by a terminal or by a component of the terminal, and the method includes: the terminal receives a second load from an access gateway, wherein the second load is encapsulated with a second Transmission Control Protocol (TCP) packet header, or the second load is encapsulated with a second Generic Routing Encapsulation (GRE) protocol header; the terminal determines whether the second load is control plane data or user plane data based on the encapsulation method of the second load.

[0096] In one possible design, the second TCP packet header includes the port number allocated by the terminal for transmitting the control plane data, and the GRE keyword in the second GRE protocol packet header includes a protocol data unit (PDU) session identifier.

[0097] In one possible design, the terminal determines, based on an encapsulation mode of the second payload, that the second payload is control plane data or user plane data, which may include one or more of the following:

[0098] When the second TCP packet header is encapsulated outside the second payload, the terminal determines that the second payload is the control plane data.

[0099] Alternatively, when the second payload is encapsulated with the second GRE protocol header, the terminal determines that the first payload is user plane data of the PDU session.

[0100] In one possible design, the second payload is encapsulated with the second TCP header, including: the second payload is encapsulated with a fourth GRE protocol header, 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.

[0101] In one possible design, before the terminal receives the second load from the access gateway, the method also includes: the terminal receives a first request message from the access gateway, the first request message including 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 is the IP address allocated by the access gateway for transmitting the control plane data.

[0102] In one possible design, the first request message also includes an IP address allocated by the access gateway for transmitting user plane data.

[0103] In one possible design, the method also includes: the terminal sends a first payload to the access gateway, the first payload is encapsulated with a first TCP packet header, or the first payload is encapsulated with a first GRE protocol packet header; wherein, when the first payload is the control plane data, the first payload is encapsulated with the first TCP packet header, and the first TCP packet header includes the port number allocated by the access gateway for transmitting the control plane data; or, when the first payload is the user plane data of the PDU, the first payload is encapsulated with a first GRE protocol packet header, and the GRE keyword in the first GRE protocol packet header includes the PDU session identifier.

[0104] In one possible design, 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 the keyword assigned by the access node to the terminal.

[0105] In an eighth aspect, the present application provides a communication method, which can be performed by an access node or by a component of the access node. The method includes: the access node receiving a first payload from a terminal, the first payload being encapsulated with a first Transmission Control Protocol (TCP) packet header; and the access node sending the first payload to an access gateway, wherein the first payload is encapsulated with a third Generic Routing Encapsulation (GRE) protocol packet header, and the third GRE protocol packet header is encapsulated with the third TCP packet header.

[0106] The third GRE protocol packet header includes a third GRE keyword, which is a keyword allocated by the access node to the terminal, and is used to determine identification information of the terminal.

[0107] In the above embodiment, 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 then the access node establishes a TCP connection with the TNGF. After receiving the first load from the terminal, the access node encapsulates the GRE protocol header outside the first load, and fills in the GRE keyword in the GRE protocol header with the keyword assigned by the access node to the terminal, and then sends the encapsulated first load to the TNGF to identify which terminal the first load comes from. In this way, the TNGF can determine the identification information of the terminal that sent the first load based on the GRE keyword in the GRE protocol header, and based on the identification information of the terminal, determine the control plane network element to establish an N2 connection with the terminal, or determine the user plane network element to establish an N3 connection with the terminal.

[0108] In one possible design, 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 second message including the correspondence between the third GRE keyword and the identification information of the terminal.

[0109] In one possible design, the method may further include: the access node sending a second message to the access gateway, the second message including a correspondence between an Internet Protocol (IP) address of the terminal and identification information of the terminal.

[0110] In one possible design, 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 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 destination address in the first IP header is the IP address of the access gateway.

[0111] In a ninth aspect, the present application provides a communication method, which can be performed by an access and mobility management function network element, or by a component of an access and mobility management function network element. The method includes: an access and mobility management function (AMF) network element determining, based on at least one of the type of the terminal and the service type of the terminal, that an Internetwork Security Protocol (IPsec) tunnel does not need to be established between the terminal and the access gateway; and the AMF network element sending indication information to the access gateway, the indication information being used to indicate that the IPsec tunnel does not need to be established between the terminal and the access gateway.

[0112] The terminal type may be a smart factory terminal (such as a robotic arm, a mobile truck, etc.), an IoT device, or a low-power device, etc. The terminal service type may be a remote control service, etc.

[0113] In the above embodiment, the AMF determines that there is no need to establish an IPsec tunnel between the terminal and the access gateway based on the type of the terminal and at least one of the service types of the terminal, that is, a simplified 5G core network access process can be performed, and sends an indication information to the access gateway to indicate that the access gateway does not need to establish an IPsec tunnel with the terminal, thereby simplifying the process of terminal access to the 5G core network and reducing the problems of transmission resource waste, time extension, and high equipment power consumption caused by IPsec encapsulation during user-side data transmission.

[0114] In the tenth aspect, the present application provides a communication device, comprising a memory, and one or more processors, wherein the memory is coupled to the one or more processors; the memory is used to store a computer program or instruction, and when the computer program or instruction is executed by the one or more processors, the communication device executes the method described in the first aspect or any one of the designs of the first aspect, or the communication device executes the method described in the fourth aspect or any one of the designs of the fourth aspect, or the communication device executes the method described in the sixth aspect or any one of the designs of the sixth aspect.

[0115] In the eleventh aspect, the present application provides a communication device, comprising a memory, and one or more processors, wherein the memory is coupled to the one or more processors; the memory is used to store a computer program or instruction, and when the computer program or instruction is executed by the one or more processors, the communication device executes the method described in the second aspect or any one of the designs of the second aspect, or the communication device executes the method described in the third aspect or any one of the designs of the third aspect, or the communication device executes the method described in the fifth aspect or any one of the designs of the fifth aspect, or the communication device executes the method described in the seventh aspect or any one of the designs of the seventh aspect.

[0116] In the twelfth aspect, the present application provides a communication device comprising a memory and one or more processors, wherein the memory is coupled to the one or more processors; the memory is used to store computer programs or instructions, and 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 eighth aspect or any one of the designs of the eighth aspect.

[0117] In the thirteenth aspect, the present application provides a communication device comprising a memory and one or more processors, wherein the memory is coupled to the one or more processors; the memory is used to store computer programs or instructions, and when the computer programs or instructions are executed by the one or more processors, the communication device executes the method described in the ninth aspect above.

[0118] In the fourteenth aspect, 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 access gateway in the above-mentioned first aspect or any one of the design examples of the first aspect, or perform the corresponding functions performed by the access gateway in the above-mentioned fourth aspect or any one of the design examples of the fourth aspect, or perform the corresponding functions performed by the access gateway in the above-mentioned sixth aspect or any one of the design examples of the sixth aspect.

[0119] In the fifteenth aspect, 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 the above-mentioned second aspect or any one of the design examples of the second aspect, or perform the corresponding functions performed by the terminal in the above-mentioned third aspect or any one of the design examples of the third aspect, or perform the corresponding functions performed by the terminal in the above-mentioned fifth aspect or any one of the design examples of the fifth aspect, or perform the corresponding functions performed by the terminal in the above-mentioned seventh aspect or any one of the design examples of the seventh aspect.

[0120] In the sixteenth aspect, 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 access node in the above-mentioned eighth aspect or any one of the design examples of the eighth aspect.

[0121] In the seventeenth aspect, 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 access and mobility management function network element in the above-mentioned ninth aspect.

[0122] In the eighteenth 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 communication device in the fifteenth aspect.

[0123] In the nineteenth aspect, 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 communication device in the sixteenth aspect.

[0124] In the twentieth aspect, the present application provides a communication system, comprising the communication device in the tenth aspect and / or the communication device in the thirteenth aspect; or comprising the communication device in the fourteenth aspect and / or the communication device in the seventeenth aspect.

[0125] In aspect 21, the present application provides a computer-readable storage medium storing a computer program or instruction. When the computer program or instruction is executed, it can implement the method described in the first aspect or any one of the designs of the first aspect, or implement the method described in the fourth aspect or any one of the designs of the fourth aspect, or implement the method described in the sixth aspect or any one of the designs of the sixth aspect.

[0126] In aspect 22, the present application provides a computer-readable storage medium storing a computer program or instruction. When the computer program or instruction is executed, it can implement the method described in the second aspect or any one of the designs of the second aspect, or implement the method described in the third aspect or any one of the designs of the third aspect, or implement the method described in the fifth aspect or any one of the designs of the fifth aspect, or implement the method described in the seventh aspect or any one of the designs of the seventh aspect.

[0127] In the twenty-third aspect, the present application provides a computer-readable storage medium, which stores a computer program or instruction. When the computer program or instruction is executed, the method described in the above-mentioned eighth aspect or any one of the designs of the eighth aspect can be implemented.

[0128] In the twenty-fourth aspect, the present application provides a computer-readable storage medium, which stores a computer program or instruction. When the computer program or instruction is executed, the method described in the ninth aspect above can be implemented.

[0129] In aspect 25, the present application provides a terminal device, which can implement the method described in the first aspect or any one of the designs of the first aspect, or implement the method described in the fourth aspect or any one of the designs of the fourth aspect, or implement the method described in the sixth aspect or any one of the designs of the sixth aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0130] Figure 1a This is a schematic diagram of a 5G network architecture based on a service-oriented architecture in an embodiment of the present application;

[0131] Figure 1b This is a schematic diagram of a 5G network architecture based on a point-to-point interface in an embodiment of the present application;

[0132] Figure 1c This is another schematic diagram of a 5G network architecture based on a point-to-point interface in an embodiment of the present application;

[0133] Figure 2 A flow chart of a communication method provided in an embodiment of the present application;

[0134] Figure 3 A flowchart of a method for obtaining an IP address and TEID for transmitting control plane data provided in an embodiment of the present application;

[0135] Figure 4 A flowchart of a method for obtaining an IP address and TEID for transmitting user plane data provided in an embodiment of the present application;

[0136] Figure 5A schematic diagram of another flow chart of a method for obtaining an IP address and TEID for transmitting user plane data provided in an embodiment of the present application;

[0137] Figure 6 A schematic diagram of another flow chart of the communication method provided in an embodiment of the present application;

[0138] Figure 7 A schematic diagram of a GRE protocol packet header provided in an embodiment of the present application;

[0139] Figure 8 A schematic diagram of a GRE key in a GRE protocol header provided in an embodiment of the present application;

[0140] Figure 9 A flowchart of a method for obtaining a GRE key for transmitting control plane data provided in an embodiment of the present application;

[0141] Figure 10 A schematic diagram of another flow chart of the communication method provided in an embodiment of the present application;

[0142] Figure 11 A flowchart of a method for obtaining a TCP port number for transmitting control plane data provided in an embodiment of the present application;

[0143] Figure 12 A schematic diagram of the structure of a communication device provided in an embodiment of the present application;

[0144] Figure 13 A schematic diagram of another structure of a communication device provided in an embodiment of the present application;

[0145] Figure 14 A flowchart of another communication method provided in an embodiment of the present application. DETAILED DESCRIPTION

[0146] In order to make the purpose, technical solutions and advantages of this application more clear, the application will be further described in detail below with reference to the accompanying drawings. The specific operation methods in the method embodiments can also be applied to the device embodiments or system embodiments.

[0147] In the embodiments of the present application, the terms "system" and "network" can be used interchangeably. "Multiple" means two or more. In view of this, in the embodiments of the present application, "multiple" can also be understood as "at least two". "At least one" can be understood as one or more, for example, one, two or more. For example, including at least one means including one, two or more, and there is no limit on which ones are included. For example, including at least one of A, B and C, then the included ones may be A, B, C, A and B, A and C, B and C, or A and B and C. Similarly, the understanding of descriptions such as "at least one" is similar. "At least one of the following" or similar expressions refers to any combination of these items, including any combination of single items or multiple items. For example, "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 three relationships can exist. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character “ / ”, unless otherwise specified, generally indicates that the previous and next associated objects are in an “or” relationship.

[0148] Unless otherwise specified, the ordinal numbers such as "first", "second", "third", and "fourth" mentioned in the embodiments of the present application are used to distinguish multiple objects, and are not used to limit the order, timing, priority or importance of multiple objects, and the descriptions of "first", "second", "third", and "fourth" do not limit the objects to be different.

[0149] like Figure 1a Figure 2 shows a schematic diagram of the fifth generation (5G) network architecture based on a service-oriented architecture. Figure 1a The 5G network architecture shown here can include three parts: the terminal part, the data network (DN), and the operator network part. The functions of some of these network elements are briefly described below.

[0150] The operator network may include, but is not limited to, one or more of the following network elements: a network slice selection function (NSSF) network element, an authentication server function (AUSF) network element, a network exposure function (NEF) network element, a network repository function (NRF) network element, an access and mobility management function (AMF) network element, a policy control function (PCF) network element, a unified data management (UDM) network element, a session management function (SMF) network element, an access network (AN) or a radio access network (RAN), and a user plane function (UPF) network element. In the above-mentioned operator network, the part other than the radio access network part can be referred to as the core network part. In a possible implementation method, the operator network also includes an application function (AF) network element.

[0151] A terminal device (terminal device), also referred to as a terminal, is a device with wireless transceiver capabilities that can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; can also be deployed on water (such as ships); and can also be deployed in the air (such as airplanes, balloons, and satellites). The terminal device can be a tablet computer (pad), a computer with wireless transceiver capabilities, a virtual reality (VR) terminal, an augmented reality (AR) terminal, a wireless terminal in industrial control (industrial control), a wireless terminal in self-driving (self-driving), a wireless terminal in remote medical care, a wireless terminal in smart grids (smart grids), a wireless terminal in transportation safety (transportation safety), a wireless terminal in smart cities (smart cities), a wireless terminal in smart homes (smart homes), user equipment (UE), terminal devices adapted to the Internet of Things (IoT) (such as terminal devices in smart factories, terminal devices in smart manufacturing, etc.), and terminal devices supporting SparkLink short-range communication technology.

[0152] The above-mentioned terminal can establish a connection with the operator network through the interface provided by the operator network (such as N1, etc.), and use the data and / or voice services provided by the operator network. The terminal can also access the DN through the operator network, use the operator services deployed on the DN, and / or services provided by a third party. Among them, the above-mentioned third party may be a service provider other than the operator network and the terminal device, and may provide other data and / or voice services to the terminal device. Among them, the specific form of the above-mentioned third party can be determined according to the actual application scenario and is not limited here.

[0153] The RAN is a subnetwork of the operator network and serves as the implementation system between service nodes and terminal devices within the operator network. To access the operator network, a terminal device first passes through the RAN, and then connects to the operator network's service nodes through the RAN. RAN equipment provides wireless communication capabilities for terminal devices and is also known as access network equipment. RAN equipment includes, but is not limited to, the following: next-generation base stations (gNBs) in 5G, evolved node Bs (eNBs), radio network controllers (RNCs), node Bs (NBs), base station controllers (BSCs), base transceiver stations (BTSs), home base stations (e.g., home evolved node Bs, or HNBs), baseband units (BBUs), transmitting and receiving points (TRPs), transmitting points (TPs), and mobile switching centers.

[0154] The AMF network element mainly performs functions such as mobility management and access authentication / authorization. In addition, it is responsible for transmitting user policies between the UE and the PCF.

[0155] The SMF network element mainly performs functions such as session management, execution of control policies issued by the PCF, selection of the UPF, and allocation of UE Internet Protocol (IP) addresses.

[0156] The UPF network element, as the interface with the data network, completes functions such as user plane data forwarding, session / flow-level billing statistics, and bandwidth limitation.

[0157] The UDM network element is mainly responsible for managing contract data, user access authorization and other functions.

[0158] NSSF network element is mainly responsible for managing information related to network slicing.

[0159] NEF network element is mainly used to support the opening of capabilities and events.

[0160] The AF network element primarily communicates application-side requirements to the network, such as Quality of Service (QoS) requirements or user status event subscriptions. The AF can be a third-party functional entity or an application service deployed by an operator, such as the IP Multimedia Subsystem (IMS) voice call service.

[0161] The PCF network element is primarily responsible for policy control functions such as session and service data flow level billing, QoS bandwidth assurance, mobility management, and UE policy decision-making. In this architecture, the PCFs to which the AMF and SMF are connected correspond to the AM PCF (PCF for Access and Mobility Control) and the SM PCF (PCF for Session Management), respectively. In actual deployment scenarios, they may not be the same PCF entity.

[0162] NRF network elements can be used to provide network element discovery capabilities, providing network element information corresponding to the network element type based on requests from other network elements. NRF also provides network element management services such as network element registration, update, and deregistration, as well as network element status subscription and push.

[0163] AUSF network element: Mainly responsible for authenticating users to determine whether users or devices are allowed to access the network.

[0164] A DN is a network located outside of a carrier network. A carrier network can connect to multiple DNs, and a variety of services can be deployed on the DN, providing data and / or voice services to terminal devices. For example, a DN is the private network of a smart factory. Sensors installed in the workshop can be terminal devices. The DN houses a sensor control server, which provides services to the sensors. Sensors can communicate with the control server, receive instructions from the control server, and transmit collected sensor data to the control server based on the instructions. Another example is a DN that is a company's internal office network. An employee's mobile phone or computer can be a terminal device, allowing them to access information and data resources on the company's internal office network.

[0165] Figure 1a Where, Nnssf, Nausf, Nnef, Nnrf, Namf, Npcf, Nsmf, Nudm, Naf, N1, N2, N3, N4, and N6 are interface sequence numbers. The meanings of these interface sequence numbers can be found in the 3GPP standard protocol and are not limited here.

[0166] When the 5G core network supports untrusted non-3GPP access, the 5G network architecture based on point-to-point interfaces is as follows: Figure 1bAs shown. Among them, the access network includes a 3GPP access network and an untrusted non-3GPP access network. The access equipment in the 3GPP access network can be called a radio access network (RAN) device. The access equipment in the untrusted non-3GPP access network can be called a non-3GPP interworking function (N3IWF) device. The N3IWF device can include, for example, a router, etc.

[0167] like Figure 1b The following is a schematic diagram of the 5G network architecture based on point-to-point interfaces. The functions of the network elements can be found in Figure 1a The introduction of the functions of the corresponding network elements will not be repeated here. Figure 1b and Figure 1a The main differences are: Figure 1b The interfaces between the network elements in the network are point-to-point interfaces, and Figure 1a The interfaces between the various network elements in the network are service-oriented interfaces.

[0168] Figure 1b Where N1, N2, N3, N4, N6, N11, NWu, Y1, and Y2 are interface serial numbers. The meanings of these interface serial numbers can be found in the 3GPP standard protocol and are not limited here.

[0169] 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 different from Figure 1b Similar. Figure 1b Replace the untrusted non-3GPP access in with a trusted non-3GPP access, and replace the N3IWF with a trusted non-3GPP access gateway (trusted non-3GPP gateway function, TNGF); or, Figure 1b The untrusted non-3GPP access in the protocol is replaced with wired network access, and the N3IWF is replaced with a wired access gateway function (W-AGF).

[0170] like Figure 1c The following is a schematic diagram of the 5G network architecture based on point-to-point interfaces. The functions of the network elements can be found in Figure 1a The introduction of the functions of the corresponding network elements will not be repeated here. Figure 1c and Figure 1a The main differences are: Figure 1c The interfaces between the network elements in the network are point-to-point interfaces, and Figure 1a The interfaces between the various network elements in the network are service-oriented interfaces.

[0171] Figure 1c Where N1, N2, N3, N4, N6, N11, NWu, and Uu are interface serial numbers. The meanings of these interface serial numbers can be found in the 3GPP standard protocol and are not limited here.

[0172] It is understood that the above-mentioned network element or function can be a network element in a hardware device, a software function running on dedicated hardware, or a virtualized function instantiated on a platform (e.g., a cloud platform). Optionally, the above-mentioned network element or function can be implemented by a single device, or by multiple devices, or can be a functional module within a single device, and this is not specifically limited in the embodiments of the present application.

[0173] The above describes the application scenarios to which the embodiments of the present application are applicable. Next, the communication method provided by the embodiments of the present application will be described with reference to the accompanying drawings.

[0174] The present invention provides a communication method that can be applied to Figure 1b or Figure 1c When the communication method provided in the embodiment of the present application is applied to the non-3GPP access scenario shown in FIG. Figure 1b In the non-trusted non-3GPP access scenario shown, the access gateway is N3IWF or next generation packet data Gateway (ngPDG). Figure 1c In the trusted non-3GPP access scenario shown, the access gateway is TNGF. Figure 1c In the wired access scenario shown, the access gateway is W-AGF. The access node (also referred to as access device) between the terminal and the access gateway can be a wireless local area network access point (WLAN AP), a fixed access network (FAN) device, a G-node supporting Star Flash short-range communication, a WiFi AP, a Bluetooth access node, a switch, or a router, etc. For the sake of convenience, the embodiment of the present application takes the trusted non-3GPP access scenario, that is, the access gateway is TNGF as an example for explanation.

[0175] In addition, the access and mobility management network element, unified data management, and user plane network element in the embodiment of the present application can be Figure 1a 、 Figure 1b or Figure 1c The AMF, UDM, and UPF mentioned above may also be network elements having the functions of the above-mentioned AMF, UDM, and UPF in future communications such as the sixth generation (6G) network. This embodiment of the present application is not limited to this. For ease of explanation, the embodiment of the present application takes the access and mobility management network element, unified data management, and user plane network element as the above-mentioned AMF, UDM, and UPF, respectively, as an example. Furthermore, the terminal is described as a UE in this application.

[0176] Example 1

[0177] Figure 2 Schematic diagram of the communication method provided in the embodiment of the present application is shown. Figure 2 As shown, this embodiment introduces the communication method provided by this embodiment from the uplink direction and the downlink direction respectively.

[0178] It should be noted that, for ease of understanding, in the following text, the tunnel endpoint identifier (TEID) allocated by TNGF for transmitting control plane data is recorded as TNGF TEID_1, the TEID allocated by TNGF for transmitting user plane data is recorded as TNGF TEID_2, the internet protocol (IP) address allocated by TNGF for transmitting control plane data is recorded as TNGF IP address 1, the IP address allocated by TNGF for transmitting user plane data is recorded as TNGF IP address 2, the TEID allocated by UE for transmitting control plane data is recorded as UE TEID_1, and the TEID allocated by UE for transmitting user plane data is recorded as UE TEID_2.

[0179] For ease of description, the following encapsulation scheme in which a payload is encapsulated with a General Packet Radio Service Tunnel Protocol-User Plane (GTP-U) header, a User Datagram Protocol (UDP) header is encapsulated within the GTP-U header, and an IP header is encapsulated within the UDP header is referred to as GTP-U / UDP / IP. Furthermore, the following encapsulation scheme in which a first message (or third message) is encapsulated with a GTP-U header, a UDP header is encapsulated within the GTP-U header, and an IP header is encapsulated within the UDP header is referred to as message / GTP-U / UDP / IP.

[0180] S201: The UE sends a first data packet to the TNGF, and the TNGF receives the first data packet accordingly.

[0181] The UE can send a 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. For example, the first payload is encapsulated with a first GTP-U header, the first GTP-U header is encapsulated with a first UDP header, and the first UDP header is encapsulated with a first IP header. Specifically, the UE can encapsulate the first payload with a first GTP-U header, encapsulate the first UDP header outside the first GTP-header, and encapsulate the first IP header outside the first UDP header to obtain a first data packet, and send the first data packet to the TNGF through the GTP-U tunnel. The payload can be control plane data, which includes control plane messages, such as non-access stratum (NAS) messages, or other control plane data exchanged between the UE and the TNGF except NAS messages; it can also be user plane data, such as remote control service data.

[0182] The first IP header includes a destination IP address and a source IP address, and the destination IP address and the source IP address are the IP address of the TNGF and the IP address of the UE, respectively. The first GTP-U header includes the TEID of the TNGF. The IP address of the TNGF may be the IP address allocated by the TNGF for transmitting control plane data (denoted as TNGF IP address 1), or the IP address allocated by the TNGF for transmitting user plane data (denoted as TNGF IP address 2). The TEID of the TNGF may be the TEID allocated by the TNGF for transmitting control plane data (denoted as TNGF TEID_1), or the TEID allocated by the TNGF for transmitting user plane data (denoted as TNGF TEID_2). At least one of the IP address of the TNGF or the TEID of the TNGF can be used to identify whether the first load is control plane data or user plane data.

[0183] For example, when the first payload is control plane data, the TEID of the TNGF is the TEID allocated by the TNGF for transmitting control plane data. Specifically, the UE may encapsulate the first payload according to the GTP-U / UDP / IP encapsulation method and fill in the TEID in the GTP-U header as TNGF TEID_1 to indicate that the first payload is control plane data.

[0184] Alternatively, when the first payload is control plane data, the TNGF IP address is the IP address allocated by the TNGF for transmitting the control plane data. Specifically, 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 packet header with TNGF IP address 1 to indicate that the first payload is control plane data.

[0185] Alternatively, when the first payload is control plane data, the TEID of the TNGF is the TEID allocated by the TNGF for transmitting control plane data, and the IP address of the TNGF is the IP address allocated by the TNGF for transmitting control plane data. Specifically, the UE may encapsulate the first payload according to the GTP-U / UDP / IP encapsulation method, and fill in the TEID in the GTP-U header with TNGF TEID_1, and fill in the destination IP address in the IP header with TNGF IP address 1, to indicate that the first payload is control plane data.

[0186] For another example, when the first payload is user plane data, the TEID of the TNGF is the TEID allocated by the TNGF for transmitting user plane data. Specifically, the UE may encapsulate the first payload according to the GTP-U / UDP / IP encapsulation method 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.

[0187] Alternatively, when the first load is user plane data, the IP address of the TNGF is the IP address allocated by the TNGF for transmitting the user plane data. Specifically, the UE may encapsulate the first load according to the GTP-U / UDP / IP encapsulation method and fill in the destination IP address in the IP packet header with TNGF as TNGF IP address 2 to indicate that the first load is user plane data.

[0188] Alternatively, when the first load is user plane data, the TEID of TNGF is the TEID allocated by TNGF for transmitting user plane data, and the IP address of TNGF is the IP address allocated by TNGF for transmitting user plane data. Specifically, the UE can encapsulate the first load according to the GTP-U / UDP / IP encapsulation method, and 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 load is user plane data.

[0189] It is worth noting that the IP address assigned by the TNGF for the transmission of control plane data and the IP address assigned by the TNGF for the transmission of user plane data can be the same or different, that is, the TNGF IP address 1 and the TNGF IP address 2 can be the same or different, and this embodiment of the application does not limit this. For example, the TNGF assigns the same IP address for the transmission of control plane data and user plane data. For another example, the TNGF assigns an IP address for the transmission of control plane data but does not assign an IP address for the transmission of user plane data. In this scenario, the IP address used to transmit user plane data is the same as the IP address used to transmit control plane data.

[0190] As mentioned above, the UE can indicate that the first load is control plane data or user plane data by filling in the destination IP address of the IP packet header with the IP address allocated by the TNGF for the transmission of control plane data or the IP address allocated by the TNGF for the transmission of user plane data, and / or, filling in the TEID in the GTP-U packet header with the TEID allocated by the TNGF for the transmission of control plane data or the TEID allocated by the TNGF for the transmission of user plane data. In one possible implementation, the UE can obtain the IP address and TEID allocated by the TNGF for the transmission of control plane data, as well as the IP address and TEID allocated by the TNGF for the transmission of user plane data, by negotiating with the TNGF; correspondingly, the TNGF can also obtain the TEID allocated by the UE for the transmission of control plane data, as well as the TEID allocated by the UE for the transmission of user plane data, by negotiating with the UE.

[0191] For example, the UE may receive a first request message from the TNGF, which includes the TEID assigned by the TNGF for transmitting control plane data, and the IP address assigned by the TNGF for transmitting control plane data. Accordingly, the UE may send a first response message to the TNGF, which includes the TEID assigned by the UE for transmitting control plane data. The first request message and the first response message may be an extended authentication protocol (EAP) message or a 5G notification (5G-notification) message. For example, the first request message is an extended authentication request (EAP-request) message, and the first response message is an extended authentication response (EAP-response) message. For another example, the first request message and the first response message are both 5G notification messages. Optionally, the first request message may also include the differentiated services code point (DSCP) used to transmit the control plane data.

[0192] For another example, the UE may receive a second request message from the TNGF, where the second request message includes a protocol data unit (PDU) session identifier and a TEID allocated by the TNGF for transmitting user plane data of the PDU session. Accordingly, 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 user plane data of the PDU session.

[0193] The following combination Figure 3 This section describes how the UE and TNGF negotiate the IP address and TEID used to transmit control plane data. Figure 3The flowchart of the method for obtaining the IP address and TEID for transmitting control plane data provided by the embodiment of the present application is shown. Figure 3 As shown, the method may include the following steps.

[0194] S301: A layer (L) 2 connection is established between the UE and the access node.

[0195] For example, the UE may establish an L2 connection with the access node via Bluetooth, Wi-Fi, radio frequency identification (RFID) technology, or Spark short-range communication technology, etc. The access node may be a G-node supporting Spark short-range communication technology, a Wi-Fi AP, or a Bluetooth access point.

[0196] S302: The access node sends an extended authentication request message to the UE. Correspondingly, the UE receives the extended authentication request message.

[0197] The access node may send an extended authentication request message or identity message to the UE. The extended authentication request message or identity message is used to request the identification information of the UE. The identification information of the UE includes at least the network access identifier (NAI) of the UE. The NAI includes the UE's device identification and public land mobile network (PLMN) information, or includes the UE's device identification and service provider information, or includes the UE's device identification, PLMN information and service provider information. For example, the UE's device identification is recorded as device ID, the PLMN information is recorded as PLMN, and the service provider information is recorded as Service provider name, then the NAI can be expressed as: NAI = device ID@PLMN.Service provider name. Optionally, the service provider information can be the Star Alliance identification.

[0198] S303: The UE sends an extended authentication response message to the access node. Correspondingly, the access node receives the extended authentication response message, wherein the extended authentication response message includes the identification information of the UE.

[0199] S304: The access node sends the UE's identification information to the TNGF. Correspondingly, the TNGF receives the UE's identification information.

[0200] The access node may select a TNGF for the UE based on the UE's identification information. For example, the access node may select a TNGF based on 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 UE's identification information to the TNGF via an authentication authorization accounting (AAA) message.

[0201] S305: The TNGF sends a 5G-Start message to the UE. Correspondingly, the UE receives the 5G-Start message.

[0202] Specifically, 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, TNGF determines that the UE needs to access the 5G core network and sends the extended authentication request message or 5G start message to the UE ( Figure 3 Taking the 5G start message as an example.) The extended authentication request message or the 5G start message can be used to instruct the UE to start accessing the 5G core network.

[0203] S306: The UE sends a registration request message to the AMF. Correspondingly, the AMF receives the registration request message.

[0204] Exemplarily, the UE initiates a registration process for accessing the 5G core network, such as the UE sending a registration request message to the AMF through the access node and 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 may be used to indicate the type of the UE, such as indicating that the UE is a UE of a smart factory (such as a robotic 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 embodiment of the present application is not limited to the type of UE in this regard. 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. The embodiment of the present application is not limited to the service type of the UE in this regard.

[0205] It should be noted that the UE sending a registration request message to the AMF through the access node and TNGF can be understood as: the UE sends a 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 the TNGF forwards it to the AMF, that is, the registration request message is transparently transmitted at the access node and TNGF.

[0206] S307: The AMF sends an authentication message to the UDM. The UDM receives the authentication message, which is used to perform the UE authentication process.

[0207] S308: UE and UDM perform authentication process.

[0208] S309: UDM sends the subscription data to AMF. In response, AMF receives the subscription data.

[0209] After the UE is successfully authenticated, the UDM may send the subscription data related to the UE to the AMF. Optionally, the subscription data may include at least one of UE type indication information and service type indication information.

[0210] S310: AMF sends an indication message to TNGF, and TNGF receives the indication message.

[0211] The indication information is used to indicate that there is no need to establish an IPsec tunnel between the UE and the TNGF. Specifically, the AMF can determine that the UE performs a simplified 5G core network access process based on 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, etc., the AMF can 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, etc., the AMF can determine that the UE performs a simplified 5G core network access process. Among them, the simplified 5G core network access process means that there is no need to establish an IPsec tunnel between the UE and the TNGF.

[0212] Currently, for trusted non-3GPP access scenarios, an unencrypted IPsec tunnel is established between the UE and the TNGF; for untrusted non-3GPP access scenarios, an encrypted IPsec tunnel is established between the UE and the N3IWF. That is, regardless of trusted non-3GPP access scenarios or untrusted non-3GPP access scenarios, an IPsec tunnel can be established between the UE and its corresponding access gateway. However, during the establishment of the IPsec tunnel, multiple signaling interactions are required between multiple network elements, which is highly complex. In addition, when transmitting user-plane data based on the IPsec tunnel, the IPsec tunnel encapsulation method requires encapsulating a double-layer IP header outside the user-plane data, resulting in a long header length of the encapsulated data packet, requiring more transmission resources to be consumed, and increasing the delay required for device encapsulation or decapsulation, thereby increasing the power consumption of the device. In step S310, the AMF determines that the UE can perform a simplified 5G core network access process based on the UE type and at least one of the UE's service types, that is, there is no need to establish an IPsec tunnel process, and sends an indication message to the TNGF to indicate that the TNGF does not need to establish an IPsec tunnel with the UE, thereby simplifying the UE's access process to the 5G core network and reducing the problems of transmission resource waste, time extension, and high equipment power consumption caused by the IPsec encapsulation method during user-plane data transmission.

[0213] Furthermore, the AMF may send an N2 message to the TNGF, which includes the indication information to indicate that the TNGF does not need to establish an IPsec tunnel with the UE. Optionally, the N2 message may also include information such as security keys.

[0214] S311: The TNGF sends a first request message to the UE. Correspondingly, the UE receives the first request message.

[0215] 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. After receiving the indication information, TNGF determines that it is not necessary to establish an IPsec tunnel with the UE. Further, TNGF may determine to establish a GTP-U tunnel with the UE. Specifically, TNGF allocates the IP address of TNGF and the TEID of TNGF to the UE, and carries the IP address of TNGF and the TEID of TNGF in an extended authentication request message or a 5G notification message and sends it to the UE. In this embodiment, the IP address of TNGF is the IP address subsequently used to transmit control plane data (i.e., TNGF IP address 1), and the TEID of TNGF is the TEID subsequently used to transmit control plane data (i.e., TNGF TEID_1). Optionally, TNGF may also determine the DSCP subsequently used to transmit control plane data, and carry the DSCP in an extended authentication request message or a 5G notification message and send it to the UE. After receiving the extended authentication request message or 5G notification message, the UE stores the TNGF IP address 1, TNGF TEID_1 and DSCP so as to subsequently send control plane data to the TNGF through the GTP-U tunnel.

[0216] S312: The UE sends a first response message to the TNGF, and the TNGF receives the first response message accordingly.

[0217] The first response message may be an extended authentication response message or a 5G notification message. The first response message includes UETEID_1. After receiving the first request message, the UE determines to establish a GTP-U tunnel with the TNGF. Specifically, the UE allocates the UE's TEID to the TNGF, and carries the UE's TEID in the extended authentication response message or the 5G notification message and sends it to the TNGF. In this embodiment, the UE's TEID is the TEID (i.e., UE TEID_1) subsequently used to transmit control plane data. After receiving the extended authentication response message or the 5G notification message, the TNGF stores the UE TEID_1 so as to subsequently send control plane data to the UE through the GTP-U tunnel.

[0218] Through steps S311 and S312, 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. In addition, the header length of data packets encapsulated using the GTP-U encapsulation method is shorter than that of data packets encapsulated using the IPsec encapsulation method, thereby reducing the problems of transmission resource waste, extended latency, and high device power consumption caused by the IPsec encapsulation method.

[0219] In step S312, the first response message sent by the UE to the TNGF includes UE TEID_1. In another possible implementation, the first response message may not include UE TEID_1. For example, the UE TEID_1 may be a pre-configured fixed value. That is, the first response message may or may not include UE TEID_1, which is not limited in this embodiment of the present application.

[0220] At this point, the UE and the TNGF have completed the negotiation of the IP address and TEID for transmitting control plane data. The following steps S313 to S317 are used to complete the registration of the UE.

[0221] S313: A dynamic host configuration protocol (DHCP) process is performed between the UE and the access node.

[0222] For example, the UE sends a configuration request message to the access node, the configuration request message is used to request the UE's IP address. After receiving the configuration request message, the access node configures an IP address for the UE and sends a configuration response message to the UE, the configuration response message including the UE's IP address.

[0223] It is worth noting that the UE's IP address 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). For example, the UE may obtain the IP address for transmitting control plane data and the IP address for transmitting user plane data respectively through step 313. UE IP address 1 and UE IP address 2 may be the same or different, and this embodiment of the present application is not limited thereto. For ease of understanding, the embodiment of the present application is described as an example in which UE IP address 1 and UE IP address 2 are the same.

[0224] S314: The access node sends a second message to the TNGF. Correspondingly, the TNGF receives the second message.

[0225] Among them, the second message includes the correspondence between the IP address of the UE and the identification information of the UE. The second message can be an AAA message. For example, the access node can carry 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. After receiving the second message, the TNGF stores the correspondence between the IP address of the UE and the identification information of the UE, so that after the TNGF subsequently receives uplink information (control plane data or user plane data), it can determine the identification information of the UE that sends the uplink information. Table 1 shows an example of the correspondence between the IP address of the UE maintained by the TNGF and the identification information of the UE. As shown in Table 1, the 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 identification information 3. It can be understood that Table 1, as an example, does not limit the specific implementation of the correspondence between the IP address of the UE maintained by the TNGF and the identification information of the UE.

[0226] Table 1

[0227] IP address UE identification information IP address 1 Identification information 1 IP address 2 Identification information 2 IP address 3 Identification information 3

[0228] It should be noted that the above step S314 is an optional step. Figure 3 For example, the TNGF may also obtain the correspondence between the UE's IP address and the UE's identification information in other ways, and the embodiments of the present application are not limited thereto.

[0229] S315: The TNGF and the AMF send an N2 connection establishment request message. Correspondingly, the AMF receives the N2 connection establishment request message.

[0230] The N2 connection establishment request message is used to establish an N2 connection between the TNGF and the AMF for the UE.

[0231] S316: AMF sends an N2 connection establishment response message to TNGF. Correspondingly, TNGF receives the N2 connection establishment response message.

[0232] The N2 connection establishment response message is used to indicate that the N2 connection established for the UE is complete. The N2 connection establishment response message may include a NAS registration complete message. The NAS registration complete message is used to indicate that the UE has successfully registered.

[0233] S317: The TNGF sends a third data packet to the UE. Correspondingly, the UE receives the third data packet.

[0234] After receiving the N2 Connection Establishment Response message, the TNGF decapsulates it to obtain the NAS Registration Complete message, encapsulates the NAS Registration Complete message using the GTP-U / UDP / IP encapsulation scheme, obtains a third data packet, and sends the third data packet to the UE. Specifically, the TNGF encapsulates the NAS Registration Complete message with a GTP-U header, sets the TEID in the GTP-U header to UE TEID_1, encapsulates the UDP header within the GTP-U header, and encapsulates the IP header within the UDP header, setting the source IP address and destination IP address in the IP header to TNGF IP Address 1 and the UE's IP address, respectively, to obtain the third data packet.

[0235] At this point, UE registration is completed.

[0236] The above describes the specific implementation method of the UE and TNGF negotiation for the IP address and TEID used to transmit control plane data. Figure 4 This section describes how the UE and TNGF negotiate the IP address and TEID for transmitting user plane data. Figure 4 The flowchart of the method for obtaining the IP address and TEID for transmitting user plane data provided by the embodiment of the present application is shown. Figure 4 As shown, the method may include the following steps.

[0237] S401: The UE sends a session establishment request message to the TNGF. Correspondingly, the TNGF receives the PDU session establishment request message.

[0238] The UE initiates the PDU session establishment process and sends a PDU session establishment request message (PDU session establishment request) to the TNGF. 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. The UE can encapsulate the PDU session establishment request message according to the GTP-U / UDP / IP encapsulation method to obtain an encapsulated data packet and send the encapsulated data packet to the TNGF. Specifically, the UE encapsulates the GTP-U header outside the PDU session establishment request message, fills in the TEID in the GTP-U with the TNGF TEID_1 obtained in the aforementioned step S311, encapsulates the PDU header outside the GTP-U header, and encapsulates the IP header outside the PDU header, and fills in the source IP address and the target IP address in the IP header with the UE's IP address and the TNGF IP address 1 obtained in the aforementioned step S311, respectively, to obtain the encapsulated data packet. Further, after receiving the encapsulated data packet, TNGF decapsulates it to obtain a PDU session establishment request message, and sends the PDU session establishment request message to AMF, that is, executing the content shown in step S402.

[0239] Alternatively, another implementation method is that 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. The UE can encapsulate the PDU session establishment request message according to the message / GTP-U / UDP / IP encapsulation method to obtain an encapsulated data packet and send the encapsulated data packet to the TNGF. Specifically, the UE uses the PDU session establishment request message as a parameter of the first message; encapsulates the GTP-U header outside the first message, fills in the TEID in the GTP-U with the TNGF TEID_1 obtained in the aforementioned step S311, and uses the message type field in the GTP-U header to indicate the message type of the first message; then encapsulates the PDU header outside the GTP-U header, and encapsulates the IP header outside the PDU header, and fills in the source IP address and the target IP address in the IP header with the UE's IP address and the TNGF IP address 1 obtained in the aforementioned step S311, respectively, to obtain an encapsulated data packet. Further, after receiving the encapsulated data packet, TNGF decapsulates it to obtain a PDU session establishment request message, and sends the PDU session establishment request message to AMF, that is, executing the content shown in step S402.

[0240] S402: TNGF sends a PDU session establishment request message to AMF. In response, AMF receives the PDU session establishment request message.

[0241] S403: The AMF network element performs the PDU session establishment process.

[0242] After receiving the PDU session establishment request message, the AMF can interact with other control plane network elements (such as AMF) and user plane network elements (UPF) to perform the PDU session establishment process. Figure 4 Take UPF as an example.

[0243] S404: AMF sends an N2 PDU session establishment request message to TNGF. Correspondingly, TNGF receives the N2 PDU session establishment request message.

[0244] The N2 PDU session establishment request message includes a PDU session identifier (PDU session ID). Optionally, the N2 PDU session establishment request message may also include quality of service (QoS) parameters related to the PDU session, a NAS message indicating successful PDU session establishment, and the like.

[0245] S405: The TNGF sends a second request message to the UE. Correspondingly, the UE receives the second request message.

[0246] The second request message includes the PDU session identifier and TNGF TEID_2. Optionally, the second request message may also include TNGF IP address_2. Specifically, the TNGF may allocate the TEID of the TNGF to the UE based on the PDU session identifier, and carry the TEID of the TNGF in the second request message and send it to the UE. Optionally, the TNGF may also allocate the IP address of the TNGF to the UE based on the PDU session identifier, and carry the IP address of the TNGF in the second request message and send it to the UE. In this embodiment, the TEID of the TNGF is the TEID (i.e., TNGF TEID_2) used to subsequently transmit the user plane data of the PDU session, and the IP address of the TNGF is the IP address (i.e., TNGF IP address 2) used to subsequently transmit the user plane data of the PDU session. 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.

[0247] S406: The UE sends a second response message to the TNGF, and the TNGF receives the second response message accordingly.

[0248] The second response message includes UE TEID_2. Specifically, the UE can allocate the UE's TEID to the TNGF and carry the UE's TEID in the second response message and send it to the UE. In this embodiment, the UE's TEID is the TEID (i.e., UE TEID_2) used to subsequently transmit the user plane data of the PDU session. After receiving the second response message, the TNGF stores UE TEID_2 so that the user plane data of the PDU session can be subsequently sent to the UE through the GTP-U tunnel.

[0249] Optionally, the second response message may also include the IP address of the UE, which may be the IP address obtained by the UE in the aforementioned step S313, or the IP address obtained by the UE through other means. This embodiment of the present application is not limited to this.

[0250] Through steps S405 and S406, a GTP-U tunnel is established between the UE and the TNGF, and information for subsequent transmission of user-plane data for the PDU session, such as TNGF IP address 2, TNGF TEID_2, and UE TEID_2, is negotiated. Furthermore, the header length of data packets encapsulated using GTP-U encapsulation is shorter than that of packets encapsulated using IPsec encapsulation, thereby reducing the waste of transmission resources, latency, and high device power consumption associated with IPsec encapsulation.

[0251] In step S406, the second response message sent by the UE to the TNGF includes UE TEID_2. In another possible implementation method, the second response message may not include UE TEID_2. For example, the UE TEID_2 may be a pre-configured fixed value. That is, the second response message may include UE TEID_2 or may not include UE TEID_2, and this embodiment of the present application is not limited to this. In addition, UE TEID_1 and UE TEID_2 may be the same or different, and this embodiment of the present application is not limited to this.

[0252] S407: The TNGF sends a NAS message to the UE indicating that the PDU session is successfully established. Correspondingly, the UE receives the NAS message indicating that the PDU session is successfully established.

[0253] The NAS message indicating successful PDU session establishment is control plane data. The TNGF encapsulates the NAS message using GTP-U / UDP / IP encapsulation to obtain an encapsulated data packet and sends the encapsulated data packet to the UE. The specific implementation of step S407 can be found in the description of step S317 above and will not be repeated here.

[0254] S408: TNGF sends an N2 PDU Session Establishment Response message to AMF. Correspondingly, AMF receives the N2 PDU Session Establishment Response message.

[0255] After step S408, the AMF interacts with other network elements to continue the PDU session establishment process until the PDU session is established. The implementation process will not be repeated here.

[0256] It is worth noting that one or more PDU sessions can be established between TNGF and UE. When TNGF establishes multiple PDU sessions with UE, TNGF can allocate multiple TNGF TEID_2s for the multiple PDUs, and UE can allocate multiple UE TEID_2s for the multiple PDUs. Among them, each TNGF TEID_2 in the multiple TNGF TEID_2s is different, that is, TNGF can allocate different TEIDs for different PDU sessions. Multiple UE TEID_2s can be the same or different, that is, UE can allocate the same TEID or different TEIDs for different PDU sessions. In order to facilitate the understanding of the embodiments of the present application, unless otherwise specified, the following description will be made by taking the establishment of a PDU session between TNGF and UE as an example.

[0257] The above describes that the UE encapsulates the GTP-U header outside the load. In another possible implementation, the UE can encapsulate the GTP-U header outside the first message, and the load is a parameter of the first message (that is, the first message includes the load). Specifically, the GTE-U header may also include a first message and a message type (message type) field. The message type field can 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 message type of the first message. The first value and the second value may be the same or different.

[0258] When the first value and the second value are the same, such as both are 255, the message type field is used to indicate whether the load encapsulated in the GTP header is user plane data or control plane data, that is, regardless of whether the load encapsulated in the GTP header is user plane data or control plane data, the message type field remains unchanged.

[0259] When the first value and the second value are different, the message type field is used to indicate the message type of the first message encapsulated in the GTP header, and the first message includes control plane data, and the control plane data is at least one of a NAS message and other access side parameters. In this case, the message type field (i.e., the second value) can be used to indicate the message type of the first message. For example, if the second value is 256, the message type of the first message may be a GTP-U message; or, if the second value is 257, the message type of the first message may be a GTP-U request message; or, if the second value is 258, the message type of the first message may be a GTP-U response message, etc. The embodiments of the present application are not limited to this. In this way, the parameters and control plane data between the TNGF and the UE can be encapsulated in a GTP-U header for interaction, which can reduce the number of signaling interactions between the TNGF and the UE and improve the utilization of network resources.

[0260] by Figure 4 Take the process shown as an example, Figure 5 Another flow chart of obtaining an IP address and TEID for transmitting user plane data is shown. Figure 5 Steps 502, S503, S504, and S507 in Figure 4 Steps S402, S403, S404, and S408 are the same except that:

[0261] S501: The UE sends a GTP-U message to the TNGF, and the TNGF receives the GTP-U message accordingly.

[0262] The GTP-U message includes a PDU Session Establishment Request message. The UE initiates the PDU Session Establishment process and encapsulates the PDU Session Establishment Request message using the encapsulation method described in step S401. Specifically, the PDU Session Establishment Request message is encapsulated in a GTP-U header, which is then encapsulated in a UDP header, which is then encapsulated in an IP header. In this case, the message type field in the GTP-U header can be 255.

[0263] Alternatively, in this embodiment, the UE may also use the PDU session establishment request message as a parameter of the first message and encapsulate the first message according to the message / GTP-U / UDP / IP encapsulation method. The first message may be a GTP-U message. Specifically, the UE encapsulates the PDU session establishment request message in a GTP-U message; encapsulates a GTP-U header outside the GTP-U message, and sets the message type field in the GTP-U header to 256; then encapsulates a UDP header outside the GTP-U header, and encapsulates an IP header outside the UDP header. In this case, the message type field in the GTP-U header may be 256.

[0264] The TEID in the GTP-U packet header is TNGF TEID_1, and the destination IP address in the IP packet header is TNGF IP address 1.

[0265] Accordingly, the TNGF can determine that the received uplink information is control plane data based on at least one of the TEID in the GTP-U header and the destination IP address in the IP header. Furthermore, when the message type field is 255, the TNGF can determine that the content carried by the GTP-U header is control plane data; when the message type field is 256, the TNGF can determine that the content carried by the GTP-U header is a GTP-U message. The TNGF then continues to parse the GTP-U message to obtain the control plane data (i.e., the PDU session establishment request message).

[0266] S505: The TNGF sends a GTP-U request message to the UE. Correspondingly, the UE receives the GTP-U request message.

[0267] The GTP-U request message includes a NAS message indicating that the PDU session has been successfully established, as well as 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 indicating that the PDU session has been successfully established as a parameter of the third message, and encapsulate the third message according to the message / GTP-U / UDP / IP encapsulation method. In this embodiment, the third message may be a GTP-U request message. For example, the TNGF may encapsulate the NAS message indicating that the PDU session has been successfully established, the TNGF IP address 2, and the TNGF TEID_2 in the GTP-U request message; encapsulate a GTP-U header outside the GTP-U request message, and fill in the message type field in the GTP-U header with 257; then encapsulate a UDP header outside the GTP-U header, and encapsulate an IP header outside the UDP header. Among them, the TEID in the GTP-U header is UE TEID_1, and the destination IP address in the IP header is TNGF IP address 1.

[0268] Accordingly, the UE can determine that the received downlink information is control plane data based on at least one of the TEID in the GTP-U header and the source IP address in the IP header. If the message type field is 257, the UE can determine that the content carried by the GTP-U header is a GTP-U request message. The UE then continues to parse the GTP-U request message to obtain control plane data (i.e., a NAS message indicating successful PDU session establishment) and parameters (i.e., TNGF IP address 2 and TNGF TEID_2).

[0269] S506: The UE sends a GTP-U response message to the TNGF, and the TNGF receives the GTP-U response message accordingly.

[0270] The GTP-U response message includes UE TEID_2. The UE may also encapsulate UE TEID_2 in the 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. In this case, the message type field in the GTP-U header may be 258. The TEID in the GTP-U header is TNGF TEID_1, and the destination IP address in the IP header is TNGF IP Address 1.

[0271] Accordingly, the TNGF can determine that the received uplink information is control plane data based on at least one of the TEID in the GTP-U header and the destination IP address in the IP header. If the message type field is 258, the TNGF can determine that the content carried by the GTP-U header is a GTP-U response message. The TNGF then continues to parse the GTP-U response message to obtain parameters (i.e., UE TEID_2).

[0272] The above describes that the UE sends the first data packet to the TNGF through the GTP-U tunnel. After receiving the first data packet, the TNGF may execute the contents shown in steps S202 to S204.

[0273] S202: The TNGF determines whether the first payload is control plane data or user plane data based on at least one of the TNGF's IP address and the TNGF's TEID. If the TNGF determines that the first payload is user plane data, the TNGF executes step S203; if the TNGF determines that the first payload is control plane data, the TNGF executes step S204.

[0274] After receiving the first data packet, the TNGF parses it to obtain the TNGF IP address, the TNGF TEID, and the first payload in the first data packet. Further, the TNGF can determine whether the first payload is control plane data or user plane data based on at least one of the TNGF IP address and the TNGF TEID. Specifically, the TNGF can determine whether the first payload is control plane data or user plane data by comparing the TNGF IP address 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 by comparing the TNGF TEID in the first data packet with the TNGF TEID_1 in the aforementioned step S311 and the TNGF TEID_2 in the aforementioned step S405.

[0275] For example, if the TEID of TNGF is TNGF TEID_1, TNGF can determine that the first load is control plane data; or, if the IP address of TNGF is TNGF IP address 1, TNGF can determine that the first load is control plane data; or, if the TEID of TNGF is TNGF TEID_1 and the IP address of TNGF is TNGF IP address 1, TNGF can determine that the first load is control plane data.

[0276] For another example, if the TEID of TNGF is TNGF TEID_2, then 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, if the TEID of TNGF 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.

[0277] In one possible implementation, the first IP packet header includes the IP address of the UE, and the TNGF can determine the identification information of the UE based on 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 based on the identification information of the UE. The context information of the UE includes the identification information of the UE, the N2 interface identifier of the UE, the N2 interface information and the N3 interface information, etc. The N2 interface information can be used to determine the control plane network element for establishing an N2 connection for the UE, and the N3 interface information can be used to determine the user plane network element for establishing an N3 connection for the UE. For example, the first load is control plane data, and the TNGF can determine the control plane network element for establishing an N2 connection for the UE based on the context information of the UE, and then send the first load to the control plane network element via the N2 connection ( Figure 2 For example, the control plane network element is AMF. For another example, the first load is user plane data. The TNGF can determine the user plane network element to establish an N3 connection for the UE based on the UE context information, and then send the first load to the user plane network element through the N3 connection ( Figure 2 Take the user plane network element as UPF as an example).

[0278] S203: The TNGF sends the first payload to the UPF, and the UPF receives the first payload accordingly.

[0279] After the TNGF determines that the first load is user plane data, the TNGF may send the first load to the UPF through the N3 connection.

[0280] S204: The TNGF sends the first payload to the AMF. In response, the AMF receives the first payload.

[0281] After the TNGF determines that the first load is control plane data, the TNGF may send the first load to the AMF through the N2 connection.

[0282] The above steps S201 to S204 describe the specific implementation process of the TNGF distinguishing whether uplink information is control plane data or user plane data in the uplink direction. Next, steps S205a to S208 describe the specific implementation process of the UE distinguishing whether downlink information is control plane data or user plane data in the downlink direction.

[0283] S205a: The UPF sends the second payload to the TNGF. Alternatively, S205b: The AMF sends the second payload to the TNGF. In response, the TNGF receives the second payload.

[0284] The second load may be user plane data or control plane data. For example, when the second load is user plane data, the TNGF may receive the second load from the UPF via the N3 connection, as shown in step S205a. For another example, when the second load is control plane data, the TNGF may receive the second load from the control plane network element ( Figure 2 The second load of AMF is taken as an example, as shown in step S205b.

[0285] It should be understood that step S205b is an optional step. Figure 2 For example, when the second load is control plane data, the second load may be control plane data received by the TNGF from other control plane network elements, or the TNGF may generate the control plane data itself.

[0286] S206: The TNGF generates a second data packet according to the second payload.

[0287] The second data packet includes a second IP header, a second GTP-U header, and a second payload. For example, the second payload is encapsulated with a second GTP-U header, the second GTP-U header is encapsulated with a second UDP header, and the second UDP header is encapsulated with a second IP header. Specifically, the TNGF may encapsulate the second GTP-U header outside the second payload, the second UDP header outside the second GTP-U header, and the second IP header outside the second UDP header to obtain the second data packet.

[0288] The second IP header includes a destination IP address and a source IP address, and the destination IP address and the source IP address are the IP address of the UE and the IP address of the TNGF, respectively. The second GTP-U header includes the TEID of the UE. The IP address of the TNGF may be the IP address allocated by the TNGF for transmitting control plane data (denoted as TNGF IP address 1), or the IP address allocated by the 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 transmitting control plane data (denoted as UE TEID_1), or the TEID allocated by the UE for transmitting user plane data (denoted as UE TEID_2). At least one of the IP address of the TNGF and the TEID of the UE can be used to identify whether the second load is control plane data or user plane data.

[0289] For example, when the second payload is control plane data, the TEID of the UE is the TEID allocated by the UE for transmitting control plane data. Specifically, the TNGF may encapsulate the second payload according to the GTP-U / UDP / IP encapsulation method and fill in the TEID in the GTP-U header as UE TEID_1 to indicate that the second payload is control plane data.

[0290] Alternatively, when the second payload is control plane data, the TNGF IP address is the IP address allocated by the TNGF for transmitting the control plane data. Specifically, the TNGF may encapsulate the second payload using the GTP-U / UDP / IP encapsulation method and set the source IP address in the IP packet header to TNGF IP address 1 to indicate that the second payload is control plane data.

[0291] Alternatively, when the second payload is control plane data, the TEID of the UE is the TEID allocated by the UE for transmitting control plane data, and the IP address of the TNGF is the IP address allocated by the TNGF for transmitting control plane data. Specifically, the TNGF may encapsulate the second payload in accordance with the GTP-U / UDP / IP encapsulation method, and fill in the TEID in the GTP-U header with UE TEID_1, and fill in the source IP address in the IP header with TNGF IP address 1, to indicate that the second payload is control plane data.

[0292] For another example, when the second payload is user plane data, the TEID of the UE is the TEID allocated by the UE for transmitting user plane data. Specifically, the TNGF may encapsulate the second payload according to the GTP-U / UDP / IP encapsulation method and fill in the TEID in the GTP-U header as UE TEID_2 to indicate that the second payload is user plane data.

[0293] Alternatively, when the second payload is user plane data, the IP address of the TNGF is the IP address allocated by the TNGF for transmitting the user plane data. Specifically, the TNGF may encapsulate the second payload in accordance with the GTP-U / UDP / IP encapsulation method and fill in the source IP address in the IP packet header with TNGF is TNGF IP address 2 to indicate that the second payload is user plane data.

[0294] Alternatively, when the second payload is user plane data, the TEID of the UE is the TEID assigned by the UE for transmitting user plane data, and the IP address of the TNGF is the IP address assigned by the TNGF for transmitting user plane data. Specifically, the TNGF may encapsulate the second payload in accordance with the GTP-U / UDP / IP encapsulation method, and fill in the TEID in the GTP-U header with UE TEID_2, and fill in the source IP address in the IP header with TNGF IP address 2, to indicate that the second payload is user plane data.

[0295] S207: The TNGF sends a second data packet to the UE. Correspondingly, the UE receives the second data packet.

[0296] For example, the TNGF sends the second data packet to the UE through the GTP-U tunnel.

[0297] S208: The UE determines 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.

[0298] After receiving the second data packet, the UE parses it to obtain the TNGF IP address, the UE TEID, and the second payload in the second data packet. Further, the UE can determine whether the second payload is control plane data or user plane data based on at least one of the TNGF IP address and the UE TEID. Specifically, the UE can determine whether the second payload is control plane data or user plane data by comparing the TNGF IP address 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 by comparing the UE TEID in the second data packet with the UE TEID_1 in the aforementioned step S312 and the UE TEID_2 in the aforementioned step S406.

[0299] For example, if the TEID of the UE is UE TEID_1, the UE can determine that the second load is control plane data; or, the IP address of the TNGF is TNGF IP address 1, the UE can determine that the second load is control plane data; or, if the TEID of the UE is UE TEID_1 and the IP address of the TNGF is TNGF IP address 1, the UE can determine that the second load is control plane data.

[0300] For another example, if the TEID of the UE is UE TEID_2, the UE can determine that the second load is user plane data; or, if the IP address of the TNGF is TNGF IP address 2, the UE can determine that the second load is user plane data; or, if the TEID of the UE is UETEID_2 and the IP address of the TNGF is TNGF IP address 2, the UE can determine that the second load is user plane data.

[0301] Example 2

[0302] Figure 14 FIG1 shows a flow chart of the communication method provided by an embodiment of the present application. In this embodiment, the first load and the second load are both control plane data. Figure 14 As shown, this embodiment introduces the communication method provided by this embodiment from the downlink direction and the uplink direction respectively.

[0303] It should be noted that, for ease of understanding, the TEID allocated by the TNGF for the transmission of control plane data is denoted as TNGF TEID_1, and the IP address allocated by the TNGF for the transmission of control plane data is denoted as TNGF IP Address 1. Furthermore, for ease of description, the encapsulation mode in which a payload is encapsulated with a GTP-U header, a UDP header is encapsulated with a GTP-U header, and an IP header is encapsulated with the UDP header is denoted as GTP-U / UDP / IP.

[0304] Among them, steps S1401-S1410 and S1411-S1414 in this embodiment are respectively Figure 3 Steps S301-S310 and S313-S316 in the example are the same, except that:

[0305] S1415: TNGF generates a second data packet.

[0306] The second data packet includes a second IP header, a second GTP-U header, and a second payload. In this embodiment, the second payload is a NAS message of registration completion. For example, the NAS message of registration completion is encapsulated with a second GTP-U header, the second GTP-U header is encapsulated with a second UDP header, and the second UDP header is encapsulated with a second IP header. For example, after receiving the N2 connection establishment response message, the TNGF decapsulates it to obtain a NAS message of registration completion, and encapsulates the NAS message of registration completion according to the GTP-U / UDP / IP encapsulation method to obtain the second data packet. Specifically, the TNGF encapsulates the second GTP-U header outside the NAS message of registration completion, 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.

[0307] The second IP header includes a destination IP address and a source IP address, which are the UE's IP address and the TNGF's IP address, respectively. The second GTP-U header includes the TNGF's TEID. In this embodiment, the second payload is a NAS message indicating registration completion, i.e., the second payload is control plane data. The TNGF's IP address is TNGF IP Address 1. Furthermore, the TNGF's TEID is TNGF TEID_1.

[0308] Exemplarily, after receiving the N2 connection establishment response message, the TNGF parses it to obtain a NAS message indicating registration completion; and, based on the instruction information received in step S1410, determines to establish a GTP-U tunnel with the UE and determines to send a NAS message indicating registration completion to the UE via the GTP-U tunnel. Specifically, the TNGF may allocate the TNGF's IP address and TNGF's TEID to the UE, insert the TNGF's IP address and TNGF's TEID into the second IP header and the second GTP-U header, respectively, and encapsulate the NAS message indicating registration completion using the GTP-U / UDP / IP encapsulation method to obtain a second data packet. In this embodiment, the TNGF's IP address allocated by the TNGF to the UE is the IP address subsequently used to transmit control plane data (i.e., TNGF IP address 1); and the TNGF's TEID allocated by the TNGF to the UE is the TEID subsequently used to transmit control plane data (i.e., TNGF TEID_1). Optionally, the TNGF may also determine the DSCP value subsequently used to transmit control plane data and send the DSCP value to the UE in the second data packet.

[0309] It is worth noting that the UE IP address may include an IP address for transmitting control plane data (denoted as UE IP address 1) and an IP address for transmitting user plane data (denoted as UE IP address 2). The method for obtaining the UE IP address can refer to the relevant description of the aforementioned step S313 and will not be repeated here. UE IP address 1 and UE IP address 2 may be the same or different, and this embodiment of the present application does not limit this.

[0310] Similarly, the TNGF IP address may include an IP address for transmitting control plane data (denoted as TNGF IP address 1) and an IP address for transmitting user plane data (denoted as TNGF IP address 2). TNGF IP address 1 and TNGF IP address 2 may be the same or different, and this embodiment of the application does not limit this.

[0311] S1416: The TNGF sends a second data packet to the UE. Correspondingly, the UE receives the second data packet.

[0312] For example, the TNGF sends the second data packet to the UE through the GTP-U tunnel.

[0313] S1417: The UE stores the TNGF IP address 1 and the TNGF TEID_1.

[0314] Exemplarily, the UE may determine that TNGF IP address 1 is the IP address used to transmit control plane data, and that TNGF TEID_1 is the TEID used to transmit control plane data, and store the TNGF IP address 1 and 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 a second payload. In this embodiment, the second payload is a NAS message indicating a registration complete. Further, based on the NAS message indicating a registration complete, the UE may determine that TNGF IP address 1 is the IP address used to transmit control plane data, and that TNGF TEID_1 is the TEID used to transmit control plane data, and store the TNGF IP address 1 and TNGF TEID_1, so that the UE can subsequently send control plane data to the TNGF via a GTP-U tunnel based on the TNGF IP address 1 and TNGF TEID_1. Optionally, the UE may parse the second data packet to obtain a DSCP, and store the DSCP, so that the UE can subsequently send control plane data to the TNGF via a GTP-U tunnel based on the DSCP.

[0315] In one possible implementation, after step S1417, the TNGF may send a fourth data packet to the UE based on the TNGF IP address 1 and the TNGF TEID_1. The fourth data packet includes a fourth payload of control plane data. For example, the TNGF inserts the TNGF IP address 1 and the TNGF TEID_1 into the IP header and the GTP-U header, respectively, and encapsulates the fourth payload using the GTP-U / UDP / IP encapsulation scheme to obtain the fourth data packet. The fourth data packet is then sent to the TNGF via the GTP-U tunnel.

[0316] Accordingly, after receiving the fourth data packet, the UE parses it to obtain the TNGF IP address, TNGF TEID, and fourth payload in the fourth data packet. The UE can determine whether the fourth payload is control plane data or user plane data based on at least one of the TNGF IP address and TNGF TEID. In this embodiment, the TNGF IP address is TNGF IP address 1, and the TNGF TEID is TNGF TEID_1. Further, the UE can determine that the fourth payload is control plane data based on TNGF IP address 1, or based on TNGF TEID_1, or based on both TNGF IP address 1 and TNGF TEID_1.

[0317] In another possible implementation, the UE may also determine whether the fourth payload is control plane data or user plane data by parsing the fourth payload. That is, on the UE side, the UE may determine whether the fourth payload is control plane data or user plane data by at least one of the IP address of the TNGF and the TEID of the TNGF, or may determine whether the fourth payload is control plane data or user plane data by parsing the fourth payload. This embodiment of the present application is not limited to this.

[0318] In the above steps S1414 to S1417, it is introduced that in the downlink direction, TNGF sends TNGF IP address 1 and TNGF TEID_1 to UE through the NAS message of registration completion, so that UE can obtain the IP address and TEID allocated by TNGF for transmitting control plane data. In this way, TNGF does not need to allocate 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 the utilization of network resources. In the subsequent communication process, TNGF can send control plane data to UE through GTP-U tunnel based on TNGF IP address 1 and TNGF TEID_1. Next, in combination with steps S1418 to S1420, it is introduced that in the uplink direction, UE sends control plane data to TNGF through GTP-U tunnel based on TNGF IP address 1 and TNGF TEID_1.

[0319] S1418: The UE sends a first data packet to the TNGF, and the TNGF receives the first data packet accordingly.

[0320] The UE can send a 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. In this embodiment, the first payload is control plane data, such as a NAS message (such as a PDU session establishment request, etc.). For example, the first payload is encapsulated with a first GTP-U header, the first GTP-U header is encapsulated with a first UDP header, and the first UDP header is encapsulated with a first IP header. Specifically, the UE can encapsulate the first payload with a first GTP-U header, encapsulate the first UDP header outside the first GTP-header, and encapsulate the first IP header outside the first UDP header to obtain a first data packet, and send the first data packet to the TNGF through the GTP-U tunnel.

[0321] The first IP header includes a destination IP address and a source IP address, and the destination IP address and the source IP address are the IP address of the TNGF and the IP address of the UE, respectively. The first GTP-U header includes the TEID of the TNGF. In this embodiment, the IP address of the TNGF is the IP address allocated by the TNGF for transmitting control plane data (denoted as TNGF IP address 1); and the TEID of the TNGF is the TEID allocated by the TNGF for transmitting control plane data (denoted as TNGF TEID_1). For example, the UE determines that the first payload sent to the TNGF is control plane data. Further, the UE can 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, respectively, and encapsulate the first payload according to the GTP-U / UDP / IP encapsulation method to obtain the first data packet, and send the first data packet to the TNGF.

[0322] S1419: The TNGF determines that the first payload is control plane data according to at least one of the TNGF IP address 1 and the TNGF TEID_1.

[0323] After receiving the first data packet, the TNGF parses it to obtain the TNGF's IP address, the TNGF's TEID, and the first payload in the first data packet. The TNGF then determines whether the first payload is control plane data or user plane data based on at least one of the TNGF's IP address and the TNGF's TEID. In this embodiment, the TNGF's IP address is TNGF IP address 1, and the TNGF's TEID is TNGFTEID_1. Furthermore, the TNGF can determine that the first payload is control plane data based on TNGF IP address 1, TNGF TEID_1, or both TNGF IP address 1 and TNGF TEID_1.

[0324] S1420: The TNGF sends a first payload to the AMF. In response, the AMF receives the first payload.

[0325] After the TNGF determines that the first load is control plane data, the TNGF may send the first load to the AMF through the N2 connection.

[0326] Example 3

[0327] Figure 6 Schematic diagram of the communication method provided in the embodiment of the present application is shown. Figure 6 As shown, this embodiment introduces the communication method provided by the embodiment of the present application from the uplink direction and the downlink direction respectively.

[0328] For ease of description, in the following text, a payload is encapsulated with a general routing encapsulation (GRE) protocol header, and an IP header is encapsulated outside the GRE protocol header is denoted as GRE / IP.

[0329] S601: The UE sends a first data packet to the TNGF, and the TNGF receives the first data packet accordingly.

[0330] The UE can send a first data packet to the TNGF via the GRE tunnel. The first data packet includes a first GRE protocol header and a first payload. For example, the first payload is encapsulated with a GRE protocol header, and the first IP header is encapsulated with the first GRE protocol header. Specifically, the UE can encapsulate the first GRE protocol header outside the first payload and the first IP header outside the first GRE protocol header to obtain a first data packet, and then send the first data packet to the TNGF via the GRE tunnel.

[0331] The first IP packet header includes a destination IP address and a source IP address, where the destination IP address and the source IP address are the IP address of the TNGF and the IP address of the UE respectively. The first GRE protocol packet header includes a first GRE keyword (GRE key) and a first protocol type (protocol type) field. Figure 7 An example diagram of a GRE protocol packet header is shown. Figure 7 As shown, the GRE protocol header consists of 8 octets. Octet 1 of the GRE protocol header includes a check bit, a key bit, and a sequence number; octet 2 of the GRE protocol header includes the version number; octets 3-4 of the GRE protocol header are the protocol type field; and octets 5-8 of the GRE protocol header are the GRE key. The check bit indicates whether the GRE protocol header includes a checksum field. If the check bit is 0, it indicates that the GRE protocol header does not include a checksum field; if the check bit is 1, it indicates that the GRE protocol header does include a checksum field. The key bit indicates whether the GRE protocol header includes a GRE key. If the key bit is 0, it indicates that the GRE protocol header does not include a GRE key; if the key bit is 1, it indicates that the GRE protocol header does include a GRE key.

[0332] The first GRE key may be a keyword assigned by the TNGF for transmitting control plane data, or the first GRE key may include 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.

[0333] For example, the first payload is control plane data, and the first GRE key is a keyword assigned by the TNGF for transmitting control plane data. Specifically, the UE may encapsulate the first payload using the GRE / IP encapsulation method and set the GREkey in the GRE protocol packet header to the keyword assigned by the TNGF for transmitting control plane data, thereby indicating that the first payload is control plane data.

[0334] Alternatively, the first payload is control plane data, and the first protocol type field is used to indicate that the first payload is control plane data. Specifically, the UE may encapsulate the first payload using a GRE / IP encapsulation method 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 predefined or pre-negotiated between the UE and the TNGF, and is not limited in this embodiment of the present application.

[0335] Alternatively, the first payload is control plane data, the first GRE key is a keyword assigned by the TNGF for transmitting control plane data, and the first protocol type field is used to indicate that the first payload is control plane data. Specifically, the UE may encapsulate the first payload using a GRE / IP encapsulation method, replace the GRE key in the GRE protocol header with the keyword assigned by the TNGF for transmitting control plane data, and use the protocol type field in the GRE protocol header to indicate that the first payload is control plane data.

[0336] For another example, the first payload is user-plane data of a PDU session, and the first GRE key includes the PDU session identifier. Specifically, the UE may encapsulate the first payload in accordance with the GRE / IP encapsulation method and fill in the GRE key in the GRE protocol header as the PDU session identifier to indicate that the first payload is user-plane data of the PDU session. Figure 8 An example diagram of a GRE key is shown. Figure 8As shown, the UE can fill in octet 6 of the GRE key as the PDU session identifier. In addition, octet 5 of the GRE key includes the QoS flow ID (QFI), which is used to identify the QoS flow in the PDU session; octet 8 of the GRE key includes the reflective QoS indicator (RQI), which is used for QoS control of data packets.

[0337] As mentioned above, the UE can identify whether the first payload is control plane data or user plane data through the GRE key field or protocol type field in the GRE protocol packet header. In one possible implementation, the UE can obtain the keyword assigned by the TNGF for transmitting control plane data through negotiation with the TNGF. For example, the UE can receive a first request message from the TNGF, where the first request message includes the keyword assigned by the TNGF for transmitting control plane data. Figure 9 The flowchart of the method for obtaining a keyword for transmitting control plane data provided by an embodiment of the present application is shown. Figure 9 Steps S901 to S910, S913 to S916 in Figure 3 Steps S301 to S310 and S313 to S316 in the embodiment are the same except that:

[0338] S911: The TNGF sends a first request message to the UE. Correspondingly, the UE receives the first request message.

[0339] 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, GRE key, and DSCP for transmitting control plane data. After receiving the indication information, the TNGF determines that an IPsec tunnel does not need to be established with the UE. Further, the TNGF may determine to establish a GRE tunnel with the UE. Specifically, the TNGF allocates the TNGF IP address 1, GRE key, and DSCP for transmitting control plane data to the UE, and carries the TNGF IP address 1, GRE key, and DSCP in an extended authentication request message (or 5G notification message) and sends it to the UE. After receiving the extended authentication request message (or 5G notification message), the UE stores the TNGF IP address 1, GRE key, and DSCP so as to subsequently send control plane data to the TNGF through the GRE tunnel.

[0340] Optionally, the first request message may further include TNGF IP address 2 for transmitting user plane data. For example, the TNGF may allocate TNGF IP address 2 for transmitting user plane data to the UE during the registration process, such as carrying TNGF IP address 2 in the first request message and sending it to the UE. Alternatively, the TNGF may also allocate TNGF IP address 2 for transmitting user plane data to the UE during the PDU session establishment process, as shown in the aforementioned step S405.

[0341] S912: The UE sends a first response message to the TNGF, and the TNGF receives the first response message accordingly.

[0342] The first response message may be an extended authentication response message or a 5G notification message. For example, after receiving the first request message, the UE may send a first response message to the TNGF.

[0343] S917: The TNGF sends a third data packet to the UE. Correspondingly, the UE receives the third data packet.

[0344] After receiving the N2 connection establishment response message, the TNGF decapsulates it to obtain a NAS message indicating that the registration is complete, encapsulates the NAS message indicating that the registration is complete according to the GRE / IP encapsulation method, obtains a third data packet, and sends the third data packet to the UE. Specifically, the TNGF encapsulates a GRE protocol header around the NAS message indicating that the registration is complete, replaces the GRE key in the GRE protocol header with the keyword assigned by the TNGF for transmitting control plane data (and / or uses the protocol type field in the GRE protocol header to indicate that the GRE protocol header includes control plane data); and encapsulates an IP header around the GRE protocol header, replaces the source IP address and destination IP address in the IP header with TNGF IP address 1 and the UE's IP address, respectively, to obtain the third data packet.

[0345] The above describes that the UE sends the first data packet to the TNGF through the GRE tunnel. After receiving the first data packet, the TNGF may execute the contents shown in steps S602 to S604.

[0346] S602: The TNGF determines whether the first payload is control plane data or user plane data based on 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 step S603; if the TNGF determines that the first payload is control plane data, the TNGF executes step S604.

[0347] After receiving the first data packet, the TNGF parses it to obtain the first GRE key, the first protocol type field, and the first payload in the first data packet. Furthermore, the TNGF may determine whether the first payload is control plane data or user plane data based on at least one of the first GRE key and the first protocol type field. For example, the TNGF may determine whether the first payload is control plane data by comparing the first GRE key with the GRE key obtained in step S911.

[0348] For example, if the first GRE key is the GRE key obtained in step S911, the TNGF can determine that the first payload is control plane data; or, if the first protocol type field is used to indicate that the first payload is control plane data, the TNGF can determine that the first payload is control plane data; or, if the first GRE key is the GRE key obtained in step S911 and the first protocol type field is used to indicate that the first payload is control plane data, the TNGF can determine that the first payload is control plane data. For another example, if the first GRE key includes a PDU session identifier, the TNGF can determine that the first payload is user plane data for the PDU session.

[0349] In one possible implementation, the first IP packet header includes the IP address of the UE. The TNGF can determine the UE's identification information based on the UE's IP address and the correspondence between the UE's IP address and the UE's identification information, and determine the UE's context information based on the UE's identification information. The specific implementation process can refer to the description corresponding to the aforementioned step S202, which will not be repeated here.

[0350] S603: The TNGF sends a first payload to the UPF, and the UPF receives the first payload accordingly.

[0351] After the TNGF determines that the first load is user plane data, the TNGF may send the first load to the UPF through the N3 connection.

[0352] S604: The TNGF sends a first payload to the AMF. In response, the AMF receives the first payload.

[0353] After the TNGF determines that the first load is user plane data, the TNGF may send the first load to the AMF through the N2 connection.

[0354] The above steps S601 to S604 describe the specific implementation process of the TNGF distinguishing whether uplink information is control plane data or user plane data in the uplink direction. Next, steps S605a to S608 describe the specific implementation process of the UE distinguishing whether downlink information is control plane data or user plane data in the downlink direction.

[0355] S605a: The UPF sends the second payload to the TNGF. Alternatively, S605b: The AMF sends the second payload to the TNGF. In response, the TNGF receives the second payload.

[0356] The specific implementation process of step S605a and step S605b can refer to the corresponding description of the aforementioned steps S205a and S205b, which will not be repeated here.

[0357] S606: TNGF generates a second data packet.

[0358] The second data packet includes a second GRE protocol header and a second payload. For example, the second payload is encapsulated with the second GRE protocol header, which in turn is encapsulated with the second IP header. Specifically, the TNGF may encapsulate the second GRE protocol header within the second payload and the second IP header within the second GRE protocol header to obtain the second data packet, and then send the second data packet to the UE via the GRE tunnel.

[0359] The second IP packet header includes a destination IP address and a source IP address, where the destination IP address and the source IP address are the IP address of the UE and the IP address of the TNGF, respectively. The second GRE protocol packet header includes a second GRE key and a second protocol type field. The second GRE key can be a keyword assigned by the TNGF for transmitting control plane data, or the second GRE key includes a PDU session identifier. The second protocol type field can 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 can be used to identify whether the second payload is control plane data or user plane data.

[0360] For example, when the second payload is control plane data, the second GRE key is the keyword assigned by the TNGF for transmitting control plane data. Specifically, the TNGF may encapsulate the second payload using the GRE / IP encapsulation method and replace the GRE key in the GRE protocol packet header with the keyword assigned by the TNGF for transmitting control plane data, thereby indicating that the second payload is control plane data.

[0361] Alternatively, when the second payload is control plane data, the second protocol type field is used to indicate that the second payload is control plane data. Specifically, the TNGF may encapsulate the second payload in accordance with the GRE / IP encapsulation method and use the protocol type field in the GRE protocol header to indicate that the second payload is control plane data.

[0362] Alternatively, when the second payload is control plane data, the second GRE key is a keyword assigned by the TNGF for the transmission of control plane data, and the second protocol type field is used to indicate that the second payload is control plane data. Specifically, the TNGF may encapsulate the second payload using the GRE / IP encapsulation method, replace the GRE key in the GRE protocol header with the keyword assigned by the TNGF for the transmission of control plane data, and use the protocol type field in the GRE protocol header to indicate that the second payload is control plane data.

[0363] For another example, when the second payload is user-plane data of a PDU session, the second GRE key includes the PDU session identifier. Specifically, the TNGF may encapsulate the second payload in accordance with the GRE / IP encapsulation method and fill in the GRE key in the GRE protocol header as the PDU session identifier to indicate that the second payload is user-plane data of the PDU session.

[0364] S607: The TNGF sends a second data packet to the UE. Correspondingly, the UE receives the second data packet.

[0365] For example, the TNGF sends the second data packet to the UE through the GRE tunnel.

[0366] S608: The UE determines 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.

[0367] 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. Furthermore, the UE may determine whether the second payload is control plane data or user plane data based on at least one of the second GRE key and the second protocol type field. For example, the UE may determine whether the first payload is control plane data by comparing the second GRE key with the GRE key obtained in step S911.

[0368] For example, if the second GRE key is the GRE key obtained in step S911, the UE can determine that the second payload is control plane data; or, if the second protocol type field is used to indicate that the second payload is control plane data, the UE can determine that the second payload is control plane data; or, if the second GRE key is the GRE key obtained in step S911 and the second protocol type field is used to indicate that the second payload is control plane data, the UE can determine that the second payload is control plane data. For another example, if the second GRE key includes a PDU session identifier, the UE can determine that the second payload is user plane data for the PDU session.

[0369] Example 4

[0370] Figure 10 Schematic diagram of the communication method provided in the embodiment of the present application is shown. Figure 10 As shown, this embodiment introduces the communication method provided by the embodiment of the present application from the uplink direction and the downlink direction respectively.

[0371] For ease of expression, the following text will encapsulate the payload in a GRE protocol header, and the GRE protocol header is encapsulated in an IP header as GRE / IP; the encapsulation method in which the payload is encapsulated in a TCP header, and the TCP header is encapsulated in an IP header is recorded as TCP / IP; and the encapsulation method in which the payload is encapsulated in a GRE protocol header, the GRE protocol header is encapsulated in a TCP header, and the TCP header is encapsulated in an IP header is recorded as GRE / TCP / IP.

[0372] S1001: The UE sends a first payload to the TNGF, and the TNGF receives the first payload accordingly.

[0373] The first payload is encapsulated with a first TCP header, and the first TCP header is encapsulated with a first IP address. For example, the UE can 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 the TNGF through the PCT connection. The first TCP header includes a source port number and a destination port number, and the source port number and the destination port number are the TCP port number of the UE and the TCP port number of the TNGF, respectively. The TCP port number of the UE is the port number allocated by the UE for transmitting control plane data. The TCP port number of the TNGF is the port number allocated by the TNGF for transmitting control plane data.

[0374] Alternatively, the first payload is encapsulated with a first GRE protocol header, and the first IP address is encapsulated with the first GRE protocol header. For example, the UE may encapsulate the first GRE protocol header with the first payload, and the first IP header with the first GRE protocol header to obtain the encapsulated first payload, and then send the encapsulated first payload to the TNGF via the GRE tunnel. The GRE keyword in the first GRE protocol header includes the PDU session identifier.

[0375] The encapsulation method of the first load includes encapsulating the first load in a first TCP header, or includes encapsulating the first load in a first GRE protocol header. The encapsulation method of the first load can be used to identify whether the first load is control plane data or user plane data. For example, when the first load is control plane data, the first load is encapsulated with a first TCP header. Specifically, the UE can encapsulate the first load according to the TCP\IP encapsulation method, and fill in the source port number and destination port number in the TCP header with the TCP port number of the UE and the TCP port number of the TNGF respectively to identify that the first load is control plane data. For another example, when the first load is user plane data, the first load is encapsulated with a first GRE protocol header. Specifically, the UE can encapsulate the first load according to the GRE / IP encapsulation method, and fill in the GRE key in the GRE protocol header as the PDU session identifier to identify that the first load is the user plane data of the PDU session.

[0376] In one possible implementation, a GRE tunnel can be established between the UE and the TNGF, and the GRE tunnel is used to transmit user-plane data. For example, in step 1001, the first payload is user-plane data for a PDU session, and the UE can send a first data packet to the TNGF via 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.

[0377] In another possible implementation, a TCP connection can be established between the UE and the TNGF, where the TCP connection is used to transmit control plane data. For example, in step 1001, the first payload is control plane data, and the UE can send a first data packet to the TNGF via the TCP connection. The TCP connection between the UE and the TNGF can be established in the following two ways.

[0378] In mode 1, an end-to-end TCP connection is established between the UE and the TNGF, which is recorded as TCP connection 1.

[0379] The IP addresses included in the IP header of the data packets transmitted over TCP connection 1 are the UE's IP address and the TNGF's IP address. For example, in step 1001, the UE can send a first data packet to the TNGF via TCP connection 1. The source IP address and destination IP address of the first IP header of the first data packet are the UE's IP address and the TNGF's IP address, respectively. In method 1, data packets between the UE and the TNGF are transparently transmitted at the access node.

[0380] In mode 2, the UE first establishes a TCP connection with the access node, which is recorded as TCP connection 2; the access node then establishes a TCP connection with the TNGF, which is recorded as TCP connection 3.

[0381] The IP addresses included in the IP header of the data packet transmitted over TCP connection 2 are the UE's IP address and the access node's IP address. The IP addresses included in the IP header of the data packet transmitted over TCP connection 3 are the access node's IP address and the TNGF's IP address. For example, in step 1001, the UE may send a first payload to the TNGF via TCP connection 2 and TCP connection 3. Specifically, the UE encapsulates a TCP header outside the first load, encapsulates an IP header outside the TCP header, and fills in the source IP address and destination IP address of the IP header with the IP address of the UE and the IP address of the access node respectively, to obtain the encapsulated first load 1, and sends the encapsulated first load 1 to the access node through TCP connection 2; the access node receives the encapsulated first load 1, parses it to obtain the first load; the access node encapsulates a GRE protocol header outside the first load, encapsulates the GRE protocol header in the TCP header, encapsulates the IP header outside the TCP header, and fills in the source IP address and destination IP address of the IP header with the IP address of the access node and the IP address of the TNGF respectively, to obtain the encapsulated first load 2, and sends the encapsulated first load 2 to the TNGF through TCP connection 3. Among them, the GRE key of the GRE protocol header is the keyword allocated by the access node to the UE.

[0382] When a TCP connection is established between the UE and the TNGF using the above-mentioned method 2, 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 through TCP connection 2; after the access node receives the control plane data, it encapsulates the control plane data according to the GRE / TCP / IP encapsulation method, and sends the encapsulated control plane data to the TNGF through TCP connection 3. In the downlink direction, the 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, it encapsulates the control plane data according to the TCP / IP encapsulation method, and sends the encapsulated control plane data to the UE through TCP connection 2. The specific implementation process is similar to that in the uplink direction and will not be repeated here.

[0383] When establishing a TCP connection between the UE and the TNGF using the aforementioned method 2, the first payload encapsulated with the first TCP header may be: the first payload encapsulated with a third GRE protocol header, and the third GRE protocol header 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 then encapsulates the first IP header outside the first TCP header. The GRE key in the third GRE protocol header is a key assigned by the access node to the UE, denoted as the third GRE key.

[0384] In a possible implementation, the UE may obtain the port number allocated for transmitting control plane data by negotiating with the TNGF. For example, the UE may receive a first request message from the TNGF, where the first request message includes the port number allocated by the TNGF for transmitting control plane data. Figure 11 The flowchart of the method for obtaining the port number for transmitting control plane data provided by the embodiment of the present application is shown. Figure 11 Steps S1101 to S1110, S1113, S1116, and S1117 in Figure 3 Steps S301 to S310, S313, S315, and S316 in the above are the same except that:

[0385] S1111: The TNGF sends a first request message to the UE. Correspondingly, the UE receives the first request message.

[0386] 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. After receiving the indication information, the TNGF determines that an IPsec tunnel does not need to be established between it and 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 transmitting control plane data to the UE, 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) and sends it 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 that the control plane data can be subsequently sent to the TNGF via a TCP connection.

[0387] Optionally, the first request message may further include TNGF IP address 2 for transmitting user plane data. For example, the TNGF may allocate TNGF IP address 2 for transmitting user plane data to the UE during the registration process, such as carrying TNGF IP address 2 in the first request message and sending it to the UE. Alternatively, the TNGF may also allocate TNGF IP address 2 for transmitting user plane data to the UE during the PDU session establishment process, as shown in the aforementioned step S405.

[0388] S1112: The UE sends a first response message to the TNGF, and the TNGF receives the first response message accordingly.

[0389] The first response message may be an extended authentication response message or a 5G notification message. For example, after receiving the first request message, the UE may send a first response message to the TNGF. Optionally, the first response message may include the UE's TCP port number.

[0390] S1114: The access node sends a second message to the TNGF. Correspondingly, the TNGF receives the second message.

[0391] Among them, the second message includes the correspondence between the UE's IP address and the UE's identification information, or includes the correspondence between the third GRE key and the UE's identification information, or includes the correspondence between the UE's IP address and the UE's identification information and the correspondence between the third GRE key and the UE's identification information. The second message can be an AAA message. For example, the access node can allocate a GRE key to the UE, recorded as the third GRE key, and carry the correspondence between the third GRE key and the UE's identification information in the AAA message and send it to the TNGF. After receiving the second message, the TNGF stores the correspondence between the third GRE key and the UE's identification information. In this way, when the TNGF subsequently receives uplink information (control plane data) through TCP connection 3, it can determine the identification information of the UE that sends the uplink information based on the correspondence between the third GRE key and the UE's identification information. Table 2 shows an example of the correspondence between the GRE key maintained by the TNGF and the UE's identification information. As shown in Table 2, TNGF establishes connections with three UEs, where the UE identification information corresponding to GRE key 1 is identification information 1, the UE identification information corresponding to GRE key 2 is identification information 2, and the UE identification information corresponding to GRE key 3 is identification information 3. It will be understood that Table 2 is an example and does not limit the specific implementation of the correspondence between the GRE keys maintained by TNGF and the UE identification information.

[0392] Table 2

[0393] GRE key UE identification information GRE key 1 Identification information 1 GRE key2 Identification information 2 GRE key 3 Identification information 3

[0394] It should be noted that the above step S1114 is an optional step. Figure 11 denoted by a dotted line. For example, the TNGF may also obtain the correspondence between the GRE key and the UE's identification information through other means, and the embodiments of the present application are not limited thereto. Furthermore, the correspondence between the UE's IP address and the UE's identification information reported by the access node to the TNGF can be referred to in the corresponding content of the aforementioned step S314 and will not be repeated here.

[0395] S1115: A TCP connection is established between the UE and the TNGF.

[0396] The UE initiates a TCP connection to the TNGF, and a TCP connection is established between the UE and the TNGF, which is used to transmit control plane data. The TCP connection between the UE and the TNGF can be established by the above two methods, which will not be repeated here.

[0397] S1118: The UE sends a third payload to the TNGF, and the TNGF receives the third payload accordingly.

[0398] When the third payload is user plane data, the UE can send the third payload to the TNGF via the GRE tunnel. For the specific implementation process, please refer to the relevant description of step S1001 above and will not be repeated here. When the third payload is control plane data, the UE can send the third payload to the TNGF via TCP connection 1 (or TCP connection 2 and TCP connection 3). For the specific implementation process, please refer to the relevant description of step S1001 above and will not be repeated here.

[0399] In one possible implementation, when the third payload is control plane data, a TCP header is encapsulated outside the third encapsulation. The source port number and destination port number of the TCP header are the TCP port number of the UE and the TCP port number of the TNGF, respectively. After receiving the encapsulated third payload, the TNGF parses it, obtains the TCP port number of the UE, and stores it for subsequent transmission of control plane data to the UE via the TCP connection.

[0400] The above describes that the UE sends the first payload to the TNGF. After receiving the first payload, the TNGF may execute the contents shown in steps S1102 to S1104.

[0401] S1002: The TNGF determines whether the first payload is control plane data or user plane data based on the encapsulation method of the first payload. If the TNGF determines that the first payload is user plane data, the TNGF executes the contents of step S1003; if the TNGF determines that the first payload is control plane data, the TNGF executes the contents of step S1004.

[0402] After receiving the first data packet, TNGF parses it to obtain the encapsulation method of the first payload. Further, TNGF can determine whether the first payload is control plane data or user plane data based on the encapsulation method of the first payload. For example, if the first payload is encapsulated with a first TCP header, TNGF can determine that the first payload is control plane data; or, if the first payload is encapsulated with a third GRE protocol header, and the third GRE protocol header is encapsulated in the first TCP header, TNGF can determine that the first payload is control plane data, wherein the GRE key of the third GRE protocol header includes the third GRE key. For another example, if 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, TNGF can determine that the first payload is user plane data of the PDU session.

[0403] In one possible implementation, the first IP packet header includes the IP address of the UE. The TNGF can determine the UE's identification information based on the UE's IP address and the correspondence between the UE's IP address and the UE's identification information, and determine the UE's context information based on the UE's identification information. The specific implementation process can refer to the description corresponding to the aforementioned step S202, which will not be repeated here.

[0404] In another possible implementation, the first load is control plane data, and the first load is encapsulated in a third GRE protocol header, that is, the TNGF receives the first load of the UE through TCP connection 1 and TCP connection 2. The TNGF can determine the identification information of the UE based on the GRE key of the third GRE protocol header and the correspondence between the GRE key and the identification information of the UE, and determine the context information of the UE based on 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 N2 interface information and the N3 interface information. The N2 interface information can be used to determine the control plane network element for establishing an N2 connection for the UE. For example, the TNGF can determine the control plane network element for establishing an N2 connection for the UE based on the context information of the UE, and then send the first load to the control plane network element through the N2 connection ( Figure 2 Take the control plane network element as AMF as an example).

[0405] S1003: The TNGF sends a first payload to the UPF, and the UPF receives the first payload accordingly.

[0406] After the TNGF determines that the first load is user plane data, the TNGF may send the first load to the UPF through the N3 connection.

[0407] S1004: The TNGF sends a first payload to the AMF. In response, the AMF receives the first payload.

[0408] After the TNGF determines that the first load is user plane data, the TNGF may send the first load to the AMF through the N2 connection.

[0409] The above steps S1001 to S1004 describe the specific implementation process of the TNGF distinguishing whether uplink information is control plane data or user plane data in the uplink direction. Next, combined with steps S605a to S608, the specific implementation process of the UE distinguishing whether downlink information is control plane data or user plane data in the downlink direction is described.

[0410] S1005a: The UPF sends the second payload to the TNGF. Alternatively, S1005b: The AMF sends the second payload to the TNGF. In response, the TNGF receives the second payload.

[0411] The specific implementation process of step S1005a and step S1005b can refer to the corresponding description of the aforementioned steps S205a and S205b, which will not be repeated here.

[0412] S1006: The TNGF sends a second payload to the UE. Correspondingly, the UE receives the second payload.

[0413] When the second payload is control plane data, a second TCP header is encapsulated outside the second payload. For example, the TNGF can encapsulate the second TCP header outside the second payload, and the second IP header outside the second TCP header to obtain the encapsulated second payload, and then send the encapsulated second payload to the UE via a TCP connection. The second TCP header includes a source port number and a destination port number, which are the TCP port number of the TNGF and the TCP port number of the UE, respectively. The second IP header includes a source IP address and a destination IP address, which are the TNGF IP address 1 and the UE's IP address, respectively.

[0414] Alternatively, when the second payload is control plane data, a fourth GRE protocol header is encapsulated outside the second payload, and a second TCP header is encapsulated outside the second payload. For example, the TNGF can 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 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 header includes a source port number and a destination port number, which are the TCP port number of the TNGF and the TCP port number of the UE, respectively. The second IP header includes a source IP address and a destination IP address, which are the TNGF IP address 1 and the UE's IP address, respectively.

[0415] Alternatively, when the second payload is user plane data, a second GRE protocol header is encapsulated outside the second payload. For example, the TNGF can 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 then send the encapsulated second payload to the UE via the GRE tunnel. The GRE key in the second GRE protocol header includes the PDU session identifier. The second IP header includes a source IP address and a destination IP address, where the source address and the destination IP address are TNGF IP address 1 and the UE's IP address, respectively.

[0416] S1007: The UE determines whether the second payload is control plane data or user plane data according to the encapsulation method of the second payload.

[0417] After receiving the encapsulated second payload, the UE parses it to obtain the encapsulation method of the second payload. Furthermore, the UE can determine whether the second payload is control plane data or user plane data based on the encapsulation method of the second payload. For example, if the second payload is encapsulated with a second TCP header, the UE can 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 can determine that the second payload is user plane data.

[0418] Through the above introduction to the scheme of the present application, it can be understood that, in order to realize the above functions, each of the above devices includes a hardware structure and / or software module corresponding to the execution of each function. It should be easily appreciated by those skilled in the art that, in combination with the units and algorithm steps of each example described in the embodiments disclosed herein, the present invention can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of the present invention.

[0419] Combination of the above Figure 1a-Figure 1c , Figures 2 to 11 The method provided in the embodiment of the present application is described in detail. Figure 12 and Figure 13 The apparatus provided in the embodiments of the present application will be described in detail. It should be understood that the description of the apparatus embodiment and the description of the method embodiment may correspond to each other. Therefore, for matters not described in detail, reference may be made to the description of the method embodiment above.

[0420] Figure 12 This is a schematic block diagram of a communication device 1200 provided in an embodiment of the present application, including a communication unit 1201 and a processing unit 1202. Communication unit 1201 is used for external communication and may also be referred to as a communication interface, a transceiver unit, or an input or output interface. Processing unit 1202 can read data or instructions from a storage unit, enabling communication device 1200 to implement the methods of the above embodiments.

[0421] In one example, the communication device 1200 may be an access gateway or a chip in an access gateway.

[0422] For example, the communication unit 1201 is configured to receive a first data packet from a terminal, the first data packet including a first IP header, a first GTP-U header, and a first payload, the first IP header including the IP address of the access gateway, and the first GTP-U header including the TEID of the access gateway. The processing unit 1202 is configured to determine, based on 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.

[0423] In one possible implementation, the processing unit 1202 is configured to perform one or more of the following:

[0424] When the TEID of the access gateway is a TEID allocated by the access gateway for transmitting the control plane data, it is determined that the first payload is the control plane data.

[0425] Alternatively, when the TEID of the access gateway is a TEID allocated by the access gateway for transmitting the user plane data, it is determined that the first load is the user plane data.

[0426] Alternatively, when the IP address of the access gateway is an IP address allocated by the access gateway for transmitting the control plane data, it is determined that the first load is the control plane data.

[0427] Alternatively, when the IP address of the access gateway is an IP address allocated by the access gateway for transmitting the user plane data, it is determined that the first load is the user plane data.

[0428] Alternatively, when the TEID of the access gateway is the TEID allocated by the access gateway for transmitting the control plane data, and the IP address of the access network is the IP address allocated by the access gateway for transmitting the control plane data, it is determined that the first load is the control plane data.

[0429] Alternatively, when the TEID of the access gateway is the TEID allocated by the access gateway for transmitting the user plane data, and the IP address of the access network is the IP address allocated by the access gateway for transmitting the user plane data, it is determined that the first load is the user plane data.

[0430] In one possible implementation, the first GTP-U packet header also includes a message type field, the first data packet also includes a first message, and the first message includes the first load; when the first load is the control plane data, the message type field is used to indicate the message type of the first message.

[0431] In one possible implementation, before the access gateway receives the first data packet from the terminal, the communication unit 1201 is used 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. Optionally, the communication unit 1201 can also be used to 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.

[0432] In one possible implementation, the method may further include: the communication unit 1201 is configured to send a second request message to the terminal, the second request message including a protocol data unit (PDU) session identifier and the TEID of the access gateway, wherein the TEID of the access gateway is a TEID allocated by the access gateway for the user plane data of the PDU session. Optionally, the communication unit 1201 may also be configured to receive a second response message from the terminal, the second response message including the TEID of the terminal, and the TEID of the terminal is a TEID allocated by the terminal for the user plane data of the PDU session.

[0433] In a possible implementation, the second request message further includes the IP address of the access gateway, where the IP address of the access gateway is an IP address allocated by the access gateway for user plane data of the PDU session.

[0434] In one possible implementation, before the access gateway receives the first data packet from the terminal, the communication unit 1201 is used to receive indication information from the access and mobility management function network element, where the indication information is used to indicate that no Internetwork Security Protocol tunnel needs to be established between the access gateway and the terminal.

[0435] In one possible implementation, the first IP packet header also includes the IP address of the terminal, and the processing unit 1202 is used to determine the identification information of the terminal based on the IP address of the terminal and the correspondence between the IP address of the terminal and the identification information of the terminal; and determine the context information of the terminal based on the identification information of the terminal.

[0436] In a possible implementation, the communication unit 1201 is configured to receive a second message from an access node, where the second message includes a correspondence between the IP address of the terminal and the identification information of the terminal.

[0437] In one possible implementation, the communication unit 1201 is used to send a second data packet to the terminal, the second data packet including a second IP header, a second GTP-U header and a second load, the second IP header including the IP address of the access gateway, and the second GTP-U header including 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 access gateway for transmitting the user plane data.

[0438] In one possible implementation, the communication unit 1201 is further used to send a second data packet to the terminal, the second data packet including a second IP header, a second GTP-U header and a second payload, the second IP header including the IP address of the access gateway, and the second GTP-U header including the TEID of the access gateway; wherein, the second payload 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, and the TEID of the access gateway is the TEID allocated by the access gateway for transmitting the control plane data.

[0439] For another example, the communication unit 1201 is configured to receive a first data packet from a terminal, the first data packet including a first Generic Routing Encapsulation (GRE) protocol header and a first payload, the first GRE protocol header including a first GRE keyword and a first protocol type field. The processing unit 1202 is configured to determine, based on 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.

[0440] In one possible implementation, the processing unit 1202 is configured to perform one or more of the following:

[0441] When the first GRE keyword is a keyword allocated by the access gateway for transmitting the control plane data, it is determined that the first payload is the control plane data.

[0442] Alternatively, when the first protocol type field is used to indicate that the first payload is the control plane data, it is determined that the first payload is the control plane data.

[0443] Alternatively, when the first GRE keyword is a keyword allocated by the access gateway for transmitting the control plane data, and the first protocol type field is used to indicate that the first payload is the control plane data, it is determined that the first payload is the control plane data.

[0444] Alternatively, when the first GRE keyword includes a protocol data unit (PDU) session identifier, it is determined that the first payload is user plane data of the PDU session.

[0445] In one possible implementation, before the access gateway receives the first data packet from the terminal, the communication unit 1201 is used to send a first request message to the terminal, wherein the first request message includes the Internet Interconnection Protocol address of the access gateway and a keyword assigned by the access gateway for transmitting the control plane data.

[0446] In one possible implementation, before the access gateway receives the first data packet from the terminal, the communication unit 1201 is used to receive indication information from the access and mobility management function network element, where the indication information is used to indicate that no Internetwork Security Protocol tunnel needs to be established between the access gateway and the terminal.

[0447] In one possible implementation, the first data packet also includes a first IP packet header, which includes the IP address of the terminal. The processing unit 1202 is used to determine the identification information of the terminal based on the IP address of the terminal and the correspondence between the IP address of the terminal and the identification information of the terminal; and determine the context information of the terminal based on the identification information of the terminal.

[0448] In a possible implementation, the communication unit 1201 is configured to receive a second message from an access node, where the second message includes a correspondence between the IP address of the terminal and the identification information of the terminal.

[0449] In one possible implementation, the communication unit 1201 is used to send a second data packet to the terminal, the second data packet including a second GRE protocol header and a second payload, the second GRE protocol header including a second GRE keyword and a second protocol type field; wherein, when the second payload is the control message, the second GRE keyword is a keyword assigned by the access gateway for transmitting the control plane data, and / or the second protocol type field is used to indicate that the second payload is the control plane data; or, when the second payload is user plane data of a PDU session, the second GRE keyword includes the PDU session identifier.

[0450] For another example, the communication unit 1201 is configured to receive a first payload from a terminal, wherein the first payload is encapsulated with a first Transmission Control Protocol (TCP) packet header, or the first payload is encapsulated with a first Generic Routing Encapsulation (GRE) protocol packet header. The processing unit 1202 is configured to determine, based on the encapsulation method of the first payload, whether the first payload is control plane data or user plane data.

[0451] In a possible implementation, the first TCP packet header includes a port number allocated by the access gateway for transmitting the control plane data, and the GRE keyword in the first GRE protocol packet header includes a protocol data unit (PDU) session identifier.

[0452] In one possible implementation, the processing unit 1202 is configured to perform one or more of the following:

[0453] When the first payload is encapsulated with the first TCP packet header, it is determined that the first payload is the control plane data.

[0454] Alternatively, when the first payload is encapsulated with the first GRE protocol header, it is determined that the first payload is user plane data of the PDU session.

[0455] In a possible implementation, the first payload is encapsulated in the first TCP packet header. This may be: the first payload is encapsulated in a third GRE protocol packet header, and the third GRE protocol packet header is encapsulated in the first TCP packet header.

[0456] In one possible implementation, the third GRE protocol packet header includes a third GRE keyword, which is a keyword assigned by the access node to the terminal. The processing unit 1202 is used to determine the identification information of the terminal based on the third GRE keyword and the correspondence between the third GRE keyword and the identification information of the terminal; and determine the context information of the terminal based on the identification information of the terminal.

[0457] In a possible implementation, the communication unit 1201 is configured to receive a second message from an access node, where the second message includes a correspondence between the third GRE keyword and the identification information of the terminal.

[0458] In one possible implementation, the first TCP packet header is encapsulated with a first Internet Protocol packet header, or the first GRE protocol packet header is encapsulated with a first IP packet header, and the first IP packet header includes the IP address of the terminal. The processing unit 1202 is used to determine the identification information of the terminal based on the IP address of the terminal and the correspondence between the IP address of the terminal and the identification information of the terminal; and determine the context information of the terminal based on the identification information of the terminal.

[0459] In a possible implementation, the communication unit 1201 is configured to receive a second message from an access node, where the second message includes a correspondence between the IP address of the terminal and the identification information of the terminal.

[0460] In one possible implementation, before the access gateway receives the first load from the terminal, the communication unit 1201 is used to send a first request message to the terminal, wherein 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 IP address of the access gateway is the IP address allocated by the access gateway for transmitting the control plane data.

[0461] In a possible implementation manner, the first request message includes an IP address allocated by the access gateway for transmitting user plane data.

[0462] In one possible implementation, before the access gateway receives the first load from the terminal, the communication unit 1201 is used to receive indication information from the access and mobility management function network element, where the indication information is used to indicate that no Internetwork Security Protocol tunnel needs to be established between the access gateway and the terminal.

[0463] In one possible implementation, the communication unit 1201 is used to send a second payload to the terminal, and the second payload is encapsulated with a second TCP packet header, or the second payload is encapsulated with a second GRE protocol packet header; wherein, when the second payload is the control plane data, the second payload is encapsulated with the second TCP packet header, and the second TCP packet header includes the port number allocated by the terminal for transmitting the control plane data; or, when the second payload is the user plane data of the PDU, the second payload is encapsulated with a second GRE protocol packet header, and the GRE keyword in the second GRE protocol packet header includes the PDU session identifier.

[0464] In one possible implementation, 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.

[0465] In another example, the communication device 1200 may be a terminal or a chip in a terminal.

[0466] For example, the communication unit 1201 is used for a second data packet from an access gateway, the second data packet including a second Internet Protocol (IP) header, a second General Packet Radio Service Tunneling Protocol-User Plane (GTP-U) header, and a second payload, the second IP header including the IP address of the access gateway, the second GTP-U header including the tunnel endpoint identifier (TEID) of the terminal or including the tunnel endpoint identifier (TEID) of the access gateway. The processing unit 1202 is used to determine whether the second payload is control plane data or user plane data based on at least one of the IP address of the access gateway and the TEID of the terminal, or based on at least one of the IP address of the access gateway and the TEID of the access gateway.

[0467] In one possible implementation, the processing unit 1202 is configured to perform one or more of the following:

[0468] When the TEID of the terminal is a TEID allocated by the terminal for transmitting the control plane data, it is determined that the second payload is the control plane data.

[0469] Alternatively, when the TEID of the terminal is a TEID allocated by the terminal for transmitting the user plane data, it is determined that the second load is the user plane data.

[0470] Alternatively, when the IP address of the access gateway is an IP address allocated by the access gateway for transmitting the control plane data, it is determined that the second load is the control plane data.

[0471] Alternatively, when the IP address of the access gateway is an IP address allocated by the access gateway for transmitting the user plane data, it is determined that the second load is the user plane data.

[0472] Alternatively, when the TEID of the terminal is a TEID allocated by the terminal for transmitting the control plane data, and the IP address of the access network is an IP address allocated by the access gateway for transmitting the control plane data, it is determined that the second load is the control plane data.

[0473] Alternatively, when the TEID of the terminal is a TEID allocated by the terminal for transmitting the user plane data, and the IP address of the access network is an IP address allocated by the access gateway for transmitting the user plane data, it is determined that the second load is the user plane data.

[0474] In one possible implementation, the second GTP-U packet header also includes a message type field, the second data packet also includes a third message, and the third message includes the second load; when the second load is the control plane data, the message type field is used to indicate the message type of the third message.

[0475] In one possible implementation, before the terminal receives the second data packet from the access gateway, the communication unit 1201 is used to receive a first request message from the access gateway, 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. Optionally, the communication unit 1201 can also be used to send a first response message to the access gateway, 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.

[0476] In one possible implementation, the communication unit 1201 is configured to receive a second request message from the access gateway, the second request message including a protocol data unit (PDU) session identifier and the TEID of the access gateway, wherein the TEID of the access gateway is a TEID allocated by the access gateway for user-plane data of the PDU session. Optionally, the communication unit 1201 may also be configured to send a second response message to the access gateway, the second response message including the TEID of the terminal, the TEID of the terminal being a TEID allocated by the terminal for user-plane data of the PDU session.

[0477] In a possible implementation, the second request message further includes the IP address of the access gateway, where the IP address of the access gateway is an IP address allocated by the access gateway for user plane data of the PDU session.

[0478] In one possible implementation, the communication unit 1201 is used to send a first data packet to the access gateway, the first data packet including a first IP header, a first GTP-U header and a first payload, the first IP header including the IP address of the access gateway, and the first GTP-U header including the TEID of the access gateway; wherein, when the first payload 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, 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 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 user plane data, and / or the TEID of the access gateway is the TEID allocated by the access gateway for transmitting the user plane data.

[0479] In one possible implementation, the processing unit 1202 is configured to perform one or more of the following:

[0480] When the TEID of the access gateway is a TEID allocated by the access gateway for transmitting the control plane data, it is determined that the second payload is the control plane data.

[0481] Alternatively, when the IP address of the access gateway is an IP address allocated by the access gateway for transmitting the control plane data, it is determined that the second load is the control plane data.

[0482] Alternatively, when the TEID of the access gateway is the TEID allocated by the access gateway for transmitting the control plane data, and the IP address of the access gateway is the IP address allocated by the access gateway for transmitting the control plane data, it is determined that the second load is the control plane data.

[0483] For another example, the communication unit 1201 is configured to receive a second data packet from an access gateway, the second data packet including a second Generic Routing Encapsulation (GRE) protocol header and a second payload, the second GRE protocol header including a second GRE keyword and a second protocol type field. The processing unit 1202 is configured to determine, based on 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.

[0484] In one possible implementation, the processing unit 1202 is configured to perform one or more of the following:

[0485] When the second GRE keyword is a keyword allocated by the access gateway for transmitting the control plane data, it is determined that the second payload is the control plane data.

[0486] Alternatively, when the second protocol type field is used to indicate that the first payload is the control plane data, it is determined that the second payload is the control plane data.

[0487] Alternatively, when the second GRE keyword is a keyword assigned by the access gateway for transmitting the control plane data, and the second protocol type field is used to indicate that the first load is the control plane data, it is determined that the second load is the control plane data.

[0488] Alternatively, when the second GRE keyword includes a protocol data unit (PDU) session identifier, it is determined that the second payload is user plane data of the PDU session.

[0489] In one possible implementation, before the terminal receives a second data packet from the access gateway, the communication unit 1201 is used to receive a first request message from the access gateway, 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 assigned by the access gateway for transmitting the control plane data.

[0490] In one possible implementation, the communication unit 1201 is used to send a first data packet to the access gateway, the first data packet including a first GRE protocol header and a first payload, 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 a keyword assigned by the access gateway for transmitting the control plane data, and / or the first protocol type field is used to indicate that the first payload is the control plane data; or, when the first payload is user plane data of a PDU session, the first GRE keyword includes the PDU session identifier.

[0491] For another example, the communication unit 1201 is configured to receive a second payload from the access gateway, wherein the second payload is encapsulated with a second Transmission Control Protocol (TCP) packet header, or the second payload is encapsulated with a second Generic Routing Encapsulation (GRE) protocol packet header. The processing unit 1202 is configured to determine, based on the encapsulation method of the second payload, whether the second payload is control plane data or user plane data.

[0492] In a possible implementation, the second TCP packet header includes a port number allocated by the terminal for transmitting the control plane data, and the GRE keyword in the second GRE protocol packet header includes a protocol data unit (PDU) session identifier.

[0493] In one possible implementation, the processing unit 1202 is configured to perform one or more of the following:

[0494] When the second payload is encapsulated with the second TCP packet header, it is determined that the second payload is the control plane data.

[0495] Alternatively, when the second payload is encapsulated with the second GRE protocol header, it is determined that the first payload is user plane data of the PDU session.

[0496] In one possible implementation, the second payload is encapsulated with the second TCP header, including: the second payload is encapsulated with a fourth GRE protocol header, 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.

[0497] In one possible implementation, before the terminal receives the second load from the access gateway, the communication unit 1201 is used to receive a first request message from the access gateway, wherein 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 IP address of the access gateway is the IP address allocated by the access gateway for transmitting the control plane data.

[0498] In a possible implementation manner, the first request message further includes an IP address allocated by the access gateway for transmitting user plane data.

[0499] In one possible implementation, the communication unit 1201 is used to send a first payload to the access gateway, wherein the first payload is encapsulated with a first TCP packet header, or the first payload is encapsulated with a first GRE protocol packet header; wherein, when the first payload is the control plane data, the first payload is encapsulated with the first TCP packet header, and the first TCP packet header includes the port number allocated by the access gateway for transmitting the control plane data; or, when the first payload is the user plane data of the PDU, the first payload is encapsulated with a first GRE protocol packet header, and the GRE keyword in the first GRE protocol packet header includes the PDU session identifier.

[0500] In one possible implementation, 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.

[0501] In another example, the communication device 1200 may also be an access node or a chip in an access node.

[0502] For example, the communication unit 1201 is used to receive a first load from the terminal, which is encapsulated with a first TCP packet header; and send the first load to the access gateway, wherein the first load is encapsulated with a third GRE protocol packet header, and the third GRE protocol packet header is encapsulated with the third TCP packet header.

[0503] In a possible implementation, the third GRE protocol packet header includes a third GRE keyword, where the third GRE keyword is a keyword allocated by the access node to the terminal, and the third GRE keyword is used to determine identification information of the terminal.

[0504] In a possible implementation, the processing unit 1202 is configured to assign a third GRE keyword to the terminal; and the communication unit 1201 is configured to send a second message to the access gateway, where the second message includes a correspondence between the third GRE keyword and the identification information of the terminal.

[0505] In a possible implementation, 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.

[0506] In one possible implementation, 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 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 destination address in the first IP header is the IP address of the access gateway.

[0507] In another example, 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.

[0508] For example, the processing unit 1202 is configured to determine, based on at least one of the terminal type and the terminal service type, that an IPsec tunnel does not need to be established between the terminal and the access gateway. 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.

[0509] It should be understood that the division of units in the above device is merely a division of logical functions. In actual implementation, they can be fully or partially integrated into one physical entity, or they can be physically separated. Moreover, the units in the device can all be implemented in the form of software called through processing elements; or they can all be implemented in the form of hardware; or some units can be implemented in the form of software called through processing elements, and some units can be implemented in the form of hardware. For example, each unit can be a separately established processing element, or it can be integrated into a certain chip of the device. In addition, it can also be stored in the form of a program in a memory, called by a certain processing element of the device and perform the function of the unit. In addition, all or part of these units can be integrated together, or they can be implemented independently. The processing element described here can also be a processor, which can be an integrated circuit with signal processing capabilities. In the implementation process, each step of the above method or each unit above can be implemented by an integrated logic circuit of hardware in the processor element or by software called through a processing element.

[0510] In one example, the unit in any of the above devices may be one or more integrated circuits configured to implement the above method, such as one or more application specific integrated circuits (ASICs), or one or more digital singnal processors (DSPs), or one or more field programmable gate arrays (FPGAs), or a combination of at least two of these integrated circuit forms. For another example, when the unit 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 (CPU) or other processor that can call a program. For another example, these units can be integrated together and implemented in the form of a system-on-a-chip (SOC).

[0511] The communication unit 1201 is an interface circuit of the device, used to receive signals from or send signals to other devices. For example, when the device is implemented as a chip, the communication unit 1201 is the interface circuit of the chip used to receive signals from or send signals to other chips or devices.

[0512] refer to Figure 13, is a schematic diagram of a communication device 1300 provided in an embodiment of the present application. The communication device 1300 includes a processor 1310 and an interface 1330. Optionally, the communication device 1300 may also include a memory 1320. The interface 1330 is used to implement communication with other devices. The interface 1330 may also be a communication module, a transceiver unit, a transceiver, a transceiver module, or a communication circuit.

[0513] The methods performed by the terminal, access gateway, or access node in the above embodiments can be implemented by the processor 1310 calling a program stored in a memory. That is, the terminal, access gateway, or access node may include a processor 1310, which executes the methods performed by the terminal, access gateway, or access node in the above method embodiments by calling a program in a memory. The processor 1310 here can be an integrated circuit with signal processing capabilities, such as a CPU. The terminal, access gateway, or access node can be implemented by one or more integrated circuits configured to implement the above methods. For example, one or more ASICs, one or more microprocessors (DSPs), one or more FPGAs, etc., or a combination of at least two of these integrated circuit forms.

[0514] Specifically, Figure 12 The functions / implementation processes of the communication unit 1201 and the processing unit 1202 can be realized by Figure 13 The processor 1310 in the communication device 1300 shown calls the computer executable instructions stored in the memory 1320 to implement. Or, Figure 12 The function / implementation process of the processing unit 1202 can be achieved by Figure 13 The processor 1310 in the communication device 1300 shown calls the computer execution instructions stored in the memory 1320 to implement, Figure 12 The function / implementation process of the communication unit 1201 can be achieved by Figure 13 The interface 1330 in the communication device 1300 shown in FIG. 1 is implemented.

[0515] It should be understood that in the various embodiments of the present application, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present invention.

[0516] The present application also provides a computer-readable storage medium on which a computer program is stored. When the computer program is executed by a computer, it can implement the functions implemented by the UE, TNGF, access node, or AMF in the above embodiments.

[0517] The present application also provides a computer program product, which, when executed by a computer, can implement the functions implemented by the UE, TNGF, access node, or AMF in the above embodiments.

[0518] The present application also provides a chip system, which includes at least one processor and an interface circuit. The processor is configured to execute instructions and / or data exchanges through the interface circuit, so that the device in which the chip system resides implements the functions implemented by the UE, TNGF, access node, or AMF in the above-mentioned embodiments. The chip system can be composed of a chip or can include a chip and other discrete components.

[0519] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0520] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When software is used for implementation, it can 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 a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from a website, computer, server or data center to another website, computer, server or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrations. The available medium can be a magnetic medium (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid-state drive (SSD)).

[0521] The various illustrative logic units and circuits described in the embodiments of the present application can be implemented or operated 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 device, a discrete gate or transistor logic, a discrete hardware component, or the design of any combination thereof. The general-purpose processor can be a microprocessor, alternatively, the general-purpose processor can also be any traditional processor, controller, microcontroller or state machine. The processor can also be implemented by a combination of computing devices, such as a digital signal processor and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a digital signal processor core, or any other similar configuration to implement.

[0522] The steps of the methods or algorithms described in the embodiments of the present application can be directly embedded in hardware, software units executed by a processor, or a combination of the two. The software unit can be stored in a random access memory (RAM), flash memory, read-only memory (ROM), EPROM memory, EEPROM memory, register, hard disk, removable disk, CD-ROM or other storage medium in any form in the art. Exemplarily, 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. Alternatively, the storage medium can also be integrated into the processor. The processor and storage medium can be arranged in an ASIC.

[0523] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, so that the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.

[0524] In one or more exemplary designs, the above-described functions described herein may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, these functions may be stored on a computer-readable medium or transmitted in the form of one or more instructions or codes on a computer-readable medium. Computer-readable media include computer storage media and communication media that facilitate the transfer of computer programs from one location to another. Storage media can be any available medium that can be accessed by a general-purpose or specialized computer. For example, such computer-readable media may include, but is not limited to, RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to carry or store program code in the form of instructions or data structures and other forms that can be read by a general-purpose or specialized computer, or a general-purpose or specialized processor. In addition, any connection can be appropriately defined as a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote resource via a coaxial cable, fiber optic cable, twisted pair cable, digital subscriber line (DSL), or wirelessly, such as infrared, wireless, and microwave, it is also included in the definition of computer-readable media. Disks and discs include compact disks, laser discs, optical discs, digital versatile discs (DVDs), floppy disks, and Blu-ray discs. Disks typically reproduce data magnetically, while discs typically reproduce data optically using lasers. Combinations of the above may also be included in computer-readable media.

[0525] Those skilled in the art will appreciate that, in one or more of the examples above, the functions described herein may be implemented using hardware, software, firmware, or any combination thereof. When implemented using software, these functions may be stored in a computer-readable medium or transmitted as one or more instructions or codes on a computer-readable medium. Computer-readable media include computer storage media and communication media, wherein communication media include any medium that facilitates the transmission of a computer program from one place to another. The storage medium may be any available medium that can be accessed by a general-purpose or special-purpose computer.

[0526] The specific implementation methods described above further explain the purpose, technical solutions and beneficial effects of the present application in detail. It should be understood that the above description is only the specific implementation method of the present application and is not intended to limit the scope of protection of the present application. Any modifications, equivalent replacements, improvements, etc. made on the basis of the technical solutions of the present application should be included in the scope of protection of the present application. The above description of the specification of this application can enable any technical personnel in the field to utilize or implement the contents of this application. Any modification based on the disclosed contents should be considered obvious in the field. The basic principles described in this application can be applied to other variations without departing from the inventive essence and scope of the present application. Therefore, the contents disclosed in this application are not limited to the described embodiments and designs, but can also be extended to the maximum scope consistent with the principles of this application and the disclosed new features.

[0527] Although the present application has been described with reference to specific features and embodiments thereof, it is apparent that various modifications and combinations may be made thereto without departing from the spirit and scope of the present application. Accordingly, this specification and the drawings are merely illustrative of the present application as defined by the appended claims and are deemed to cover any and all modifications, variations, combinations or equivalents within the scope of the present application. Obviously, those skilled in the art may make various modifications and variations to the present application without departing from the scope of the present application. Thus, the present application is intended to include such modifications and variations if they fall within the scope of the claims of the present application and their equivalents.

Claims

1. A communication method, characterized in that: include: The access gateway receives a first data packet from the terminal, the first data packet including a first Internet Protocol (IP) header, a first General Packet Radio Service Tunneling Protocol-User Plane (GTP-U) header, and a first payload, the first IP header including the IP address of the access gateway, and the first GTP-U header including a tunnel endpoint identifier (TEID) of the access gateway; The access gateway determines whether the first 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 access gateway.

2. The method according to claim 1, characterized in that The access gateway determines, according to at least one of an IP address of the access gateway and a TEID of the access gateway, that the first load is control plane data or user plane data, including: When the TEID of the access gateway is a TEID allocated by the access gateway for transmitting the control plane data, the access gateway determines that the first payload is the control plane data; or, When the TEID of the access gateway is a TEID allocated by the access gateway for transmitting the user plane data, the access gateway determines that the first load is the user plane data; or, When the IP address of the access gateway is an IP address allocated by the access gateway for transmitting the control plane data, the access gateway determines that the first load is the control plane data; or, When the IP address of the access gateway is an IP address allocated by the access gateway for transmitting the user plane data, the access gateway determines that the first load is the user plane data; or, When the TEID of the access gateway is a TEID allocated by the access gateway for transmitting the control plane data, and the IP address of the access network is an IP address allocated by the access gateway for transmitting the control plane data, the access gateway determines that the first load is the control plane data; or, When the TEID of the access gateway is the TEID allocated by the access gateway for transmitting the user plane data, and the IP address of the access network is the IP address allocated by the access gateway for transmitting the user plane data, the access gateway determines that the first load is the user plane data.

3. The method according to claim 1 or 2, characterized in that The first GTP-U packet header further includes a message type field, the first data packet further includes a first message, and the first message includes the first payload; When the first payload is the control plane data, the message type field is used to indicate the message type of the first message.

4. The method according to claim 1 or 2, characterized in that 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, 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 a TEID allocated by the access gateway for transmitting the control plane data; The access gateway receives 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 a TEID allocated by the terminal for transmitting the control plane data.

5. The method according to claim 1 or 2, characterized in that The method further comprises: The access gateway sends a second request message to the terminal, where the second request message includes a protocol data unit (PDU) session identifier and a TEID of the access gateway, wherein the TEID of the access gateway is a TEID allocated by the access gateway for user plane data of the PDU session; The access gateway receives a second response message from the terminal, where the second response message includes the TEID of the terminal, where the TEID of the terminal is a TEID allocated by the terminal for user plane data of the PDU session.

6. The method according to claim 5, characterized in that The second request message also includes the IP address of the access gateway, where the IP address of the access gateway is an IP address allocated by the access gateway for user plane data of the PDU session.

7. The method according to claim 1 or 2, characterized in that Before the access gateway receives the first data packet from the terminal, the method further includes: The access gateway receives indication information from an access and mobility management function (AMF) network element, where the indication information is used to indicate that an Internetwork Security Protocol (IPsec) tunnel does not need to be established between the access gateway and the terminal.

8. The method according to claim 1 or 2, characterized in that The first IP packet header further includes the IP address of the terminal, and the method further includes: The access gateway determines 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; The access gateway determines the context information of the terminal according to the identification information of the terminal.

9. The method according to claim 8, characterized in that The method further comprises: The access gateway receives 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.

10. The method according to claim 1 or 2, characterized in that The method further comprises: The access gateway sends 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, the second IP header includes the IP address of the access gateway, and the second GTP-U header includes the TEID of the terminal; In which, 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 access gateway for transmitting the user plane data.

11. The method according to claim 1, wherein The method further comprises: The access gateway sends a second data packet to the terminal, the second data packet includes a second IP header, a second GTP-U header and a 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; wherein, the second payload 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, and the TEID of the access gateway is the TEID allocated by the access gateway for transmitting the control plane data.

12. A communication method, characterized in that: The method comprises: The terminal receives a second data packet from the access gateway, the second data packet including a second Internet Protocol (IP) header, a second General Packet Radio Service Tunneling Protocol-User Plane (GTP-U) header, and a second payload, the second IP header including the IP address of the access gateway, and the second GTP-U header including a tunnel endpoint identifier (TEID) of the terminal; The terminal determines, based on at least one of the IP address of the access gateway and the TEID of the terminal, whether the second load is control plane data or user plane data.

13. The method according to claim 12, characterized in that The terminal determines, based on at least one of the IP address of the access gateway and the TEID of the terminal, that the second load is control plane data or user plane data, including: When the TEID of the terminal is a TEID allocated by the terminal for transmitting the control plane data, the terminal determines that the second payload is the control plane data; or, When the TEID of the terminal is a TEID allocated by the terminal for transmitting the user plane data, the terminal determines that the second payload is the user plane data; or, When the IP address of the access gateway is an IP address allocated by the access gateway for transmitting the control plane data, the terminal determines that the second load is the control plane data; or, When the IP address of the access gateway is an IP address allocated by the access gateway for transmitting the user plane data, the terminal determines that the second load is the user plane data; or, When the TEID of the terminal is a TEID allocated by the terminal for transmitting the control plane data, and the IP address of the access network is an IP address allocated by the access gateway for transmitting the control plane data, the terminal determines that the second load is the control plane data; or, When the TEID of the terminal is the TEID allocated by the terminal for transmitting the user plane data, and the IP address of the access network is the IP address allocated by the access gateway for transmitting the user plane data, the terminal determines that the second load is the user plane data.

14. The method according to claim 12 or 13, characterized in that The second GTP-U packet header further includes a message type field, the second data packet further includes a third message, and the third message includes the second payload; When the second payload is the control plane data, the message type field is used to indicate the message type of the third message.

15. The method according to claim 12 or 13, characterized in that 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, where the first request message includes a TEID of the access gateway and an IP address of the access gateway, wherein the TEID of the access gateway is a TEID allocated by the access gateway for transmitting the control plane data; The terminal sends a first response message to the access gateway, where the first response message includes the TEID of the terminal, where the TEID of the terminal is a TEID allocated by the terminal for transmitting the control plane data.

16. The method according to claim 12 or 13, characterized in that The method further comprises: The terminal receives a second request message from the access gateway, where the second request message includes a protocol data unit (PDU) session identifier and a TEID of the access gateway, wherein the TEID of the access gateway is a TEID allocated by the access gateway for user plane data of the PDU session; The terminal sends a second response message to the access gateway, where the second response message includes the TEID of the terminal, where the TEID of the terminal is a TEID allocated by the terminal for user plane data of the PDU session.

17. The method according to claim 16, characterized in that The second request message also includes the IP address of the access gateway, where the IP address of the access gateway is an IP address allocated by the access gateway for user plane data of the PDU session.

18. The method according to claim 12 or 13, characterized in that The method further comprises: The terminal sends 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, where 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; In which, when the first 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, 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 TEID of the access gateway is the TEID allocated by the access gateway for transmitting the user plane data.

19. A communication method, characterized in that: include: The terminal generates a first data packet, the first data packet including a first Internet Protocol (IP) header, a first General Packet Radio Service Tunneling Protocol-User Plane (GTP-U), and a first payload, the first IP header including an IP address of an access gateway, and the first GTP-U header including a tunnel endpoint identifier (TEID) of the access gateway; wherein the first payload is 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, and the TEID of the access gateway is a TEID allocated by the access gateway for transmitting the control plane data; or, the first payload is user plane data, the IP address of the access gateway is an IP address allocated by the access gateway for transmitting the user plane data, and the TEID of the access gateway is a TEID allocated by the access gateway for transmitting the user plane data; The terminal sends a first data packet to the access gateway.

20. The method according to claim 19, characterized in that The method further comprises: The terminal receives a second data packet from the access gateway, the second data packet includes a second IP header, a second GTP-U header and a 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.

21. The method according to claim 20, characterized in that The method further comprises: The terminal determines, based on 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; or The terminal determines whether the second payload is control plane data or user plane data by parsing the second payload.

22. The method according to claim 21, characterized in that The terminal determines, based on 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, including: When the TEID of the access gateway is a TEID allocated by the access gateway for transmitting the control plane data, the terminal determines that the second payload is the control plane data; or, When the IP address of the access gateway is an IP address allocated by the access gateway for transmitting the control plane data, the terminal determines that the second load is the control plane data; or, When the TEID of the access gateway is the TEID allocated by the access gateway for transmitting the control plane data, and the IP address of the access gateway is the IP address allocated by the access gateway for transmitting the control plane data, the terminal determines that the second load is the control plane data.

23. The method according to any one of claims 19 to 22, characterized in that 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.

24. A communication device, characterized in that: comprising a memory, and one or more processors, the memory being coupled to the one or more processors; The memory is configured to store a computer program or instruction, which, when executed by the one or more processors, causes the communication device to perform the method according to any one of claims 1 to 11.

25. A communication device, characterized in that: comprising a memory, and one or more processors, the memory being coupled to the one or more processors; The memory is used to store a computer program or instruction, which, when executed by the one or more processors, causes the communication device to perform the method according to any one of claims 12 to 18, or causes the communication device to perform the method according to any one of claims 19 to 23.

26. A computer-readable storage medium, characterized in that The computer-readable storage medium stores instructions, which, when executed on a computer, enable the computer to perform the method according to any one of claims 1 to 11.

27. A computer-readable storage medium, characterized in that The computer-readable storage medium stores instructions, which, when executed on a computer, enable the computer to execute the method according to any one of claims 12 to 18, or enable the computer to execute the method according to any one of claims 19 to 23.

Images