Communication method, apparatus and system

Abstract

The present application provides a communication method, apparatus and system, which are applied to the technical field of communications. The communication method provided in the present application comprises: a third communication device receives first information from a first communication device via a first protocol; and the third communication device transmits the first information to a second communication device via a second protocol, wherein at least one of the first protocol and the second protocol is a QUIC protocol. The method can transmit information via a QUIC protocol. Owing to the adaptability of the QUIC protocol to path changes and path switching, service interruption, latency, additional signaling overhead, etc. can be reduced during path switching, thereby improving service transmission performance.

Description

Communication methods, devices and systems

[0001] This application claims priority to Chinese Patent Application No. 202510189712.0, filed on February 19, 2025, entitled "Communication Method, Apparatus and System", the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of communication technology, and in particular to communication methods, apparatus and systems. Background Technology

[0003] Currently, the core network (CN) is logically divided into the user plane and the control plane. The interface between the control plane core network and the radio access network is based on the stream control transmission protocol (SCTP), while the interface between the user plane core network and the radio access network (RAN) is based on the GPRS tunneling protocol user plane (GTP-U) used for user plane data transmission in the general packet radio service (GPRS) network.

[0004] However, the above technical solutions suffer from poor service transmission performance. For example, when switching between different service paths, control plane connection interruptions or re-establishment issues may occur, leading to additional signaling overhead and latency, and even service interruption. Summary of the Invention

[0005] This application provides communication methods, apparatus, and systems that can improve service transmission performance.

[0006] The embodiments of this application adopt the following technical solutions:

[0007] Firstly, a communication method is provided, which can be executed by a third communication device or by a module (e.g., a processor, chip, or chip system) applied to the third communication device. Taking the execution of the method by a third communication device as an example, the method includes: the third communication device receiving first information from a first communication device via a first protocol; and the third communication device sending the first information to a second communication device via a second protocol, wherein at least one of the first and second protocols is a Fast User Datagram Protocol (UDP) or a Quick User Datagram Protocol (QUIC).

[0008] Based on the communication method provided in this application, communication devices can transmit information via the QUIC protocol, offering flexibility in response to path changes and switching. During control plane connection / user plane session establishment, a QUIC connection only needs to be established once on a specific path. When a path switch is required, thanks to the characteristics of QUIC, a direct switch to another path is possible without re-establishing the link. This reduces service interruptions, latency, and additional signaling overhead, thereby improving service transmission performance. Furthermore, compared to existing user plane protocols, the QUIC protocol offers better topology scalability, extensibility, and flexibility, supporting superior flow control, congestion control, and security mechanisms, enabling it to better support new services in future networks.

[0009] In one possible design, the first protocol is the GTP-U protocol, a tunneling protocol used for user plane data transmission in a General Packet Radio Service (GPRS) network, and the second protocol is the QUIC protocol. First information from the first communication device is carried in a first message, which includes first identification information used to identify the GTP-U tunnel. First information sent to the second communication device is carried in a second message, which includes second identification information used to identify the QUIC connection. A mapping relationship exists between the second and first identification information.

[0010] In one possible design, the method further includes: a third communication device acquiring first configuration information, the first configuration information being used to configure a mapping relationship, the first configuration information including first identification information and second identification information.

[0011] In one possible design, the first configuration information may also include at least one of the following: identification information of the QUIC flow included in the QUIC connection, identification information of the path corresponding to the QUIC connection, identification information of the session, or identification information of the quality of service flow included in the session.

[0012] In one possible design, the first information includes at least one of the following: session identification information, QoS flow identification information, first identification information, priority information, or identification information of the path corresponding to the GTP-U tunnel.

[0013] In one possible design, the first protocol is the Stream Control Transfer Protocol (SCTP), and the second protocol is the QUIC protocol. First information from the first communication device is carried in a first message, which includes first identification information and / or third identification information. The first identification information identifies the SCTP connection, and the third identification information identifies the SCTP flow belonging to that connection. First information sent to the second communication device is carried in a second message, which includes second identification information. The second identification information identifies the QUIC connection, and a mapping relationship exists between the second identification information and either the first or third identification information.

[0014] In one possible design, the method further includes: a third communication device acquiring second configuration information, the second configuration information being used to configure a mapping relationship, the second configuration information including second identification information and at least one of the following: first identification information or third identification information.

[0015] In one possible design, the second configuration information further includes at least one of the following: identification information of the QUIC stream included in the QUIC connection, identification information of the path corresponding to the QUIC connection, fourth identification information, or fifth identification information, wherein the fourth identification information is used to identify the type of message transmitted through the SCTP connection, SCTP stream, QUIC connection, or QUIC stream, and the fifth identification information is used to identify at least one message belonging to the same process transmitted through the SCTP connection, SCTP stream, QUIC connection, or QUIC stream.

[0016] In one possible design, the first information includes at least one of the following: sixth identification information, seventh identification information, terminal identification information, first identification information, third identification information, priority information, or identification information of the path corresponding to the SCTP connection, wherein the sixth identification information is used to identify the type of message transmitted through the SCTP connection or SCTP stream, and the seventh identification information is used to identify at least one message belonging to the same process transmitted through the SCTP connection or SCTP stream.

[0017] In one possible design, the first protocol is the Transmission Control Protocol (TCP), and the second protocol is the QUIC protocol. First information from the first communication device is carried in a first message, which includes an eighth identification information used to identify the TCP connection. First information sent to the second communication device is carried in a second message, which includes first identification information used to identify the QUIC connection. A mapping relationship exists between the first identification information and the eighth identification information.

[0018] In one possible design, the method further includes: a third communication device acquiring third configuration information, the third configuration information being used to configure the mapping relationship, the third configuration information including first identification information and eighth identification information.

[0019] In one possible design, the third configuration information also includes at least one of the following: identification information of the QUIC stream included in the QUIC connection, identification information of the path corresponding to the QUIC connection, ninth identification information, or tenth identification information, wherein the ninth identification information is used to identify the type of message transmitted through the TCP connection, QUIC connection, or QUIC stream, and the tenth identification information is used to identify at least one message belonging to the same process transmitted through the TCP connection, QUIC connection, or QUIC stream.

[0020] In one possible design, the first information includes at least one of the following: eleventh identification information, twelfth identification information, terminal identification information, first identification information, eighth identification information, priority information, or identification information of the path corresponding to the TCP connection, wherein the eleventh identification information is used to identify the type of message transmitted through the TCP connection, and the twelfth identification information is used to identify at least one message belonging to the same process transmitted through the TCP connection.

[0021] In one possible design, the thirteenth identification information in the header of the second message includes the first information, and the thirteenth identification information is either the source QUIC connection identifier or the destination QUIC connection identifier; or, the identification information of the QUIC flow in the payload of the second message includes the first information; or, the thirteenth identification information in the header of the second message includes part of the first information, and the identification information of the QUIC flow in the payload of the second message includes another part of the first information, and the thirteenth identification information is either the source QUIC connection identifier or the destination QUIC connection identifier.

[0022] In one possible design, the first protocol is the Radio Resource Control (RRC) layer protocol, the Service Data Adaptation (SDAP) layer protocol, the Packet Data Convergence (PDCP) layer protocol, the Radio Link Control (RLC) layer protocol, the Media Access Control (MAC) layer protocol, the Physical (PHY) layer protocol, or the Non-Access NAS (NAS) layer protocol, and the second protocol is the QUIC protocol.

[0023] In one possible design, the method further includes: a third communication device acquiring fourth configuration information, the fourth configuration information being used to configure the mapping relationship between the radio bearer and the QUIC connection, the fourth configuration information including the identification information of the radio bearer and the identification information of the QUIC connection.

[0024] In one possible design, the method further includes: a third communication device acquiring fifth configuration information, which includes identification information of the QUIC connection and identification information of the path supporting the QUIC connection.

[0025] In one possible design, the fifth configuration information may also include at least one of the following: priority information of the path that supports QUIC connection and identification information of the default path that supports QUIC connection.

[0026] In one possible design, the first communication device is a radio access network (RAN) node, terminal, core network element, or bearer network node; the second communication device is a radio access network (RAN) node, terminal, core network element, or bearer network node.

[0027] In one possible design, the message carrying the first information is transmitted via any of the following paths: a path connected via a non-terrestrial communication network, a path connected via a terrestrial communication network, a path connected via a sub-network, a path connected via microwave, a path connected via a first network, or a path connected via a second network, wherein the first network and the second network are different.

[0028] In one possible design, the first protocol is the QUIC protocol, the second communication device does not support the QUIC protocol, and the first communication device is used to perform tasks related to at least one of the following services: artificial intelligence (AI) service, data service, or communication sensing integrated (ISAC) service. Alternatively, the first communication device is used to manage a fourth communication device, which is used to perform tasks related to at least one of the following services: artificial intelligence (AI) service, data service, or communication sensing integrated (ISAC) service.

[0029] In one possible design, the second protocol is the QUIC protocol, the first communication device does not support the QUIC protocol, and the second communication device is used to perform tasks related to at least one of the following services: artificial intelligence (AI) services, data services, or communication sensing integrated (ISAC) services. Alternatively, the second communication device is used to manage a fourth communication device, which is used to perform tasks related to at least one of the following services: artificial intelligence (AI) services, data services, or communication sensing integrated (ISAC) services.

[0030] In one possible design, the third communication device is a RAN node, a terminal, a core network element, or a bearer network node.

[0031] Secondly, a communication device is provided for implementing the method in the first aspect described above.

[0032] The communication device includes modules, units, or means that implement the above methods. These modules, units, or means can be implemented in hardware, software, or by hardware executing corresponding software. The hardware or software includes one or more modules or units corresponding to the above functions.

[0033] The communication device can be a third communication device (or a component, such as a chip, in any possible design of the first aspect) as described above.

[0034] In one possible design, the communication device includes a transceiver module and a processing module: the transceiver module is used to receive first information from a first communication device via a first protocol. The processing module is used to determine whether to send the first information to a second communication device. The transceiver module is also used to send the first information to the second communication device via a second protocol, wherein at least one of the first and second protocols is the QUIC protocol.

[0035] In one possible design, the first protocol is the GTP-U protocol, a tunneling protocol used for user plane data transmission in a General Packet Radio Service (GPRS) network, and the second protocol is the QUIC protocol. First information from the first communication device is carried in a first message, which includes first identification information used to identify the GTP-U tunnel. First information sent to the second communication device is carried in a second message, which includes second identification information used to identify the QUIC connection. A mapping relationship exists between the second and first identification information.

[0036] In one possible design, the processing module is also used to obtain first configuration information, which is used to configure the mapping relationship. The first configuration information includes first identification information and second identification information.

[0037] In one possible design, the first configuration information may also include at least one of the following: identification information of the QUIC flow included in the QUIC connection, identification information of the path corresponding to the QUIC connection, identification information of the session, or identification information of the quality of service flow included in the session.

[0038] In one possible design, the first information includes at least one of the following: session identification information, QoS flow identification information, first identification information, priority information, or identification information of the path corresponding to the GTP-U tunnel.

[0039] In one possible design, the first protocol is the Stream Control Transfer Protocol (SCTP), and the second protocol is the QUIC protocol. First information from the first communication device is carried in a first message, which includes first identification information and / or third identification information. The first identification information identifies the SCTP connection, and the third identification information identifies the SCTP flow belonging to that connection. First information sent to the second communication device is carried in a second message, which includes second identification information. The second identification information identifies the QUIC connection, and a mapping relationship exists between the second identification information and either the first or third identification information.

[0040] In one possible design, the processing module is further configured to obtain second configuration information, which is used to configure the mapping relationship. The second configuration information includes second identification information and at least one of the following: first identification information or third identification information.

[0041] In one possible design, the second configuration information further includes at least one of the following: identification information of the QUIC stream included in the QUIC connection, identification information of the path corresponding to the QUIC connection, fourth identification information, or fifth identification information, wherein the fourth identification information is used to identify the type of message transmitted through the SCTP connection, SCTP stream, QUIC connection, or QUIC stream, and the fifth identification information is used to identify at least one message belonging to the same process transmitted through the SCTP connection, SCTP stream, QUIC connection, or QUIC stream.

[0042] In one possible design, the first information includes at least one of the following: sixth identification information, seventh identification information, terminal identification information, first identification information, third identification information, priority information, or identification information of the path corresponding to the SCTP connection, wherein the sixth identification information is used to identify the type of message transmitted through the SCTP connection or SCTP stream, and the seventh identification information is used to identify at least one message belonging to the same process transmitted through the SCTP connection or SCTP stream.

[0043] In one possible design, the first protocol is the Transmission Control Protocol (TCP), and the second protocol is the QUIC protocol. First information from the first communication device is carried in a first message, which includes an eighth identification information used to identify the TCP connection. First information sent to the second communication device is carried in a second message, which includes first identification information used to identify the QUIC connection. A mapping relationship exists between the first identification information and the eighth identification information.

[0044] In one possible design, the processing module is also used to obtain third configuration information, which is used to configure the mapping relationship. The third configuration information includes first identification information and eighth identification information.

[0045] In one possible design, the third configuration information also includes at least one of the following: identification information of the QUIC stream included in the QUIC connection, identification information of the path corresponding to the QUIC connection, ninth identification information, or tenth identification information, wherein the ninth identification information is used to identify the type of message transmitted through the TCP connection, QUIC connection, or QUIC stream, and the tenth identification information is used to identify at least one message belonging to the same process transmitted through the TCP connection, QUIC connection, or QUIC stream.

[0046] In one possible design, the first information includes at least one of the following: eleventh identification information, twelfth identification information, terminal identification information, first identification information, eighth identification information, priority information, or identification information of the path corresponding to the TCP connection, wherein the eleventh identification information is used to identify the type of message transmitted through the TCP connection, and the twelfth identification information is used to identify at least one message belonging to the same process transmitted through the TCP connection.

[0047] In one possible design, the thirteenth identification information in the header of the second message includes the first information, and the thirteenth identification information is either the source QUIC connection identifier or the destination QUIC connection identifier; or, the identification information of the QUIC flow in the payload of the second message includes the first information; or, the thirteenth identification information in the header of the second message includes part of the first information, and the identification information of the QUIC flow in the payload of the second message includes another part of the first information, and the thirteenth identification information is either the source QUIC connection identifier or the destination QUIC connection identifier.

[0048] In one possible design, the first protocol is the Radio Resource Control (RRC) layer protocol, the Service Data Adaptation (SDAP) layer protocol, the Packet Data Convergence (PDCP) layer protocol, the Radio Link Control (RLC) layer protocol, the Media Access Control (MAC) layer protocol, the Physical (PHY) layer protocol, or the Non-Access NAS (NAS) layer protocol, and the second protocol is the QUIC protocol.

[0049] In one possible design, the processing module is also used to obtain fourth configuration information, which is used to configure the mapping relationship between the radio bearer and the QUIC connection. The fourth configuration information includes the identification information of the radio bearer and the identification information of the QUIC connection.

[0050] In one possible design, the processing module is also used to obtain fifth configuration information, which includes identification information of the QUIC connection and identification information of the path that supports the QUIC connection.

[0051] In one possible design, the fifth configuration information may also include at least one of the following: priority information of the path that supports QUIC connection and identification information of the default path that supports QUIC connection.

[0052] In one possible design, the first communication device is a radio access network (RAN) node, terminal, core network element, or bearer network node; the second communication device is a radio access network (RAN) node, terminal, core network element, or bearer network node.

[0053] In one possible design, the message carrying the first information is transmitted via any of the following paths: a path connected via a non-terrestrial communication network, a path connected via a terrestrial communication network, a path connected via a sub-network, a path connected via a 5th generation (5G) mobile communication network, a path connected via a future mobile communication network, or a path connected via microwave.

[0054] In one possible design, the first protocol is the QUIC protocol, the second communication device does not support the QUIC protocol, and the first communication device is used to perform tasks related to at least one of the following services: artificial intelligence (AI) service, data service, or communication sensing integrated (ISAC) service. Alternatively, the first communication device is used to manage a fourth communication device, which is used to perform tasks related to at least one of the following services: artificial intelligence (AI) service, data service, or communication sensing integrated (ISAC) service.

[0055] In one possible design, the second protocol is the QUIC protocol, the first communication device does not support the QUIC protocol, and the second communication device is used to perform tasks related to at least one of the following services: artificial intelligence (AI) services, data services, or communication sensing integrated (ISAC) services. Alternatively, the second communication device is used to manage a fourth communication device, which is used to perform tasks related to at least one of the following services: artificial intelligence (AI) services, data services, or communication sensing integrated (ISAC) services.

