Communication configuration method, apparatus, storage medium, and program product

Abstract

A communication configuration method, an apparatus, a storage medium, and a program product. The method comprises: receiving a first message from a second node, the first message being used for requesting a remote direct memory access transport channel established between a first node and a third node; and sending a second message to the second node, the second message being used for responding to the remote direct memory access transport channel established between the first node and the third node.

Description

Communication configuration methods, devices, storage media and software products

[0001] This disclosure claims priority to Chinese patent application No. 202510121168.6, filed on January 24, 2025, the entire contents of which are incorporated herein by reference. Technical Field

[0002] This disclosure relates to the field of communication technology, and in particular to a communication configuration method, apparatus, storage medium, and program product. Background Technology

[0003] The continuous development of digital data applications and services has led to a surge in demand for data traffic transmission. Furthermore, the introduction of new technologies such as communication sensing and artificial intelligence (AI) means that future communication systems will need to handle not only traditional user service data transmission but also the massive amounts of data generated and acquired by the systems themselves due to these new technologies. Meeting the ever-increasing demands for diverse communication transmission is one of the major technological challenges currently facing communication systems.

[0004] Here, communication transmission requirements mainly include connection data rate, latency, quality of service (QoS), security, and availability. Summary of the Invention

[0005] On one hand, a communication configuration method is provided, including: receiving a first message from a second node; the first message is used to request the establishment of a remote direct memory access transmission channel between the first node and a third node; sending a second message to the second node; the second message is used to respond to the establishment of the remote direct memory access transmission channel between the first node and the third node.

[0006] On the other hand, another communication configuration method is provided, including: sending a first message to a first node; the first message is used to request the establishment of a remote direct memory access transmission channel between the first node and the third node; receiving a second message from the first node; the second message is used to respond to the establishment of the remote direct memory access transmission channel between the first node and the third node.

[0007] In another aspect, a communication device is provided, comprising: a processing unit and a communication unit; the communication unit is configured to receive a first message from a second node; the first message is configured to request the establishment of a remote direct memory access transmission channel between the first node and a third node; the communication unit is configured to send a second message to the second node; the second message is configured to respond to the establishment of the remote direct memory access transmission channel between the first node and the third node.

[0008] In another aspect, a communication device is provided, comprising: a processing unit and a communication unit; the communication unit is configured to send a first message to a first node; the first message is configured to request the establishment of a remote direct memory access transmission channel between the first node and a third node; the communication unit is configured to receive a second message from the first node; the second message is configured to respond to the establishment of the remote direct memory access transmission channel between the first node and the third node.

[0009] In another aspect, a communication device is provided, comprising: a memory and a processor; the memory and the processor are coupled; the memory is used to store a computer program; and the processor implements the communication configuration method described above when executing the computer program.

[0010] In another aspect, a computer-readable storage medium is provided, on which computer program instructions are stored, which, when executed by a processor, implement the communication configuration method described above.

[0011] In another aspect, a computer program product is provided, which includes computer program instructions that, when executed by a processor, implement the communication configuration method described above. Attached Figure Description

[0012] To more clearly illustrate the technical solutions in this disclosure, the accompanying drawings used in some embodiments of this disclosure will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of this disclosure. For those skilled in the art, other drawings can be obtained based on these drawings.

[0013] Figure 1 is an architecture diagram of a communication system according to some embodiments;

[0014] Figure 2 is a structural diagram of a protocol stack according to some embodiments;

[0015] Figure 3 is a structural diagram of another protocol stack according to some embodiments;

[0016] Figure 4 is a structural diagram of another protocol stack according to some embodiments;

[0017] Figure 5 is an architecture diagram of another communication system according to some embodiments;

[0018] Figure 6 is a flowchart of a communication configuration method according to some embodiments;

[0019] Figure 7 is a structural diagram of a transmission channel according to some embodiments;

[0020] Figure 8 is a flowchart of another communication configuration method according to some embodiments;

[0021] Figure 9 is a flowchart of a communication configuration method according to some embodiments;

[0022] Figure 10 is a flowchart of yet another communication configuration method according to some embodiments;

[0023] Figure 11 is a flowchart of another communication configuration method according to some embodiments;

[0024] Figure 12 is a flowchart of another communication configuration method according to some embodiments;

[0025] Figure 13 is a flowchart of yet another communication configuration method according to some embodiments;

[0026] Figure 14 is a flowchart of yet another communication configuration method according to some embodiments;

[0027] Figure 15 is a block diagram of a first node according to some embodiments;

[0028] Figure 16 is a block diagram of a second node according to some embodiments;

[0029] Figure 17 is a block diagram of a communication device according to some embodiments. Detailed Implementation

[0030] The technical solutions of this disclosure will now be clearly and completely described with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this disclosure, and not all embodiments. Based on the embodiments of this disclosure, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this disclosure.

[0031] It should be noted that, in this disclosure, the words "exemplarily" or "for example" are used to indicate examples, illustrations, or explanations. Any embodiment or design described as "exemplarily" or "for example" in this disclosure should not be construed as being more preferred or advantageous than other embodiments or designs. Specifically, the use of the words "exemplarily" or "for example" is intended to present the relevant concepts in a specific manner.

[0032] Hereinafter, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of that feature.

[0033] In the description of this disclosure, unless otherwise stated, " / " means "or," for example, A / B can mean A or B. "And / or" in this document 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 alone, A and B simultaneously, and B alone. Furthermore, "at least one" means one or more, and "more than one" means two or more.

[0034] The continuous development of digital data applications and services has led to a surge in data traffic transmission demands. Furthermore, the introduction of new technologies such as communication sensing and AI means that future communication systems must not only meet the traditional user service data transmission needs but also handle the massive amounts of data generated and acquired by the communication system itself. This data can originate from communication devices such as terminals, base stations, edge servers, and the core network within the communication system. Compared to traditional communication data, the sensing and AI data brought by new technologies exhibit characteristics of greater volume, diversity, temporality, and correlation. Meeting the ever-increasing demands for diverse communication transmission is one of the significant technical challenges currently facing communication systems. These demands primarily include aspects such as connection data rate, latency, QoS, security, and availability.

[0035] For example, in traditional Transmission Control Protocol / Internet Protocol (TCP / IP) communication networks, the data sender needs to copy data from the user application space buffer to the socket buffer in the kernel space. Then, the kernel adds a data packet header to the data for encapsulation. Through a series of multi-layered network protocol packet processing steps, such as TCP, User Datagram Protocol (UDP), and IP, the data is pushed into the network interface card's buffer for network transmission.

[0036] After receiving data from a remote device, the receiving end needs to copy the data from the network card buffer to the socket buffer in the kernel space of the receiving end. Then, it undergoes a series of multi-layer network protocols for data parsing. The parsed data is copied to the corresponding user space buffer, and a system context switch occurs before the user application can access the received data. Therefore, sending and receiving a message in a traditional TCP / IP communication network requires kernel transmission, four memory copies (user buffer, kernel buffer, network card buffer), two context switches (user space and kernel space), TCP protocol stack processing, two interrupt handling delays, plus system calls for each read / write operation. This results in a long overall transmission latency and reliance on the processing power of the central processing unit (CPU).

[0037] The current communication system's transmission efficiency is insufficient to meet the ever-increasing demand for communication transmission.

[0038] Therefore, in this embodiment of the present disclosure, the first node can receive a first message from the second node. This first message requests the establishment of a remote direct memory access (RDA) transmission channel between the first node and the third node. Subsequently, the first node can send a second message to the second node. This second message responds to the establishment of the RDA transmission channel between the first node and the third node. Thus, this embodiment of the present disclosure can configure a RDA transmission channel between the first node and the third node, thereby enabling data transmission via RDA. Compared to current data transmission methods in communication systems, this method allows direct reading and writing of data from device memory, reducing processing operations during data transmission and improving transmission efficiency.

[0039] In this disclosure, the mobile communication networks include, but are not limited to, third-generation mobile communication technology (3G), fourth-generation mobile communication technology (4G), fifth-generation mobile communication technology (5G), and future mobile communication networks.

[0040] It should be understood that, in this example, the communication node in the network architecture of the mobile communication network can be a terminal-side device (e.g., including but not limited to a terminal), an access network-side device (e.g., including but not limited to a base station), or a core network-side device (e.g., including but not limited to core network elements). A communication node can also be simply referred to as a node. Furthermore, a node can also be a module of a device in the communication system, or a protocol layer in the communication system. This module can be implemented as a software module, a hardware module, or a combination of software and hardware modules.

[0041] As exemplarily shown in FIG1, a communication system provided in an embodiment of the present disclosure includes a wireless access network 10 and a core network 20. The wireless access network 10 includes a base station 101 and a terminal 102. There may be one or more base stations 101 and terminals 102, and the number is not limited.

[0042] Here, base station 101 is connected to terminal 102 via a communication link. Base station 101 is also connected to core network 20 via a communication link. This communication link can be a wired communication link or a wireless communication link, and this disclosure does not limit it in this way. The core network node in core network 20 and base station 101 in wireless access network 10 can be different physical devices, or they can be the same physical device that integrates the logical functions of core network 20 and wireless access network 10.

[0043] In some embodiments, a core network node may refer to a device in the core network 20 that provides service support to the terminal 102. The core network node in the core network 20 may include at least one of the following: access and mobility management function (AMF) network elements, session management function (SMF) network elements, user plane function (UPF) network elements, policy control function (PCF) network elements, unified data management (UDM) network elements, application function (AF) network elements, network exposure function (NEF) network elements, network slice selection function (NSSF) network elements, data analytics function (DAF) network elements, data plane function (DPF) network elements, or sensing function (SF) network elements, etc. Of course, the core network 20 may also include other core network nodes, without limitation.

[0044] The AMF (Agency Flow Manager) network element is deployed in the core network 20, providing mobility management and connectivity management for the network, such as user location updates, user registration, and user handover. The AMF network element can act as an intermediate route between the LMF (Local Messaging Function), SMF (Small Mobile Messaging Function), and base station 101. The SMF network element is primarily responsible for session management in the mobile network, such as session establishment, modification, and release. The UPF (User Plane Function) network element is responsible for connecting to external networks and processing user packets, such as forwarding and charging. The PCF (Programmable Flow Function) network element is primarily responsible for providing policies to the AMF and SMF, such as QoS policies and slice selection policies. The UDM (User Data Management) network element is used to store user data, such as subscription information and authentication / authorization information. The AF (Agency Flow) network element is responsible for providing services to the 3GPP network. The NEF (Network Electronic Function) network element is mainly used to open up the capabilities of various network functions and is responsible for converting internal and external information. The DAF (Network Data Analytics Function) network element, also known as the NWDAF (Network Data Analytics Function) network element, is mainly used to provide data analysis functions. The DPF (Data Plane Function) network element is mainly used to carry data plane data. SF network elements are mainly used to implement sensing functions, which include sensing control functions and / or sensing computing functions.

[0045] In some embodiments, base station 101 is a device located on the access network side of the aforementioned communication system and having wireless transceiver functionality, or a chip or chip system that can be installed on such device. Base station 101 includes, but is not limited to: access points (APs) in WiFi systems, such as home gateways, routers, servers, switches, bridges, etc.; evolved NodeBs (eNBs), radio network controllers (RNCs), NodeBs (NBs), base station controllers (BSCs), base transceiver stations (BTSs), home base stations (e.g., home evolved NodeBs, or home NodeBs, HNBs), base band units (BBUs), wireless relay nodes, wireless backhaul nodes (e.g., integrated access and backhaul (IAB) nodes), transmission and reception points (TRPs or transmission points, TPs), etc., and can also be 5G base stations, such as new radio (NR) stations. In a 5G radio (NR) system, a gNB, or a transmission point (TRP or TP), can be a gNB or a group of antenna panels (including multiple antenna panels) in a 5G system base station. Alternatively, it can be a network node constituting a gNB or transmission point, such as a baseband unit (BBU), a distributed unit (DU), a roadside unit (RSU) with base station functionality, NG radio access network (NG-RAN) equipment, or a 6G base station. Base station 101 also includes base stations in different networking modes, such as a master evolved NodeB (MeNB) and a secondary eNB (SeNB, or secondary gNB, SgNB). Base station 101 also includes different types, such as terrestrial base stations, airborne base stations, and satellite base stations.