[0056] In one possible design, the communication device is a RAN node, a terminal, a core network element, or a bearer network node.

[0057] Thirdly, a communication device is provided, comprising: a processor configured to execute instructions stored in a memory, wherein when the processor executes the instructions, the communication device performs the method described in any of the preceding aspects. The communication device may be a first communication device, a second communication device, or a third communication device as described in the first aspect or any possible design of the first aspect.

[0058] In one possible design, the communication device also includes a memory for storing computer instructions. Optionally, the processor and memory are integrated together, or they are separate.

[0059] In one possible design, the memory is coupled to the processor and is located outside the communication device.

[0060] Fourthly, a communication device is provided, comprising: a processor and an interface circuit for communicating with a module outside the communication device; the processor for executing the method described in any of the preceding aspects via logic circuitry or by running a computer program or instructions. The communication device may be a first communication device (or a component in a first communication device, such as a chip), a second communication device (or a component in a second communication device, such as a chip), or a third communication device (or a component in a third communication device, such as a chip) in any possible design of the first aspect.

[0061] Alternatively, the interface circuit can be a code / data read / write interface circuit, which receives computer execution instructions (which are stored in memory and may be read directly from memory or may be transmitted through other devices) and transmits them to the processor so that the processor runs the computer execution instructions to perform the methods described in any of the above aspects.

[0062] In one possible design, the communication device also includes a memory for storing computer programs or instructions. Optionally, the processor and memory are integrated together, or the processor and memory are separate.

[0063] In one possible design, the memory is coupled to the processor and is located outside the communication device.

[0064] In some possible designs, the communication device can be a chip or a chip system.

[0065] Fifthly, this application provides a computer-readable storage medium storing instructions that, when executed on a computer, enable the computer to perform the methods described in the first aspect above, or any possible design of the first aspect.

[0066] In a sixth aspect, this application provides a computer program product containing instructions that, when executed on a computer, enable the computer to perform the methods described in the first aspect above, or any possible design of the first aspect.

[0067] In a seventh aspect, a communication device (e.g., a chip or a chip system) is provided, comprising a processor for implementing the functions described in the first aspect or any possible design of the first aspect. In one possible design, the communication device further comprises a memory for storing necessary program instructions and data. When the communication device is a chip system, it may be composed of chips or may include chips and other discrete devices.

[0068] Eighthly, a communication system is provided, comprising a first communication device, a second communication device, and a third communication device. The third communication device is used to implement the methods described in the first aspect, or any possible design of the first aspect.

[0069] The technical effects of any of the design methods in aspects two through eight can be found in the technical effects of the different design methods in aspect one above, and will not be repeated here.

[0070] It should be noted that any of the possible implementations of any of the above aspects can be combined, provided that the solutions do not contradict each other. Attached Figure Description

[0071] Figure 1 is a schematic diagram of multiple paths between a RAN node and the core network;

[0072] Figure 2 is a schematic diagram of the control plane protocol stack of the N2 interface;

[0073] Figure 3 is a schematic diagram of the user plane protocol stack of the N3 interface;

[0074] Figure 4 is a schematic diagram of the structure of a communication system provided in an embodiment of this application;

[0075] Figure 5 is an interactive schematic diagram of a communication method provided in an embodiment of this application;

[0076] Figure 6 is a schematic diagram of a protocol stack provided in an embodiment of this application;

[0077] Figure 7 is a schematic diagram of a protocol stack provided in an embodiment of this application;

[0078] Figure 8 is a schematic diagram of a protocol stack provided in an embodiment of this application;

[0079] Figure 9 is a schematic diagram of a protocol stack provided in an embodiment of this application;

[0080] Figure 10 is a schematic diagram of a protocol stack provided in an embodiment of this application;

[0081] Figure 11 is a schematic diagram of a protocol stack provided in an embodiment of this application;

[0082] Figure 12 is a schematic diagram of a protocol stack provided in an embodiment of this application;

[0083] Figure 13 is a schematic diagram of the structure of a QUIC message provided in an embodiment of this application;

[0084] Figure 14 is a schematic diagram of a scenario provided by an embodiment of this application;

[0085] Figure 15 is a schematic diagram of another scenario provided by an embodiment of this application;

[0086] Figure 16 is a flowchart illustrating a method for configuring configuration information according to an embodiment of this application;

[0087] Figure 17 is a schematic diagram of the structure of a communication device provided in an embodiment of this application;

[0088] Figure 18 is a schematic diagram of another communication device provided in an embodiment of this application. Detailed Implementation

[0089] To facilitate understanding of the technical solutions of the embodiments of this application, a brief introduction to the relevant technologies of this application is given below.

[0090] 1. Multi-path backhaul:

[0091] In communication systems, the connection between RAN nodes (e.g., base stations) and core network elements can be carried on different types of links, such as terrestrial links, microwave links, non-terrestrial network (NTN) links (or satellite links), distributed networking links, 5th generation (5G) mobile communication network links, and future mobile communication network links. Furthermore, for reasons such as link status, load balancing, traffic offloading, and disaster recovery, the connection between RAN nodes and core network elements can be flexibly switched between different links (or different paths). For example, as shown in Figure 1, the connection between User Equipment (UE) and RAN nodes, and the connection between RAN nodes and core network elements, are carried on terrestrial links and can switch between terrestrial links, microwave links, or satellite links. Core network elements can connect to the data network (DN).

[0092] 2. Quick UDP Internet Connection (QUIC) protocol:

[0093] QUIC is an Internet transport layer protocol that is connectionless, meaning a QUIC connection (a connection established based on the QUIC protocol) is not bound to an IP 5-tuple. A QUIC connection is identified by a QUIC connection identifier (CID) and features connection migration, intrinsic transport layer security (TLS), zero round-trip time (0-RTT), and flow control and congestion control mechanisms. Optionally, a QUIC connection can include one or more QUIC streams. For details on the QUIC protocol, refer to the Internet Engineering Task Force (IETF) Request for Comments (RFC) documents, such as RFCs 8999 and 9000.

[0094] 3. Interface protocols in 5G mobile communication networks:

[0095] RAN nodes are connected to core network elements via corresponding interfaces. For example, in a 5G network, RAN nodes are connected to core network control plane elements, such as access and mobility management functions (AMF), via the N2 interface, and RAN nodes are connected to core network user plane elements, such as user plane functions (UPF), via the N3 interface. In future networks, the interfaces connecting RAN nodes to core network elements (such as control plane elements, user plane elements, data plane elements, or other plane elements) may retain the interfaces used in the 5G network or may be replaced with new interfaces.

[0096] In current communication networks, the logical functional planes of the core network include the control plane and the user plane. In future networks, the logical functional planes may not be divided into control and user planes as described above; they may also include other logical functional planes, such as the data plane. For example, future networks might be divided into control and data planes. The data plane would be used to transmit traditional connection-oriented data (such as traditional user call data, user multimedia data, user application data, etc.) and new data oriented beyond connection (such as sensory service data, artificial intelligence (AI) service data, digital twin service data, etc.). Optionally, the data plane would also be used to process new data oriented beyond connection, such as AI training / inference, sensory data processing, digital twin data processing, data privacy protection, data collection, data distribution, and data analysis. Another example is that future networks might be divided into control, user, and data planes, adding a data plane to the existing control and user planes. The user plane is used to transmit data for traditional connection-oriented services (such as traditional user call data, user multimedia data, user application data, etc.), while the data plane is used to transmit and / or process new types of data for services beyond connectivity (such as sensor data, AI data, digital twin data, etc.). Similarly, new logical functional planes will be used for signaling transmission. For example, in future networks, new logical functional planes can be used to transmit signaling for traditional connection-oriented services (such as control signaling for establishing traditional user call data transmission resources, control signaling for establishing user multimedia data transmission resources, control signaling for establishing user application data transmission resources, etc.) and signaling for new types of services beyond connectivity (such as control signaling for establishing resources for the transmission and / or processing of sensor data, control signaling for establishing resources for the transmission and / or processing of AI data, control signaling for establishing resources for the transmission and / or processing of digital twin data, etc.). For example, future networks may include a control plane and a new logical functional plane. The control plane is used to transmit data for traditional connection-oriented services (such as traditional user call data, user multimedia data, user application data, etc.). The control plane can also be used to transmit signaling for traditional connection-oriented services (such as control signaling for establishing traditional user call data transmission resources, control signaling for establishing user multimedia data transmission resources, control signaling for establishing user application data transmission resources, etc.). The new logical functional plane is used to transmit new signaling for beyond-connectivity services (such as control signaling for establishing resources for the transmission and / or processing of sensor data, control signaling for establishing resources for the transmission and / or processing of AI data, control signaling for establishing resources for the transmission and / or processing of digital twin data, etc.). In this paper, for the sake of simplicity, the user plane may be replaced by other new logical functional planes in the network used for data transmission and / or processing, such as the data plane, which will not be elaborated further.For the sake of simplicity, the control plane in the following text can be replaced by new logical functional planes in other networks used for signaling transmission and / or processing, which will not be elaborated further.

[0097] In 5G networks, the N2 interface protocol stack between the RAN node and the core network control plane elements, as shown in Figure 2, is based on the SCTP protocol. Above the SCTP protocol layer is the Next Generation Application Protocol (NGAP) layer, and below it are the Internet Protocol (IP) layer, the Data Link Layer (DL), and the Physical Layer. The SCTP protocol is connection-oriented; an SCTP connection (a connection established based on the SCTP protocol) is bound to an IP 5-tuple.

[0098] In 5G networks, the N3 interface protocol stack between the RAN node and the core network user plane elements, as shown in Figure 3, is based on the GTP-U protocol. Above the GTP-U protocol layer are Protocol Data Unit (PDU) session user plane PDUs, Multimedia Broadcast Service (MBS) session user plane PDUs, etc. Below the GTP-U protocol layer are the User Datagram Protocol (UDP) layer, IP layer, Network Data Link Layer, and Physical Layer. For details on the SCTP and GTP-U protocols, please refer to existing protocols.

[0099] However, the existing interface protocol stack between RAN nodes and the core network suffers from poor service transmission performance. For example, with the existing N2 interface protocol stack, because SCTP connections are bound to IP 5-tuples, changes to the underlying IP 5-tuple will cause the corresponding SCTP connection to change or be interrupted. In flexible networking scenarios (such as NTN networks, distributed networks, etc.), the IP 5-tuples of RAN nodes may differ on different paths. For instance, RAN nodes may be assigned different IP addresses or use different port numbers depending on the link they are connected to. For example, when a RAN node is shared by an NTN network and a terrestrial network (TN), if the NTN and TN networks belong to different networks or are deployed by different operators, the RAN node will be assigned one IP address when connecting to an NTN network node and a different IP address when connecting to a TN network node. This means that when a RAN node switches between different paths, if the RAN node's IP 5-tuple changes, the control plane connection will be interrupted or re-established, resulting in additional signaling overhead and latency, and ultimately, service interruption.

[0100] For example, the existing N3 interface protocol stack suffers from poor topology scalability, extensibility, and flexibility of existing user plane protocols (such as GTP-U protocol). Its flow control and congestion control mechanisms and reliable transmission are not perfect or advanced enough, its service awareness is weak, and its security capabilities are low (GTP-U protocol layer itself does not support TLS). It needs to rely on transport layer security (TLS) protocol to ensure security, making it difficult to support new types of services in future networks, such as AI services, data services, XR services, and ISAC services.

[0101] Based on the problems existing in the interface protocol stack between the RAN node and the core network, this application provides a communication method, apparatus and system that can improve the service transmission performance between communication devices in the communication system.

[0102] The technical solutions of the embodiments of this application will be described below with reference to the accompanying drawings. In the description of this application, unless otherwise stated, " / " indicates that the objects before and after are in an "or" relationship. For example, A / B can represent A or B. "And / or" in this application is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, and B existing alone, where A and B can be singular or plural. Furthermore, in the description of this application, unless otherwise stated, "multiple" refers to two or more. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, and / or c can represent the following situations: a existing alone, b existing alone, c existing alone, a and b existing simultaneously, b and c existing simultaneously, a and c existing simultaneously, and a, b, and c existing simultaneously, where a, b, and c can be single or multiple. Furthermore, to facilitate a clear description of the technical solutions in the embodiments of this application, the terms "first" and "second" are used in the embodiments of this application to distinguish identical or similar items with substantially the same function and effect. Those skilled in the art will understand that the terms "first" and "second" do not limit the quantity or execution order, and that "first" and "second" are not necessarily different. Meanwhile, in the embodiments of this application, the terms "exemplary" or "for example" are used to indicate that something is being used as an example, illustration, or description. Any embodiment or design scheme described as "exemplary" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or design schemes. Specifically, the use of terms such as "exemplary" or "for example" is intended to present related concepts in a concrete manner for ease of understanding.

[0103] In the embodiments of this application, "instruction" can include direct and indirect instructions, as well as explicit and implicit instructions. The information indicated by a certain piece of information (such as the first information below) is called the information to be instructed. In the specific implementation process, there are many ways to instruct the information to be instructed, such as, but not limited to, directly instructing the information to be instructed, such as the information to be instructed itself or its index. It can also indirectly instruct the information to be instructed by instructing other information, where there is a correlation between the other information and the information to be instructed. It can also instruct only a part of the information to be instructed, while the other parts are known or pre-agreed upon. For example, the instruction of specific information can be achieved by using a pre-agreed (e.g., protocol-defined) arrangement order of various pieces of information, thereby reducing instruction overhead to some extent. At the same time, common parts of various pieces of information can be identified and uniformly indicated to reduce the instruction overhead caused by individually indicating the same information.

[0104] Furthermore, the specific indication method can also be any existing indication method, such as, but not limited to, the above-mentioned indication methods and their various combinations. Specific details of various indication methods can be found in existing technologies, and will not be repeated here. As described above, for example, when multiple pieces of information of the same type need to be indicated, the indication methods for different pieces of information may differ. In the specific implementation process, the required indication method can be selected according to specific needs. This application embodiment does not limit the selected indication method; therefore, the indication methods involved in this application embodiment should be understood to cover various methods that enable the party to be indicated to obtain the information to be indicated.

[0105] It should be understood that the information to be indicated can be sent as a whole or divided into multiple sub-information messages sent separately, and the sending period and / or timing of these sub-information messages can be the same or different. The specific sending method is not limited in this application embodiment. The sending period and / or timing of these sub-information messages can be predefined, for example, according to a protocol, or configured by the sending device by sending configuration information to the receiving device.

[0106] In this application embodiment, "predefined," "pre-configured," or "pre-configured" can be implemented by pre-saving corresponding codes, tables, or other methods that can be used to indicate relevant information in the device. For example, it can be burned into the device when it leaves the factory, or configured when it first connects to the network. This application embodiment does not limit the specific implementation method. "Saving" can refer to saving in one or more memories. The one or more memories can be separate settings or integrated into the encoder or decoder, processor, or communication device. The one or more memories can also be partially separate settings and partially integrated into the decoder, processor, or communication device. The type of memory can be any form of storage medium, and this application embodiment does not limit this.

[0107] The “protocol” mentioned in the embodiments of this application may refer to a protocol family in the field of communication, a standard protocol with a similar protocol family frame structure, or a related protocol applied to future communication systems. The embodiments of this application do not specifically limit this.

[0108] In the embodiments of this application, descriptions such as "when," "under the circumstances," "if," and "if" all refer to the device making corresponding processing under certain objective circumstances, and are not limited to a specific time. They do not require the device to make a judgment action during implementation, nor do they imply any other limitations.

[0109] In this embodiment of the application, "sending information" can be understood as one device sending information to another device, or it can also be understood as one logic module inside a device sending information to another logic module. For example, "sending" can also be understood as the "output" of a chip interface. For example, "the first communication device sending information" can be understood as the first communication device sending information to another device (such as the second communication device), or it can be understood as logic module 1 in the first communication device sending information to logic module 2 in the first communication device.

[0110] In this application, "receiving information" can be understood as one device receiving information from another device, or it can be understood as a logic module within a device receiving information from another logic module. For example, "receiving" can also be understood as "input" of a chip interface. For example, "the first communication device receiving information" can be understood as the first communication device receiving information from another device (such as the second communication device), or it can be understood as logic module 1 in the first communication device receiving information from logic module 2 in the first communication device.

[0111] In this application, the phrase "sending information to... (e.g., the first communication device)" or the related illustrations in the accompanying drawings can be understood as the destination of the information being the first communication device. This can include sending information directly or indirectly to the first communication device. Similarly, the phrases "receiving information from... (e.g., the first communication device)," "receiving information from... (e.g., the first communication device)," or "receiving information sent (e.g., by the first communication device)," or the related illustrations in the accompanying drawings, can be understood as the source of the information being the first communication device. This can include receiving information directly or indirectly from the first communication device. The information may undergo necessary processing between the source and destination, such as format changes, but the destination can understand the valid information from the source. Similar expressions in this application can be interpreted similarly, and will not be elaborated further here.

[0112] The technical solutions provided in this application can be used in various communication systems, such as 3rd Generation Partnership Project (3GPP) communication systems, including 4th generation (4G) mobile communication systems, Long Term Evolution (LTE) systems, 5G mobile communication systems and their evolution systems, NTN systems, Narrow Band Internet of Things (NB-IoT) systems, Vehicle to Everything (V2X) systems, LTE and New Radio (NR) hybrid networking systems, NR systems, or device-to-device (D2D) systems, machine-to-machine (M2M) communication systems, Internet of Things (IoT), Wireless Fidelity (WiFi) systems, and other communication systems, such as future communication systems. Furthermore, the term "system" can be used interchangeably with "network."

[0113] It should be noted that the network architecture and business scenarios described in the embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided in the embodiments of this application. As those skilled in the art will know, with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0114] Figure 4 is a schematic diagram of a non-limiting, possible communication system applicable to an embodiment of this application. As shown in Figure 4, the communication system 40 includes RAN 400 and CN 500. RAN 400 includes at least one RAN node (410a and 410b in Figure 4, collectively referred to as 410) and at least one terminal device (420a-420j in Figure 4, collectively referred to as 420). RAN 400 may also include other RAN nodes, such as wireless relay devices and / or wireless backhaul devices (not shown in Figure 4). Terminal device 420 is wirelessly connected to RAN node 410. RAN node 410 is wirelessly or wired connected to core network 400. The core network device in core network 400 and RAN node 410 in RAN 400 can be different physical devices, or they can be the same physical device integrating core network logical functions and wireless access network logical functions.

[0115] Optionally, the communication system 40 may also include a data network (DN). The data network may be connected to the core network 400.

[0116] RAN 400 can be a 3GPP-related cellular system, such as a 4G, 5G mobile communication system, or a future-oriented evolution system. RAN 400 can also be an open access network (O-RAN or ORAN), a cloud radio access network (CRAN), or a wireless fidelity (WiFi) system. RAN 400 can also be a communication system that integrates two or more of the above systems.

[0117] RAN node 410, sometimes also referred to as access network equipment, network equipment, RAN entity, or access node, constitutes part of the communication system and is used to help terminal equipment achieve wireless access. Multiple RAN nodes 410 in communication system 40 can be of the same type or different types. In some scenarios, the roles of RAN node 410 and terminal equipment 420 are relative. For example, network element 420i in Figure 4 can be a helicopter or drone, which can be configured as a mobile base station. For terminal equipment 420j accessing RAN 400 through network element 420i, network element 420i is a base station; but for base station 410a, network element 420i is a terminal equipment. RAN node 410 and terminal equipment 420 are sometimes both referred to as communication devices. For example, network elements 410a and 410b in Figure 4 can be understood as communication devices with base station functions, and network elements 420a-420j can be understood as communication devices with terminal functions.

[0118] In one possible scenario, a RAN node can be a base station, an evolved NodeB (eNodeB), an access point (AP), a transmission reception point (TRP), a next-generation NodeB (gNB), a base station in a future mobile communication system, or an access node in a WiFi system. A RAN node can be a macro base station (as shown in Figure 4, 410a), a micro base station or indoor station (as shown in Figure 4, 410b), a relay node or donor node, or a radio controller in a CRAN scenario. Optionally, a RAN node can also be a server, wearable device, vehicle, or in-vehicle equipment. For example, in V2X technology, the RAN node can be a roadside unit (RSU).

[0119] In another possible scenario, multiple RAN nodes collaborate to assist terminal devices in achieving wireless access, with different RAN nodes each implementing a portion of the base station's functions. For example, RAN nodes can be central units (CUs), distributed units (DUs), CU-control plane (CPs), CU-user plane (UPs), or radio units (RUs), etc. CUs and DUs can be set up separately or included in the same network element, such as a baseband unit (BBU). RUs can be included in radio frequency equipment or radio frequency units, such as remote radio units (RRUs), active antenna units (AAUs), or remote radio heads (RRHs).

[0120] In different systems, CU (or CU-CP and CU-UP), DU, or RU may have different names, but those skilled in the art will understand their meaning. For example, in an ORAN system, CU can also be called O-CU (open CU), DU can also be called O-DU, CU-CP can also be called O-CU-CP, CU-UP can also be called O-CU-UP, and RU can also be called O-RU. For ease of description, this application uses CU, CU-CP, CU-UP, DU, and RU as examples. Any of the units among CU (or CU-CP, CU-UP), DU, and RU in this application can be implemented through software modules, hardware modules, or a combination of software and hardware modules.

[0121] In another possible scenario, one type of RAN node is used to relay data / signaling between other RAN nodes (e.g., base stations) and core network elements. This type of RAN node may not be used to assist terminal devices in achieving wireless access.

[0122] All or part of the functions of the RAN node in this application can also be implemented through software functions running on hardware, or through virtualization functions instantiated on a platform (e.g., a cloud platform). The RAN node may also be equipped with communication modules, circuits, or chips that perform corresponding communication functions. The RAN node may also be configured with program instructions for performing corresponding communication functions and corresponding program instructions. The RAN node in this application can also be a logical node, logical module, or software capable of implementing all or part of the RAN node functions.

[0123] Terminal devices can be devices or modules that access the aforementioned communication systems and possess corresponding communication functions. Terminal devices can also be referred to as terminals, user interfaces (UEs), mobile stations, mobile terminals, etc. Terminal devices can be widely used in various scenarios, such as D2D, V2X communication, machine-type communication (MTC), IoT, virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grids, smart furniture, smart offices, smart wearables, smart transportation, smart cities, etc. Terminal devices can be mobile phones, tablets, computers with wireless transceiver capabilities, wearable devices, vehicles, drones, helicopters, airplanes, ships, robots, robotic arms, smart home devices, transportation vehicles with wireless communication capabilities, communication modules, etc. The embodiments of this application do not limit the device form of the terminal device. Terminal devices typically contain communication modules, circuits, or chips that perform corresponding communication functions. Terminal devices can also be configured with program instructions for performing corresponding communication functions.

[0124] Logically, the core network can be divided into two parts: the user plane and the control plane. The control plane is responsible for the management of the mobile network, while the user plane is responsible for the transmission of service data. Different network elements in the core network are responsible for different functions. Taking the 5G core network as an example, the AMF (Access Detection and Detection) network element is mainly responsible for user access management, security authentication, and mobility management. The UPF (User Detection and Forwarding) network element is mainly responsible for the routing and forwarding of user plane data packets.

[0125] In one possible scenario, a core network element is used to relay data / signaling between other core network elements and RAN nodes, and / or to relay data / signaling between different core network elements, and / or to relay data / signaling between core network elements and data network (DN).

[0126] In this embodiment of the application, the network element can also be referred to as an entity or functional entity.

[0127] The communication method provided in the embodiments of this application will be described in detail below with reference to Figure 4.

[0128] It should be noted that the message name or the name of each parameter in the message in the following embodiments of this application is just an example, and other names may be used in the specific implementation. This application does not specifically limit this.

[0129] It should be noted that the names of the various devices in the following embodiments of this application are just examples, and other names may be used in the actual implementation. This application does not specifically limit the names of the devices.

[0130] Figure 5 illustrates a communication method provided in an embodiment of this application. Figure 5 uses a first communication device, a second communication device, and a third communication device as illustrative execution entities to illustrate the method, but this application does not limit the illustrative execution entities. For example, the first communication device in Figure 5 can also be a module applied to the first communication device, such as a chip, chip system, or processor, or it can be a logical node, logical module, or software capable of implementing all or part of the functions of the first communication device. Similarly, the second communication device in Figure 5 can also be a module applied to the second communication device, such as a chip, chip system, or processor, or it can be a logical node, logical module, or software capable of implementing all or part of the functions of the second communication device. Likewise, the third communication device in Figure 5 can also be a module applied to the third communication device, such as a chip, chip system, or processor, or it can be a logical node, logical module, or software capable of implementing all or part of the functions of the third communication device. Furthermore, the processing performed by a single execution entity can be divided into multiple execution entities, which can be logically and / or physically separated. For example, if the first, second, or third communication device is a RAN node, the processing performed by the first, second, or third communication device can be divided and executed by at least one of CU, DU, RU, etc. The communication method includes the following steps:

[0131] S501, the first communication device sends first information to the third communication device via a first protocol. Correspondingly, the third communication device receives the first information from the first communication device via the first protocol.

[0132] S502, the third communication device sends first information to the second communication device through the second protocol, and correspondingly, the second communication device receives the first information from the third communication device through the second protocol. Wherein, at least one of the first and second protocols is the QUIC protocol.

[0133] In this application embodiment, the first communication device, the second communication device, or the third communication device can be a gateway (GW), a RAN node, a terminal, a core network element, or a bearer network node. For example, if this application embodiment is applied to a future network, the first communication device, the second communication device, or the third communication device can be a new RAN node, a terminal, a network element, or an enhancement of the functions of an existing network element.

[0134] In this context, a Gateway (GW) is a node capable of exchanging data / signaling with other network nodes. This application does not limit the form of the GW. A GW can be a node independent of a RAN node, terminal, core network element, or bearer network node; alternatively, a GW can be a RAN node, terminal, core network element, or bearer network node; or, a GW can be a module within a RAN node, terminal, core network element, or bearer network node. For example, a GW can be deployed as an RAN node within the RAN and can be called a RAN GW; or, for instance, a GW can be used as a core network element and can be called a CN GW. GWs can also have other names and forms.

[0135] For at least one of the first and second protocols to be the QUIC protocol, the following different scenarios are possible: the first protocol is a protocol different from the QUIC protocol, and the second protocol is the QUIC protocol. Alternatively, the first protocol is the QUIC protocol, and the second protocol is a protocol different from the QUIC protocol. Or, both the first and second protocols are the QUIC protocol.

[0136] This application does not specifically limit the use of protocols other than QUIC. Optionally, the protocol other than QUIC can be an existing communication protocol, such as GTP-U, SCTP, or Transmission Control Protocol (TCP).

[0137] Based on the communication method provided in this application, communication devices can transmit information via the QUIC protocol. Benefiting from the flexibility of the QUIC protocol in handling path changes and switching, when establishing a control plane connection / user plane session, a QUIC connection only needs to be established once on a specific path. When a path switch is required, it can be directly switched to another path without re-establishing the link. This reduces service interruptions, latency, and additional signaling overhead, thereby improving service transmission performance. Furthermore, compared to existing user plane protocols, the QUIC protocol offers better topology scalability, extensibility, and flexibility, supports superior flow control, congestion control, and security mechanisms, and can better support new services in future networks.

[0138] In S501-S502, the transmission of the first information from the first communication device to the second communication device may include: the first communication device sending a first message to the third communication device, the first message including the first information (or, in other words, the first information is carried in the first message). After receiving the first message, the third communication device sends a second message to the second communication device, the second message including the first information (or, in other words, the first information is carried in the second message).

[0139] In this application, the path used for transmitting data / signaling is not limited. Taking a message carrying first information as an example, the message carrying first information can be transmitted through any of the following paths: a path connected via a non-terrestrial communication network (NTN link), a path connected via a terrestrial communication network (TN link), a path connected via a sub-network (distributed networking link), a path connected via microwave (microwave link), a path connected via a first network, or a path connected via a second network. The first network and the second network are different. For example, the first network can be a 5G mobile communication network, and the second network can be a future mobile communication network.

[0140] Optionally, there may be one or more paths for transmitting data / signaling between the first and second communication devices, and / or between the second and third communication devices. When transmitting data / signaling, the first, second, or third communication device may select or switch the path used for transmitting data / signaling. For example, the communication devices may have paths connecting through a first network and paths connecting through a second network. For instance, referring to Figure 1, there are multiple paths for transmitting data / signaling between the RAN node and the core network element.

[0141] In this embodiment of the application, the communication device (e.g., a first communication device, a second communication device, or a third communication device) can obtain the mapping relationship between various transmission channels and determine the transmission channel used for transmitting data / signaling based on the mapping relationship. Taking the transmission of first information as an example, after receiving the first message, the third communication device can determine the transmission channel used for transmitting the second message based on the mapping relationship.

[0142] In this embodiment, the transmission channel used for transmitting data / signaling may have different names depending on the protocol employed. For example, the transmission channel may be a path, tunnel, connection, or stream. For instance, if the transmission channel uses the GTP-U protocol, it may be called a GTP-U tunnel. As another example, if the transmission channel uses the SCTP protocol, it may be called an SCTP connection. Optionally, an SCTP connection may include one or more SCTP streams, or one or more SCTP streams may belong to the SCTP connection. In this case, data / signaling is transmitted through the SCTP streams included in the SCTP connection. As yet another example, if the transmission channel uses the TCP protocol, it may be called a TCP connection.

[0143] This application does not limit the implementation of how the communication device obtains the mapping relationships between various transmission channels. In one possible implementation, the communication device can obtain configuration information used to configure the mapping relationships between various transmission channels.

[0144] The mapping relationships between various transmission channels can be indicated by the mapping relationships between the identification information of various transmission channels. Taking the example that a transmission channel can be a path, tunnel, connection, or stream, the mapping relationship between the identification information of a connection and the identification information of a tunnel can indicate the mapping relationship between a connection and a tunnel. In this paper, "the mapping relationship between the identification information of a connection and the identification information of a tunnel" and "the mapping relationship between a connection and a tunnel" can be used interchangeably. The mapping relationship between the identification information of a connection and the identification information of a connection can indicate the mapping relationship between connections. In this paper, "the mapping relationship between the identification information of a connection and the identification information of a connection" and "the mapping relationship between connections and connections" can be used interchangeably. The mapping relationship between the identification information of a connection and the identification information of a stream can indicate the mapping relationship between a connection and a stream. In this paper, "the mapping relationship between the identification information of a connection and the identification information of a stream" and "the mapping relationship between a connection and a stream" can be used interchangeably. The mapping relationship between the identification information of a connection and the identification information of a path can indicate the mapping relationship between a connection and a path. In this paper, "the mapping relationship between the identification information of a connection and the identification information of a path" and "the mapping relationship between a connection and a path" can be used interchangeably.

[0145] This application does not specifically limit the identification information of the transmission channel. For example, the identification information of a GTP-U tunnel can be the GTP-U tunnel ID, i.e., the GTP-U tunnel end ID (GTP-U TEID). The identification information of an SCTP connection can be the SCTP connection ID (SCTP ID). The identification information of an SCTP stream can be the SCTP stream ID. The identification information of a QUIC connection can be the QUIC CID. The identification information of a QUIC stream can be the QUIC stream ID. The path identification information (link ID) can include one or more of the following: network ID (e.g., public land mobile network (PLMN ID), NTN ID), network type ID (e.g., TN network type ID, NTN network type ID), sub-network ID, etc.

[0146] Optionally, the configuration information used to configure the mapping relationship between connections and paths / tunnels / connections / flows can also be called connection mapping rules.

[0147] Similarly, the mapping relationship between tunnel identification information and path / tunnel / connection / flow identification information can indicate the mapping relationship between tunnels and paths / tunnels / connections / flows. In this paper, "the mapping relationship between tunnel identification information and path / tunnel / connection / flow identification information" and "the mapping relationship between tunnels and paths / tunnels / connections / flows" can be used interchangeably.

[0148] Optionally, the configuration information used to configure the mapping relationship between tunnels and paths / tunnels / connections / flows can also be called tunnel mapping rules.

[0149] Similarly, the mapping relationship between flow identification information and path / tunnel / connection / flow identification information can indicate the mapping relationship between flow and path / tunnel / connection / flow. In this paper, "the mapping relationship between flow identification information and path / tunnel / connection / flow identification information" and "the mapping relationship between flow and path / tunnel / connection / flow" can be used interchangeably.