[0046] In some embodiments, terminal 102 is a device with wireless communication capabilities that can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted. It can also be deployed on water (such as on ships). Furthermore, it can be deployed in the air (e.g., on airplanes, balloons, and satellites). Terminal 102 is also referred to as user equipment (UE), mobile station (MS), mobile terminal (MT), and terminal equipment, etc., and is a device that provides voice and / or data connectivity to users. For example, terminal 102 includes handheld devices, vehicle-mounted devices, etc., with wireless connectivity capabilities. Currently, terminal 102 can be: mobile phone, tablet computer, laptop computer, PDA, mobile internet device (MID), wearable device (e.g., smartwatch, smart bracelet, pedometer, etc.), in-vehicle device (e.g., car, bicycle, electric vehicle, airplane, ship, train, high-speed rail, etc.), virtual reality (VR) device, augmented reality (AR) device, wireless terminal in industrial control, smart home device (e.g., refrigerator, television, air conditioner, electricity meter, etc.), smart robot, workshop equipment, wireless terminal in self-driving, wireless terminal in remote medical surgery, wireless terminal in smart grid, wireless terminal in transportation safety, wireless terminal in smart city, or wireless terminal in smart home, flying device (e.g., smart robot, hot air balloon, drone, airplane), etc. In one possible application scenario disclosed in this disclosure, the terminal is a terminal that frequently operates on the ground, such as in-vehicle device. In this disclosure, for ease of description, the chip deployed in the above-mentioned device, such as a system-on-a-chip (SOC), a baseband chip, or other chip with communication functions, may also be referred to as a terminal.

[0047] The nodes in this embodiment can be various communication devices in the above-mentioned communication system. Here, different nodes can transmit data through remote direct memory access.

[0048] For example, taking the Remote Direct Memory Access (RDMA) protocol in the remote direct memory access method as an example, RDMA technology can realize the direct transfer of data from the memory of one communication device to the memory of another communication device without the intervention of the operating systems of both parties. It has the characteristics of zero copy, low latency, and low CPU usage, and can realize high throughput and low latency network communication.

[0049] Here, the data transmission, reception, and memory access process of the RDMA protocol is as follows:

[0050] 1. The sending application prepares the data transmission request message in user space.

[0051] 2. Request messages are placed into a queue pair (QP).

[0052] 3. The RDMA network interface card (RNIC) at the transmitting end reads data from memory.

[0053] 4. The sending RNIC sends the data to the receiving end.

[0054] 5. The receiving RNIC writes the data into memory.

[0055] 6. The receiving application reads data from memory.

[0056] Compared to traditional TCP / IP protocols, RDMA offers several advantages: no context switching (operations occur directly in user space), zero copy (data is transferred directly from source memory to destination memory without intermediate copying), kernel bypass (avoiding the operating system kernel and protocol stack processing latency), no interrupts (data reception does not require CPU intervention), and no system calls (all operations are completed in user space). These advantages significantly reduce latency. For example, in a 10Gbps network environment, RDMA's end-to-end latency can be as low as 1-2 microseconds, while kernel-based TCP may require 50-100 microseconds or more.

[0057] In some embodiments, RDMA provides point-to-point communication based on message queues, allowing each application to directly retrieve its corresponding messages without the intervention of the operating system and protocol stack. The message service is built upon a transport channel connection established between the local and remote applications. When an application needs to communicate, a transport channel connection is created, with each channel consisting of two pairs of QPs at its endpoints. Each QP pair comprises a send queue (SQ) and a receive queue (RQ), which manage various message types. The SQ and RQ are collectively referred to as work queues (WQs). QPs are mapped to the application's virtual address space, allowing the application to directly access the RNIC through the QP. In addition to the two basic queues in the QP, RDMA also provides a complete queue (CQ), used to notify that messages on the WQ have been processed.

[0058] RDMA provides a software transport interface to facilitate applications in creating work requests (WRs). WRs indicate the message content that the application needs to transmit to the other end of the transport channel. WRs can notify a specific queue (WQ) in the QP. Here, WRs can be further divided into receive requests (RRs) and send requests (SRs). RRs correspond to an asynchronous event description used to describe a receive request, which is placed in the RQ. Similarly, SRs correspond to an asynchronous event description used to describe a send request. SRs are placed in the SQ, and then the network interface card (NIC) retrieves the SR from the SQ and sends the corresponding data. In other words, the two communicating parties need to establish a QP first. The receiving party needs to place the receive request (RR) into the receive queue (RQ) through the QP, and the sending party needs to place the send request (SR) into the send queue (SQ) through the QP. Then, the NIC performs data transmission and reception (the data transmission and reception process does not require CPU involvement). After data transmission and reception are completed, the NIC generates a corresponding completion event in the CQ to notify the application layer.

[0059] For example, current RDMA protocols mainly include the InfiniBand (IB) protocol, RDMA over Converged Ethernet (RoCE) protocol, and the Internet Wide Area RDMA protocol (iWARP). Taking RoCE v2 as an example, this protocol is based on the Ethernet UDP protocol, uses UDP destination port 4791 as the data traffic for transmitting RoCE v2, and uses the IB transport layer as the UDP payload data.

[0060] As shown in Figure 2, a typical network protocol stack includes the application layer, application programming interface (API) layer, transport layer, network layer, data link layer, and physical layer. The TCP / IP protocol stack includes the application layer, socket layer, TCP / UDP layer, IP layer, medium access control (MAC) layer, and Ethernet hardware layer. The RoCE v2 protocol stack includes the application layer, driver (Verbs) layer, IB transport layer, UDP layer, IP layer, MAC layer, and Ethernet hardware layer.

[0061] Here, the functions of the application layer, verbs layer, UDP layer, IP layer, MAC layer, and Ethernet hardware layer can be found in the relevant protocols. The IB transport layer mainly provides the following functions:

[0062] 1-1. Reliable connection (RC): Used to provide reliable, connection-oriented communication services, ensuring the orderly and reliable delivery of data packets.

[0063] 2-1. Unreliable Datagram (UD): Used to provide unreliable, connectionless communication services. UD allows one-to-many communication but does not guarantee reliable delivery of data packets. It is suitable for applications that can tolerate a small amount of data loss, such as streaming media transmission.

[0064] 3-1. Reliable datagram (RD): Used to provide reliable, connectionless communication services. RD combines the reliability of RC with the flexibility of UD and is used in scenarios that require reliability but also need to maintain connection flexibility.

[0065] 4-1 Extended Reliable Connection (XRC): Allows multiple processes to share a single transmission resource, reducing resource consumption in large-scale parallel applications and is suitable for parallel applications in high-performance computing clusters.

[0066] 5-1. Dynamic Connected Transport (DCT): Provides the ability to dynamically create and destroy connections, combining the reliability of Responsive Connectivity (RC) with the scalability of Unspontaneous Connectivity (UD). Suitable for scenarios requiring frequent establishment of short-lived connections.

[0067] In addition, the IB transport layer also supports atomic operations, memory management, QP management, multipath support, flow control, QoS support, and error detection and recovery.

[0068] In some embodiments, the communication system itself generates and acquires a large amount of data due to new technologies such as communication sensing and AI. This data can come from base station 101, terminal 102, edge server, and core network 20. Therefore, each node in the communication system has a need for data collection, analysis, and processing, and the transmission of this data may occur between any nodes in the communication network. As shown in Table 1, for AI data, data transmission may occur between the UE and the radio access network (RAN) / core network (CN) / AF, and between the RAN and RAN / CN / AF / network management equipment. For example, the network management equipment can be an operation administration and maintenance (OAM) device, and data transmission may occur between CN and CN / AF / OAM, between AF and AF, and between OAM and OAM. For sensing data, data transmission may occur between the UE and RAN / CN / AF, between RAN and RAN / CN / AF, and between CN and CN / AF.

[0069] Table 1 Data Types and Data Transmission Scenarios

[0070] For data transmission between the UE and the RAN / CN / AF, the UE can transmit data across the radio air interface via the RNIC. For data transmission between the RAN, CN, AF, and OAM, in this scenario, RAN and RAN, RAN and CN, CN and CN, CN and AF, RAN and AF, RAN and OAM, and CN and OAM may be deployed in the same or different data centers. Data between these nodes can be transmitted via remote direct memory access.

[0071] In some embodiments, control signaling for Xn, NG, and F1 interfaces can be transmitted via the Stream Control Transmission Protocol (SCTP). SCTP supports multi-homing, allows a single connection to use multiple IP addresses, supports message-level transmission, and supports independent multiple data streams, allowing parallel transmission of different types of signaling messages. SCTP improves congestion control, supporting independent congestion control for each flow and faster packet loss detection and recovery, thus enhancing network reliability and redundancy. SCTP can also better handle intermittent connections and network changes based on mobile network characteristics.

[0072] For user plane data transmission via Xn and NG interfaces, communication networks typically employ the General Packet Radio Service Tunneling Protocol (GTP). GTP provides efficient packet encapsulation and tunneling mechanisms, and can be combined with Internet Protocol Security (IPSec) for secure transmission. Given the large volume of user plane data traffic, Remote Direct Memory Access (RDM) can leverage its low latency, high throughput, and CPU offloading advantages. However, applying RDM to GTP requires defining appropriate encapsulation and decapsulation operations, and also necessitates ensuring that the RNIC supports IPSec.

[0073] For example, as shown in Figure 3, user plane data for the Xn, NG, and F1 interfaces can be transmitted via the protocol stack shown in Figure 3. For instance, this protocol stack can be a GTP over Roce v2 protocol stack. Here, the GTP over Roce v2 protocol stack includes a Protocol Data Unit (PDU) layer, a GTP layer, an IB transport layer, a UDP / IP layer, and an Ethernet link layer. The GTP over Roce v2 protocol stack can terminate between RANs, between RANs and UPFs, or between DUs and CUs. The PDU layer corresponds to the PDU session type between the UE and the data network. For example, IPv4, IPv6, IPv4v6, or Ethernet frames. The GTP layer can encapsulate the UE's PDU. The GTP layer subheader can contain a tunnel endpoint identifier (TEID), a QoS flow identifier (QFI) associated with the data packet, and / or other state information. Different QFIs are associated with different QoS requirements. To accommodate different data transmission differential requirements, the Differentiated Services Code Point (DSCP) value at the IP layer can be uniformly configured by the SMF according to the associated QoS flow. After the user plane data completes GTP header encapsulation, it can be handed over to the IB network interface card (NIC) for IB transport layer sub-header encapsulation and subsequent UDP / IP / Ethernet sub-header encapsulation, and then data transmission can begin.

[0074] For example, as shown in Figure 4, the transmission of AI, sensing, and other data is performed through the protocol stack shown in Figure 4. For instance, this protocol stack can be a RoCE v2-based transport protocol stack. Here, the protocol stack includes an application layer, a data layer, an IB transport layer, a UDP / IP layer, and an Ethernet link layer. The RoCE v2-based data transmission protocol stack can terminate between RANs, or between RANs and CNs, or between RANs and OAMs, or between RANs and AFs, or between CNs, or between CNs and OAMs, or between CNs and AFs.

[0075] In some embodiments, the RAN may include at least one of a radio unit (RU), a centralized unit (CU), a distributed unit (DU), and / or a next-generation NodeB (xNB). Therefore, data transmission between RANs can occur between CU and DU, between CU and RU, between RU and DU, between CU and CU, between xNB and xNB, or between DU and DU, etc. Correspondingly, data transmission between the RAN and CN can occur between xNB and CN, between DU and CN, between RU and CN, etc. Exemplarily, the CN may include at least one of AMF, UPF, DPF, NWDAF, and SF.

[0076] This approach can reuse the retransmission and congestion control provided by the IB transport layer of RoCE v2. For example, the IB transport layer provides the following transmission modes:

[0077] 2-1. Reliable connection (RC) transmission mode: This transmission mode can improve the reliability of connection-oriented transmission, with QPs at both ends of the communication being bound one-to-one.

[0078] 2-2 Unreliable connection (UC) transmission mode: This transmission mode improves connection-oriented unreliable transmission, with QPs at both ends of the communication being bound one-to-one.