[0150] Optionally, the configuration information used to configure the mapping relationship between streams and paths / tunnels / connections / streams can also be called stream mapping rules.

[0151] The following section uses the example of a transmission channel using the QUIC protocol (such as a QUIC connection or QUIC stream) and a transmission channel using other protocols (such as a GTP-U tunnel, SCTP connection, SCTP stream, or TCP connection) to illustrate the mapping relationship between different transmission channels.

[0152] Optionally, in this embodiment, the mapping relationship between the identification information of the GTP-U tunnel and the identification information of the QUIC connection can be a one-to-one correspondence, or a many-to-one correspondence (the identification information of multiple GTP-U tunnels corresponds to the identification information of the same QUIC connection), or a one-to-many correspondence (the identification information of multiple QUIC connections corresponds to the identification information of the same GTP-U tunnel). That is, the configuration information used to configure this mapping relationship can include the identification information of at least one GTP-U tunnel and the identification information of at least one QUIC connection. In this configuration information, the identification information of one GTP-U tunnel can correspond to the identification information of one or more QUIC connections, representing that the GTP-U tunnel corresponds to one or more QUIC connections, and the identification information of one QUIC connection can correspond to the identification information of one or more GTP-U tunnels, representing that the QUIC connection corresponds to one or more GTP-U tunnels.

[0153] Optionally, in this embodiment, the mapping relationship between the identification information of the GTP-U tunnel and the identification information of the QUIC stream (e.g., QUIC Stream ID) can be one-to-one, or many-to-one (the identification information of multiple GTP-U tunnels corresponds to the identification information of the same QUIC stream), or one-to-many (the identification information of multiple QUIC streams corresponds to the identification information of the same GTP-U tunnel). That is, the configuration information used to configure the mapping relationship between the identification information of the GTP-U tunnel and the identification information of the QUIC stream can include the identification information of at least one GTP-U tunnel and the identification information of at least one QUIC stream. In this configuration information, the identification information of one GTP-U tunnel can correspond to the identification information of one or more QUIC streams, representing that the GTP-U tunnel corresponds to one or more QUIC streams, and the identification information of one QUIC stream can correspond to the identification information of one or more GTP-U tunnels, representing that the QUIC stream corresponds to one or more GTP-U tunnels.

[0154] Optionally, the configuration information used to configure the mapping relationship between the identification information of GTP-U tunnels and the identification information of QUIC connections can also configure the mapping relationship between the identification information of GTP-U tunnels and the identification information of QUIC flows. In this case, the configuration information includes the identification information of at least one GTP-U tunnel, the identification information of at least one QUIC connection, and the identification information of at least one QUIC flow. The correspondence between the identification information of GTP-U tunnels and the identification information of QUIC connections in this configuration information can be referred to the above description. In this configuration information, for the identification information of any QUIC connection corresponding to the identification information of a certain GTP-U tunnel, the identification information of the QUIC connection may correspond to the identification information of one or more QUIC flows, representing that these one or more QUIC flows belong to the QUIC connection (these one or more QUIC flows are all or part of the QUIC flows included in the QUIC connection), and these one or more QUIC flows correspond to the GTP-U tunnel corresponding to the QUIC connection.

[0155] Optionally, in this configuration information, the identification information of a QUIC connection corresponding to the identification information of a certain GTP-U tunnel may not correspond to the identification information of any QUIC flow, which means that the QUIC connection does not include a QUIC flow.

[0156] Optionally, the configuration information used to configure the mapping relationship between the identification information of the GTP-U tunnel and the identification information of the QUIC connection may also include at least one of the following: identification information of at least one path, identification information of at least one session, or identification information of at least one quality of service (QoS) flow included in at least one session.

[0157] In this context, the identification information of at least one path may correspond to the identification information of one or more QUIC connections, indicating that these one or more QUIC connections are carried by that path. Optionally, the identification information of a path may also correspond to the identification information of one or more QUIC streams, indicating that these one or more QUIC streams are carried by that path. The identification information of a path can also be referred to as the identification information of the path corresponding to a QUIC connection or a QUIC stream.

[0158] This application does not limit the path, and it can be a satellite link, a 5G mobile communication network link, a future mobile communication network link, a terrestrial link, or a microwave link. For example, the path identification information can be a Link ID.

[0159] In this embodiment, the identification information of at least one session may correspond to the identification information of one or more GTP-U tunnels, indicating that the data of the session can be transmitted through these one or more GTP-U tunnels. Optionally, the identification information of a session may also correspond to the identification information of one or more QUIC connections, indicating that the data of the session can be transmitted through these one or more QUIC connections. Optionally, the identification information of a session may also correspond to the identification information of one or more QUIC streams, indicating that the data of the session can be transmitted through these one or more QUIC streams. This application embodiment does not limit the session; for example, it can be a PDU session. Exemplarily, the identification information of a session can be a Session ID.

[0160] In this context, at least one session includes identification information for a Quality of Service (QoS) flow. The identification information of one QoS flow may correspond to the identification information of one or more GTP-U tunnels, indicating that the data of the QoS flow can be transmitted through these one or more GTP-U tunnels. Optionally, the identification information of one QoS flow may also correspond to the identification information of one or more QUIC connections, indicating that the data of the QoS flow can be transmitted through these one or more QUIC connections. Alternatively, the identification information of one QoS flow may also correspond to the identification information of one or more QUIC flows, indicating that the data of the session can be transmitted through these one or more QUIC flows. For example, the identification information of the QoS flow may be the QoS flow ID (QFI).

[0161] Optionally, in this embodiment, the mapping relationship between the identification information of SCTP connections and the identification information of QUIC connections can be a one-to-one correspondence, or a many-to-one correspondence (the identification information of multiple SCTP connections corresponds to the identification information of the same QUIC connection), or a one-to-many correspondence (the identification information of multiple QUIC connections corresponds to the identification information of the same SCTP connection). That is, the configuration information used to configure this mapping relationship can include the identification information of at least one SCTP connection and the identification information of at least one QUIC connection. In this configuration information, the identification information of one SCTP connection can correspond to the identification information of one or more QUIC connections, representing that the SCTP connection corresponds to one or more QUIC connections, and the identification information of one QUIC connection can correspond to the identification information of one or more SCTP connections, representing that the QUIC connection corresponds to one or more SCTP connections.

[0162] Optionally, in this embodiment, the mapping relationship between the identification information of SCTP connections and the identification information of QUIC streams can be one-to-one, many-to-one (the identification information of multiple SCTP connections corresponds to the identification information of the same QUIC stream), or one-to-many (the identification information of multiple QUIC streams corresponds to the identification information of the same SCTP connection). That is, the configuration information used to configure the mapping relationship between the identification information of SCTP connections and the identification information of QUIC streams can include the identification information of at least one SCTP connection and the identification information of at least one QUIC stream. In this configuration information, the identification information of one SCTP connection can correspond to the identification information of one or more QUIC streams, representing that the SCTP connection corresponds to one or more QUIC streams, and the identification information of one QUIC stream can correspond to the identification information of one or more SCTP connections, representing that the QUIC stream corresponds to one or more SCTP connections.

[0163] Optionally, in this embodiment, the mapping relationship between the identification information of SCTP streams and the identification information of QUIC connections can be a one-to-one correspondence, or a many-to-one correspondence (the identification information of multiple SCTP streams corresponds to the identification information of the same QUIC connection), or a one-to-many correspondence (the identification information of multiple QUIC connections corresponds to the identification information of the same SCTP stream). That is, the configuration information used to configure the mapping relationship between the identification information of SCTP streams and the identification information of QUIC connections can include the identification information of at least one SCTP stream and the identification information of at least one QUIC connection. In this configuration information, the identification information of one SCTP stream can correspond to the identification information of one or more QUIC connections, representing that the SCTP stream corresponds to one or more QUIC connections, and the identification information of one QUIC connection can correspond to the identification information of one or more SCTP streams, representing that the QUIC connection corresponds to one or more SCTP streams.

[0164] Optionally, in this embodiment, the mapping relationship between the identification information of SCTP streams and the identification information of QUIC streams can be a one-to-one correspondence, or a many-to-one correspondence (the identification information of multiple SCTP streams corresponds to the identification information of the same QUIC stream), or a one-to-many correspondence (the identification information of multiple QUIC streams corresponds to the identification information of the same SCTP stream). That is, the configuration information used to configure the mapping relationship between the identification information of SCTP streams and the identification information of QUIC streams can include at least one identification information of SCTP streams and at least one identification information of QUIC streams. In this configuration information, the identification information of one SCTP stream can correspond to the identification information of one or more QUIC streams, representing that the SCTP stream corresponds to one or more QUIC streams, and the identification information of one QUIC stream can correspond to the identification information of one or more SCTP streams, representing that the QUIC stream corresponds to one or more SCTP streams.

[0165] Optionally, the configuration information used to configure the mapping relationship between the identification information of SCTP connections and the identification information of QUIC connections can also configure the mapping relationship between the identification information of SCTP connections and the identification information of QUIC streams. In this case, the configuration information includes the identification information of at least one SCTP connection, the identification information of at least one QUIC connection, and the identification information of at least one QUIC stream. The correspondence between the identification information of SCTP connections and the identification information of QUIC connections in this configuration information can be referred to the above description. In this configuration information, for the identification information of a QUIC connection corresponding to the identification information of a certain SCTP connection, the identification information of the QUIC connection may correspond to the identification information of one or more QUIC streams, representing that these one or more QUIC streams belong to the QUIC connection (these one or more QUIC streams are all or part of the QUIC streams included in the QUIC connection), and these one or more QUIC streams correspond to the SCTP connection corresponding to the QUIC connection.

[0166] Optionally, the configuration information used to configure the mapping relationship between the identification information of SCTP connections and the identification information of QUIC connections can also configure the mapping relationship between the identification information of SCTP flows and the identification information of QUIC connections. In this case, the configuration information includes the identification information of at least one SCTP connection, the identification information of at least one SCTP flow, and the identification information of at least one QUIC connection. The correspondence between the identification information of SCTP connections and the identification information of QUIC connections in this configuration information can be referred to the above description. In this configuration information, for the identification information of any SCTP connection corresponding to the identification information of a certain QUIC connection, the identification information of the SCTP connection may correspond to the identification information of one or more SCTP flows, representing that these one or more SCTP flows belong to the SCTP connection (these one or more SCTP flows are all or part of the SCTP flows included in the SCTP connection), and these one or more SCTP flows correspond to the QUIC connection corresponding to the SCTP connection.

[0167] Optionally, the configuration information used to configure the mapping relationship between the identification information of SCTP connections and the identification information of QUIC connections can also configure the mapping relationship between the identification information of SCTP streams and the identification information of QUIC streams. In this case, the configuration information includes the identification information of at least one SCTP connection, the identification information of at least one SCTP stream, the identification information of at least one QUIC connection, and the identification information of at least one QUIC stream. The correspondence between the identification information of SCTP connections and the identification information of QUIC connections, the correspondence between the identification information of SCTP connections and the identification information of QUIC streams, and the correspondence between the identification information of SCTP streams and the identification information of QUIC connections can be referred to the above description. In this configuration information, for the identification information of any SCTP connection corresponding to the identification information of a certain QUIC stream, the identification information of the SCTP connection may correspond to the identification information of one or more SCTP streams, representing that these one or more SCTP streams belong to the SCTP connection (these one or more SCTP streams are all or part of the SCTP streams included in the SCTP connection), and these one or more SCTP streams correspond to the QUIC streams corresponding to the SCTP connection. Similarly, for the identification information of any QUIC connection corresponding to the identification information of a certain SCTP flow, the identification information of the QUIC connection may correspond to the identification information of one or more QUIC flows, indicating that the one or more QUIC flows belong to the QUIC connection (the one or more QUIC flows are all or part of the QUIC flows included in the QUIC connection), and the one or more QUIC flows correspond to the SCTP flow corresponding to the QUIC connection.

[0168] Optionally, the configuration information used to configure the mapping relationship between the identification information of SCTP connection / SCTP flow and the identification information of QUIC connection / QUIC flow may further include at least one of the following: identification information of at least one path, identification information of at least one message type, or identification information of at least one message.

[0169] The path identification information can also be referred to as the path identification information corresponding to a QUIC connection or QUIC stream. For details, please refer to the above introduction on the path identification information corresponding to a QUIC connection or QUIC stream.

[0170] Among the at least one message type identification information, the identification information of one message type can correspond to at least one of the identification information of at least one SCTP connection, at least one SCTP stream, at least one QUIC connection, or at least one QUIC stream, to indicate that a message belonging to that message type can be transmitted through at least one of the corresponding at least one SCTP connection, at least one SCTP stream, at least one QUIC connection, or at least one QUIC stream. That is, the identification information of at least one message type indicates at the granularity of the message type. For example, the identification information of the message type can be a message type ID.

[0171] The number of identification information for at least one message may be one or more, wherein one identification information is used to identify at least one message belonging to the same process. The identification information for at least one message may correspond to at least one of the identification information of at least one SCTP connection, at least one SCTP stream, at least one QUIC connection, or at least one QUIC stream, and is used to indicate that at least one message belonging to the same process identified by the identification information can be transmitted through the corresponding at least one SCTP connection, at least one SCTP stream, at least one QUIC connection, or at least one QUIC stream.

[0172] For example, at least one message may be identified by a transaction ID, used to associate related messages belonging to the same procedure. Messages belonging to the same procedure should contain the same transaction ID. For instance, a request message and its corresponding response message carrying the same transaction ID belong to the same procedure.

[0173] Taking Radio Resource Control (RRC) messages as an example, the following rules apply to whether or not to carry a transaction ID. These rules also apply to other types of messages (such as messages on the interface between RAN and CN, messages on the interface between RANs, messages on the interface within the RAN, messages on the interface between core network elements, etc.), and will not be elaborated further:

[0174] 1. By default, downlink messages initiated by the network should include an interaction identifier.

[0175] 2: Uplink messages that directly respond to downlink messages with interaction identifiers should include interaction identifiers.

[0176] 3: Uplink messages that require a direct downlink response should include an interaction identifier.

[0177] 4: Uplink messages that are neither a response to downlink messages nor require a response from the network may not contain an interaction identifier.

[0178] Optionally, in this embodiment, the mapping relationship between the identification information of the TCP connection and the identification information of the QUIC connection can be one-to-one, many-to-one, or one-to-many. That is, the configuration information used to configure this mapping relationship can include the identification information of at least one TCP connection and the identification information of at least one QUIC connection. For details, please refer to the above description of the mapping relationship between the identification information of the SCTP connection and the identification information of the QUIC connection.

[0179] Optionally, in this embodiment, the mapping relationship between the TCP connection identification information and the QUIC stream identification information can be one-to-one, many-to-one, or one-to-many. That is, the configuration information used to configure the mapping relationship between the TCP connection identification information and the QUIC stream identification information can include the identification information of at least one TCP connection and the identification information of at least one QUIC stream. For details, please refer to the above description of the mapping relationship between the SCTP connection identification information and the QUIC stream identification information.

[0180] Optionally, the configuration information used to configure the mapping relationship between the identification information of the TCP connection and the identification information of the QUIC connection can also configure the mapping relationship between the identification information of the TCP connection and the identification information of the QUIC stream. For details, please refer to the above description of the configuration information used to configure the mapping relationship between the identification information of the SCTP connection and the identification information of the QUIC connection, and also the description of the mapping relationship between the identification information of the SCTP connection and the identification information of the QUIC stream.

[0181] Optionally, the configuration information used to configure the mapping relationship between the identification information of the TCP connection and the identification information of the QUIC connection / QUIC stream may further include at least one of the following: identification information of at least one path, identification information of at least one message type, or identification information of at least one message.

[0182] For details on the path identification information, please refer to the above description of the path identification information corresponding to QUIC connections or QUIC streams.

[0183] Among them, the identification information of at least one message type can correspond to at least one of the identification information of at least one TCP connection, at least one QUIC connection, or at least one QUIC stream, and is used to indicate that a message belonging to that message type can be transmitted through at least one of the corresponding at least one TCP connection, at least one QUIC connection, or at least one QUIC stream.