[0079] UD is used to provide unreliable packet-oriented transmission, with no one-to-one binding between the two ends of the communication, similar to UDP.

[0080] Depending on the configured IB transmission method, RD can be used for reliable or unreliable data transmission.

[0081] If the data volume is small, data requests and data transmission responses can be made directly through control plane signaling without needing to establish a dedicated data transmission channel. If the data volume is large, a request can be sent first through control signaling, and the data transmission channel information can be configured during the interaction between the data transmission request and response control signaling.

[0082] Here, the application layer is used to transmit AI, perception, and other data. This application layer can be configured with application layer protocols such as Hypertext Transfer Protocol (HTTP), File Transfer Protocol (FTP), Remote Procedure Call (RPC), Web Real-Time Communication (WebRTC), Message Queuing Telemetry Transport (MQTT), WebSocket, or Constrained Application Protocol (CoAP). The data layer can carry a protocol stack header, which includes at least one of the following fields: data type, data identifier, data length, QoS indicator, protocol type, whether encrypted, whether compressed, and timestamp. The data type can be one of the following: AI data, perception data, and other data. If it is an AI data type, the data layer header also includes at least one of the following: AI data identifier, AI model type information, AI training data type information, AI inference data type information, AI analysis type information, and AI model performance type information. If it is a sense data type, the data layer subheading may also include at least one of the following: sense data identifier, communication sense data type information, environment sense data type information, target object sense data type information, etc. The protocol identifier in the data layer subheading can be used to indicate the application layer protocol type. The timestamp can be used to indicate at least one of the following: data generation time, data latency budget, etc.

[0083] In some embodiments, the data layer subheading may also include at least one of the following: UE ID, source node ID, source node port number, one or more target node IDs, target node port number, data identifier, subscriber identifier, notification identifier, etc. For non-IP application layer data, the data receiving node can identify the corresponding application based on the target port number in the data layer subheading, and then deliver the data to the corresponding application. Similarly, the source port number of the source node in the data plane is used to identify the application corresponding to the source end. For example, the data layer can be used to support reliable data transmission. Exemplarily, the data layer subheading may include information such as packet transmission sequence number (SN), request acknowledgment indication, and packet reception acknowledgment SN. This information can provide additional reliable data transmission guarantees through the data layer when the application layer data is of non-IP type.

[0084] For example, the data sending node encapsulates AI data or perception data based on application layer protocols. For instance, this application layer data can be further encapsulated with a data layer sub-header. The data layer sub-header can contain any combination of the above information. This data can then be passed to the IB network interface card (NIC) for encapsulation with the IB transport layer sub-header and subsequent UDP / IP / Ethernet sub-headers, and finally the data packet is transmitted to the data receiving node at the other end.

[0085] In some embodiments, two nodes can transmit data directly or indirectly through an intermediate node.

[0086] Taking control plane signaling transmission between the xNB and the core network as an example, as shown in Figure 5, in traditional wireless communication networks, control plane signaling between the xNB and the core network can be exchanged between the xNB and the AMF via next-generation application protocol (NGAP) signaling. Control signaling between the xNB and other core network elements can also be forwarded to other core network elements via the AMF. Furthermore, user plane data between the xNB and the core network can be transmitted between the xNB and the UPF via an NG-U tunnel, and then sent to the data network by the UPF.

[0087] For data plane data transmission, as shown in Figure 5, the AMF can send data tunnel configuration signaling to the DPF to configure the data tunnel, thereby enabling the forwarding of data plane data. The AMF can also send data tunnel configuration signaling to the xNB to configure the data tunnel.

[0088] In some embodiments, the xNB can adopt a separate architecture for the RU, DU, and CU. If the SF in the core network needs to acquire the sensing data from the xNB, it can transmit it in the following ways:

[0089] 3-1. Sensing data from RU and / or DU can be sent from RU and / or DU to CU, and then from CU to DPF, which forwards it to SF.

[0090] 3-2. Sensing data from RU and / or DU can be sent from RU and / or DU to CU, and then from CU to SF.

[0091] 3-3. Sensing data from RU and / or DU can be sent from RU and / or DU to DPF, and then forwarded by DPF to SF.

[0092] 3-4. Sensing data from RU and / or DU can be sent directly from RU and / or DU to SF.

[0093] For AI data, if the DAF in the core network needs to obtain AI training data from the RU or DU, or if the DAF in the core network needs to send AI analysis data or AI model data to the RU or DU, it can be transmitted in the following ways:

[0094] 4-1. AI data can be sent from RU and / or DU to CU, then from CU to DPF, and then from DPF to DAF.

[0095] 4-2. AI data can be sent from DAF to DPF, DPF to CU, and then CU to RU and / or DU.

[0096] 4-3. AI data can be sent from RU and / or DU to CU, and then from CU to DAF.

[0097] 4-4. AI data can be sent from DAF to CU, and then from CU to RU and / or DU.

[0098] 4-5. AI data can be sent from RU and / or DU to DPF, and then forwarded by DPF to DAF.

[0099] 4-6. AI data can be sent from DAF to DPF, and then from DPF to RU and / or DU.

[0100] 4-7. AI data can be sent directly from RU and / or DU to DAF.

[0101] 4-8. AI data can be sent directly from DAF to RU and / or DU.

[0102] It should be noted that the various embodiments of this disclosure can be referenced or learned from each other. For example, the same or similar steps, method embodiments, system embodiments and device embodiments can be referenced from each other without limitation.

[0103] Figure 6 is a flowchart of a communication configuration method provided in an embodiment of this disclosure, applied to a first node. As shown in Figure 6, the method includes the following steps:

[0104] Step 601: Receive the first message from the second node.

[0105] Here, the first message is used to request the establishment of a remote direct memory access transmission channel between the first node and the third node.

[0106] In some embodiments, the second node and the third node can be the same node, or the second node and the third node can be different nodes.

[0107] For example, the first node, the second node, and the third node are any one of the following nodes: access network node, core network node, network management node, and application node.

[0108] In one example, the access network node includes at least one of the following: RU, CU, DU, xNB.

[0109] The core network node includes at least one of the following: AMF network element, UPF network element, DPF network element, NWDAF network element, SF network element, and AF network element.

[0110] Taking data transmission between the RAN and UPF as an example, communication configuration is required between the RAN and the AMF / MME (mobility management entity). In this case, the first node can be the RAN, the second node can be the AMF / MME, and the third node can be the UPF.

[0111] Taking data transmission between CU and DU as an example, communication can be configured between CU and DU. In this case, the first node can be DU, and the second and third nodes can be CU.

[0112] For example, for the RoCEv2 protocol based on RDMA, an RDMA connection needs to be established, i.e., the QP needs to be configured. The established QP has multiple states. A newly created QP is in a reset state. For a QP in the reset state, the corresponding resources have been requested and confirmed, but not yet configured, and communication is not possible. Afterwards, the node can initiate the QP into the init state through an initialization operation, and through QP configuration, it can enter the ready to receive (RTR) state. A QP in the RTR state is ready to receive data, but cannot yet send data. By modifying the QP configuration, the QP can transition from the RTR state to the ready to send (RTS) state. A QP in this state can both receive and send data; therefore, this state is the primary operating state of the QP. During the transition of the QP from the reset state to the ready to send state, the node needs to configure the QP's attribute parameters. Therefore, communication configuration between the nodes at both ends of the data transmission can be achieved through configuration messages.

[0113] In some embodiments, the first message includes remote direct memory access transport channel configuration information on the third node side.

[0114] During the configuration process, the configuration parameters involved include parameter fields that can be provided or determined locally, parameter fields that depend on the peer's provision, and fields that need to be negotiated by both parties.

[0115] Here, the parameters that can be provided or determined locally include the local maximum transmission unit (MTU), local port number, packet loss timeout retransmission time, retransmission time, and local packet sequence number (PSN).

[0116] The parameters provided by the peer include the peer's queue pair number (QPN), peer's PSN, and peer's global identifier (GID). Here, the peer's QPN can be represented by a 24-bit number, serving as a unique identifier for the QP within the network interface card (NIC). The peer's PSN can also be represented by a 24-bit number, corresponding to the number of the first data packet initiated by the QP. The PSN can be randomly generated by the peer node and then transmitted to the peer, or both parties can agree on a fixed value, such as 0 for both. The peer's GID corresponds to a 128-bit identifier used to identify a port on the NIC, similar to the RoCE transport layer identifier.

[0117] Fields that need to be negotiated by both parties include the data retransmission mechanism, flow control mechanism, data encryption mechanism, and data compression mechanism, which need to be determined through negotiation between the data sending node and the data receiving node.

[0118] During the establishment of a remote direct memory access transmission channel between the first node and the third node, fields that can be provided or determined locally can be configured by the node itself. For fields that need to be provided by the peer node, the node can obtain relevant information from the peer node and then configure them.

[0119] In one example, the configuration information of the remote direct memory access transmission channel on the third node side includes at least one of the following: remote direct memory access indication information, remote direct memory access type, QPN on the third node side, PSN on the third node side, GID of the third node, flow control type, data encryption type, data retransmission type, data transmission protocol stack, and address information corresponding to the third node.

[0120] For example, remote direct memory access indication information is used to indicate whether remote direct memory access is used. Remote direct memory access types include at least one of the following: infiniteiband, RoCE v1, RoCE v2, iWARP. Flow control types include at least one of the following: global pause, priority-based flow control (PFC), explicit congestion notification (ECN), and data center quantized congestion notification (DCQCN). Data encryption types include at least one of the following: IPSec, data layer encryption, and application layer encryption. Data retransmission types include at least one of the following: Go-Back-N, selective retransmission, timeout retransmission, and link layer retransmission. Data transmission protocol stacks include at least one of the following: GTP tunnel, SCTP tunnel, and RoCEv2 tunnel.

[0121] For example, the flow control type, data encryption type, and data retransmission type mentioned above can be determined based on transmission requirements (e.g., reliability, security) and the capabilities of the first and third nodes. Taking reliability as an example, whether to introduce retransmission and which type of retransmission mechanism to use can be determined based on different reliability requirements. For instance, for data stream transmissions with low reliability requirements but high latency requirements, transmission can be performed based on UC transmission mode using the retransmission mechanism of the RoCE v2 transport layer, which can be disabled. For data stream transmissions with high reliability requirements but low latency sensitivity, the RC transmission mode of RoCE v2 can be enabled for selective retransmission based on selective requests. For data stream transmissions with particularly high reliability requirements, two data transmission channels can be configured for duplication-based transmission, etc.

[0122] Step 602: Send the second message to the second node.

[0123] Here, the second message is used to respond to the remote direct memory access transmission channel established between the first node and the third node.

[0124] In some embodiments, the second message includes remote direct memory access transport channel configuration information on the first node side.

[0125] In one example, the configuration information of the remote direct memory access transport channel on the first node side includes at least one of the following: the QPN on the first node side, the PSN on the first node side, the GID of the first node, and the address information corresponding to the first node.

[0126] After receiving the first message, the first node can determine whether it can support the corresponding data transmission request and the corresponding transmission channel configuration. For example, the first node can send a second message to the second node in response to the established remote direct memory access transmission channel, and provide the second node with its own relevant remote direct memory access transmission channel configuration information to facilitate communication configuration by the peer. The relevant parameters in the configuration information can be referred to step 601 above, and will not be elaborated further.

[0127] Based on the above technical solution, in this embodiment of the present disclosure, the first node can receive a first message from the second node. This first message requests the establishment of a remote direct memory access (RDA) transmission channel between the first node and the third node. Subsequently, the first node can send a second message to the second node. This second message responds to the establishment of the RDA transmission channel between the first node and the third node. Thus, this embodiment of the present disclosure can configure a RDA transmission channel between the first node and the third node, thereby enabling data transmission via RDA. Compared with current data transmission methods in communication systems, this method can directly read and write data from device memory, reducing processing operations during data transmission and improving transmission efficiency.

[0128] In one embodiment, the address information corresponding to the above-mentioned node includes at least one of the following: the node's communication address, port, and data subscription identifier.

[0129] For example, for regular data transmission between two nodes, the nodes can transmit data using the communication address (e.g., IP address) and port of the peer node. For subscription / notification type data transmission, the subscribed data can be obtained through a data subscription identifier. By carrying different types of address information, the technical solution provided in this disclosure is applicable to various transmission modes.

[0130] In one embodiment, the first message and the second message may also carry relevant configuration information of the data to be transmitted.

[0131] In some embodiments, the first message includes data transmission request information.

[0132] Here, the data transmission request information includes at least one of the following: network slice identifier, data type, data identifier, QoS requirements, data reporting cycle, and data reporting event trigger threshold.

[0133] For example, the data type includes at least one of the following: AI data, perception data, and other data besides AI data and perception data.

[0134] Here, AI data includes at least one of the following: AI models, AI training data, AI inference data, AI analysis data, and AI performance data. Perception data includes at least one of the following: communication perception data, environmental perception data, and target object perception data.

[0135] In some embodiments, the second message includes data information that allows transmission and / or data information that rejects transmission.

[0136] Here, the data information that is allowed to be transmitted includes at least one of the following: the data type that is allowed to be transmitted, and the data identifier that is allowed to be transmitted. The data information that is denied to be transmitted includes at least one of the following: the data type that is denied to be transmitted, the data identifier that is denied to be transmitted, and the reason for denial.

[0137] For example, the rejection reason information can be indicated by a numerical value. Nodes can be pre-configured to correspond to numerical values ​​and rejection reasons, thereby determining the rejection reason based on the received numerical value.

[0138] In one embodiment, the remote direct memory access transmission channel in this disclosure can be configured with different granularities according to actual conditions to adapt to different transmission requirements.

[0139] In some embodiments, the granularity of the remote direct memory access transport channel for transmitting corresponding data includes at least one of the following: per node, per slice, per UE, per data type, per QoS type, and per notification / subscription ID.

[0140] Taking data subscription as an example, each data subscription ID corresponds to an independent transmission channel. This fine-grained data granularity can better guarantee QoS. When there are a large number of data subscriptions, and each subscription only transmits a small amount of data occasionally or over very long periods, a relatively coarse-grained transmission channel can be used. For example, a transmission channel based on QoS type or data type granularity. Data of the same data type or the same QoS type can be mapped to the same transmission channel. For data streams with different QoS types, they can be mapped to different transmission channels based on QoS characteristics (reliability, latency, priority).

[0141] For example, as shown in Figure 7, QoS type = 1 corresponds to one transmission channel, and QoS type = 2 corresponds to one transmission channel. Data with data identifiers 1, 2, and 3 are transmitted through the transmission channel corresponding to QoS type = 1, while data with data identifiers 4 and 5 are transmitted through the transmission channel corresponding to QoS type = 2.

[0142] In some embodiments, when the granularity of the remote direct memory access transport channel used to transmit corresponding data is QoS type, data of the same data type or QoS type is mapped to the same remote direct memory access transport channel, and data of different QoS types is mapped to different remote direct memory access channels according to QoS characteristics.

[0143] In some embodiments, the first node and the second node may also report their capabilities before configuring communication, so that both parties can determine the capabilities of the other node. Referring to the embodiment shown in Figure 6, as shown in Figure 8, the method further includes steps 801 and / or 802.

[0144] Step 801: Send the capability information corresponding to the first node to the second node.

[0145] Step 802: Receive capability information corresponding to the third node from the second node.

[0146] Here, the capability information can carry capability information related to remote direct memory access, capability information related to data transmission, and other capability information required for communication.

[0147] In some embodiments, the capability information includes remote direct memory access capability information of the node. The remote direct memory access capability information is used to indicate at least one of the following:

[0148] 5-1. Does this node support remote direct memory access?

[0149] 5-2. The types of remote direct memory access supported by this node;

[0150] 5-3. Does this node support flow control?

[0151] 5-4. The types of flow control supported by this node;

[0152] 5-5. Does this node support data encryption?

[0153] 5-6. The types of data encryption supported by this node;

[0154] 5-7. Does this node support data retransmission?

[0155] 5-8. Data retransmission types supported by this node.

[0156] It should be understood that during the capability reporting process, a node reports whether it supports the relevant capability and the type of capability it supports. In the communication configuration process described in the above embodiments, the node indicates the type of transmission channel configured. Related descriptions can be found in the descriptions in the above embodiments, and will not be repeated here.

[0157] For example, before communication configuration, the first node and the second node can determine whether the first node and the third node have remote direct memory access capabilities through capability reporting. Only when both the first node and the third node have remote direct memory access capabilities will a remote direct memory access transmission channel be configured for data transmission.

[0158] In some embodiments, the capability information includes data transmission capability information of the node. The data transmission capability information is used to indicate at least one of the following:

[0159] 6-1. Data types supported by this node;

[0160] 6-2. The QoS types supported by this node;

[0161] 6-3. Size of the maximum transmission unit;

[0162] 6-4. Does this node support data compression?

[0163] 6-5. Data compression types supported by this node.

[0164] The relevant descriptions can be found in the above embodiments, and will not be repeated here.

[0165] In one embodiment, the above-described communication configuration and capability reporting process can be carried out using the same message carrier.

[0166] In some embodiments, the first message includes capability information corresponding to the third node, and / or the second message includes capability information corresponding to the first node.

[0167] For example, for a transmission channel with nodes as the granularity, the relevant configuration information of the transmission channel can be carried along when the two nodes report their capability information, thereby improving configuration efficiency.

[0168] In some embodiments, the remote direct memory access transport channel is a transport channel based on a first protocol stack. For example, the first protocol stack can be the GTP over RoCE v2 protocol stack shown in Figure 3 above.

[0169] In some embodiments, the first protocol stack includes at least one of the following: PDU layer, GTP layer, IB transport layer, UDP / IP layer, and Ethernet link layer.

[0170] In some embodiments, the GTP layer subheader includes TEID and / or QoSQFI information associated with the data packet; and / or, the DSCP in the IP layer subheader is configured based on the QoS flow associated with the data packet; and / or, data on the remote direct memory access transport channel is transmitted after being encapsulated by the GTP layer, IB transport layer, UDP / IP layer, and Ethernet link layer.

[0171] In some embodiments, the remote direct memory access transport channel is a transport channel based on a second protocol stack. For example, the second protocol stack can be the RoCEv2-based protocol stack shown in Figure 4 above.

[0172] In some embodiments, the second protocol stack includes at least one of the following: application layer, data layer, IB transport layer, UDP / IP layer, and Ethernet link layer.

[0173] In some embodiments, the application layer includes at least one of the following: Hypertext Transfer Protocol (HTTP) layer, File Transfer Protocol (FTP) layer, Remote Procedure Call (gRPC) layer, WebRTC layer, Message Queuing Telemetry Transport (MQTT) layer, WebSocket layer, and CoAP layer.

[0174] In some embodiments, the data layer subheader includes at least one of the following: data type, data identifier, data length, QoS indication, protocol type, whether encrypted, whether compressed, timestamp, terminal identifier, source node identifier, source node port number, one or more target node identifiers, target node port number, data identifier, subscriber identifier, and notification identifier.

[0175] For example, the data type can be one of the following: AI data, perception data, or other data. If it is an AI data type, the data layer subheading also includes at least one of the following: AI data identifier, AI model type information, AI training data type information, AI inference data type information, AI analysis type information, AI model performance type information, etc. If it is a perception data type, the data layer subheading may also include at least one of the following: perception data identifier, communication perception data type information, environment perception data type information, target object perception data type information, etc. The protocol identifier in the data layer subheading can be used to indicate the application layer protocol type. The timestamp can be used to indicate at least one of the following: data generation time, data latency budget, etc.

[0176] In some embodiments, the data layer subheading further includes at least one of the following: a packet transmission sequence number, a request for acknowledgment indication, and a packet reception acknowledgment sequence number. This information can provide additional reliable data transmission guarantees through the data layer when the application layer data is of non-IP type.

[0177] Figure 9 is a flowchart of a communication configuration method provided in an embodiment of this disclosure, applied to a second node. As shown in Figure 9, the method includes the following steps:

[0178] Step 901: Send the first message to the first node.

[0179] Here, the first message is used to request the establishment of a remote direct memory access transmission channel between the first node and the third node.

[0180] In some embodiments, the second node and the third node are the same node, or the second node and the third node are different nodes.

[0181] In some embodiments, the first node, the second node, and the third node are any of the following nodes: access network node, core network node, network management node, and application node.

[0182] In one example, the access network node includes at least one of the following: RU, CU, DU, xNB.

[0183] The core network node includes at least one of the following: AMF network element, UPF network element, DPF network element, NWDAF network element, SF network element, and AF network element.

[0184] In some embodiments, the first message includes remote direct memory access transport channel configuration information on the third node side.

[0185] In one example, the configuration information of the remote direct memory access transmission channel on the third node side includes at least one of the following: remote direct memory access indication information, remote direct memory access type, QPN on the third node side, PSN on the third node side, GID of the third node, flow control type, data encryption type, data retransmission type, data transmission protocol stack, and address information corresponding to the third node.

[0186] For example, remote direct memory access types include at least one of the following: Infiniband, RoCE v1, RoCE v2, and iWARP. Flow control types include at least one of the following: global pause, priority-based flow control (PFC), explicit congestion notification (ECN), and data center quantified congestion notification (DCQCN). Data encryption types include at least one of the following: Internet Security (IPSec), data layer encryption, and application layer encryption. Data retransmission types include at least one of the following: go-back-to-N, selective retransmission, timeout retransmission, and link layer retransmission.

[0187] The relevant descriptions can be found in the above embodiments, and will not be repeated here.

[0188] Step 902: Receive the second message from the first node.

[0189] Here, the second message is used to respond to the remote direct memory access transmission channel established between the first node and the third node.

[0190] In some embodiments, the second message includes remote direct memory access transport channel configuration information on the first node side.

[0191] In one example, the configuration information of the remote direct memory access transport channel on the first node side includes at least one of the following: the QPN on the first node side, the PSN on the first node side, the GID of the first node, and the address information corresponding to the first node.

[0192] The relevant descriptions can be found in the above embodiments, and will not be repeated here.

[0193] In one embodiment, the address information corresponding to the node includes at least one of the following: the node's communication address, port, and data subscription identifier.

[0194] In one embodiment, the first message and the second message may also carry relevant configuration information of the data to be transmitted.

[0195] In some embodiments, the first message includes data transmission request information.

[0196] Here, the data transmission request information includes at least one of the following: network slice identifier, data type, data identifier, QoS requirements, data reporting cycle, and data reporting event trigger threshold.

[0197] In some embodiments, the second message includes data information that allows transmission and / or data information that rejects transmission.

[0198] Here, the data information that is allowed to be transmitted includes at least one of the following: the data type that is allowed to be transmitted, and the data identifier that is allowed to be transmitted. The data information that is denied to be transmitted includes at least one of the following: the data type that is denied to be transmitted, the data identifier that is denied to be transmitted, and the reason for denial.

[0199] In some embodiments, the granularity of the remote direct memory access transport channel for transmitting corresponding data includes at least one of the following: node, network slice, terminal, data type, QoS type, and data subscription.

[0200] In some embodiments, when the granularity of the remote direct memory access transport channel for transmitting corresponding data is QoS type, data of the same data type or QoS type is mapped to the same remote direct memory access transport channel, and data of different QoS types is mapped to different remote direct memory access channels according to QoS characteristics.

[0201] As one embodiment provided in this disclosure, the first node and the second node may also report their capabilities before configuring communication, so that both parties can determine the capabilities of the other node. Referring to the embodiment shown in Figure 9, as shown in Figure 10, the method further includes steps 1001 and / or 1002.

[0202] Step 1001: Receive capability information corresponding to the first node from the first node.

[0203] Step 1002: Send the capability information corresponding to the third node to the first node.

[0204] In some embodiments, the capability information includes remote direct memory access capability information of the node. The remote direct memory access capability information is used to indicate at least one of the following:

[0205] 7-1. Does the node support remote direct memory access?

[0206] 7-2. Remote direct memory access types supported by the node;

[0207] 7-3. Does the node support flow control?

[0208] 7-4. Flow control types supported by the node;

[0209] 7-5. Does the node support data encryption?

[0210] 7-6. Data encryption types supported by the node;

[0211] 7-7. Does the node support data retransmission?