[0184] The number of identification information for at least one message may be one or more, wherein one identification information is used to identify at least one message belonging to the same process. The identification information for at least one message may correspond to at least one of the identification information of at least one TCP connection, at least one QUIC connection, or at least one QUIC stream, and is used to indicate that at least one message belonging to the same process identified by the identification information can be transmitted through the corresponding at least one TCP connection, at least one QUIC connection, or at least one QUIC stream.

[0185] The configuration information used to configure the mapping relationship between the identification information of TCP connections and the identification information of QUIC connections / QUIC streams may also include other information. For details, please refer to the above description of the configuration information used to configure the mapping relationship between the identification information of SCTP connections / SCTP streams and the identification information of QUIC connections / QUIC streams.

[0186] In this embodiment of the application, the mapping relationship between transmission channels using other protocols and transmission channels using the QUIC protocol can be specifically referred to in the above description of the mapping relationship between transmission channels using the GTP-U protocol, transmission channels using the SCTP protocol, transmission channels using the TCP protocol, and transmission channels using the QUIC protocol.

[0187] The following describes S501-S502 in several exemplary scenarios where at least one of the first and second protocols is the QUIC protocol.

[0188] Scenario 1: The first protocol is GTP-U, and the second protocol is QUIC. It's understandable that Scenario 1 refers to the user plane; the first protocol is the user plane protocol, and the first information is user plane data / signaling.

[0189] In Scenario 1, the first communication device supports the GTP-U protocol. The third communication device supports both the GTP-U and QUIC protocols. The second communication device supports the QUIC protocol.

[0190] In Scenario 1, one or more GTP-U tunnels are established between the first and third communication devices. One or more QUIC connections are established between the third and second communication devices. Optionally, a QUIC connection may include one or more QUIC streams.

[0191] Optionally, the first, second, or third communication device may also support other protocols. For example, the second communication device may also support the GTP-U protocol.

[0192] Optionally, the first communication device may or may not support the QUIC protocol. If the first communication device supports both the QUIC and GTP-U protocols, the first communication device will choose to transmit the first information via the GTP-U protocol.

[0193] For example, Figure 6 is a possible protocol stack diagram for Scenario 1. In Figure 6, the first communication device is a RAN node that supports the GTP-U protocol but not the QUIC protocol. The third communication device is a GW (denoted as RAN GW in Figure 6) that supports both the GTP-U and QUIC protocols and is connected to the first communication device. The second communication device is a GW (denoted as CN GW in Figure 6) that supports both the QUIC and GTP-U protocols and is connected to the third communication device, as well as to core network elements that support the GTP-U protocol. The GW can act as an intermediate node to transmit user plane data / signaling between the RAN and the core network. Other protocol stacks shown in Figure 6 can be referenced from existing communication protocols and will not be elaborated here.

[0194] For example, Figure 7 shows another possible protocol stack diagram for Scenario 1. In Figure 7, the first communication device is a RAN node that supports the GTP-U protocol but not the QUIC protocol; the third communication device is a GW that supports both the GTP-U and QUIC protocols (denoted as RAN GW in Figure 7); and the second communication device is a core network element that supports the QUIC protocol (Figure 7 uses a UPF network element as an example). The GW can act as an intermediate node to transmit user plane data / signaling between the RAN and the core network. Other protocol stacks shown in Figure 7 can be referenced from existing communication protocols and will not be elaborated upon here.

[0195] The various protocols appearing in the embodiments of this application, such as the service data adaptation protocol (SDAP), packet data convergence protocol (PDCP), radio link control (RLC) layer protocol, media access control (MAC) layer protocol, and physical (PHY) layer protocol, can be referred to existing protocols for details.

[0196] In Scenario 1, the first message includes first identification information, which identifies a GTP-U tunnel between the first and third communication devices for transmitting the first message. For example, the first identification information can be a GTP-UTEID. The second message includes second identification information, which identifies a QUIC connection between the third and second communication devices for transmitting the second message. For example, the second identification information can be a QUIC CID.

[0197] There is a mapping relationship between the second identification information and the first identification information. After receiving the first message, the third communication device can determine the second identification information corresponding to the first identification information based on the first identification information and the mapping relationship, and then carry the second identification information in the second message and transmit the second message through the QUIC connection identified by the second identification information.

[0198] This application does not limit the specific implementation of the third communication device obtaining the mapping relationship between the second identification information and the first identification information. In one possible implementation, the third communication device can obtain configuration information (which may be called first configuration information) used to configure the mapping relationship, and the first configuration information includes the first identification information and the second identification information.

[0199] Optionally, the first configuration information may include first identification information, second identification information, and at least one of the following: identification information of the QUIC flow included in the QUIC connection identified by the second identification information, identification information of the path corresponding to the QUIC connection or QUIC flow, identification information of at least one session, or identification information of the quality of service flow included in at least one session. For details on the first configuration information, please refer to the above description of the configuration information used to configure the mapping relationship between the GTP-U tunnel and the QUIC connection.

[0200] In Scenario 1, after receiving the first message, the third communication device can determine the QUIC connection (i.e., the QUIC connection identified by the second identification information) for transmitting the second message based on the mapping relationship configured by the first identification information and the first configuration information. Optionally, it can also determine the QUIC stream for transmitting the second message (the QUIC stream belongs to the QUIC connection identified by the second identification information, and the identification information of the QUIC stream corresponds to the first identification information). Optionally, it can also determine the path for transmitting the second message (the identification information of the path corresponds to the identification information of the QUIC connection or the QUIC stream).

[0201] Optionally, if the first configuration information does not include the identification information of the QUIC stream corresponding to the first identification information, the third communication device may select any QUIC stream from the QUIC streams included in the QUIC connection identified by the second identification information to transmit the second message. If the first configuration information does not include the identification information of the path corresponding to the QUIC connection or QUIC stream used to transmit the second message, the third communication device may select any path to transmit the second message.

[0202] Optionally, the second message may also include identification information of the QUIC stream used to transmit the second message, and / or identification information of the path used to transmit the second message.

[0203] Optionally, in scenario one, the first information may include at least one of the following: session identification information, QoS flow identification information, first identification information, priority information, or identification information of the path corresponding to the GTP-U tunnel.

[0204] The session identification information identifies the session to which the first information belongs. The QoS flow identification information identifies the QoS flow to which the first information belongs. The priority level information indicates at least one of the following priorities: the priority of selecting different paths for data transmission, the priority of transmitting the first information, or the priority of scheduling the first information. The path identification information corresponding to the GTP-U tunnel identifies the path for transmitting the first message (i.e., the path used to carry the SCTP connection identified by the first identification information).

[0205] Optionally, the first information may also include other information, which is not limited in this embodiment of the application.

[0206] Scenario 2: The first protocol is SCTP, and the second protocol is QUIC. It's understandable that Scenario 2 pertains to the control plane; the first protocol is a control plane protocol, and the first information is control plane data / signaling.

[0207] In Scenario 2, the first communication device supports the SCTP protocol. The third communication device supports both the SCTP and QUIC protocols. The second communication device supports the QUIC protocol.

[0208] In Scenario 2, one or more SCTP connections are established between the first and third communication devices. Optionally, an SCTP connection may include one or more SCTP streams. One or more QUIC connections are established between the third and second communication devices. Optionally, a QUIC connection may include one or more QUIC streams.

[0209] Optionally, the first, second, or third communication device may also support other protocols. For example, the second communication device may also support the SCTP protocol.

[0210] Optionally, the first communication device may or may not support the QUIC protocol. If the first communication device supports both the QUIC and SCTP protocols, it will choose to transmit the first information via the SCTP protocol.

[0211] For example, Figure 8 is a possible protocol stack diagram for Scenario 2. In Figure 8, the first communication device is a RAN node that supports the SCTP protocol but not the QUIC protocol. The third communication device is a GW (denoted as RAN GW in Figure 8) that supports both the SCTP and QUIC protocols and is connected to the first communication device. The second communication device is a GW (denoted as CN GW in Figure 8) that supports both the QUIC and SCTP protocols and is connected to the third communication device, as well as to core network elements that support the SCTP protocol. The GW can act as an intermediate node to transmit user plane data / signaling between the RAN and the core network. Other protocol stacks shown in Figure 8 can be referenced from existing communication protocols and will not be elaborated here.

[0212] For example, Figure 9 shows another possible protocol stack diagram for Scenario 1. In Figure 9, the first communication device is a RAN node that supports the SCTP protocol but not the QUIC protocol; the third communication device is a GW that supports both the SCTP and QUIC protocols (denoted as RAN GW in Figure 9); and the second communication device is a core network element that supports the QUIC protocol (Figure 9 uses an AMF network element as an example). The GW can act as an intermediate node to transmit user plane data / signaling between the RAN and the core network. Other protocol stacks shown in Figure 9 can be referenced from existing communication protocols and will not be elaborated upon here.

[0213] In Scenario 2, the first message includes first identification information, which identifies an SCTP connection between a first communication device and a third communication device for transmitting the first message. For example, the first identification information can be an SCTP ID. The first identification information can be an IP 5-tuple (including the following information: source IP address, destination IP address, source port number, destination port number, and protocol type). Optionally, the first message may also include third identification information, which identifies an SCTP stream belonging to the SCTP connection identified by the first identification information and is an SCTP stream between the first communication device and the third communication device for transmitting the first message. For example, the third identification information can be an SCTP stream ID.

[0214] In scenario two, the second message includes second identification information, which identifies a QUIC connection between the third communication device and the second communication device for transmitting the second message. For example, the second identification information can be a QUIC CID.

[0215] There is a mapping relationship between the first identification information and / or the third identification information and the second identification information. After receiving the first message, the third communication device can determine the second identification information corresponding to the first identification information and / or the third identification information based on the first identification information and / or the third identification information and the mapping relationship, and then carry the second identification information in the second message and transmit the second message through the QUIC connection identified by the second identification information.

[0216] This application does not limit the specific implementation of the third communication device obtaining the first identification information and / or the mapping relationship between the third identification information and the second identification information. In one possible implementation, the third communication device may obtain configuration information (which may be referred to as the second configuration information) for configuring the mapping relationship. The second configuration information includes the second identification information and at least one of the following: the first identification information or the third identification information.

[0217] Optionally, the second configuration information may include at least one of the first identification information or the third identification information, and the second identification information may include at least one of the following: identification information of the QUIC stream included in the QUIC connection identified by the second identification information, identification information of the path corresponding to the QUIC connection or QUIC stream, and a fourth identification information or a fifth identification information. The fourth identification information is used to identify the type of message transmitted through the SCTP connection (the SCTP connection identified by the first identification information), the SCTP stream (the SCTP stream identified by the third identification information), the QUIC connection, or the QUIC stream. The fifth identification information is used to identify at least one message belonging to the same process transmitted through the SCTP connection, SCTP stream, QUIC connection, or QUIC stream. For details on the second configuration information, please refer to the above description of the configuration information used to configure the mapping relationship between the SCTP connection / SCTP stream and the QUIC connection.

[0218] In Scenario 2, after receiving the first message, the third communication device can determine the QUIC connection (i.e., the QUIC connection identified by the second identification information) for transmitting the second message based on the mapping relationship configured by the first identification information and / or the third identification information and the second configuration information. Optionally, it can also determine the QUIC stream for transmitting the second message (the QUIC stream belongs to the QUIC connection identified by the second identification information, and the identification information of the QUIC stream corresponds to the first identification information and / or the third identification information). Optionally, it can also determine the path for transmitting the second message (the identification information of the path corresponds to the identification information of the QUIC connection or the QUIC stream).

[0219] Optionally, if the second configuration information does not include the identification information of the QUIC stream corresponding to the first identification information and / or the third identification information, the third communication device may select any QUIC stream from the QUIC streams included in the QUIC connection identified by the second identification information to transmit the second message. If the second configuration information does not include the identification information of the path corresponding to the QUIC connection or QUIC stream used to transmit the second message, the third communication device may select any path to transmit the second message.

[0220] Optionally, the second message may also include identification information of the QUIC stream used to transmit the second message, and / or identification information of the path used to transmit the second message.

[0221] Optionally, in Scenario 2, the first information may include at least one of the following: sixth identification information, seventh identification information, terminal identification information, first identification information, third identification information, priority information, or identification information of the path corresponding to the SCTP connection or SCTP stream. The sixth identification information is used to identify the type of message transmitted through the SCTP connection (the SCTP connection identified by the first identification information) or the SCTP stream (the SCTP stream identified by the third identification information), and the seventh identification information is used to identify at least one message belonging to the same process transmitted through the SCTP connection or SCTP stream. The terminal identification information is used to identify the terminal that sends the first information to the network and / or to identify the terminal associated with the first information. For example, the terminal identification information may be the UE ID of the NG interface assigned by the RAN (RAN NG UE ID), or the UE ID of the NG interface assigned by the AMF (AMF NG UE ID). The identification information of the path corresponding to the SCTP connection or SCTP stream is used to identify the path for transmitting the first message (i.e., the path carrying the SCTP connection identified by the first identification information or the SCTP stream identified by the third identification information).

[0222] Scenario 3: The first protocol is TCP, and the second protocol is QUIC. It's understood that Scenario 3 pertains to the control plane and / or user plane. For example, the first protocol is a control plane protocol, and the first information is control plane data / signaling; or, the first protocol is a user plane protocol, and the first information is user plane data / signaling.

[0223] In scenario three, the first communication device supports the TCP protocol. The third communication device supports both the TCP and QUIC protocols. The second communication device supports the QUIC protocol.

[0224] In Scenario 3, one or more TCP connections are established between the first and third communication devices. One or more QUIC connections are established between the third and second communication devices. Optionally, a QUIC connection may include one or more QUIC streams.

[0225] Optionally, the first, second, or third communication device may also support other protocols. For example, the second communication device may also support the TCP protocol.

[0226] Optionally, the first communication device may or may not support the QUIC protocol. If the first communication device supports both the QUIC and TCP protocols, it will choose to transmit the first information via the TCP protocol.

[0227] In Scenario 3, the first message includes an eighth identification information, which identifies a TCP connection between the first and third communication devices for transmitting the first message. For example, the eighth identification information can be a TCP ID. This eighth identification information can be an IP 5-tuple (including the following information: source IP address, destination IP address, source port number, destination port number, and protocol type).

[0228] In scenario three, the second message includes second identification information, which identifies a QUIC connection between the third communication device and the second communication device for transmitting the second message. For example, the second identification information can be a QUIC CID.

[0229] There is a mapping relationship between the eighth identification information and the second identification information. After receiving the first message, the third communication device can determine the second identification information corresponding to the eighth identification information based on the eighth identification information and the mapping relationship, and then carry the second identification information in the second message and transmit the second message through the QUIC connection identified by the second identification information.

[0230] This application does not limit the specific implementation of the third communication device obtaining the mapping relationship between the eighth identification information and the second identification information. In one possible implementation, the third communication device can obtain configuration information (which may be called third configuration information) used to configure the mapping relationship, and the third configuration information includes the second identification information and the eighth identification information.

[0231] Optionally, the third configuration information may include the eighth identification information, the second identification information, and at least one of the following: identification information of the QUIC stream included in the QUIC connection identified by the second identification information, identification information of the path corresponding to the QUIC connection or QUIC stream, the ninth identification information, or the tenth identification information. The ninth identification information is used to identify the type of message transmitted through a TCP connection (the SCTP connection identified by the eighth identification information), a QUIC connection, or a QUIC stream, and the tenth identification information is used to identify at least one message belonging to the same process transmitted through a TCP connection, a QUIC connection, or a QUIC stream. For details on the third configuration information, please refer to the above description of the configuration information used to configure the mapping relationship between TCP connections and QUIC connections.

[0232] In Scenario 3, after receiving the first message, the third communication device can determine the QUIC connection (i.e., the QUIC connection identified by the second identification information) for transmitting the second message based on the mapping relationship configured by the eighth identification information and the third configuration information. Optionally, it can also determine the QUIC stream for transmitting the second message (the QUIC stream belongs to the QUIC connection identified by the second identification information, and the identification information of the QUIC stream corresponds to the eighth identification information). Optionally, it can also determine the path for transmitting the second message (the identification information of the path corresponds to the identification information of the QUIC connection or the QUIC stream).

[0233] Optionally, if the third configuration information does not include the identification information of the QUIC stream corresponding to the eighth identification information, the third communication device may select any QUIC stream from the QUIC streams included in the QUIC connection identified by the second identification information to transmit the second message. If the second configuration information does not include the identification information of the path corresponding to the QUIC connection or QUIC stream used to transmit the second message, the third communication device may select any path to transmit the second message.