[0212] 7-8. Data retransmission types supported by the node.

[0213] In some embodiments, the capability information includes data transmission capability information of the node; the data transmission capability information is used to indicate at least one of the following:

[0214] 8-1. Data types supported by the node;

[0215] 8-2. QoS types supported by the node;

[0216] 8-3. Size of the maximum transmission unit;

[0217] 8-4. Does the node support data compression?

[0218] 8-5. Data compression types supported by the node.

[0219] For example, the data types include at least one of the following: AI data, perception data, and other data besides AI data and perception data.

[0220] Here, AI data includes at least one of the following: AI models, AI training data, AI inference data, AI analysis data, and AI performance data. Perception data includes at least one of the following: communication perception data, environmental perception data, and target object perception data.

[0221] In some embodiments, the remote direct memory access transport channel is a transport channel based on a first protocol stack.

[0222] In some embodiments, the first protocol stack includes at least one of the following: PDU layer, GTP layer, IB transport layer, UDP / IP layer, and Ethernet link layer.

[0223] In some embodiments, the GTP layer subheader includes TEID and / or QFI information associated with the data packet; and / or, the DSCP in the IP layer subheader is based on the QoS flow configuration associated with the data packet; and / or, data on the remote direct memory access transport channel is transmitted after being encapsulated through the GTP layer, IB transport layer, UDP / IP layer, and Ethernet link layer.

[0224] In some embodiments, the first protocol stack is the GTP over RoCE v2 protocol stack.

[0225] In some embodiments, the remote direct memory access transport channel is a transport channel based on a second protocol stack.

[0226] In some embodiments, the second protocol stack includes at least one of the following: application layer, data layer, IB transport layer, UDP / IP layer, and Ethernet link layer.

[0227] In some embodiments, the application layer includes at least one of the following: HTTP layer, FTP layer, gRPC layer, webRTC layer, MQTT layer, WebSocket layer, and CoAP layer.

[0228] In some embodiments, the data layer subheading may further include at least one of the following: data type, data identifier, data length, QoS indication, protocol type, whether encrypted, whether compressed, timestamp, terminal identifier, source node identifier, source node port number, one or more target node identifiers, target node port number, data identifier, subscriber identifier, and notification identifier.

[0229] In some embodiments, the data layer subheading may further include at least one of the following: a data packet transmission sequence number, a request confirmation indication, and a data packet reception confirmation sequence number.

[0230] In some embodiments, the second protocol stack is a RoCEv2-based protocol stack.

[0231] The relevant descriptions can be found in the above embodiments, and will not be repeated here.

[0232] The overall process of the communication configuration method provided in this disclosure has been explained above. The implementation of the communication configuration method provided in this disclosure will be explained below using several application scenarios as examples.

[0233] In some embodiments, taking data transmission between the RAN and UPF as an example, as shown in Figure 11, the communication configuration method includes the following steps:

[0234] Step 1101: RAN and AMF / MME perform RDMA capability interaction.

[0235] For example, this application scenario could be the establishment or modification of a PDU session. Before adopting Remote Direct Memory Access (RDMA) transmission, the RAN node and AMF / MME could exchange user plane transmission capabilities. Only when both have RDMA capabilities can user plane data be transmitted subsequently using RDMA. For instance, the RAN can send user plane transmission capability information to core network elements such as the AMF when establishing an interface with the core network.

[0236] After receiving the RAN's user plane transmission capability information, the AMF can send this information to the SMF and / or UPF. After the SMF selects a UPF for the UE, the AMF can send the RAN's user plane transmission capability information to the UPF through the SMF.

[0237] Step 1102: The AMF / MME sends a PDU session establishment or modification request message to the RAN. Correspondingly, the RAN receives the PDU session establishment or modification request message from the AMF / MME.

[0238] Here, the PDU session establishment or modification request message can be the first message in the above embodiments.

[0239] For example, in a communication network, when a PDU session is established or modified, the AMF sends the QoS information of the corresponding PDU session's QoS flow and uplink user plane transport layer information to the RAN. Here, the uplink user plane transport layer information includes the UPF IP address information and TEID information of the GTP-U tunnel.

[0240] After capability exchange, the SMF and / or UPF can, based on the RAN's user plane transmission capability information, choose to configure an RDMA-based transmission channel when configuring the GTP-U tunnel between the RAN and UPF. For example, a RoCEv2-based GTP tunnel can be used. In this case, the PDU session establishment or modification request message sent by the AMF to the RAN may contain at least one of the following information: the UPF IP address information and TEID information of the uplink GTP-U tunnel, and RDMA-related configuration.

[0241] For example, a PDU session can be associated with one RDMA transport channel or multiple RDMA transport channels. For each RDMA transport channel, the RDMA-related configuration can include at least one of the following: whether RDMA is used, RDMA type, UPF-side QPN, UPF-side PSN, UPF-side GID, flow control type, encryption type, data retransmission type, etc.

[0242] Step 1103: The RAN sends a PDU session establishment or modification response message to the AMF / MME. Correspondingly, the AMF / MME receives the PDU session establishment or modification response message from the RAN.

[0243] Here, the PDU session establishment or modification response message can be the second message in the above embodiments.

[0244] The response message sent by the RAN to the AMF / MME may include downlink user plane transport layer information, which includes the IP address of the RAN node and TEID information.

[0245] After receiving a PDU session establishment or modification request message from the AMF / MME, the RAN can create or modify the corresponding PDU session and GTP tunnel accordingly, and send a PDU session establishment or modification response message to the AMF / MME. This PDU session establishment or modification response message may contain at least one of the following information: the downlink GTP-U tunnel's UPF IP address information and TEID information, and RDMA-related configurations.

[0246] For example, a PDU session can be associated with one RDMA transport channel or multiple RDMA transport channels. For each RDMA transport channel, the RDMA-related configuration can include at least one of the following: RAN-side QPN, RAN-side PSN, RAN-side GID, etc. The AMF can further send the PDU session establishment or modification response message to the SMF. The SMF can then send the content of the PDU session establishment or modification response message to the UPF.

[0247] Step 1104: RAN and UPF transmit data through the transmission channel.

[0248] After the RDMA transport channel is configured, the RAN and UPF can use the RDMA-based transport channel for user plane data transmission. For example, the RDMA transport channel can be a GTP over RoCE v2-based transport channel.

[0249] In some embodiments, taking data transmission between CU and DU as an example, as shown in Figure 12, the communication configuration method includes the following steps:

[0250] Step 1201: CU and DU perform RDMA capability interaction.

[0251] For example, in a CU / DU split architecture, user plane data can be transferred between the CU and DU. This application scenario can establish or modify the UE context. Before adopting remote direct memory access transport, the CU and DU can interact with user plane transport capabilities.

[0252] For example, the DU can send its user plane data transmission capability information to the CU. The CU can also send its user plane transmission capability information to the DU. Here, user plane transmission capability may include at least one of the following: whether RDMA is supported, the supported RDMA type, whether flow control is supported, the supported flow control type, whether encryption is supported, the supported encryption mechanism type, whether data retransmission is supported, and the supported data retransmission type, etc.

[0253] Step 1202: The CU sends a UE context establishment or modification request message to the DU. Correspondingly, the DU receives the UE context establishment or modification request message from the CU.

[0254] Here, the UE context establishment or modification request message can be the first message in the above embodiments.

[0255] In some embodiments, under the CU / DU split architecture, the UE context establishment or modification request message sent by the CU to the DU may include uplink user plane transport layer information corresponding to each DRB.

[0256] Here, the uplink username transport layer information includes the CU IP address and TEID information corresponding to the F1 transport bearer.

[0257] When the CU sends a UE context establishment or modification request message to the DU, the UE context establishment or modification request message contains at least one of the following information: DRB id, uplink user plane transport layer information, and RDMA related configuration information.

[0258] RDMA-related configuration information includes at least one of the following: whether RDMA is used, RDMA type, QPN on the CU side, PSN on the CU side, GID on the CU side, flow control type, data encryption type, data retransmission type, etc.

[0259] Step 1203: The DU sends a UE context establishment or modification response message to the CU. Correspondingly, the CU receives the UE context establishment or modification response message from the DU.

[0260] Here, the UE context establishment or modification response message can be the second message in the above embodiments.

[0261] The UE context establishment or modification response message sent by the DU to the CU may include downlink user plane transport layer information corresponding to each DRB.

[0262] Here, the downlink user plane transport layer information includes the IP address of the DU node and the TEID information.

[0263] After receiving the UE context establishment or modification request message from the CU, the DU can create or modify the corresponding DRB and GTP tunnel accordingly, and send a UE context establishment or modification response message to the CU. This UE context establishment or modification response message may contain at least one of the following information: the DU IP address information and TEID information of the downlink F1 transport bearer, and RDMA-related configuration. The RDMA-related configuration may contain at least one of the following information: the DU-side QPN, the DU-side PSN, the DU-side GID, etc.

[0264] Step 1204: CU and DU transmit data through the transmission channel.

[0265] After the RDMA transport channel is configured, user plane data transmission can be performed between the DU and CU using the RDMA-based transport channel. For example, the RDMA transport channel can be a GTP over RoCE v2-based transport channel.

[0266] As one embodiment of this disclosure, taking data transmission between the RAN and SF as an example, the RAN can send the sensed data to the SF via the DPF, or the RAN can directly send the sensed data to the SF. As shown in Figure 13, the communication configuration method includes the following steps:

[0267] Step 1301: RAN and SF perform RDMA capability interaction.

[0268] For example, a RAN with sensing capabilities can send sensing capability and / or data transmission capability information to the SF via the AMF.

[0269] Here, the data transmission capability information may include at least one of the following: supported data types, supported QoS types, whether RDMA is supported, supported RDMA types, MTU size, whether flow control is supported, supported flow control types, whether data encryption is supported, supported data encryption types, whether data retransmission is supported, supported data retransmission types, whether data compression is supported, and supported data compression types, etc.

[0270] Here, the data type includes at least one of the following: AI data, perception data, and other data. If it is AI data, the data type may also include at least one of the following: AI model, AI training data, AI inference data, AI analysis data, AI model performance data, etc. If it is perception data, the data type may also include at least one of the following: perception data identifier, perception data type. For example, perception data types include communication perception data, environmental perception data, target object perception data, etc.

[0271] Step 1302: SF selects the RAN for sensing.

[0272] After receiving a sensing request from a user or customer, the SF can determine which candidate RANs to participate in the sensing task based on the RAN's sensing capabilities and the sensing requirements, thereby instructing the selected RANs to execute subsequent sensing tasks. This requires establishing transmission channels between the RAN and DPF, as well as between the SF and DPF, to carry the sensing data. For example, the RAN and DPF can use a GTP over RoCEv2 protocol stack for transmission, and the DPF and SF can use a RoCEv2-based data transmission protocol stack for transmission.

[0273] Step 1303: The SF sends a data channel establishment or modification request message to the DPF. Correspondingly, the DPF receives the data channel establishment or modification request message from the SF.

[0274] For example, a data tunnel establishment or modification request message can be a data tunnel establishment / modification request message. This message may include at least one of the following: a sensing identifier, a slice identifier, a sensing data identifier, a data port number, a data IP address, data flow QoS information, and RDMA-related configuration between the DPF and SF. Here, the data IP address and data port number correspond to the RAN's IP address and the RAN-side sensing data port number. The RDMA-related configuration between the DPF and SF also includes information such as the SF-side QPN, the SF-side PSN, and the SF-side GID.

[0275] Step 1304: The DPF sends a data channel establishment or modification response message to the SF. Correspondingly, the SF receives the data channel establishment or modification response message from the DPF.

[0276] For example, the data tunnel establishment or modification response message can be a data tunnel establishment / modification response message.

[0277] After receiving a data channel establishment or modification request message, DPF can configure the transport channel between SF and DPF. DPF can also store the mapping relationship between data IP addresses and data ports and the transport channel.

[0278] The data channel establishment or modification response message may contain at least one of the following information: sensing identifier, slice identifier, sensing data identifier, transport channel transport layer information, and RDMA-related configuration between the DPF and SF. Here, the transport channel transport layer information includes the DPF-side IP address and TEID information. The RDMA-related configuration includes at least one of the following: whether RDMA is used, RDMA type, flow control type, encryption type, data retransmission type, DPF-side QPN, DPF-side PSN, and DPF-side GID. Through the above process, a transport channel between the SF and DPF can be established.