[0234] Optionally, the second message may also include identification information of the QUIC stream used to transmit the second message, and / or identification information of the path used to transmit the second message.

[0235] Optionally, in scenario three, the first information may include at least one of the following: eleventh identification information, twelfth identification information, terminal identification information, first identification information, eighth identification information, priority information, or identification information of the path corresponding to the TCP connection. The eleventh identification information is used to identify the type of message transmitted through the TCP connection (the TCP connection identified by the eighth identification information), and the twelfth identification information is used to identify at least one message belonging to the same process transmitted through the TCP connection (the TCP connection identified by the eighth identification information). The identification information of the path corresponding to the TCP connection is used to identify the path for transmitting the first message (i.e., the path used to carry the SCTP connection identified by the eighth identification information).

[0236] Scenario 4: Both the first and second protocols are QUIC protocols.

[0237] In Scenario 4, the first communication device, the third communication device, and the second communication device all support the QUIC protocol.

[0238] In Scenario 4, one or more QUIC connections are established between the first communication device and the third communication device, and one or more QUIC connections are established between the third communication device and the second communication device. Optionally, a QUIC connection may include one or more QUIC streams.

[0239] Optionally, the first, second, or third communication device may also support other protocols. For example, the first, second, or third communication device may also support the GTP-U protocol or the SCTP protocol.

[0240] For example, Figure 10 is a possible protocol stack diagram for scenario four. In Figure 10, when used for the user plane, the first communication device is a RAN node supporting the QUIC protocol. The third communication device is a core network element (Figure 10 uses a UPF as an example) or a RAN node supporting the QUIC protocol, connected to the first communication device. The second communication device is a network element in the data network (DN) supporting the QUIC protocol or a processing service function (PSF) in the core network supporting the QUIC protocol, connected to the third communication device. In addition, the first communication device also supports the Service Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP), Radio Link Control (RLC) layer protocol, Media Access Control (MAC) layer protocol, and Physical (PHY) layer protocol.

[0241] In Figure 10, if used for control plane signaling transmission, the first communication device is a RAN node supporting the QUIC protocol. The third communication device is a core network control plane element (in Figure 10, the control plane element, such as AMF, replaces UPF) or a RAN node supporting the QUIC protocol, connected to the first communication device, such as through a RAN-CN interface (e.g., NG interface) or through an inter-RAN interface (e.g., Xn interface). Other protocol layers may be deployed above the QUIC layer, such as application protocols on the RAN-CN interface (e.g., NG interface) or inter-RAN interface (e.g., Xn interface). The second communication device is an application function (AF) network element supporting the QUIC protocol or a control plane network element in the core network supporting the QUIC protocol. It connects to the third communication device. Other protocol layers may be deployed above the QUIC layer, such as HTTP / 3-based application protocols, service-based interface (SBI) application protocols, enhanced service-based interface (eSBI) application protocols, or beyond service-based interface (bSBI) application protocols. Additionally, the first communication device also supports the RRC protocol (in Figure 10, the RRC protocol replaces the SDAP protocol), PDCP, RLC layer protocols, MAC layer protocols, and PHY layer protocols. In this case, the PDU protocol layer is not deployed in the first and third communication devices in Figure 10. The specific protocol stack shown in Figure 10 can be found in existing protocols and will not be elaborated upon here.

[0242] In Scenario 4, the first message includes first identification information, which identifies the QUIC connection between the first communication device and the third communication device for transmitting the first message. Optionally, the first message may also include third identification information, which identifies a QUIC stream belonging to the QUIC connection identified by the first identification information and is the QUIC stream between the first communication device and the third communication device for transmitting the first message.

[0243] In Scenario 4, the second message includes second identification information, which is used to identify the QUIC connection between the third communication device and the second communication device for transmitting the second message. For example, the second identification information can be a QUIC CID. Optionally, the second message may also include identification information for identifying the QUIC stream between the third communication device and the second communication device for transmitting the second message.

[0244] There is a mapping relationship between the first identification information and / or the third identification information and the second identification information. After receiving the first message, the third communication device can determine the second identification information corresponding to the first identification information and / or the third identification information based on the first identification information and / or the third identification information and the mapping relationship, and then carry the second identification information in the second message and transmit the second message through the QUIC connection identified by the second identification information.

[0245] This application embodiment does not limit the specific implementation of the mapping relationship between the third communication device obtaining the first identification information and / or the third identification information and the second identification information. In one possible implementation, the third communication device can obtain configuration information for configuring the mapping relationship, which includes the second identification information and at least one of the following: the first identification information or the third identification information. Optionally, the configuration information may further include at least one of the following: identification information of the QUIC stream included in the QUIC connection identified by the second identification information; identification information of the path corresponding to the QUIC connection or QUIC stream (the QUIC connection identified by the second identification information or the QUIC stream included in the QUIC connection); information for identifying the type of message transmitted through the QUIC connection (the QUIC connection identified by the first identification information or the QUIC connection identified by the second identification information) or the QUIC stream (the QUIC stream identified by the third identification information, or the QUIC stream included in the QUIC connection identified by the second identification information); and information for identifying at least one message belonging to the same process transmitted through the QUIC connection (the QUIC connection identified by the first identification information or the QUIC connection identified by the second identification information) or the QUIC stream (the QUIC stream identified by the third identification information, or the QUIC stream included in the QUIC connection identified by the second identification information). For details on this configuration information, please refer to the above description of the configuration information used to configure the mapping relationship between SCTP connections / SCTP streams and QUIC connections.

[0246] In Scenario 4, after receiving the first message, the third communication device can determine the QUIC connection (i.e., the QUIC connection identified by the second identification information) for transmitting the second message based on the first identification information and / or the third identification information, as well as the mapping relationship. Optionally, it can also determine the QUIC stream for transmitting the second message (the QUIC stream belongs to the QUIC connection identified by the second identification information, and the identification information of the QUIC stream corresponds to the first identification information and / or the third identification information). Optionally, it can also determine the path for carrying the QUIC connection or QUIC stream (the identification information of the path corresponds to the identification information of the QUIC connection or QUIC stream used for transmitting the second message).

[0247] Optionally, if the configuration information used to configure the mapping relationship does not include the identification information of the QUIC stream corresponding to the first identification information and / or the third identification information, the third communication device may select any QUIC stream from the QUIC streams included in the QUIC connection identified by the second identification information to transmit the second message. If the second configuration information does not include the identification information of the path corresponding to the QUIC connection or QUIC stream used to transmit the second message, the third communication device may select any path to transmit the second message.

[0248] Optionally, the second message may also include identification information of the QUIC stream used to transmit the second message, and / or identification information of the path used to transmit the second message.

[0249] Optionally, in scenario four, the first information may include at least one of the following: terminal identification information, first identification information, third identification information, priority information, identification information of the path corresponding to the QUIC connection or QUIC stream, used to identify the type of message transmitted through the QUIC connection (the QUIC connection identified by the first identification information) or the QUIC stream (the SCTP stream identified by the third identification information), and used to identify at least one message belonging to the same process transmitted through the QUIC connection (the QUIC connection identified by the first identification information) or the QUIC stream (the SCTP stream identified by the third identification information). The terminal identification information is used to identify the terminal sending the first information to the network and / or to identify the terminal associated with the first information. For example, the terminal identification information may be the UE ID of the NG interface assigned by the RAN (RAN NG UE ID), or the UE ID of the NG interface assigned by the AMF (AMF NG UE ID). The identification information of the path corresponding to the QUIC connection or QUIC stream is used to identify the path for transmitting the first message (i.e., the path carrying the QUIC connection identified by the first identification information or the QUIC stream identified by the third identification information).

[0250] Scenario 5: The first protocol is an RRC layer protocol, SDAP protocol, PDCP protocol, RLC layer protocol, MAC layer protocol, PHY layer protocol, or non-access stratum (NAS) layer protocol. The second protocol is the QUIC protocol.

[0251] In Scenario 5, the first communication device supports the first protocol, the third communication device supports both the first protocol and the QUIC protocol, and the second communication device supports the QUIC protocol.

[0252] In Scenario 5, one or more QUIC connections are established between the third communication device and the second communication device. Optionally, a QUIC connection may include one or more QUIC streams.

[0253] Optionally, the first, second, or third communication device may also support other protocols. For example, the second communication device may also support the GTP-U protocol, the SCTP protocol, or the TCP protocol.

[0254] Optionally, the second communication device may also support other protocols, such as other protocols above the QUIC protocol layer, such as application protocols on RAN-CN interfaces (e.g., NG interfaces), application protocols on inter-RAN interfaces (e.g., Xn interfaces), HTTP / 3-based application protocols, service-based interface (SBI) application protocols, or enhanced service-based interface (eSBI) application protocols, or beyond service-based interface (bSBI) application protocols.

[0255] Optionally, the third communication device may also support other protocols, such as other protocols above the QUIC protocol layer, such as application protocols on RAN-CN interfaces (e.g., NG interfaces), application protocols on inter-RAN interfaces (e.g., Xn interfaces), HTTP / 3-based application protocols, service-based interface (SBI) application protocols, enhanced service-based interface (eSBI) application protocols, or beyond service-based interface (bSBI) application protocols.

[0256] For example, Figure 11 is a possible protocol stack diagram for Scenario 5. In Figure 11, the first communication device is a UE that supports NAS, RRC, PDCP, RLC, MAC, or PHY protocols. The third communication device is a RAN node that supports the QUIC protocol and is connected to the first communication device. The second communication device is a core network element that supports the QUIC protocol (Figure 11 uses AMF as an example) and is connected to the third communication device. The specific protocol stack shown in Figure 11 can refer to existing protocols and will not be elaborated here.

[0257] In Scenario 5, after receiving the first message, the third communication device can determine the second identification information based on the first message, and then carry the second identification information in the second message, and transmit the second message through the QUIC connection identified by the second identification information.

[0258] In Scenario 5, optionally, the third communication device can obtain configuration information. This configuration information is used to configure the mapping relationship between at least one of a radio bearer (RB), a session, or a QoS stream, and a QUIC connection or QUIC stream. The configuration information includes at least one of the following: radio bearer identification information, session identification, QoS stream identification information, QUIC connection identification information, and / or QUIC stream identification information. Based on this mapping relationship, the third device can determine at least one of the following corresponding to the data / signaling transmitted through the QUIC connection or QUIC stream: radio bearer, session, or QoS stream. In Scenario 5, optionally, the first message includes a session identification and / or a QoS stream identification. For example, the SDAP protocol message includes a session identification and / or a QoS stream identification.

[0259] In Scenario 5, optionally, the third communication device can obtain configuration information. This configuration information is used to configure the mapping relationship between a terminal, message type, radio signaling bearer, or at least one of the at least one messages, and a QUIC connection or QUIC stream. The configuration information includes terminal identification information, message type identification information, radio signaling bearer identification information, at least one of the at least one message identification information, QUIC connection identification information, and / or QUIC stream identification information. The terminal identification information is used to identify the terminal sending the first information to the network and / or to identify the terminal associated with the first information. The message type identification information is used to identify the message type corresponding to the first message. The radio signaling bearer identification information is used to identify the radio signaling bearer corresponding to the first message. The number of at least one message identification information can be one or more, where one identification information is used to identify at least one message belonging to the same process. The at least one message identification information can correspond to at least one of the at least one QUIC connection identification information or at least one QUIC stream identification information, indicating that the at least one message belonging to the same process identified by that identification information can be transmitted through the corresponding at least one QUIC connection or at least one QUIC stream. For example, the identification information of at least one message can be a transaction ID, used to associate related messages belonging to the same process. The third communication device can determine, based on this mapping relationship, the data / signaling transmitted via a QUIC connection or QUIC stream that is related to at least one of the following: terminal, message type, radio signaling bearer, and at least one message. For example, the first message of the RRC protocol may contain at least one of the above-mentioned pieces of information.

[0260] Optionally, S501-S502 can also be applied to scenarios where the first protocol is QUIC and the second protocol is another protocol, such as GTP-U, SCTP, TCP, RRC layer protocol, SDAP, PDCP, RLC layer protocol, MAC layer protocol, PHY layer protocol, or NAS layer protocol. In scenarios where the first protocol is QUIC and the second protocol is another protocol, the first communication device supports QUIC, the third communication device supports other protocols and QUIC, and the second communication device supports other protocols. For details, please refer to the above introduction to scenarios where the first protocol is another protocol and the second protocol is QUIC.

[0261] Optionally, in various scenarios of this application embodiment, the third communication device may also receive information from the second communication device and send that information to the first communication device. For details, please refer to the above description of the third communication device receiving first information from the first communication device and sending the first information to the second communication device.

[0262] Optionally, in this embodiment, the communication device can obtain fourth configuration information. This fourth configuration information is used to configure the mapping relationship between a radio bearer (RB) and a QUIC connection or QUIC stream. The fourth configuration information includes the identification information of the radio bearer and the identification information of the QUIC connection. The communication device can determine the radio bearer corresponding to the data / signaling transmitted through the QUIC connection or QUIC stream based on this mapping relationship.

[0263] For example, the identification information of a radio bearer can be the identification information (SRB ID) of a signaling radio bearer (SRB), the identification information (DRB ID) of a data radio bearer (DRB), or the identification information (XRB ID) of a radio bearer used to carry data beyond connectivity service X (such as sensing service, AI service, data twin service, etc.).

[0264] Optionally, the fourth configuration information may include the identification information of the radio bearer, the identification information of the QUIC connection, and the identification information of the QUIC streams included in the QUIC connection, used to configure the mapping relationship between the radio bearer and the QUIC connection, and the mapping relationship between the radio bearer and the QUIC streams included in the QUIC connection. For details on the fourth configuration information, please refer to the above description of the configuration information (e.g., the first configuration information) used to configure the mapping relationship related to the QUIC connection / QUIC streams.

[0265] Optionally, in this embodiment, the communication device (e.g., a first communication device, a second communication device, or a third communication device) can obtain fifth configuration information. This fifth configuration information includes identification information for at least one QUIC connection and identification information for at least one path supporting each QUIC connection. After determining a QUIC connection, the communication device can select the actual path to carry the QUIC connection from among the paths supporting that connection, based on the fifth configuration information. Alternatively, when the communication device wants to switch the path carrying the QUIC connection, it can select the path to switch to from among the paths supporting that connection, based on the fifth configuration information.

[0266] Optionally, the fifth configuration information may further include at least one of the following: for each QUIC connection in at least one QUIC connection, the priority information (Link priority) of the path supporting the QUIC connection, and the identification information (default link ID) of the default path supporting the QUIC connection. The priority information of the path supporting the QUIC connection indicates the priority of the selected path; for example, the priority information is a priority value, where a higher priority value indicates a higher priority for the selected path, or vice versa. The identification information of the default path supporting the QUIC connection identifies the path selected by default for the QUIC connection.

[0267] Optionally, the fifth configuration information can also be called a link selection rule. That is, the fifth configuration information can configure link selection rules at the QUIC connection granularity.

[0268] Optionally, the fifth configuration information may further include at least one of the following: identification information of at least one session (Session ID), identification information of at least one QoS stream (QFI) included in at least one session, identification information of at least one GTP-U tunnel (GTP-UTEID), identification information of at least one message type, identification information of at least one message, identification information of at least one SCTP connection (SCTP ID), identification information of at least one SCTP stream (SCTP stream ID) included in at least one SCTP connection, identification information of at least one TCP connection, identification information of at least one QUIC stream (QUIC Stream ID) included in at least one QUIC connection, or other identification information (e.g., identification information of a transport channel using other protocols), and identification information corresponding to the above at least one identification information, supporting at least one path of the session / QoS stream / GTP-U tunnel / message type / message / SCTP connection / SCTP stream / TCP connection / QUIC stream / transport channel using other protocols that carries the identification information. Optionally, the fifth configuration information may further include priority information corresponding to at least one of the aforementioned identification information, supporting the path carrying the session / QoS stream / GTP-U tunnel / message type / message / SCTP connection / SCTP stream / TCP connection / QUIC stream / transmission channel using other protocols identified by that identification information, and / or, the default identification information of the path carrying the session / QoS stream / GTP-U tunnel / message type / message / SCTP connection / SCTP stream / TCP connection / QUIC stream / transmission channel using other protocols identified by that identification information. In other words, the fifth configuration information may also configure path selection rules at the granularity of session / QoS stream / GTP-U tunnel / message type / message / SCTP connection / SCTP stream / TCP connection / QUIC stream / transmission channel using other protocols.