[0279] Step 1305: The SF sends a perception request message to the RAN. Correspondingly, the DPF receives the perception request message from the SF.

[0280] For example, the SF can send this perception request message to the RAN via the AMF. The perception request information includes perception task information and / or perception data reporting information. The perception request information may also include data transmission channel configuration information, which includes at least one of the following: slice information, perception data identifier, DPF-side IP address, DPF-side TEID, and RDMA-related configuration. The RDMA-related configuration may include at least one of the following: whether RDMA is used, RDMA type, flow control type, data encryption type, data retransmission type, DPF-side QPN, DPF-side PSN, DPF-side GID, etc.

[0281] Step 1306: The RAN sends a sensing response message to the SF. Correspondingly, the SF receives the sensing response message from the RAN.

[0282] After receiving a sensing request message from the SF via the AMF, the RAN can send a sensing response message to the SF through the AMF. This sensing response message may contain at least one of the following: acceptable sensing identifiers, unacceptable sensing identifiers and their reasons, the RAN-side IP address of the downlink GTP-U tunnel, the RAN-side TEID, and RDMA-related configurations. The RDMA-related configurations may contain at least one of the following: the RAN-side QPN, the RAN-side PSN, and the RAN-side GID.

[0283] Step 1307: The SF sends a data channel establishment or modification request message to the DPF. Correspondingly, the DPF receives the data channel establishment or modification request message from the SF.

[0284] For example, the SF can initiate a data channel establishment or modification procedure again based on the received sensing response message, informing the DPF of the GTP tunnel and / or RDMA-related configurations corresponding to the RAN side. This data channel establishment or modification request message may include the RDMA-related configurations between the RAN and the DPF.

[0285] Step 1308: The DPF sends a data channel establishment or modification response message to the SF. Correspondingly, the SF receives the data channel establishment or modification response message from the DPF.

[0286] For example, after receiving a data channel establishment or modification request message, the DPF can configure the transmission channel between the RAN and the DPF. The DPF can also store the mapping relationship between data IP addresses and data ports and the transmission channel. In this way, the transmission channels between the RAN and the DPF, and between the DPF and the SF, are all configured.

[0287] Step 1309: RAN performs sensing operations.

[0288] For example, the RAN performs sensing operations and acquires sensing data based on the received sensing configuration.

[0289] Step 1310: The RAN transmits sensing data between the DPF and SF.

[0290] When the sensing data reporting conditions are triggered, the RAN generates sensing data according to the sensing data format requirements and sends the sensing data to the DPF using a data channel based on GTP over RoCEv2. After receiving the sensing data, the DPF further sends the sensing data to the SF through the RoCEv2-based data channel.

[0291] In some embodiments, the RAN can also directly establish a transmission channel with the SF for data transmission. As shown in Figure 14, the communication configuration method includes the following steps:

[0292] Step 1401: RAN and SF perform RDMA capability interaction.

[0293] For related information, please refer to step 1301 above; it will not be repeated here.

[0294] Step 1402: SF selects the RAN for sensing.

[0295] For related information, please refer to step 1302 above; it will not be repeated here.

[0296] Step 1403: The SF sends a sensing request message to the RAN. Correspondingly, the DPF receives the sensing request message from the SF.

[0297] For related information, please refer to step 1305 above; it will not be repeated here.

[0298] Step 1404: The RAN sends a sensing response message to the SF. Correspondingly, the SF receives the sensing response message from the RAN.

[0299] For related information, please refer to step 1306 above; it will not be repeated here.

[0300] Step 1405: RAN performs sensing operations.

[0301] Step 1406: Sensing data is transmitted between RAN and SF.

[0302] It is understood that, in order to achieve the above-mentioned 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, based on the algorithmic steps of the examples described in conjunction with the embodiments of this disclosure, this disclosure can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in 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 disclosure.

[0303] This disclosure 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 functional module. The integrated module can be implemented in hardware or software. It should be noted that the module division in this disclosure embodiment is illustrative and only represents one logical functional division. In actual implementation, there may be other division methods. The following description uses the example of dividing each functional module according to each function.

[0304] For example, taking a communication device as the first node in the above method embodiment as an example, Figure 15 is a structural diagram of a first node 150 provided in an embodiment of this disclosure. The first node 150 can execute the communication configuration method provided in the above method embodiment. As shown in Figure 15, the first node 150 includes: a processing unit 1501 and a communication unit 1502.

[0305] The communication unit 1502 is used to receive a first message from the second node; the first message is used to request the establishment of a remote direct memory access transmission channel between the first node and the third node.

[0306] The communication unit 1502 is used to send a second message to the second node; the second message is used to respond to the remote direct memory access transmission channel established between the first node and the third node.

[0307] In some embodiments, the first message includes remote direct memory access transport channel configuration information on the third node side.

[0308] In some embodiments, the configuration information of the remote direct memory access transmission channel on the third node side includes at least one of the following: remote direct memory access indication information, remote direct memory access type, queue pair number (QPN) on the third node side, packet sequence number (PSN) on the third node side, global identifier (GID) of the third node, flow control type, data encryption type, data retransmission type, data transmission protocol stack, and address information corresponding to the third node.

[0309] In some embodiments, remote direct memory access types include at least one of the following:

[0310] Infiniband (unlimited bandwidth), RoCE v1 and RoCE v2 (remote direct memory access over aggregated Ethernet), and iWARP (Internet Wide Area Remote Direct Memory Access Protocol).

[0311] The flow control type includes at least one of the following: global pause, priority-based flow control (PFC), explicit congestion notification (ECN), and data center quantitative congestion notification (DCQCN).

[0312] Data encryption types include at least one of the following: Internet Security IPSec, data layer data encryption, and application layer data encryption;

[0313] Data retransmission types include at least one of the following: Go-Back-N, Selective Retransmission, Timeout Retransmission, and Link Layer Retransmission.

[0314] In some embodiments, the second message includes remote direct memory access transport channel configuration information on the first node side.

[0315] In some embodiments, the configuration information of the remote direct memory access transmission channel on the first node side includes at least one of the following: the QPN on the first node side, the PSN on the first node side, the GID of the first node, and the address information corresponding to the first node.

[0316] In some embodiments, the address information corresponding to a node includes at least one of the following: the node's communication address, port, and data subscription identifier.

[0317] In some embodiments, the first message includes data transmission request information; the data transmission request information includes at least one of the following: network slice identifier, data type, data identifier, quality of service (QoS) requirements, data reporting cycle, and data reporting event trigger threshold.

[0318] In some embodiments, the second message includes data information that allows transmission and / or data information that refuses transmission;

[0319] The data information that is allowed to be transmitted includes at least one of the following: the data type that is allowed to be transmitted, and the data identifier that is allowed to be transmitted;

[0320] The data information that is refused to be transmitted includes at least one of the following: the data type that is refused to be transmitted, the data identifier that is refused to be transmitted, and the reason for refusal.

[0321] In some embodiments, the granularity of the remote direct memory access transport channel for transmitting corresponding data includes at least one of the following: node, network slice, terminal, data type, QoS type, and data subscription.

[0322] In some embodiments, when the granularity of the remote direct memory access transport channel for transmitting corresponding data is QoS type, data of the same data type or QoS type is mapped to the same remote direct memory access transport channel, and data of different QoS types is mapped to different remote direct memory access channels according to QoS characteristics.

[0323] In some embodiments, the communication unit 1502 is configured to: send capability information corresponding to the first node to the second node; and / or receive capability information corresponding to the third node from the second node.

[0324] In some embodiments, the capability information includes remote direct memory access capability information of the node; the remote direct memory access capability information is used to indicate at least one of the following:

[0325] Does the node support remote direct memory access?

[0326] The types of remote direct memory access supported by the node;

[0327] Does the node support flow control?

[0328] The types of flow control supported by the node;

[0329] Does the node support data encryption?

[0330] The node supports the following data encryption types;

[0331] Does the node support data retransmission?

[0332] The types of data retransmission supported by the node.

[0333] In some embodiments, the capability information includes data transmission capability information of the node; the data transmission capability information is used to indicate at least one of the following:

[0334] The data types supported by the node;

[0335] The QoS types supported by the node;

[0336] The size of the maximum transmission unit;

[0337] Does the node support data compression?

[0338] The data compression types supported by the node.

[0339] In some embodiments, the data types supported by the node include at least one of the following: artificial intelligence (AI) data, perception data, and other data besides AI data and perception data;

[0340] Here, AI data includes at least one of the following: AI models, AI training data, AI inference data, AI analysis data, and AI performance data;

[0341] The sensing data includes at least one of the following: communication sensing data, environmental sensing data, and target object sensing data.

[0342] In some embodiments, the remote direct memory access transport channel is a transport channel based on a first protocol stack.

[0343] In some embodiments, the first protocol stack includes at least one of the following:

[0344] Protocol Data Unit (PDU) layer, General Packet Radio Service Tunneling Protocol (GTP) layer, IB transport layer, User Datagram Protocol (UDP) / Internet Protocol (IP) layer, and Ethernet link layer.

[0345] In some embodiments, the GTP layer subheader includes a tunnel endpoint identifier (TEID) and / or QoS flow identifier (QFI) information associated with the packet; and / or,

[0346] The Differential Service Code Point (DSCP) in the IP layer subheader is based on the QoS flow configuration associated with the packet; and / or,

[0347] Data on the remote direct memory access transmission channel is transmitted after being encapsulated by the GTP layer, IB transport layer, UDP / IP layer, and Ethernet link layer.

[0348] In some embodiments, the first protocol stack is the GTP over RoCE v2 protocol stack.

[0349] In some embodiments, the remote direct memory access transport channel is a transport channel based on a second protocol stack.

[0350] In some embodiments, the second protocol stack includes at least one of the following:

[0351] Application layer, data layer, IB transport layer, UDP / IP layer, Ethernet link layer.

[0352] In some embodiments, the application layer includes at least one of the following:

[0353] Hypertext Transfer Protocol (HTTP) layer, File Transfer Protocol (FTP) layer, Remote Procedure Call (gRPC) layer, WebRTC layer, Message Queuing Telemetry Transport (MQTT) layer, WebSocket layer, and CoAP layer.

[0354] In some embodiments, the data layer subheading also includes at least one of the following:

[0355] Data type, data identifier, data length, QoS indicator, protocol type, whether encrypted, whether compressed, timestamp, terminal identifier, source node identifier, source node port number, one or more target node identifiers, target node port number, data identifier, subscriber identifier, notification identifier.

[0356] In some embodiments, the data layer subheading also includes at least one of the following:

[0357] Data packet sending sequence number, request confirmation indication, data packet receiving confirmation sequence number.

[0358] In some embodiments, the second protocol stack is a RoCEv2-based protocol stack.

[0359] In some embodiments, the second node and the third node are the same node, or the second node and the third node are different nodes.

[0360] In some embodiments, the first node, the second node, and the third node are any of the following nodes: access network node, core network node, network management node, and application node.

[0361] In some embodiments, the access network node includes at least one of the following: radio frequency unit RU, centralized unit CU, distributed unit DU, and next-generation base station xNB;

[0362] The core network node includes at least one of the following: Mobility Management Function (AMF) network element, User Plane Function (UPF) network element, Data Plane Function (DPF) network element, Network Data Analysis Function (NWDAF) network element, Sensing Function (SF) network element, and Application Function (AF) network element.

[0363] For example, taking a communication device as the second node in the above method embodiment, Figure 16 is a structural diagram of a second node 160 provided in an embodiment of this disclosure. The second node 160 can execute the communication configuration method provided in the above method embodiment. As shown in Figure 16, the second node 160 includes a processing unit 1601 and a communication unit 1602.

[0364] The communication unit 1602 is used to send a first message to the first node; the first message is used to request the establishment of a remote direct memory access transmission channel between the first node and the third node.

[0365] The communication unit 1602 is used to receive a second message from the first node; the second message is used to respond to the remote direct memory access transmission channel established between the first node and the third node.

[0366] In some embodiments, the first message includes remote direct memory access transport channel configuration information on the third node side.

[0367] In some embodiments, the configuration information of the remote direct memory access transmission channel on the third node side includes at least one of the following: remote direct memory access indication information, remote direct memory access type, queue pair number (QPN) on the third node side, packet sequence number (PSN) on the third node side, global identifier (GID) of the third node, flow control type, data encryption type, data retransmission type, data transmission protocol stack, and address information corresponding to the third node.

[0368] In some embodiments, remote direct memory access types include at least one of the following:

[0369] Infiniband (unlimited bandwidth), RoCE v1 and RoCE v2 (remote direct memory access over aggregated Ethernet), and iWARP (Internet Wide Area Remote Direct Memory Access Protocol).

[0370] The flow control type includes at least one of the following: global pause, priority-based flow control (PFC), explicit congestion notification (ECN), and data center quantitative congestion notification (DCQCN).

[0371] Data encryption types include at least one of the following: Internet Security IPSec, data layer data encryption, and application layer data encryption;

[0372] Data retransmission types include at least one of the following: Go-Back-N, Selective Retransmission, Timeout Retransmission, and Link Layer Retransmission.

[0373] In some embodiments, the second message includes remote direct memory access transport channel configuration information on the first node side.

[0374] In some embodiments, the configuration information of the remote direct memory access transmission channel on the first node side includes at least one of the following: the QPN on the first node side, the PSN on the first node side, the GID of the first node, and the address information corresponding to the first node.

[0375] In some embodiments, the address information corresponding to a node includes at least one of the following: the node's communication address, port, and data subscription identifier.

[0376] In some embodiments, the first message includes data transmission request information; the data transmission request information includes at least one of the following: network slice identifier, data type, data identifier, quality of service (QoS) requirements, data reporting cycle, and data reporting event trigger threshold.

[0377] In some embodiments, the second message includes data information that allows transmission and / or data information that refuses transmission;

[0378] The data information that is allowed to be transmitted includes at least one of the following: the data type that is allowed to be transmitted, and the data identifier that is allowed to be transmitted;

[0379] The data information that is refused to be transmitted includes at least one of the following: the data type that is refused to be transmitted, the data identifier that is refused to be transmitted, and the reason for refusal.

[0380] In some embodiments, the granularity of the remote direct memory access transport channel for transmitting corresponding data includes at least one of the following: node, network slice, terminal, data type, QoS type, and data subscription.

[0381] In some embodiments, when the granularity of the remote direct memory access transport channel for transmitting corresponding data is QoS type, data of the same data type or QoS type is mapped to the same remote direct memory access transport channel, and data of different QoS types is mapped to different remote direct memory access channels according to QoS characteristics.

[0382] In some embodiments, the communication unit 1602 is configured to: receive capability information corresponding to the first node from the first node; and / or send capability information corresponding to the third node to the first node.

[0383] In some embodiments, the capability information includes remote direct memory access capability information of the node; the remote direct memory access capability information is used to indicate at least one of the following:

[0384] Does the node support remote direct memory access?

[0385] The types of remote direct memory access supported by the node;

[0386] Does the node support flow control?

[0387] The types of flow control supported by the node;

[0388] Does the node support data encryption?

[0389] The node supports the following data encryption types;

[0390] Does the node support data retransmission?

[0391] The types of data retransmission supported by the node.

[0392] In some embodiments, the capability information includes data transmission capability information of the node; the data transmission capability information is used to indicate at least one of the following:

[0393] The data types supported by the node;

[0394] The QoS types supported by the node;

[0395] The size of the maximum transmission unit;

[0396] Does the node support data compression?

[0397] The data compression types supported by the node.

[0398] In some embodiments, the data types supported by the node include at least one of the following: artificial intelligence (AI) data, perception data, and other data besides AI data and perception data;

[0399] Here, AI data includes at least one of the following: AI models, AI training data, AI inference data, AI analysis data, and AI performance data;

[0400] The sensing data includes at least one of the following: communication sensing data, environmental sensing data, and target object sensing data.

[0401] In some embodiments, the remote direct memory access transport channel is a transport channel based on a first protocol stack.

[0402] In some embodiments, the first protocol stack includes at least one of the following:

[0403] Protocol Data Unit (PDU) layer, General Packet Radio Service Tunneling Protocol (GTP) layer, IB transport layer, User Datagram Protocol (UDP) / Internet Protocol (IP) layer, and Ethernet link layer.

[0404] In some embodiments, the GTP layer subheader includes a tunnel endpoint identifier (TEID) and / or QoS flow identifier (QFI) information associated with the packet; and / or,

[0405] The Differential Service Code Point (DSCP) in the IP layer subheader is based on the QoS flow configuration associated with the packet; and / or,

[0406] Data on the remote direct memory access transmission channel is transmitted after being encapsulated by the GTP layer, IB transport layer, UDP / IP layer, and Ethernet link layer.

[0407] In some embodiments, the first protocol stack is the GTP over RoCE v2 protocol stack.

[0408] In some embodiments, the remote direct memory access transport channel is a transport channel based on a second protocol stack.

[0409] In some embodiments, the second protocol stack includes at least one of the following:

[0410] Application layer, data layer, IB transport layer, UDP / IP layer, Ethernet link layer.

[0411] In some embodiments, the application layer includes at least one of the following:

[0412] Hypertext Transfer Protocol (HTTP) layer, File Transfer Protocol (FTP) layer, Remote Procedure Call (gRPC) layer, WebRTC layer, Message Queuing Telemetry Transport (MQTT) layer, WebSocket layer, and CoAP layer.

[0413] In some embodiments, the data layer subheading also includes at least one of the following:

[0414] Data type, data identifier, data length, QoS indicator, protocol type, whether encrypted, whether compressed, timestamp, terminal identifier, source node identifier, source node port number, one or more target node identifiers, target node port number, data identifier, subscriber identifier, notification identifier.

[0415] In some embodiments, the data layer subheading also includes at least one of the following:

[0416] Data packet sending sequence number, request confirmation indication, data packet receiving confirmation sequence number.

[0417] In some embodiments, the second protocol stack is a RoCEv2-based protocol stack.

[0418] In some embodiments, the second node and the third node are the same node, or the second node and the third node are different nodes.

[0419] In some embodiments, the first node, the second node, and the third node are any of the following nodes: access network node, core network node, network management node, and application node.

[0420] In some embodiments, the access network node includes at least one of the following: radio frequency unit RU, centralized unit CU, distributed unit DU, and next-generation base station xNB;

[0421] The core network node includes at least one of the following: Mobility Management Function (AMF) network element, User Plane Function (UPF) network element, Data Plane Function (DPF) network element, Network Data Analysis Function (NWDAF) network element, Sensing Function (SF) network element, and Application Function (AF) network element.

[0422] In the case of implementing the functions of the integrated modules described above in hardware, this disclosure provides another structure of the communication device involved in the above embodiments. As shown in FIG17, the communication device 170 includes a processor 1702 and a bus 1704. In some embodiments, the communication device 170 may further include a memory 1701; in some embodiments, the communication device 170 may further include a communication interface 1703.

[0423] Processor 1702 may implement or execute various exemplary logic blocks, modules, and circuits described in conjunction with embodiments of this disclosure. Processor 1702 may be a central processing unit, a general-purpose processor, a digital signal processor, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It may implement or execute various exemplary logic blocks, modules, and circuits described in conjunction with embodiments of this disclosure. Processor 1702 may also be a combination of functions implementing computational capabilities, such as a combination of one or more microprocessors, a digital signal processor (DSP), and a microprocessor.

[0424] The communication interface 1703 is used to connect to other devices via a communication network. This communication network can be Ethernet, wireless access network, wireless local area network (WLAN), etc.

[0425] The memory 1701 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 electrically erasable programmable read-only memory (EEPROM), 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 is not limited thereto.

[0426] In one embodiment, the memory 1701 may exist independently of the processor 1702. The memory 1701 may be connected to the processor 1702 via a bus 1704 and may be used to store instructions or program code. When the processor 1702 calls and executes the instructions or program code stored in the memory 1701, it may implement the method described in any embodiment of this disclosure.

[0427] In another embodiment, the memory 1701 may also be integrated with the processor 1702.

[0428] Bus 1704 can be an extended industry standard architecture (EISA) bus, etc. Bus 1704 can be divided into address bus, data bus, control bus, etc. For ease of illustration, only one thick line is used to represent it in Figure 17, but this does not mean that there is only one bus or one type of bus.

[0429] Some embodiments of this disclosure provide a computer-readable storage medium (e.g., a non-transitory computer-readable storage medium) storing computer program instructions that, when executed on a computer, cause the computer to perform the methods described in any of the above embodiments.

[0430] Exemplary examples show that the aforementioned computer-readable storage media may include, but are not limited to: magnetic storage devices (e.g., hard disks, floppy disks, or magnetic tapes), optical discs (e.g., compact disks (CDs), digital versatile disks (DVDs), etc.), smart cards, and flash memory devices (e.g., erasable programmable read-only memory (EPROMs), cards, sticks, or key drives, etc.). The various computer-readable storage media described in this disclosure may represent one or more devices for storing information and / or other machine-readable storage media. The term "machine-readable storage media" may include, but is not limited to, wireless channels and various other media capable of storing, containing, and / or carrying instructions and / or data.

[0431] This disclosure provides a computer program product containing instructions that, when run on a computer, cause the computer to perform the methods described in any of the above embodiments.

[0432] The above description is merely a specific embodiment of this disclosure, but the scope of protection of this disclosure is not limited thereto. Any changes or substitutions within the technical scope disclosed in this disclosure should be included within the scope of protection of this disclosure. Therefore, the scope of protection of this disclosure should be determined by the scope of the claims.

Claims

1. A communication configuration method, characterized in that, Applied to the first node, the method includes: Receive a first message from the second node; the first message is used to request the establishment of a remote direct memory access transmission channel between the first node and the third node; Send a second message to the second node; the second message is used to respond to the remote direct memory access transmission channel established between the first node and the third node.

2. The method according to claim 1, characterized in that, The first message includes configuration information for the remote direct memory access transport channel on the third node side.

3. The method according to claim 2, characterized in that, The configuration information of the remote direct memory access transmission channel on the third node side includes at least one of the following: Remote direct memory access indication information, remote direct memory access type, queue pair number (QPN) on the third node side, packet sequence number (PSN) on the third node side, global identifier (GID) of the third node, flow control type, data encryption type, data retransmission type, data transmission protocol stack, and address information corresponding to the third node.

4. The method according to claim 3, characterized in that, The remote direct memory access type includes at least one of the following: Infiniband (unlimited bandwidth), RoCE v1 and RoCE v2 (remote direct memory access over aggregated Ethernet), and iWARP (Internet Wide Area Remote Direct Memory Access Protocol). The flow control type includes at least one of the following: Global pause, priority-based flow control, explicit congestion notification (ECN), and data center quantitative congestion notification (DCQCN); The data encryption type includes at least one of the following: IPSec, an internet security platform, provides data encryption at both the data layer and the application layer. The data retransmission type includes at least one of the following: Go-back N, selective retransmission, timeout retransmission, link layer retransmission.

5. The method according to claim 1, characterized in that, The second message includes configuration information for the remote direct memory access transport channel on the first node side.

6. The method according to claim 5, characterized in that, The configuration information of the remote direct memory access transport channel on the first node side includes at least one of the following: The QPN on the first node side, the PSN on the first node side, the GID of the first node, and the address information corresponding to the first node.

7. The method according to claim 3 or 6, characterized in that, The address information corresponding to the node includes at least one of the following: The node's communication address, port, and data subscription identifier.

8. The method according to claim 1, characterized in that, The first message includes data transmission request information; The data transmission request information includes at least one of the following: Network slice identifier, data type, data identifier, Quality of Service (QoS) requirements, data reporting cycle, and data reporting event trigger threshold.

9. The method according to claim 1, characterized in that, The second message includes data information that allows transmission and / or data information that denies transmission; The permitted data information includes at least one of the following: Permitted data types and permitted data identifiers; The data information that is refused to be transmitted includes at least one of the following: The data type that was refused transmission, the identifier of the data that was refused transmission, and the reason for the refusal.