[0269] In scenarios where the first and second protocols differ, after receiving the first message, the third communication device can perform message conversion and encapsulation between different protocols to obtain the second message. In other words, the third communication device can convert and encapsulate messages using other protocols (hereinafter referred to as other protocol messages, such as GTP-U messages, SCTP messages, or TCP messages) into messages using the QUIC protocol (hereinafter referred to as QUIC messages), or convert and encapsulate QUIC messages into messages using other protocols.

[0270] Taking the conversion and encapsulation of other protocol messages into QUIC messages by a third communication device as an example, one possible implementation is that the third communication device can encapsulate the information in the packet header of the other protocol message into the header of the QUIC message, delete the header of the other protocol message, and encapsulate the information in the payload of the other protocol message into the payload of the QUIC message. Another possible implementation is that the third communication device can encapsulate the other protocol message within a QUIC protocol message. For example, the third communication device may not delete the header of the other protocol message and directly encapsulate the other protocol message (header + payload) into the payload of the QUIC message. For the specific implementation of the third communication device converting QUIC messages into other protocol messages, please refer to the implementation of the conversion and encapsulation of other protocol messages into QUIC messages by a third communication device.

[0271] Optionally, when the third communication device converts and encapsulates other protocol messages into QUIC messages, the third communication device can parse the other protocol messages to obtain information such as the first identification information, the third identification information, or the eighth identification information, and determine the second identification information according to the mapping relationship. Alternatively, when the third communication device converts and encapsulates other protocol messages into QUIC messages, it can choose not to parse the other protocol messages, but directly encapsulate the other protocol messages in the payload of the QUIC protocol message. Optionally, the implementation of the third communication device not parsing other protocol messages can be applied to scenarios where the communication device sending other protocol messages (e.g., the first or second communication device) does not need to interface with the third communication device on transport layer protocols (e.g., GTP-U, SCTP, or TCP). Optionally, in this scenario, the third communication device and the communication device sending other protocol messages can interface on the IP layer. For example, the IP layer can be based on segment routing IPv6 (SRv6) of the IPv6 forwarding plane.

[0272] Optionally, in this scenario, the third communication device can obtain configuration information used to configure at least one of the following for the message: source IP address / port number, destination IP address / port number, and the mapping relationship between these and the QUIC connection / QUIC stream. For example, after receiving other protocol messages, the third communication device can determine the QUIC connection or QUIC stream used to transmit the QUIC message based on the source IP address / port number, destination IP address / port number, and the mapping relationship of the other protocol message.

[0273] Optionally, in this scenario, the communication device sending other protocol messages can obtain at least one of the following information: the peer's TEID, the peer's port number, or the IP address of the third communication device. The other protocol messages sent by the communication device can carry the peer's TEID and / or port number. The communication device can send messages to the third communication device based on the third communication device's IP address. Here, the peer can also be understood as the destination network element of the message; for example, the peer of a RAN node is the core network element it faces, and the peer of a core network element is the RAN node.

[0274] For example, Figure 12 is a schematic diagram of a possible protocol stack. As shown in Figure 12, the RAN node supports the GTP-U protocol but not the QUIC protocol. The RAN GW and CN GW support the QUIC protocol. The core network elements support the GTP-U protocol but not the QUIC protocol. The RAN GW connected to the RAN node does not interface with the RAN node's transport layer protocol but instead interfaces with the IP layer. If the RAN GW receives a packet from the RAN node, and the destination network element of the packet is a core network element, the RAN GW can directly encapsulate the packet in a QUIC packet payload and send it to the CN GW, which then forwards it to the core network element. The CN GW connected to the core network element does not interface with the core network element's transport layer protocol but instead interfaces with the IP layer. If the CN GW receives a packet from the core network element, and the destination network element of the packet is the RAN node, the CN GW can directly encapsulate the packet in a QUIC packet payload and send it to the RAN GW, which then forwards it to the RAN node.

[0275] Based on this scheme, communication devices do not need to parse transport layer messages (such as GTP-U messages and SCTP messages). They can directly act as relays to forward transport layer messages as the payload of QUIC messages, reducing complexity.

[0276] Optionally, if the first communication device and / or the second communication device also support different protocols, the first communication device and / or the second communication device can also perform message conversion and encapsulation between different protocols. For details, please refer to the above introduction on message conversion and encapsulation between different protocols by the third communication device.

[0277] Based on the communication method provided in the embodiments of this application, the communication device can convert the original message using other protocols into a QUIC message, and can support the continued carrying of the information carried in the original message in the QUIC message, thus preventing the loss of necessary information.

[0278] This application does not limit the specific structure of messages using the QUIC protocol (hereinafter referred to as QUIC messages). Figure 13 is a schematic diagram of an exemplary QUIC message structure. As shown in Figure 13, the QUIC header includes a destination QUIC connection ID (DCID), and optionally, a source QUIC connection ID (SCID). The QUIC message payload includes a QUIC stream ID. For the meaning and purpose of each field in the QUIC message, please refer to IETF RFC documents 8999, 9000, etc.

[0279] Optionally, the length of the DCID or SCID in the QUIC message can be between 0 and 255 bytes. For example, the structure of the DCID or SCID can be:

[0280] Optionally, the QUIC Stream ID in a QUIC message can be 62 bits long. If a QUIC connection includes multiple QUIC streams, the Stream ID values ​​for different QUIC streams will be different. For example, the structure of a QUIC Stream ID can be:

[0281] Optionally, in scenario one and / or scenario four, when the third communication device converts and encapsulates the first message into a second message, the first information can be encapsulated in the thirteenth identification information in the header of the second message, where the thirteenth identification information is SCID or DCID.

[0282] For example, the SCID or DCID in the header of the second message may include the following information:

[0283] Optionally, in Scenario 1 and / or Scenario 4, when the third communication device converts and encapsulates the first message into a second message, the first information can be encapsulated in the QUIC stream identification information (Steam ID) included in the payload of the second message. For example, the Steam ID in the payload of the second message may include the following information:

[0284] Optionally, in Scenario 1 and / or Scenario 4, when the third communication device converts and encapsulates the first message into a second message, some information from the first message can be encapsulated in the thirteenth identification information in the header of the second message, and other information can be encapsulated in the identification information of the QUIC stream included in the payload of the second message. For example, the SCID or DCID in the header of the second message may include the following information:

[0285] The Steam ID in the payload of the second message can include the following information:

[0286] Optionally, in scenarios two, three, or five, when the third communication device converts and encapsulates the first message into a second message, the first information can be encapsulated in the thirteenth identification information in the header of the second message. For example, the SCID or DCID in the header of the second message may include the following information:

[0287] Optionally, in this embodiment of the application, where the first protocol is the QUIC protocol (i.e., the first communication device supports the QUIC protocol) and the second communication device does not support the QUIC protocol, the first communication device can be used to execute a new type of service. This new service can be a service in a future communication network, such as an AI service, an XR service, a data service, or an ISAC service. For example, the first communication device can be a new service processing node (XaaS processing service function, PSF). The first communication device can be used to execute tasks related to at least one of the following services: AI service, XR service, data service, or ISAC service. Optionally, in this scenario, the first and second communication devices can be user plane core network elements; for example, the second communication device can be a UPF network element.

[0288] Optionally, in a scenario where the first protocol is the QUIC protocol and the second communication device does not support the QUIC protocol, the first communication device can be used to manage a fourth communication device, which can then be used to execute new services. For example, the fourth communication device can be a PSF (Programmable Serving Function), and the first communication device can be a New Service Task Control Function (TCF) for managing the PSF. The fourth communication device can be used to execute tasks related to at least one of the following services: AI service, XR service, data service, or ISAC service. Optionally, in this scenario, the first and second communication devices can be control plane core network elements; for example, the second communication device can be an SMF (Small and Medium Functions) or AMF (Ampere and Multiple Functions) element.

[0289] Optionally, in this embodiment of the application, where the second protocol is the QUIC protocol (i.e., the second communication device supports the QUIC protocol) and the first communication device does not support the QUIC protocol, the second communication device can be used to execute new services. For example, the second communication device can be used to execute tasks related to at least one of the following services: AI services, XR services, data services, or ISAC services. For details, please refer to the above description of the first communication device being used to execute new services. Optionally, in this scenario, both the first and second communication devices can be user plane core network elements; for example, the first communication device can be a UPF network element.

[0290] Optionally, in scenarios where the second protocol is the QUIC protocol and the first communication device does not support the QUIC protocol, the second communication device can be used to manage the fourth communication device, and the fourth communication device can be used to execute new services. For example, the fourth communication device can be used to perform tasks related to at least one of the following services: AI service, XR service, data service, or ISAC service. For details, please refer to the above description of the first communication device managing the fourth communication device and the fourth communication device executing new services. Optionally, in this scenario, the first and second communication devices can be control plane core network elements; for example, the first communication device can be an SMF or AMF network element.

[0291] For example, Figure 14 is a schematic diagram of a possible scenario. As shown in Figure 14, the traditional user plane network element (Figure 14 uses UPF as an example) does not support the QUIC protocol but supports the GTP-U protocol. The GW supports both the GTP-U and QUIC protocols. The XaaS PSF network element is used to execute tasks related to new services and supports the QUIC protocol. The GW can act as an intermediate node, deployed between the traditional user plane network element and the XaaS PSF network element node.

[0292] For example, Figure 15 illustrates another possible scenario. As shown in Figure 15, traditional control plane network elements (using SMF as an example) do not support the QUIC protocol but support the SCTP / TCP protocol. The GW supports both SCTP / TCP and QUIC protocols. The XaaS TCF network element is used to control and configure new service processing nodes and supports the QUIC protocol. The GW can act as an intermediate node, deployed between the traditional control plane network elements and the XaaS TCF network elements.

[0293] Furthermore, this application embodiment does not limit the specific implementation of the communication device (e.g., the first communication device, the second communication device, or the third communication device) obtaining the configuration information used to configure the mapping relationship as described in the above embodiments. In one possible implementation, the network node can configure the configuration information used to configure the mapping relationship, such as tunnel mapping rules and link selection rules, to the communication device when the control plane connection / user plane session is established (e.g., when the UE PDU session is established, when the UE context is established, or when the N2 interface is established).

[0294] Optionally, the network node that configures the configuration information for the communication equipment can be a GW, RAN node, or core network element (e.g., a control plane network element).

[0295] For example, Figure 16 illustrates a possible flow of a control plane network element configuring tunnel mapping rules and path selection rules for a communication device supporting the QUIC protocol. As shown in Figure 16, the control plane network element sends a session establishment request or a UE context setting request to the communication device, the request message carrying the tunnel mapping rules and path selection rules.

[0296] In addition, this application embodiment also provides a communication method, which includes: a first communication device sending first information to a second communication device via the QUIC protocol; and correspondingly, the second communication device receiving the first information. In this communication method, the second communication device does not need to send the first information to another communication device.

[0297] The first information can be carried in the first message. For details on this communication method, please refer to the above description of scenario four, where the first communication device sends the first information to the second communication device. Further details will not be elaborated here. For example, referring to the scenario shown in Figure 11, the first communication device can be a RAN node supporting the QUIC protocol, and the second communication device can be a core network element supporting the QUIC protocol.

[0298] The first or second communication device can be a GW, RAN node, terminal, core network element, or bearer network node. If this embodiment is applied to a future network, the first or second communication device can be a new network element.

[0299] The first communication device executing the communication method can also be a module applied to the first communication device, such as a chip, chip system, or processor, or a logical node, logical module, or software capable of implementing all or part of the functions of the first communication device. The second communication device can also be a module applied to the second communication device, such as a chip, chip system, or processor, or a logical node, logical module, or software capable of implementing all or part of the functions of the second communication device. Furthermore, the processing performed by a single executing entity can be divided among multiple executing entities, which can be logically and / or physically separated. For example, if the first, second, or third communication device is a RAN node, the processing performed by the first, second, or third communication device can be divided among at least one of CU, DU, RU, etc.

[0300] The above mainly describes the solutions provided by the embodiments of this application from the perspective of interaction between various devices. Correspondingly, the embodiments of this application also provide a communication device for implementing the various methods described above. This communication device can be a first communication device in the above method embodiments, or a device containing the first communication device, or a component usable in the first communication device; or, this communication device can be a second communication device in the above method embodiments, or a device containing the second communication device, or a component usable in the second communication device. It is understood that, in order to achieve the above functions, the communication device includes hardware structures and / or software modules corresponding to the execution of each function. Those skilled in the art should readily recognize that, in conjunction with the units and algorithm steps of the various examples described in the embodiments disclosed herein, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed by hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0301] This application embodiment can divide the communication device into functional modules according to the above method embodiment. For example, each function can be divided into a separate functional module, or two or more functions can be integrated into one processing module. The integrated module can be implemented in hardware or as a software functional module. It should be understood that the module division in this application embodiment is illustrative and is only a logical functional division. In actual implementation, there may be other division methods.

[0302] Figure 17 shows a schematic diagram of a communication device 1700. The communication device 1700 includes a transceiver module 1702 and a processing module 1701. Optionally, the communication device 1700 may also include a storage module 1703. The transceiver module 1702, also referred to as a transceiver unit, is used to implement transceiver functions; for example, it may be a transceiver circuit, transceiver, transceiver adapter, or communication interface.

[0303] The communication device 1700 can be the first communication device in the above embodiments, or it can be a chip in the first communication device. Alternatively, the communication device can be the second communication device in the above embodiments, or it can be a chip in the second communication device. Alternatively, the communication device can be the third communication device in the above embodiments, or it can be a chip in the third communication device. The communication device 1700 can be used to implement the communication method of any of the above embodiments.

[0304] For example, the transceiver module 1702 is used to support the communication device 1700 in sending and receiving information, or to communicate with other devices. The processing module 1701 is used to control and manage the operation of the communication device 1700, and to execute the processing performed by the communication device 1700 in the above embodiments. Optionally, if the communication device 1700 includes a storage module 1703, the processing module 1701 can also execute programs or instructions stored in the memory, so that the communication device 1700 implements the methods and functions involved in any of the above embodiments.

[0305] For example, if the communication device 1700 is the first communication device in the above embodiments, the transceiver module 1702 can be used to execute, for example, step S501 in FIG5, and / or other processes of the technology described herein. The processing module 1701 can be used for other processes of the technology described herein. All relevant content of each step involved in the above method embodiments can be referenced to the functional description of the corresponding functional module, and will not be repeated here.

[0306] For example, if the communication device 1700 is the second communication device in the above embodiments, the transceiver module 1702 can be used to execute, for example, step S502 in FIG5, and the processing module 1701 can be used for other processes of the technology described herein. All relevant content of each step involved in the above method embodiments can be referenced to the functional description of the corresponding functional module, and will not be repeated here.

[0307] For example, if the communication device 1700 is the third communication device in the above embodiments, the transceiver module 1702 can be used to execute steps S501 and S502 in FIG5, and the processing module 1701 can be used for other processes of the technology described herein. All relevant content of each step involved in the above method embodiments can be referenced to the functional description of the corresponding functional module, and will not be repeated here.

[0308] For example, in hardware implementation, the functions of processing module 1701 can be executed by a processor, and the functions of transceiver module 1702 can be executed by a transceiver (transmitter / receiver) and / or communication interface. Processing module 1701 can be embedded in or independent of the processor of communication device 1700 in hardware form, or it can be stored in the memory of communication device 1700 in software form, so that the processor can call and execute the operations corresponding to the above functional units.

[0309] Alternatively, the modules in Figure 17 can also be called units. For example, a processing module can be called a processing unit, and a transceiver module can be called a transceiver unit. Furthermore, in the embodiment shown in Figure 17, the names of the units may not be those shown in the figure; for example, a transceiver module can also be called a communication module or a communication unit.

[0310] If the units in Figure 17 are implemented as software functional modules and sold or used as independent products, they can be stored in a computer-readable storage medium. This computer software product, stored in a storage medium, includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) or processor to execute all or part of the steps of the methods described in the various embodiments of this application. Storage media for storing computer software products include various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0311] In this embodiment, the communication device 1700 is presented in an integrated manner, divided into various functional modules. Here, "module" can refer to a specific ASIC, circuitry, a processor and memory executing one or more software or firmware programs, integrated logic circuitry, and / or other devices that can provide the aforementioned functions. In a simplified embodiment, those skilled in the art will recognize that the communication device 1700 can take the form of the communication device shown in FIG18.

[0312] As shown in Figure 18, the communication device 1800 includes one or more processors 1801 (Figure 18 is merely an example illustrating the inclusion of one processor 1801). The processor 1801 can be used to execute instructions, causing the communication device 1800 to implement the methods described in the above-described method embodiments. The processor 1801 can be a general-purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits used to control the execution of the program according to this application.

[0313] Optionally, the communication device 1800 may also include a communication line 1802. The communication line 1802 may include a path for connecting different components.

[0314] Optionally, the communication device 1800 may further include at least one communication interface (Figure 18 is merely exemplary, including communication interface 1804, and is described using this as an example). Communication interface 1804 may be a transceiver module for communicating with other devices or communication networks, such as Ethernet, RAN, terminals, wireless local area networks (WLANs), etc. For example, the transceiver module may be a transceiver or similar device. Optionally, the communication interface 1804 may also be a transceiver circuit or input / output interface located within the processor 1801, used to implement signal input and signal output for the processor.

[0315] Optionally, the communication device 1800 may also include a memory 1803. The memory 1803 may be a device with storage functionality. For example, it may be a read-only memory (ROM) or other type of static storage device capable of storing static information and instructions, random access memory (RAM) or other type of dynamic storage device capable of storing information and instructions, or it may be an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compressed optical discs, laser discs, optical discs, digital universal optical discs, Blu-ray discs, etc.), magnetic disk storage media, or other magnetic storage devices, or any other medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible by a computer, but not limited thereto. The memory may exist independently and be connected to the processor via the communication line 1802. The memory may also be integrated with the processor.

[0316] The memory 1803 stores computer execution instructions for implementing the scheme of this application, and its execution is controlled by the processor 1801. The processor 1801 executes the computer execution instructions stored in the memory 1803, thereby implementing the communication method provided in the embodiments of this application.

[0317] Alternatively, in this embodiment, the processor 1801 may execute the processing-related functions in the communication method provided in this embodiment, and the communication interface 1804 may be responsible for communicating with other devices or communication networks. This embodiment does not specifically limit this.

[0318] Optionally, the computer execution instructions in the embodiments of this application may also be referred to as application code, and the embodiments of this application do not specifically limit this.

[0319] In a specific implementation, as one example, processor 1801 may include one or more CPUs, such as CPU0 and CPU1 in FIG18.

[0320] In a specific implementation, as one embodiment, the communication device 1800 may include multiple processors, such as processors 1801 and 1807 in FIG. 18. Each of these processors may be a single-core processor or a multi-core processor. The processors here may include, but are not limited to, at least one of the following: a central processing unit (CPU), a microprocessor, a digital signal processor (DSP), a microcontroller unit (MCU), or an artificial intelligence processor, etc., and various computing devices that run software. Each computing device may include one or more cores for executing software instructions to perform calculations or processing.

[0321] In a specific implementation, as one embodiment, the communication device 1800 may further include an output device 1805 and an input device 1806. The output device 1805 communicates with the processor 1801 and can display information in various ways. For example, the output device 1805 may be a liquid crystal display (LCD), a light-emitting diode (LED) display device, a cathode ray tube (CRT) display device, or a projector, etc. The input device 1806 communicates with the processor 1801 and can receive user input in various ways. For example, the input device 1806 may be a mouse, keyboard, touchscreen device, or sensing device, etc.

[0322] The aforementioned communication device 1800 may sometimes be referred to as a communication equipment, which can be a general-purpose device or a special-purpose device. For example, the communication device 1800 may be a desktop computer, a portable computer, a web server, a handheld computer (PDA), a mobile phone, a tablet computer, a wireless terminal device, an embedded device, or a device with a similar structure to that in Figure 18. The embodiments of this application do not limit the type of communication device 1800.

[0323] Furthermore, the composition shown in FIG18 does not constitute a limitation on the communication device. In addition to the components shown in FIG18, the communication device 1800 may include more or fewer components than shown, or combine certain components, or have different component arrangements.

[0324] In the communication device 1800 shown in Figure 18, the processor 1801 can call the computer execution instructions stored in the memory 1803 to make the communication device 1800 execute the communication method in the above method embodiment.

[0325] Specifically, the functions / implementation processes of the transceiver module 1702 and processing module 1701 in Figure 17 can be implemented by the processor 1801 in the communication device 1800 shown in Figure 18 calling computer execution instructions stored in the memory 1803. Alternatively, the functions / implementation processes of the processing module 1701 in Figure 17 can be implemented by the processor 1801 in the communication device 1800 shown in Figure 18 calling computer execution instructions stored in the memory 1803, and the functions / implementation processes of the transceiver module 1702 in Figure 17 can be implemented by the communication interface 1804 in the communication device 1800 shown in Figure 18.

[0326] It should be understood that one or more of the above modules or units can be implemented by software, hardware, or a combination of both. When any of the above modules or units are implemented by software, the software exists as computer program instructions and is stored in memory. The processor can be used to execute the program instructions and implement the above method flow. The processor can be built into a SoC or ASIC, or it can be a separate semiconductor chip. In addition to the core that executes software instructions for computation or processing, the processor may further include necessary hardware accelerators, such as field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), or logic circuits that implement dedicated logic operations.

[0327] When the above modules or units are implemented in hardware, the hardware can be any one or any combination of a CPU, microprocessor, digital signal processing (DSP) chip, microcontroller unit (MCU), artificial intelligence processor, ASIC, SoC, FPGA, PLD, application-specific digital circuit, hardware accelerator, or non-integrated discrete device, which can run the necessary software or perform the above method flow independently of software.

[0328] Optionally, embodiments of this application also provide a communication device (e.g., the communication device may be a chip or a chip system), which includes a processor for implementing the methods in any of the above method embodiments. In one possible design, the communication device further includes a memory. The memory is used to store necessary program instructions and data, and the processor can call the program code stored in the memory to instruct the communication device to execute the methods in any of the above method embodiments. Of course, the memory may not be included in the communication device. When the communication device is a chip system, it may be composed of chips or may include chips and other discrete devices; embodiments of this application do not specifically limit this.

[0329] Optionally, embodiments of this application also provide a computer-readable storage medium storing a computer program or instructions that, when run on a communication device, enable the communication device to execute the methods described in any of the above method embodiments or any implementation thereof.

[0330] Optionally, embodiments of this application also provide a computer program product, which includes a computer program or instructions that, when run on a communication device, enable the communication device to execute the methods described in any of the above method embodiments or any implementation thereof.

[0331] Optionally, embodiments of this application also provide a communication system, which includes the first communication device and the second communication device described in the above method embodiments.

[0332] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented using software programs, implementation can be, in whole or in part, in the form of a computer program product. This computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the flow or function according to the embodiments of this application is generated. 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. For example, computer instructions can be transmitted from one website, computer, server, or data center to another via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium accessible to a computer or a data storage device containing one or more servers, data centers, etc., that can be integrated with the medium. The available media can be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., DVDs), or semiconductor media (e.g., solid-state drives (SSDs)).

[0333] Although this application has been described herein in conjunction with various embodiments, those skilled in the art, by reviewing the accompanying drawings, the disclosure, and the appended claims, will understand and implement other variations of the disclosed embodiments in carrying out the claimed application. In the claims, the word "comprising" does not exclude other components or steps, and "a" or "an" does not exclude multiple instances. A single processor or other unit can implement several functions listed in the claims. While different dependent claims may recite certain measures, this does not mean that these measures cannot be combined to produce good results.

[0334] Although this application has been described in conjunction with specific features and embodiments, it is obvious that various modifications and combinations can be made thereto without departing from the scope of this application. Accordingly, this specification and drawings are merely exemplary illustrations of the application as defined by the appended claims, and are considered to cover any and all modifications, variations, combinations, or equivalents within the scope of this application. Clearly, those skilled in the art can make various alterations and modifications to this application without departing from its scope. Thus, if such modifications and modifications fall within the scope of the claims and their equivalents, this application is also intended to include such modifications and modifications.

Claims

1. A communication method, characterized in that, The method includes: Receive first information from the first communication device through the first protocol; The first information is sent to the second communication device via the second protocol, wherein at least one of the first and second protocols is a Fast User Datagram Protocol (UDP) or an Internet Connection Protocol (QUIC).

2. The method according to claim 1, characterized in that, The first protocol is the GTP-U protocol, a tunneling protocol used for user plane data transmission in the General Packet Radio Service (GPRS) network, and the second protocol is the QUIC protocol; The first information from the first communication device is carried in a first message, the first message including first identification information, the first identification information being used to identify the GTP-U tunnel; The first information sent to the second communication device is carried in a second message, the second message including second identification information, the second identification information being used to identify the QUIC connection, and there is a mapping relationship between the second identification information and the first identification information.

3. The method according to claim 2, characterized in that, The method further includes: Obtain first configuration information, which is used to configure the mapping relationship. The first configuration information includes the first identification information and the second identification information.

4. The method according to claim 3, characterized in that, The first configuration information also includes at least one of the following: The QUIC connection includes the identification information of the QUIC flow, the identification information of the path corresponding to the QUIC connection, the identification information of the session, or the identification information of the quality of service flow included in the session.

5. The method according to any one of claims 2-4, characterized in that, The first information includes at least one of the following: session identification information, QoS flow identification information, the first identification information, priority information, or the identification information of the path corresponding to the GTP-U tunnel.

6. The method according to claim 1, characterized in that, The first protocol is the Stream Control Transport Protocol (SCTP), and the second protocol is the QUIC protocol. The first information from the first communication device is carried in a first message, the first message including first identification information and / or third identification information, the first identification information being used to identify an SCTP connection, and the third identification information being used to identify an SCTP stream belonging to the SCTP connection; The first information sent to the second communication device is carried in a second message. The second message includes second identification information, which is used to identify the QUIC connection. There is a mapping relationship between the second identification information and the first identification information or the third identification information.

7. The method according to claim 6, characterized in that, The method further includes: Obtain second configuration information, which is used to configure the mapping relationship. The second configuration information includes the second identification information and at least one of the following: the first identification information or the third identification information.

8. The method according to claim 7, characterized in that, The second configuration information also includes at least one of the following: The QUIC connection includes QUIC stream identification information, path identification information corresponding to the QUIC connection, fourth identification information, or fifth identification information. The fourth identification information is used to identify the type of message transmitted through the SCTP connection, the SCTP stream, the QUIC connection, or the QUIC stream. The fifth identification information is used to identify at least one message belonging to the same process transmitted through the SCTP connection, the SCTP stream, the QUIC connection, or the QUIC stream.

9. The method according to any one of claims 6-8, characterized in that, The first information includes at least one of the following: sixth identification information, seventh identification information, terminal identification information, first identification information, third identification information, priority information, or identification information of the path corresponding to the SCTP connection, wherein the sixth identification information is used to identify the type of message transmitted through the SCTP connection or the SCTP stream, and the seventh identification information is used to identify at least one message belonging to the same process transmitted through the SCTP connection or the SCTP stream.

10. The method according to claim 1, characterized in that, The first protocol is the Transmission Control Protocol (TCP), and the second protocol is the QUIC protocol; The first information from the first communication device is carried in a first message, and the first message includes eighth identification information, which is used to identify the TCP connection. The first information sent to the second communication device is carried in a second message, the second message including first identification information, the first identification information being used to identify the QUIC connection, and there is a mapping relationship between the first identification information and the eighth identification information.

11. The method according to claim 10, characterized in that, The method further includes: Obtain third configuration information, which is used to configure the mapping relationship. The second configuration information includes the first identification information and the eighth identification information.

12. The method according to claim 11, characterized in that, The third configuration information also includes at least one of the following: The QUIC connection includes QUIC stream identification information, QUIC connection path identification information, ninth identification information, or tenth identification information. The ninth identification information is used to identify the type of message transmitted through the TCP connection, the QUIC connection, or the QUIC stream. The tenth identification information is used to identify at least one message belonging to the same process transmitted through the TCP connection, the QUIC connection, or the QUIC stream.

13. The method according to any one of claims 10-12, characterized in that, The first information includes at least one of the following: eleventh identification information, twelfth identification information, terminal identification information, first identification information, eighth identification information, priority information, or identification information of the path corresponding to the TCP connection, wherein the eleventh identification information is used to identify the type of message transmitted through the TCP connection, and the twelfth identification information is used to identify at least one message belonging to the same process transmitted through the TCP connection.

14. The method according to any one of claims 2-13, characterized in that, The thirteenth identification information in the header of the second message includes the first information, and the thirteenth identification information is either the source QUIC connection identifier or the destination QUIC connection identifier; or, The QUIC stream identification information in the payload of the second message includes the first information; or, The thirteenth identification information in the header of the second message includes part of the information in the first message, and the QUIC stream identification information in the payload of the second message includes another part of the information in the first message. The thirteenth identification information is either the source QUIC connection identifier or the destination QUIC connection identifier.

15. The method according to claim 1, characterized in that, The first protocol is a Radio Resource Control (RRC) layer protocol, Service Data Adaptation (SDAP) layer protocol, Packet Data Convergence (PDCP) layer protocol, Radio Link Control (RLC) layer protocol, Media Access Control (MAC) layer protocol, Physical (PHY) layer protocol, or Non-Access NAS layer protocol, and the second protocol is a QUIC protocol.

16. The method according to any one of claims 1-15, characterized in that, The method further includes: Obtain fourth configuration information, which is used to configure the mapping relationship between the radio bearer and the QUIC connection. The third configuration information includes the identification information of the radio bearer and the identification information of the QUIC connection.

17. The method according to any one of claims 1-16, characterized in that, The method further includes: Obtain the fifth configuration information, which includes the identification information of the QUIC connection and the identification information of the path that supports the QUIC connection.

18. The method according to claim 17, characterized in that, The fifth configuration information also includes at least one of the following: It supports priority information for paths carrying QUIC connections and identification information for paths that default to carrying the QUIC connections.

19. The method according to any one of claims 1-18, characterized in that, The first communication device is a radio access network (RAN) node, terminal, core network element, or bearer network node; the second communication device is a radio access network (RAN) node, terminal, core network element, or bearer network node.

20. The method according to any one of claims 1-19, characterized in that, The message carrying the first information is transmitted via any of the following paths: a path connected via a non-terrestrial communication network, a path connected via a terrestrial communication network, a path connected via a sub-network, a path connected via microwave, a path connected via a first network, or a path connected via a second network, wherein the first network and the second network are different.

21. The method according to any one of claims 1-20, characterized in that, The first protocol is the QUIC protocol, the second communication device does not support the QUIC protocol, the first communication device is used to perform tasks related to at least one of the following services: artificial intelligence (AI) service, data service, or communication sensing integrated (ISAC) service, or the first communication device is used to manage a fourth communication device, the fourth communication device is used to perform tasks related to at least one of the following services: artificial intelligence (AI) service, data service, or communication sensing integrated (ISAC) service.

22. The method according to any one of claims 1-20, characterized in that, The second protocol is the QUIC protocol. The first communication device does not support the QUIC protocol. The second communication device is used to perform tasks related to at least one of the following services: artificial intelligence (AI) services, data services, or communication sensing integrated (ISAC) services. Alternatively, the second communication device is used to manage a fourth communication device, which is used to perform tasks related to at least one of the following services: artificial intelligence (AI) services, data services, or communication sensing integrated (ISAC) services.

23. The method according to any one of claims 1-21, characterized in that, The method is applied to a third communication device, which is a RAN node, a terminal, a core network element, or a bearer network node.

24. A communication device, characterized in that, The communication device includes modules or units for implementing the method of any one of claims 1-23.

25. A communication device, characterized in that, The communication device includes a processor, which, when executing instructions, causes the communication device to perform the method of any one of claims 1-23.

26. A computer-readable storage medium, characterized in that, It stores instructions that, when executed by a computer, cause the method of any one of claims 1-23 to be performed.

27. A computer program product, characterized in that, The computer program product includes instructions that, when executed by a computer, cause the method of any one of claims 1-23 to be performed.

28. A communication system, characterized in that, The communication system includes a first communication device, a second communication device, and a third communication device, wherein the third communication device is used to perform the method according to any one of claims 1-23.

Images