10. The method according to claim 1, characterized in that, The granularity at which the remote direct memory access transmission channel transmits the corresponding data includes at least one of the following: Nodes, network slices, terminals, data types, QoS types, and data subscriptions.

11. The method according to claim 10, characterized in that, When the granularity of the corresponding data transmitted by the remote direct memory access transmission channel is QoS type, data of the same data type or QoS type are mapped to the same remote direct memory access transmission channel, and data of different QoS types are mapped to different remote direct memory access channels according to QoS characteristics.

12. The method according to claim 1, characterized in that, The method further includes: Send the capability information corresponding to the first node to the second node; and / or receive the capability information corresponding to the third node from the second node.

13. The method according to claim 12, characterized in that, The capability information includes the node's remote direct memory access capability information; the remote direct memory access capability information is used to indicate at least one of the following: Does the node support remote direct memory access? The node supports the following remote direct memory access types; Does the node support flow control? The node supports the following flow control types; Does the node support data encryption? The node supports the following data encryption types; Does the node support data retransmission? The node supports the following data retransmission types.

14. The method according to claim 12, characterized in that, The capability information includes the node's data transmission capability information; the data transmission capability information is used to indicate at least one of the following: The data types supported by the node; The QoS types supported by the node; The size of the maximum transmission unit; Does the node support data compression? The node supports the following data compression types.

15. The method according to claim 14, characterized in that, The data types supported by the node include at least one of the following: Artificial intelligence (AI) data, sensory data, and other data besides the AI ​​data and sensory data mentioned above; Here, the AI ​​data includes at least one of the following: AI models, AI training data, AI inference data, AI analysis data, AI performance data; The sensed data includes at least one of the following: Communication-sensing data, environmental-sensing data, and target-object-sensing data.

16. The method according to claim 1, characterized in that, The remote direct memory access transmission channel is a transmission channel based on the first protocol stack.

17. The method according to claim 16, characterized in that, The first protocol stack includes at least one of the following: Protocol Data Unit (PDU) layer, General Packet Radio Service Tunneling Protocol (GTP) layer, IB transport layer, User Datagram Protocol (UDP) / Internet Protocol (IP) layer, and Ethernet link layer.

18. The method according to claim 17, characterized in that, The GTP layer subheader includes a tunnel endpoint identifier (TEID) and / or QoS flow identifier (QFI) information associated with the data packet; and / or, The Differential Service Code Point (DSCP) in the IP layer subheader is based on the QoS flow configuration associated with the packet; And / or, Data on the remote direct memory access transmission channel is transmitted after being encapsulated by the GTP layer, the IB transport layer, the UDP / IP layer, and the Ethernet link layer.

19. The method according to claim 16, characterized in that, The first protocol stack is the GTP over RoCE v2 protocol stack.

20. The method according to claim 1, characterized in that, The remote direct memory access transmission channel is a transmission channel based on the second protocol stack.

21. The method according to claim 20, characterized in that, The second protocol stack includes at least one of the following: Application layer, data layer, IB transport layer, UDP / IP layer, Ethernet link layer.

22. The method according to claim 21, characterized in that, The application layer includes at least one of the following: Hypertext Transfer Protocol (HTTP) layer, File Transfer Protocol (FTP) layer, Remote Procedure Call (gRPC) layer, WebRTC layer, Message Queuing Telemetry Transport (MQTT) layer, WebSocket layer, and CoAP layer.

23. The method according to claim 21, characterized in that, The data layer subheader includes at least one of the following: Data type, data identifier, data length, QoS indicator, protocol type, whether encrypted, whether compressed, timestamp, terminal identifier, source node identifier, source node port number, one or more target node identifiers, target node port number, data identifier, subscriber identifier, notification identifier.

24. The method according to claim 23, characterized in that, The data layer subheader also includes at least one of the following: Data packet sending sequence number, request confirmation indication, data packet receiving confirmation sequence number.

25. The method according to claim 20, characterized in that, The second protocol stack is a RoCEv2-based protocol stack.

26. The method according to claim 1, characterized in that, The second node and the third node are the same node, or the second node and the third node are different nodes.

27. The method according to claim 1, characterized in that, The first node, the second node, and the third node are any of the following nodes: Access network nodes, core network nodes, network management nodes, and application nodes.

28. The method according to claim 27, characterized in that, The access network node includes at least one of the following: Radio frequency unit (RU), centralized unit (CU), distributed unit (DU), next-generation base station (xNB); The core network node includes at least one of the following: Mobility Management Function (AMF) network element, User Plane Function (UPF) network element, Data Plane Function (DPF) network element, Network Data Analysis Function (NWDAF) network element, Sensing Function (SF) network element, and Application Function (AF) network element.

29. A communication configuration method, characterized in that, Applied to the second node, the method includes: Send a first message to the first node; the first message is used to request the establishment of a remote direct memory access transmission channel between the first node and the third node; Receive a second message from the first node; the second message is used to respond to the remote direct memory access transmission channel established between the first node and the third node.

30. The method according to claim 29, characterized in that, The first message includes configuration information for the remote direct memory access transport channel on the third node side.

31. The method according to claim 30, characterized in that, The configuration information of the remote direct memory access transmission channel on the third node side includes at least one of the following: Remote direct memory access indication information, remote direct memory access type, queue pair number (QPN) on the third node side, packet sequence number (PSN) on the third node side, global identifier (GID) of the third node, flow control type, data encryption type, data retransmission type, data transmission protocol stack, and address information corresponding to the third node.

32. The method according to claim 31, characterized in that, The remote direct memory access type includes at least one of the following: Infiniband (unlimited bandwidth), RoCE v1 and RoCE v2 (remote direct memory access over aggregated Ethernet), and iWARP (Internet Wide Area Remote Direct Memory Access Protocol). The flow control type includes at least one of the following: Global pause, priority-based flow control, explicit congestion notification (ECN), and data center quantitative congestion notification (DCQCN); The data encryption type includes at least one of the following: IPSec, an internet security platform, provides data encryption at both the data layer and the application layer. The data retransmission type includes at least one of the following: Go-back N, selective retransmission, timeout retransmission, link layer retransmission.

33. The method according to claim 29, characterized in that, The second message includes configuration information for the remote direct memory access transport channel on the first node side.

34. The method according to claim 33, characterized in that, The configuration information of the remote direct memory access transport channel on the first node side includes at least one of the following: The QPN on the first node side, the PSN on the first node side, the GID of the first node, and the address information corresponding to the first node.

35. The method according to claim 31 or 34, characterized in that, The address information corresponding to the node includes at least one of the following: The node's communication address, port, and data subscription identifier.

36. The method according to claim 29, characterized in that, The first message includes data transmission request information; The data transmission request information includes at least one of the following: Network slice identifier, data type, data identifier, Quality of Service (QoS) requirements, data reporting cycle, and data reporting event trigger threshold.

37. The method according to claim 29, characterized in that, The second message includes data information that allows transmission and / or data information that denies transmission; The permitted data information includes at least one of the following: Permitted data types and permitted data identifiers; The data information that is refused to be transmitted includes at least one of the following: The data type that was refused transmission, the identifier of the data that was refused transmission, and the reason for the refusal.

38. The method according to claim 29, characterized in that, The granularity at which the remote direct memory access transmission channel transmits the corresponding data includes at least one of the following: Nodes, network slices, terminals, data types, QoS types, and data subscriptions.

39. The method according to claim 38, characterized in that, When the granularity of the corresponding data transmitted by the remote direct memory access transmission channel is QoS type, data of the same data type or QoS type are mapped to the same remote direct memory access transmission channel, and data of different QoS types are mapped to different remote direct memory access channels according to QoS characteristics.

40. The method according to claim 29, characterized in that, The method further includes: Receive capability information corresponding to the first node from the first node; and / or send capability information corresponding to the third node to the first node.

41. The method according to claim 40, characterized in that, The capability information includes the node's remote direct memory access capability information; the remote direct memory access capability information is used to indicate at least one of the following: Does the node support remote direct memory access? The node supports the following remote direct memory access types; Does the node support flow control? The node supports the following flow control types; Does the node support data encryption? The node supports the following data encryption types; Does the node support data retransmission? The node supports the following data retransmission types.

42. The method according to claim 40, characterized in that, The capability information includes the node's data transmission capability information; the data transmission capability information is used to indicate at least one of the following: The data types supported by the node; The QoS types supported by the node; The size of the maximum transmission unit; Does the node support data compression? The node supports the following data compression types.

43. The method according to claim 42, characterized in that, The data types supported by the node include at least one of the following: Artificial intelligence (AI) data, sensory data, and other data besides the AI ​​data and sensory data mentioned above; Here, the AI ​​data includes at least one of the following: AI models, AI training data, AI inference data, AI analysis data, AI performance data; The sensed data includes at least one of the following: Communication-sensing data, environmental-sensing data, and target-object-sensing data.

44. The method according to claim 29, characterized in that, The remote direct memory access transmission channel is a transmission channel based on the first protocol stack.

45. The method according to claim 44, characterized in that, The first protocol stack includes at least one of the following: Protocol Data Unit (PDU) layer, General Packet Radio Service Tunneling Protocol (GTP) layer, IB transport layer, User Datagram Protocol (UDP) / Internet Protocol (IP) layer, and Ethernet link layer.

46. ​​The method according to claim 45, characterized in that, The GTP layer subheader includes a tunnel endpoint identifier (TEID) and / or QoS flow identifier (QFI) information associated with the data packet; and / or, The Differential Service Code Point (DSCP) in the IP layer subheader is based on the QoS flow configuration associated with the packet; And / or, Data on the remote direct memory access transmission channel is transmitted after being encapsulated by the GTP layer, the IB transport layer, the UDP / IP layer, and the Ethernet link layer.

47. The method according to claim 44, characterized in that, The first protocol stack is the GTP over RoCE v2 protocol stack.

48. The method according to claim 29, characterized in that, The remote direct memory access transmission channel is a transmission channel based on the second protocol stack.

49. The method according to claim 48, characterized in that, The second protocol stack includes at least one of the following: Application layer, data layer, IB transport layer, UDP / IP layer, Ethernet link layer.

50. The method according to claim 49, characterized in that, The application layer includes at least one of the following: Hypertext Transfer Protocol (HTTP) layer, File Transfer Protocol (FTP) layer, Remote Procedure Call (gRPC) layer, WebRTC layer, Message Queuing Telemetry Transport (MQTT) layer, WebSocket layer, and CoAP layer.

51. The method according to claim 49, characterized in that, The data layer subheader includes at least one of the following: Data type, data identifier, data length, QoS indicator, protocol type, whether encrypted, whether compressed, timestamp, terminal identifier, source node identifier, source node port number, one or more target node identifiers, target node port number, data identifier, subscriber identifier, notification identifier.

52. The method according to claim 51, characterized in that, The data layer subheader also includes at least one of the following: Data packet sending sequence number, request confirmation indication, data packet receiving confirmation sequence number.

53. The method according to claim 48, characterized in that, The second protocol stack is a RoCEv2-based protocol stack.

54. The method according to claim 29, characterized in that, The second node and the third node are the same node, or the second node and the third node are different nodes.

55. The method according to claim 29, characterized in that, The first node, the second node, and the third node are any of the following nodes: Access network nodes, core network nodes, network management nodes, and application nodes.

56. The method according to claim 55, characterized in that, The access network node includes at least one of the following: Radio frequency unit (RU), centralized unit (CU), distributed unit (DU), next-generation base station (xNB); The core network node includes at least one of the following: Mobility Management Function (AMF) network element, User Plane Function (UPF) network element, Data Plane Function (DPF) network element, Network Data Analysis Function (NWDAF) network element, Sensing Function (SF) network element, and Application Function (AF) network element.

57. A communication device, characterized in that, include: Memory and processor; Memory and processor are coupled; The memory is used to store instructions that can be executed by the processor; When the processor executes the instructions, it performs the method as described in any one of claims 1 to 28, or the method as described in any one of claims 29 to 56.

58. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer instructions that, when executed on a computer, cause the computer to perform the method as described in any one of claims 1 to 28, or the method as described in any one of claims 29 to 56.

59. A computer program product, characterized in that, The computer program product includes computer program instructions that, when executed by a processor, implement the method as described in any one of claims 1 to 28, or implement the method as described in any one of claims 29 to 56.

Images