Data transmission method, communication apparatus, storage medium, and program product

Abstract

A data transmission method, a communication apparatus, a storage medium, and a program product. The method comprises: on the basis of a first radio bearer, a first node transmits data plane data with a second node, the transmission comprising sending or receiving.

Description

Data transmission method, communication apparatus, storage medium and program product

[0001] The present disclosure claims priority to Chinese Patent Application No. 202411589452.8, filed on November 7, 2024, the entire contents of which are incorporated herein by reference. TECHNICAL FIELD

[0002] The present disclosure relates to the field of communication technology, and in particular to a data transmission method, a communication apparatus, a storage medium and a program product. BACKGROUND

[0003] With the ever-increasing number of digital data applications and services, the demand and challenge to network resources and operators will continue to increase. The ability to provide various network performance features required by future services is one of the main technical challenges faced by today's service providers. The performance requirements of the network mainly include the data rate, delay, quality of service (QoS), security, availability, etc. of the connection, and the above performance requirements vary from service to service.

[0004] Therefore, on the one hand, future communication networks (e.g., the 6th generation mobile networks (6G)) require to support flexible resource allocation methods to provide customized connections for each different type of service, and to enhance the ability of the network to meet future demands. On the other hand, with the introduction of new scenarios such as communication perception and artificial intelligence (AI), the future 6G communication network adds a large amount of data generated and obtained by the 6G system on the basis of traditional user business data transmission. These data can come from terminals, base stations, edge servers, core networks, etc. Compared with the 5th generation mobile networks (5G), the data of 6G presents more massive, polymorphic, time-series, and associated characteristics. SUMMARY

[0005] In a first aspect, a data transmission method is provided, applied to a first node, the method comprising:

[0006] transmitting, based on the first radio bearer, data plane data with a second node, the transmitting comprising receiving or sending.

[0007] In a second aspect, a data transmission method is provided, applied to a second node, the method comprising:

[0008] transmitting, with a third node, data plane data, the transmitting comprising receiving or sending.

[0009] Thirdly, a communication device is provided for use in a first node, comprising:

[0010] The communication unit is used to transmit data plane data with the second node based on the first wireless bearer, and the transmission includes receiving or sending.

[0011] Fourthly, a communication device is provided for use in a second node, comprising:

[0012] The communication unit is used to transmit data plane data with a third node, including receiving or sending.

[0013] Fifthly, a communication device is provided, comprising: a processor and a memory; the memory and the processor are coupled; the memory is used to store instructions executable by the processor, the memory storing the processor-executable instructions; when the processor is configured to execute the instructions, the communication device implements the method described above.

[0014] Sixthly, a computer-readable storage medium is provided that stores computer instructions that, when executed on a computer, cause the computer to perform the methods described above.

[0015] In a seventh aspect, a computer program product containing computer instructions is provided, which, when executed on a computer, causes the computer to perform the methods described above. Attached Figure Description

[0016] The accompanying drawings are provided to further understand the technical solutions of this disclosure and constitute a part of the specification. They are used together with the embodiments of this disclosure to explain the technical solutions of this disclosure and do not constitute a limitation on the technical solutions of this disclosure.

[0017] Figure 1 is a schematic diagram of a username data transmission architecture according to some embodiments;

[0018] Figure 2 is a schematic diagram of a communication system according to some embodiments;

[0019] Figure 3 is a flowchart of a data transmission method according to some embodiments;

[0020] Figure 4 is a schematic diagram of an air interface protocol stack corresponding to a first radio bearer according to some embodiments;

[0021] Figure 5 is a schematic diagram of a sensing data plane transmission architecture according to some embodiments;

[0022] Figure 6 is a schematic diagram of a data plane transmission architecture according to some embodiments;

[0023] Figure 7 is a flowchart of another data transmission method according to some embodiments;

[0024] Figure 8 is a schematic diagram of a protocol stack corresponding to a GTP according to some embodiments;

[0025] Figure 9 is a schematic diagram of a protocol stack corresponding to a DPAP according to some embodiments;

[0026] Figure 10 is a schematic diagram of a protocol stack corresponding to another DPAP according to some embodiments;

[0027] Figure 11 is a schematic diagram of a protocol stack corresponding to QUIC according to some embodiments;

[0028] Figure 12 is a schematic diagram of a data plane data transmission protocol stack according to some embodiments;

[0029] Figure 13 is a schematic diagram of another data plane data transmission protocol stack according to some embodiments;

[0030] Figure 14 is a schematic diagram of yet another data plane data transmission protocol stack according to some embodiments;

[0031] Figure 15 is a schematic diagram of yet another data plane data transmission protocol stack according to some embodiments;

[0032] Figure 16 is a schematic diagram of yet another data plane data transmission protocol stack according to some embodiments;

[0033] Figure 17 is a schematic diagram of a data plane architecture between a base station and a core network according to some embodiments;

[0034] Figure 18 is a schematic diagram of another data plane transmission architecture according to some embodiments;

[0035] Figure 19 is a schematic diagram of another sensing data plane transmission architecture according to some embodiments;

[0036] Figure 20 is a block diagram of a communication device according to some embodiments;

[0037] Figure 21 is a block diagram of another communication device according to some embodiments;

[0038] Figure 22 is a block diagram of another communication device according to some embodiments. Detailed Implementation

[0039] The technical solutions of the embodiments of this disclosure will be clearly and completely described below 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 of ordinary skill in the art without creative effort are within the scope of protection of this disclosure.

[0040] Unless the context otherwise requires, throughout the specification and claims, the term "comprise" and other forms such as the third-person singular "comprises" and the present participle "comprising" are interpreted as open-ended and encompassing, meaning "including, but not limited to." In the description of the specification, terms such as "one embodiment," "some embodiments," "exemplary embodiments," "example," "specific example," or "some examples" are intended to indicate that a particular feature, structure, material, or characteristic associated with that embodiment or example is included in at least one embodiment or example of this disclosure. The illustrative representations of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics mentioned may be included in any suitable manner in any one or more embodiments or examples.

[0041] 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. In the description of this disclosure, unless otherwise stated, "a plurality of" means two or more.

[0042] In this disclosure, the terms "exemplary" or "for example" are used to indicate that something is an example, illustration, or description. Any embodiment or design described as "exemplary" 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 terms such as "exemplary" or "for example" is intended to present the relevant concepts in a specific manner.

[0043] In addition, the use of “based on” implies openness and inclusivity, because processes, steps, calculations or other actions “based on” one or more of the stated conditions or values ​​may in practice be based on additional conditions or values ​​beyond those stated.

[0044] Referring, Figure 1 illustrates a user plane data transmission architecture according to some embodiments. In a 5G network, service data of user equipment (UE) can be mapped to different packet data unit (PDU) sessions based on its associated data network (DN) and single network slice selection assistance information (S-NSSAI). Within a PDU session, there can be various types of data, which can be mapped to individual service data flows according to service data flow (SDF) / traffic flow template (TFT) templates. In some embodiments, the user plane function (UPF) / UE maps these service data to different quality of service (QoS) flows according to the session management function (SMF) configuration flow in downlink / uplink respectively. Between the base station and the UPF, a next-generation tunnel (NG tunnel) is established at the PDU session granularity for corresponding data transmission. Between the UE and the base station, uplink and downlink QoS flows are associated with data radio bearers (DRBs) according to the base station's access stratum (AS) level mapping rules. The base station can establish one or more DRBs for each QoS flow in a PDU session. At the non-access stratum (NAS) level, the QoS flow is the smallest granularity for QoS differentiation within a PDU session. Each QoS flow within a PDU session is identified by a QoS flow ID (QFI) and is packaged, encapsulated, and transmitted by the next-generation user plane tunnel (NG-U tunnel). At the access stratum (AS) level, QoS guarantees between the UE and the base station are implemented at the DRB granularity.Once the PDU session, NG-Utunnel, DRB, service data to QoS Flow, and QoS Flow to DRB mappings are all configured, the UE can transmit uplink and downlink service data with the DN.

[0045] It should be noted that in Figure 1, NG-RAN stands for Next Generation Radio Access Network (NG-RAN), NR stands for New Radio (NR), NG-UP stands for Next Generation User Plane (NG-UP), E2E stands for End-to-End (E2E), SDF stands for Service Data Flow (SDF), and NG stands for Next Generation (NG).

[0046] Future 6G communication networks will incorporate new scenarios such as communication sensing and AI into traditional user service data transmission. Communication sensing and AI will generate massive amounts of data, which can originate from terminals, base stations, edge servers, and the core network. This means that all network element nodes in the 6G network will have a need for data collection, analysis, and processing, and data transmission may occur between any network element nodes within the 6G network. Furthermore, 6G networks need to process data based on its inherent relationships, transforming and optimizing it to achieve the desired state for data analysis and intelligent applications.

[0047] Table 1 below shows the data types and transmission requirements for 6G networks.

[0048] Table 1

[0049] Table 1 above shows the potential data types and data transmission scenarios for 6G.

[0050] Referring to Table 1 above, taking AI models as an example, the generator of an AI model can be a UE, RAN, CN, AF, or OAM; while the consumer of an AI model can be a UE, RAN, CN, AF, or OAM. When the AI ​​model generator and consumer are different, it is necessary to transmit the AI ​​model between different network elements. For example, an AI model generated by OAM is transmitted to the RAN or core network equipment, an AI model generated by the core network is transmitted to the RAN or UE, an AI model generated by the RAN is transmitted to the UE, or an AI model generated by the AF is transmitted to the UE, etc.

[0051] Taking federated learning as an example, UE, RAN, CN, or AF can act as the initiator of federated learning, and UE, RAN, CN, or AF can act as the participants. Intermediate computational results of the AI ​​model (e.g., intermediate model result updates and model gradients) need to be transferred between the initiator and participants. For example, UE, as a participant, sends AI model gradient updates to RAN, while RAN, as the initiator, sends intermediate model update results to UE.

[0052] AI training data: The producers of AI training data can be UE, RAN, CN, or AF, and the consumers of the data can be UE, RAN, CN, AF, or OAM. AI model producers can collect AI training data from network elements of interest. For example, OAM can collect training data from RAN or core network, RAN can collect training data from UE or core network, and core network can also collect AI training data from UE or RAN, etc.

[0053] AI analytics: Network elements performing AI model inference, such as UE, AN, CN, AF, or OAM, can generate AI statistical analysis or predictive data, collectively referred to as AI analytics. Consumers of AI analytics can be UE, RAN, CN, AF, or OAM. Consumers of AI analytics can request or subscribe to AI analytics of interest from the producers of AI analytics. For example, the core network can obtain AI analytics of interest from the RAN or AF, and the AF can also obtain AI analytics of interest from the RAN or core network. Similarly, the RAN can obtain AI analytics of interest from the CN or AF.

[0054] Communication-aware measurement data: Communication-aware measurement data can be generated by the UE or the RAN, or processed on the UE or the RAN side. Communication-aware measurement data generated by the UE side can be transmitted to the RAN for further processing, and vice versa.

[0055] Environmental or target perception data: Environmental or target object perception data can be generated by the UE or RAN. This perception data can be processed directly by the UE or RAN, or the UE can send the perception data to the RAN for processing. Alternatively, the UE or RAN can send the generated perception data to the core network for processing. Or, the UE or RAN can send the generated perception data to the AF for processing.

[0056] In summary, data transmission in 6G networks is no longer a simple end-to-end user plane data transmission between the UE and the user plane function (UPF). Instead, it needs to support distributed data transmission between any network elements and between any network element and a terminal. Therefore, improving data transmission efficiency is a pressing issue that needs to be addressed in future communication systems.

[0057] Based on this, the present disclosure provides a data transmission method, a communication device, a storage medium, and a program product, wherein the first node transmits data plane data with the second node based on the first wireless bearer, which can improve data transmission efficiency.

[0058] The embodiments of this disclosure will now be described in conjunction with the accompanying drawings.

[0059] The technical solutions provided in this disclosure can be applied to various mobile communication networks, such as 5G NR mobile communication networks, future mobile communication networks (e.g., 6G wireless communication systems), or multiple communication convergence systems, etc. This disclosure does not limit them.

[0060] Figure 2 is a schematic diagram of a communication system according to some embodiments. As shown in Figure 2, the communication system includes, but is not limited to, a terminal 110, an access network device 120, a core network device 130, and an application server (AS) 140. Here, the terminal 110, access network device 120, core network device 130, and AS 140 can transmit and receive wireless signals and perform related interactions. The devices shown in Figure 2 can be connected via a wired network or a wireless network. Here, the wired network or wireless network can include routers, switches, or other devices that facilitate communication between the devices, and this disclosure does not limit this.

[0061] In some embodiments, terminal 110 can be a device with wireless transceiver capabilities, such as a mobile phone, tablet computer, wearable device, in-vehicle device, augmented reality (AR) / virtual reality (VR) device, laptop computer, ultra-mobile personal computer (UMPC), netbook, personal digital assistant (PDA), etc. This disclosure does not limit the type of terminal 110.

[0062] In some embodiments, the access network device 120 is a base station, which can be any of the following: an evolved NodeB (eNB), a next-generation NodeB (gNB), a transmission receive point (TRP), a transmission point (TP), a femtocell, or some other type of access node. Based on the size of the service coverage area provided, base stations can be further categorized as macro base stations for providing macrocells, micro base stations for providing microcells, pico base stations for providing picocells, and femto base stations for providing femtocells. As wireless communication technology continues to evolve, future base stations may also adopt other names.

[0063] In some embodiments, the core network device 130 includes at least one of the following:

[0064] Core network, some functions / functional entities of the core network, servers, clients, third-party clients, and application layer.

[0065] In some examples, core network equipment 130 includes access and mobility management function (AMF) network elements, session management function (SMF) network elements, UPF network elements, data analytics function (DAF) network elements, data plane function (DPF) network elements, and sensing function (SF) network elements.

[0066] In some embodiments, the DPF network element can be co-located with the UPF network element, or the function of the DPF network element can be included in the function of the UPF network element, that is, the UPF network element can have the function of the DPF network element.

[0067] Core network equipment may also have other names, such as core network element, and this disclosure does not limit this.

[0068] In some embodiments, AS140 is used for at least one of the following:

[0069] Provides the application runtime environment;

[0070] Hosting and managing applications;

[0071] Provide services and functions; or

[0072] Integrate with other systems and services, etc.

[0073] In some embodiments, AS140 includes an application function (AF), meaning that AS140 integrates an AF.

[0074] In some embodiments, AS140 is connected to AF, meaning that AF can exist as an independent service component and interact with AS140 through specific interfaces or protocols.

[0075] It should be understood that Figure 2 is an exemplary block diagram, and the number of devices included in the communication system shown in Figure 2 is not limited. For example, the number of terminals 110 and access network devices 120 is not limited. Furthermore, the communication system shown in Figure 2 may include other devices besides those shown in Figure 2, and this is not limited.

[0076] Next, as shown in Figure 3, this embodiment of the present disclosure provides a data transmission method, which can be applied to a first node, and the method may include the following step S101.

[0077] In S101, data plane data is transmitted based on the first wireless bearer and the second node.

[0078] Here, transmission includes sending or receiving, that is, receiving data plane data from the second node based on the first radio bearer, or sending data plane data to the second node based on the first radio bearer.

[0079] In some embodiments, the first node is a terminal and the second node is an access network device (e.g., a base station); or, the first node is a terminal and the second node is a core network device; or, the first node is a terminal and the second node is an application server or application function.

[0080] Taking the first node as the terminal and the second node as the access network device as an example, the terminal can be the terminal 110 shown in Figure 2 above, and the access network device can be the access network device 120 shown in Figure 2 above.

[0081] In some embodiments, the data plane data includes at least one of the following:

[0082] AI data identification;

[0083] AI models;

[0084] AI training data;

[0085] AI inference data;

[0086] AI data analysis;

[0087] AI model performance data;

[0088] Sensing data identification;

[0089] Communication-sensing data;

[0090] Environmental sensing data; or

[0091] Data perceived by the target object.

[0092] In some embodiments, the first radio bearer is not associated with the PDU session, and different first radio bearers may correspond to different QoS parameter requirements.

[0093] It should be understood that in traditional wireless communication networks, Uu interface data transmission supports two radio bearer modes: signaling radio bearer (SRB) and DRB.

[0094] Here, SRBs are radio bearers used for transmitting Radio Resource Control (RRC) and NAS messages, including SRB0 to SRB3. SRB0 is used for transmitting RRC messages using the common control channel (CCCH) logical channel; SRB1 is used for RRC messages (which may include carried NAS messages) and for NAS message transmission before SRB2 is established, all using the dedicated control channel (DCCH) logical channel; SRB2 is used for NAS message transmission, using the DCCH logical channel. SRB2 has a lower priority than SRB1 and can be configured by the network after AS security activation; SRB3 is used for specific RRC message transmission when the UE is in Long Term Evolution (LTE) and 5G dual connectivity (EUTRA-NR dual connection, EN-DC) or new radio dual connectivity (NR-DC), using the DCCH logical channel.

[0095] DRBs are used to transmit user plane data. In NR, user data is mapped to QoS Flows using UE-preset or network-configured SDF templates (Service Data Templates), and then the Service Data Adaptation Protocol (SDAP) layer maps the QoS Flows to DRBs. In NR, the maximum number of DRBs a UE can establish increases from the LTE maximum of 8 to a maximum of 29, with a minimum capacity of 16 DRBs. Different DRBs can map to different QoS Flows, configure different logical channel priorities, radio link control (RLC) retransmission processing, and packet data convergence protocol (PDCP) encryption and deduplication mechanisms, etc.

[0096] Data plane data can include AI-related data, perception-related data, and data from emerging future scenarios. For data plane data transmitted between the UE and the base station, this data only needs to be sent to the other end and does not need to be associated with a PDU session. On the other hand, data plane data has different QoS requirements. For example, AI training data and AI model data have low real-time requirements, high reliability requirements, and large data volumes. AI inference data, on the other hand, has high real-time and high reliability requirements, and small data volumes. In some embodiments, different types of perception data also have different QoS requirements. For example, agricultural sensor networks have low latency and low reliability requirements, and small data volumes. Vehicle-mounted sensors, however, have high reliability, high real-time requirements, and large data volumes.

[0097] Therefore, different bearers need to be configured to distinguish different QoS data transmission requirements for different types of data plane data. Traditional SRBs only associate different priorities, without considering QoS parameters in detail like DRBs, such as PDB, packet error rate (PER), and guaranteed bit rate (GBR). While traditional DRBs consider various QoS and different data processing mechanisms, they are all associated with PDU sessions. To differentiate from SRBs and DRBs, dedicated radio bearers for the data plane can be designed to transmit data plane data. Based on this, embodiments of this disclosure propose a new radio bearer, namely a first radio bearer, which is not associated with a PDU session, and different first radio bearers can correspond to different QoS parameter requirements.

[0098] In this way, the first node transmits data plane data to the second node based on the first wireless bearer, thereby improving data transmission efficiency.

[0099] In some embodiments, the first radio bearer may also have other names, such as data plane radio bearer (DPRB). This disclosure does not limit the name of the first radio bearer.

[0100] The first wireless bearer is described below.

[0101] In some embodiments, the air interface protocol stack corresponding to the first radio bearer includes at least one of the following:

[0102] DPAP layer;

[0103] PDCP layer;

[0104] RLC layer; or

[0105] MAC layer.

[0106] In some embodiments, the air interface protocol stack corresponding to the first radio bearer further includes a physical layer (PHY).

[0107] For example, referring to Figure 4, is a schematic diagram of an air interface protocol stack corresponding to a first radio bearer according to some embodiments. As shown in Figure 4, the air interface protocol stack corresponding to the first radio bearer includes, from top to bottom, a DPAP layer, a PDCP layer, an RLC layer, a MAC layer, and a PHY layer, terminating between the UE and the RAN. Here, the functions of the MAC layer, RLC layer, and PDCP layer are similar to those of the DRB.

[0108] In some embodiments, the DPAP layer is used for at least one of the following:

[0109] Transmit data plane data;

[0110] Map the quality of service flow or service flow of data plane data to the first radio bearer;

[0111] Encapsulate the DPAP header; or

[0112] Remove the DPAP header.

[0113] Here, the head may also have other names, such as sub-head, and this disclosure does not limit this.

[0114] In some embodiments, the DPAP header includes at least one of the following:

[0115] QoS indication;

[0116] Data type indicator;

[0117] Data identification;

[0118] Source node identifier;

[0119] At least one target node identifier;

[0120] Source port number;

[0121] Target port number;

[0122] Protocol identifier; or

[0123] Timestamp.

[0124] QoS indications include at least one of the following:

[0125] Data quality indicator (DQI);

[0126] Data stream identifier.

[0127] Data type indicators are used to indicate at least one of the following types:

[0128] AI data;

[0129] Sensing data; or

[0130] Other data.

[0131] Here, "other data" refers to data other than AI data and perception data.

[0132] In some embodiments, where the data type indicator is used to indicate that the data type is AI data, the DPAP header also includes at least one of the following:

[0133] AI data identification;

[0134] AI models;

[0135] AI training data;

[0136] AI inference data;

[0137] AI data analysis data; or

[0138] AI model performance data, that is, data used to indicate the performance of AI models.

[0139] In some embodiments, where the data type indicator is used to indicate that the data type is perceptual data, the DPAP header also includes at least one of the following:

[0140] Sensing data identification;

[0141] Communication-sensing data;

[0142] Environmental sensing data; or

[0143] Data perceived by the target object.

[0144] For non-IP data plane data, there may be different protocol types based on the application layer. The protocol identifier in the DPAP header can be used to indicate the protocol type. The protocol identifier is used to indicate at least one of the following protocols:

[0145] Hypertext Transfer Protocol (HTTP);

[0146] File Transfer Protocol (FTP);

[0147] g Remote Procedure Call (Google Remote Procedure Call, gRPC);

[0148] Web real-time communications (WebRTC);

[0149] Message Queuing Telemetry Transport (MQTT);

[0150] WebSocket; or

[0151] Constrained application protocol (CoAP).

[0152] The source node identifier or the target node identifier may include at least one of the following:

[0153] UE identifier, access network device identifier (e.g., base station identifier), or core network device identifier.

[0154] It should be noted that multiple base stations or core network devices may subscribe to the same data plane data, therefore the DPAP header may contain multiple target node identifiers.

[0155] For non-IP data plane data, the target node can identify the corresponding application based on the target port number, and then deliver the data table to the appropriate application. Similarly, the source port number of the source node in the data plane identifies the application at the source end.

[0156] A timestamp is used to indicate at least one of the following:

[0157] Data generation time; or

[0158] Data latency budget.

[0159] For non-IP data plane data, the DPAP layer can further support reliable data transmission. In this case, the DPAP header also includes at least one of the following:

[0160] Data packet transmission sequence number;

[0161] Request confirmation instructions; or

[0162] Data packet reception confirmation sequence number.

[0163] In some embodiments, data plane data is above the DPAP layer, meaning the DPAP layer is used to carry data plane data.

[0164] In some embodiments, the data plane data is IP-based data or non-IP-based data.

[0165] When the data plane data is IP-based, at least one of the following protocol stacks exists above the DPAP layer: Transmission Control Protocol (TCP) / IP protocol stack, User Datagram Protocol (UDP) / IP protocol stack, or Quick UDP Internet Connection (QUIC) / UDP / IP protocol stack. Alternatively, when the data plane data is non-IP-based, an application protocol layer can exist above the DPAP layer; that is, application layer data is included above the DPAP layer.

[0166] In some examples, data plane data transmission with a second node includes: transmitting data plane data with the second node based on RRC signaling, or transmitting RRC signaling with the second node, where the data plane data is carried in a non-access stratum (NAS) message within the RRC signaling; that is, sending RRC signaling to the second node, or receiving RRC signaling sent by the second node. For example, the first node sends RRC signaling to the second node, and the data plane data is carried in a NAS message within the RRC signaling. In other words, either the first or second node can place the data plane data in a NAS message and then carry the data plane data over the air interface through a NAS container within the RRC signaling.

[0167] In some embodiments, the first node or the second node transmits data plane data via SRB2.

[0168] In other embodiments, since data plane data typically has lower priority than signaling, one or more new DP-SRBs can be added to the Uu interface specifically for carrying data plane data between the UE and core network equipment. Traditional SRBs are usually established based on default configurations, while these newly added first radio bearers can be dynamically configured by the base station based on RRC reconfiguration messages according to data plane data transmission requirements. In other words, the first radio bearer is a newly added SRB in the Uu interface between the first node and the second node.

[0169] In some embodiments, the first wireless bearer is a Uu interface SRB, DRB, or DPRB between the first node and the second node.

[0170] In this embodiment of the disclosure, the first node transmits data plane data with the second node based on the newly added first wireless bearer. Since the first wireless bearer is not associated with the PDU session, different first wireless bearers may correspond to different QoS parameter requirements. Therefore, transmitting data plane data with the second node based on the first wireless bearer can improve data transmission efficiency.

[0171] In some embodiments, the sensing data includes communication-related sensing data, environment-related sensing data, and target object-related sensing data. Sensing is divided into terminal-side sensing and base station-side sensing. Taking the terminal as an example, it can include sensing in various scenarios such as smartphone environmental sensing, vehicle-mounted sensors, industrial internet sensors, medical wearable devices, VR and AR devices, or agricultural sensor networks. From the perspective of the base station, it can include various sensing scenarios and tasks such as wireless signal sensing (RF fingerprint recognition), environmental sensing (temperature, humidity, or air pressure, etc.), pedestrian flow and mobility analysis, drone detection and tracking, vehicle flow monitoring, or weather and air quality detection.

[0172] To support the acquisition and processing of sensing data in future wireless communication networks, terminals, base stations, core networks, or AF / AS can all support sensing functions (SF) to perform sensing data acquisition, sensing data storage, and sensing data processing. Figure 5 illustrates a sensing data plane transmission architecture according to some embodiments. The SF can be located at the UE, xNB, CN, and AS or AF. Here, the UE and xNB themselves can possess sensing functions, perform sensing operations, and acquire raw sensing data. The AF or AS may acquire sensing data from third-party sensors. From the UE's perspective, the UE's sensing data can be processed directly on the UE side to obtain sensing results. Furthermore, the UE's sensing data can also be sent to the xNB, core network equipment, or AF / AS for further processing. Similarly, the xNB's sensing data can also be processed directly at the base station to obtain sensing results. Furthermore, the xNB's sensing data can also be sent to the core network equipment or AF / AS for further processing.

[0173] It should be noted that xNB in ​​Figure 5 represents a certain generation of base station, such as eNB, gNB, and base stations that may appear in future communication systems, which will not be elaborated on further below.

[0174] Based on this, in some embodiments, the first node or the second node supports a sensing function, which includes at least one of the following:

[0175] Sensor data acquisition;

[0176] Sensing data storage; or

[0177] Sensing data processing.

[0178] To support data analysis and processing in any topology of future wireless communication networks, UEs, base stations, core networks, or AFs / ASs all support data analytics functions (DAF), which can perform data acquisition, data storage, data processing, model training, model inference, and model monitoring. Figure 6 shows a schematic diagram of a data plane transmission architecture according to some embodiments; the DAF can be located in the UE, RAN, CN, and AS or AF.

[0179] Based on this, the first or second node supports data analysis functions, which include at least one of the following:

[0180] AI data collection;

[0181] AI data storage;

[0182] AI data processing;

[0183] AI model training;

[0184] AI reasoning; or

[0185] AI model performance monitoring.

[0186] In addition, the UE, base station, core network, or AF / AS can be configured to support a data collection function (DPF), also known as a data plane function (DPF), separating the sensing data acquisition function from the SF. As shown in Figure 5, the UE can directly interact with the xNB, core network, or AS / AF through the SF to exchange sensing data, or it can complete data acquisition through the DPF. Subsequently, the SF performs sensing data analysis and derives sensing results or intermediate results. The data plane data acquisition function can also be separated from the DAF. As shown in Figure 6, the UE can directly interact with the xNB, core network, or AS / AF through the DAF to exchange AI-related data, or it can complete data acquisition through the DPF. Subsequently, the DAF performs AI model training and / or AI model inference and AI analytics generation.

[0187] Based on this, the first node supports data plane functionality, which is used for sensing data acquisition and / or data plane data processing.

[0188] In some embodiments, perception data acquisition includes not only the collection of perception data from various perception scenarios, but also the transmission of perception analysis results. Data consumers can collect data from data producers one-time based on a request-response model, periodically push data between data consumers and data producers based on a subscription notification model, or trigger data collection based on specific events.

[0189] To support efficient data acquisition, the collectable data and data transmission methods need to be pre-configured. For example, the UE can inform the xNB, CN, or AF / AS of its various sensing capabilities, what data it can provide, and which sensing scenarios it supports.

[0190] Similarly, to support efficient data acquisition, the collectable data and data transmission methods need to be pre-configured. For example, the UE and xNB, CN, or AF / AS need to inform each other what data can be provided, which AI models are supported, AI analytics, and whether AI model training is supported.

[0191] Based on this, in some embodiments, the first node sends first information to the second node, the first information being used to indicate at least one of the following:

[0192] The first node possesses the ability to perceive;

[0193] The first node can provide sensing data;

[0194] The first node supports the following perception scenarios;

[0195] The first node can provide data plane data;

[0196] The first node supports the following information processing methods;

[0197] The first node supports artificial intelligence analysis; or

[0198] Does the first node support training on information processing methods?

[0199] The transmission of sensing data can be based on traditional RRC signaling (UE and xNB), NAS signaling (UE and CN), or user plane data (UE and AF / AS). Furthermore, based on the characteristics of data plane data, a new radio bearer (i.e., the aforementioned first radio bearer) can be designed on the Uu interface for data plane data transmission, and a new data tunnel can be designed between the xNB and CN for data plane data transmission, improving data plane data transmission efficiency. In addition, for raw sensing data acquisition, the sensing data can be compressed to reduce the data volume. To ensure the security of data transmission, it is necessary to further enhance data security encryption and integrity protection. To protect privacy, SF can de-identify sensitive information contained in the raw sensing data before transmitting the sensing data.

[0200] Data transmission methods for the data plane can be based on traditional RRC signaling (UE and xNB), NAS signaling (UE and CN), or user plane data (UE and AF / AS). Furthermore, based on the characteristics of data plane data, a new radio bearer (i.e., the aforementioned first radio bearer) can be designed on the Uu interface for data plane data transmission, and a new data tunnel can be designed between the xNB and CN for data plane data transmission, improving data plane data transmission efficiency. In addition, for raw data acquisition or AI model transmission, batch data and AI models can be compressed to reduce data volume. To ensure data transmission security, further improvements are needed in data security and integrity protection.

[0201] In some embodiments, AI needs to support functions such as data acquisition, data storage, data processing, AI model training, AI model monitoring, and AI model inference. From the UE's perspective, the UE can obtain AI-related data from the xNB, core network, and application server (AS / AF) for its own model training. In some embodiments, the UE can perform AI inference and generate AI analytics based on the AI ​​model. Furthermore, the AI ​​model used by the UE can also be trained via the xNB, core network equipment, or AS / AF, and then sent to the UE after training. On the other hand, the UE can provide AI training data and AI analytics according to the needs of the xNB, core network, or AS / AF. For scenarios where the AI ​​model used by the UE is trained by the xNB, core network, or AS / AF, the UE can further provide AI model performance testing information to the xNB, core network, or AS / AF.

[0202] Based on this, when the first node transmits data plane data to the second node based on the first wireless bearer, and the first node receives data plane data from the second node based on the first wireless bearer, the first node can train its AI model based on the data plane data after receiving the data plane data from the second node.

[0203] In some embodiments, data plane data is used to indicate the AI ​​model that the first node should use.

[0204] In some embodiments, after using the AI ​​model indicated by the second node, the first node sends performance detection information of the AI ​​model to the second node to inform the second node of the performance of the AI ​​model.

[0205] The above embodiments are exemplary descriptions of a data transmission method provided by this disclosure from the perspective of a first node. In some embodiments, as shown in FIG7, this disclosure provides a data transmission method applied to a second node, which may include the following step S201.

[0206] In S201, data plane data is transmitted with the third node.

[0207] Here, transmission includes receiving or sending. For example, sending data plane data to a third node, or receiving data plane data from a third node. The description of data plane data can be found in the above embodiments and will not be repeated here.

[0208] In some embodiments, the second node is an access network device and the third node is a core network device; or...

[0209] The second node is the access network equipment, and the third node is one of the following: application server, application function, or data analysis function; or...

[0210] The second node is core network equipment, and the third node is access network equipment; or...

[0211] The second node is an access network device, and the third node is an access network device. For example, the second node is a base station, and the third node is a neighboring base station of the base station.

[0212] The transmission of data plane data between the second and third nodes can be understood as the transmission of data plane data between network elements.

[0213] In some embodiments, the data plane data sent by the second node to the third node is generated by the second node.

[0214] In some embodiments, data plane data transmission between base stations (such as xNB, RU, CU, DU) and core network elements (such as DPF, SF, DAF of the core network), between the core network (such as DPF, SF, DAF of the core network) and AF / AS, between base stations (such as between xNBs), and within base stations (such as between RU, DU, CU), can be based on the following protocols, that is, the second node transmits data plane data with the third node based on at least one of the following protocols:

[0215] Next-generation application protocol NGAP;

[0216] General Packet Radio Service Tunneling Protocol (GTP);

[0217] IP;

[0218] QUIC protocol; or

[0219] DPAP.

[0220] Taking the transmission of data plane data between the second node and the third node based on GTP as an example, the transmission of data plane data between the second node and the third node based on GTP includes:

[0221] Sending GTP data packets to the third node, or receiving GTP data packets from the third node. GTP data packets are obtained by encapsulating the data plane data of the first radio bearer with the corresponding GTP tunnel.

[0222] Tunnels can also have other names, such as passageways.

[0223] In some embodiments, multiple GTP tunnels can be established based on the different QoS requirements of the data plane data transmitted between network elements. GTP tunnels can be configured with different granularities; for example, a GTP tunnel can correspond one-to-one with a first radio bearer of a first node, or one GTP tunnel can correspond to multiple first radio bearers of a certain first node. Furthermore, GTP tunnels can also correspond to different fragments of a first node; for example, AI data and sensing data can correspond to different data plane fragments. For network elements that support both AI data and sensing data data plane transmission, different GTP tunnels are established between network elements for the data plane data related to AI data and sensing data, respectively.

[0224] It should be noted that the data encapsulated within the GTP tunnel can be either IP packets or non-IP packets.

[0225] To better transmit data plane data and improve data transmission efficiency, the GTP header of a GTP packet includes at least one of the following:

[0226] QoS indication;

[0227] Data type indicator;

[0228] Data identification;

[0229] Source node identifier;

[0230] At least one target node identifier;

[0231] Source port number;

[0232] Target port number;

[0233] Protocol identifier; or

[0234] Timestamp.

[0235] For a description of the contents of the GTP header, please refer to the description of the contents of the DPAP header in the embodiment shown in Figure 3 above, which will not be repeated here.

[0236] In some embodiments, as shown in Figure 8, the protocol stack corresponding to GTP includes at least one of the following:

[0237] DPAP;

[0238] GTP;

[0239] UDP; or

[0240] IP.

[0241] Taking the transmission of data plane data between the second node and the third node based on DPAP as an example, the transmission of data plane data between the second node and the third node based on DPAP includes: sending DPAP data packets to the third node, or receiving DPAP data packets from the third node. The DPAP data packets are obtained by encapsulating the data plane data of the first radio bearer with the corresponding DPAP tunnel.

[0242] In some embodiments, multiple DPAP tunnels can be established based on the different QoS requirements of the data plane data transmitted between network elements. DPAP tunnels can be configured with different granularities; for example, a DPAP tunnel can correspond one-to-one with a first radio bearer of a first node, or one DPAP tunnel can correspond to multiple first radio bearers of a certain first node. Furthermore, DPAP tunnels can also correspond to different fragments of a first node; for example, AI data and sensing data can correspond to different data plane fragments. For network elements that support both AI data and sensing data data plane transmission, different DPAP tunnels are established between network elements for the data plane data related to AI data and sensing data, respectively.

[0243] It should be noted that the data encapsulated within the DPAP tunnel can be either IP packets or non-IP packets.

[0244] To better transmit data plane data and improve data transmission efficiency, the DPAP header of a DPAP packet includes at least one of the following:

[0245] QoS indication;

[0246] Data type indicator;

[0247] Data identification;

[0248] Source node identifier;

[0249] At least one target node identifier;

[0250] Source port number;

[0251] Target port number;

[0252] Protocol identifier; or

[0253] Timestamp.

[0254] For a description of the contents of the DPAP header, please refer to the description of the contents of the DPAP header in the embodiment shown in Figure 3 above, which will not be repeated here.

[0255] In some embodiments, as shown in FIG9 or FIG10, the protocol stack corresponding to DPAP includes at least one of the following:

[0256] DPAP; UDP; Stream Control Transmission Protocol (SCTP); or, IP.

[0257] Taking data plane data transmission between a base station and a SF (Secondary Service Provider) in the core network as an example, the base station can encapsulate the data plane data into a DPAP tunnel and then deliver it to the DPF (Digital Distribution Provider) in the core network. The DPF then delivers the IP or non-IP data packets inside to the SF or DAF (Digital Distribution Provider). In scenarios where the DPAP header contains multiple target node identifiers, the DPF is responsible for further delivering the data packet to multiple network elements corresponding to the core network.

[0258] In some embodiments, taking data plane data transmission between a base station and a neighboring base station as an example, the base station can encapsulate the data plane data into a DPAP tunnel and then send it to the neighboring base station.

[0259] In some embodiments, the protocol stack corresponding to QUIC can be as shown in Figure 11.

[0260] The above embodiments are illustrated using the example of data plane data generated by the second node being transmitted between the second node and the third node. In some embodiments, the data plane data transmitted between the second node and the third node is sent from the first node to the second node. That is, before the second node and the third node transmit data plane data, the second node transmits data plane data with the first node based on the first radio bearer to obtain the data plane data, and then sends the data plane data to the third node.

[0261] Based on this, in some embodiments, the second node receives data plane data sent by the first node based on the first radio bearer, or sends data plane data to the first node based on the first radio bearer.

[0262] Here, the first radio bearer is not associated with the PDU session, and different first radio bearers can correspond to different QoS parameter requirements. For a description of the first radio bearer, please refer to the corresponding description of the first radio bearer in the embodiment shown in Figure 3 above, which will not be repeated here.

[0263] The above embodiments illustrate the example of a first node sending data plane data to a second node based on a first radio bearer. In some embodiments, the first node sends RRC signaling to the second node, and the NAS message in the RRC signaling carries the data plane data. Accordingly, the second node receives the RRC signaling sent by the first node and obtains the data plane data based on the RRC signaling.

[0264] In some embodiments, the first node is a terminal.

[0265] It should be understood that the first node, second node and third node mentioned above are different devices corresponding to different application scenarios. Those skilled in the art can determine the devices corresponding to the first node, second node and third node based on the actual application scenario.

[0266] Taking a UE as the first node, a base station as the second node, and a core network device as the third node as an example, an exemplary description of a data transmission method provided in this disclosure embodiment will be given.

[0267] Example 1: Data plane data is transmitted between terminals, base stations, and core network equipment based on NAS signaling.

[0268] Taking the second node receiving the RRC signaling sent by the first node, and the NAS message in the RRC signaling carrying data plane data as an example, see Figure 12, which is a schematic diagram of a data plane data transmission protocol stack according to some embodiments. After the base station (i.e., the RAN in Figure 12) receives the data plane data carried by the NAS container, the base station can send the data plane data to the AMF through the NGAP protocol. After the AMF receives the data plane data, it delivers the data plane data to the corresponding core network equipment, such as DAF, SF or DPF.

[0269] Example 2: Data plane data is transmitted between the terminal and the base station based on the first radio bearer, and data plane data is transmitted between the base station and the core network equipment based on GTP.

[0270] In some embodiments, data plane data transmitted between the UE and core network equipment can be transmitted using the transport protocol stack shown in Figure 13. For example, data plane data can be transmitted between the UE and the base station based on a first radio bearer (the protocol stack is DPAP / PDCP / RLC / MAC), and data plane data can be transmitted between the base station and core network equipment (such as SF, DAF, or DPF) based on GTP. The protocol stack can be DPAP / GTP / UDP / IP or GTP / UDP / IP.

[0271] Based on this, data plane data is sent to the third node via GTP, including sending GTP data packets to the third node. The GTP data packets are obtained by encapsulating the GTP tunnel corresponding to the first radio bearer of the data plane data.

[0272] In some embodiments, multiple first radio bearers and GTP tunnels can be established based on the different QoS requirements of the data plane data transmitted between the UE and the core network. GTP tunnels can be configured with different granularities; for example, a GTP tunnel can correspond one-to-one with a UE's first radio bearer, or one GTP tunnel can correspond to one or more first radio bearers of a certain first node. Furthermore, GTP tunnels can also correspond to different fragments of a certain first node; for example, AI data and sensing data can correspond to different data plane fragments. For UEs supporting both AI data and sensing data data transmission, the data plane data related to AI data and sensing data between the UE and the base station are transmitted through different DPRBs, while two different GTP tunnels are established between the base station and the SF and DAF, or two GTP tunnels are established between the base station and the DPF, respectively corresponding to AI data and sensing data.

[0273] If the data transmitted between the UE and the core network equipment is an IP packet, then the DPAP header need not be encapsulated. If the data plane data packet contains a DPAP header, the data contained in the DPAP header can be referred to the description of the DPAP header in the embodiment shown in Figure 3 above, which will not be repeated here. In addition, the DPAP header can also be encapsulated at the Uu interface. When transmitting data plane data between the base station and the core network equipment, the DPAP header is not included, and the relevant data of the DPAP header is encapsulated in the GTP header to transmit data plane data.

[0274] Taking uplink data plane data transmission as an example, after the base station receives data plane data sent by the terminal through the first radio bearer, the base station can encapsulate the GTP tunnel corresponding to the first radio bearer of the data plane data into a GTP data packet and then deliver it to the core network equipment (such as SF, DAF or DPF).

[0275] In some embodiments, if the core network is uniformly responsible for data plane data acquisition by the DPF, the base station delivers the data plane data packets to the DPF through the GTP tunnel. The DPF can then further deliver the data packets to the corresponding SF or DAF according to the data type in the DPAP header of the data packet, the destination node identifier, or the destination IP address in the IP header of the data packet.

[0276] Taking downlink data plane data transmission as an example, after the base station receives data plane data from core network equipment (such as SF, DAF, or DPF), it maps it to the first radio bearer of the corresponding terminal based on at least one of the QoS identifier, data identifier, data type, target node identifier, and target port number information in the GTP tunnel and / or DPAP header, and then sends it to the corresponding UE. This means that the base station needs to receive in advance the mapping information from the AMF or UE of at least one of the QoS identifier, data identifier, data type, target node identifier, and target port number information in the GTP tunnel and / or DPAP header to the UE's first radio bearer.

[0277] Example 3: Data plane data is transmitted between the UE and the base station based on the first radio bearer, and data plane data is transmitted between the base station and the core network equipment based on IP.

[0278] In some embodiments, data plane data transmitted between the UE and the core network equipment can be transmitted using the transport protocol stack shown in Figure 14. In this example, the data packets transmitted between the UE and the core network are already IP data packets. Data packets are transmitted between the UE and the base station based on the first radio bearer transport (protocol stack is DPAP / PDCP / RLC / MAC), while IP data packets are transmitted directly between the base station and the core network equipment (such as SF, DAF, or DPF). In this case, there is no need to encapsulate the DPAP header.

[0279] Taking uplink data plane data transmission as an example, after the base station receives the data plane data sent by the terminal through the first radio bearer, the base station can directly deliver the IP data packets of the data plane data to the core network equipment (such as SF, DAF, or DPF) without encapsulating additional IP tunnels. This also means that when the UE encapsulates the data plane data, it needs to know the IP address and corresponding port number of the corresponding core network equipment in advance.

[0280] Taking downlink data plane data transmission as an example, after the base station receives an IP data packet from a core network device (such as SF, DAF, or DPF), it determines that the IP data packet corresponds to the UE's data plane data based on the destination IP address and port number of the IP data packet. The base station then maps the data packet to the corresponding UE's first radio bearer and sends it to the UE. This means that the base station needs to receive the mapping information from the AMF or UE in advance, from the destination IP address and port number to the UE's first radio bearer.

[0281] Example 4: Data plane data is transmitted between the UE and the base station based on the first radio bearer, and data plane data is transmitted between the base station and the core network equipment based on QUIC.

[0282] Data plane data transmitted between the UE and core network equipment can be transmitted using the transport protocol stack shown in Figure 15 or Figure 16. Here, the transmission between the UE and the base station is based on the first radio bearer (the protocol stack is DPAP / PDCP / RLC / MAC), and the transmission between the base station and core network equipment (such as SF, DAF, or DPF) is based on QUIC, with the protocol stack being DPAP / QUIC / UDP / IP (as shown in Figure 15) or QUIC / UDP / IP (as shown in Figure 16).

[0283] Multiple DPRB and QUIC tunnels can be established based on the different QoS requirements of the data plane data transmitted between the UE and the core network. QUIC tunnels can be configured with different granularities; for example, a QUIC tunnel can correspond one-to-one with the UE's first radio bearer, or one QUIC tunnel can correspond to one or more first radio bearers of a certain first node. Furthermore, QUIC tunnels can also correspond to different fragments of a certain first node; for example, AI and sensing data can correspond to different data plane fragments. For UEs supporting both AI data and sensing data transmission, the data plane data related to AI data and sensing data between the UE and the base station are transmitted through different first radio bearers, while two different QUIC tunnels are established between the base station and the SF and DAF, or two QUIC tunnels are established between the base station and the DPF, respectively corresponding to AI data and sensing data.

[0284] It is important to note that the DPAP header is not mandatory. If the data packets transmitted between the UE and the core network equipment are IP packets, a DPAP header is not necessarily required. If the data plane data packets contain a DPAP header, the information contained in the DPAP header can be found in the description of the information contained in the DPAP header in the embodiment shown in Figure 3 above, and will not be repeated here.

[0285] Taking uplink data plane data transmission as an example, after the base station receives the data plane data sent by the UE through the first radio bearer, the base station can encapsulate the QUIC tunnel corresponding to the first radio bearer of the data plane data into a QUIC data packet and then deliver it to the core network equipment (such as SF, DAF or DPF).

[0286] In some embodiments, if the core network is uniformly handled by the DPF for data plane data acquisition, the base station delivers the data plane data packets to the DPF through the QUIC tunnel. The DPF can then further deliver the data packets to the corresponding SF or DAF based on the data type in the DPAP header of the data packet, the destination node identifier, or the destination IP address in the IP header of the data packet.

[0287] Taking downlink data plane data transmission as an example, after the base station receives data plane data from core network equipment (such as SF, DAF, or DPF), it maps the data to the first radio bearer of the corresponding UE based on at least one of the QoS identifier, data identifier, data type, target node identifier, and target port number information in the GTP tunnel and / or DPAP header, and then sends it to the corresponding UE. This means that the base station needs to receive in advance the mapping information from the AMF or UE from at least one of the QoS identifier, data identifier, data type, target node identifier, and target port number information in the GTP tunnel and / or DPAP subheader to the UE's first radio bearer.

[0288] Example 5: Data plane data is transmitted between the UE and the base station based on the first radio bearer, and data plane data is transmitted between the base station and the core network equipment based on DPAP.

[0289] In some embodiments, the base station and the core network equipment can transmit data plane data based on DPAP, and the protocol stack can be DPAP / UDP / IP, DPAP / SCTP / IP, or DPAP / SCTP / IP.

[0290] The DPAP header of a DPAP packet includes at least one of the following:

[0291] QoS indication;

[0292] Data type indicator;

[0293] Data identification;

[0294] Source node identifier;

[0295] At least one target node identifier;

[0296] Source port number;

[0297] Target port number;

[0298] Protocol identifier; or

[0299] Timestamp.

[0300] For a description of the DPAP header, please refer to the corresponding description in the embodiment shown in Figure 3 above, which will not be repeated here.

[0301] The protocol stack corresponding to DPAP includes at least one of the following:

[0302] DPAP;

[0303] UDP;

[0304] Stream Control Transmission Protocol (SCTP); or

[0305] IP.

[0306] In some embodiments, multiple DPAP tunnels can be established based on the different QoS requirements of the data plane data transmitted between network elements. DPAP tunnels can be configured with different granularities; for example, a DPAP tunnel can correspond one-to-one with a UE's first radio bearer, or one DPAP tunnel can correspond to multiple first radio bearers of a UE. Furthermore, DPAP tunnels can also correspond to different fragments of a UE; for example, AI data and sensing data can correspond to different data plane fragments. For network elements that support both AI data and sensing data transmission, different DPAP tunnels are established between network elements corresponding to AI and sensing-related data plane data, respectively.

[0307] It should be noted that the data encapsulated within the DPAP tunnel includes both IP packets and non-IP packets.

[0308] Taking data plane data transmission between a base station and the core network SF as an example, the base station can encapsulate the data plane data into a DPAP tunnel and then deliver it to the core network device DPF. The DPF then delivers the IP or non-IP data packets inside to the SF or DAF. In scenarios where the DPAP header contains multiple target node identifiers, the DPF is responsible for further delivering the data packet to the corresponding network elements of the core network.

[0309] In some embodiments, taking data plane data transmission between a base station and a neighboring base station as an example, the base station can encapsulate the data plane data into a DPAP tunnel and then send it to the neighboring base station.

[0310] In traditional wireless communication networks, control plane signaling between the base station and the core network is exchanged via NGAP signaling between the base station and the AMF (Active Data Center). Control signaling between the base station and other core network devices is also first sent to the AMF and then forwarded to other core network devices by the AMF. On the other hand, user plane data between the base station and the core network is transmitted via NG-U tunnel between the base station and the UPF (User Data Center), and then sent to the data network by the UPF.

[0311] For data plane data transmission between the base station and the core network, a Data Transfer Provider (DPF) can be introduced. This means that data plane data transmission between the base station and the core network can be uniformly sent from the base station to the DPF, which then forwards the corresponding data to other data plane-related core network devices such as the Data Access Provider (DAF) and the First Radio Bearer (SF). For example, Figure 17 illustrates a data plane architecture between a base station and the core network according to some embodiments. In some embodiments, for the data tunnel corresponding to data plane data transmission, the AMF can send data tunnel configuration-related signaling to the DPF for configuring the relevant data tunnel for data plane data forwarding processing. In some embodiments, the AMF can also send data tunnel configuration-related signaling to the base station for configuring the relevant data tunnel and / or the corresponding first radio bearer.

[0312] It is important to note that base stations can adopt an architecture that separates remote units (RUs), distributed units (DUs), and centralized units (CUs). In this case, if the core network's SF needs to acquire sensing data from the base station, it can do so in the following ways:

[0313] Sensing data from RU and / or DU can be sent from RU and / or DU to CU, then from CU to DPF, and finally from DPF to SF; or,

[0314] Sensing data from RU and / or DU can be sent from RU and / or DU to CU, and then from CU to SF; or,

[0315] Sensing data from the RU and / or DU can be sent from the RU and / or DU to the DPF, and then forwarded by the DPF to the SF; or,

[0316] Sensing data from RU and / or DU can be sent directly from RU and / or DU to SF.

[0317] Similarly, for AI-related data, if the core network's DAF needs to obtain AI training data from the RU or DU, or if the core network's DAF needs to send AI analysis data or AI models to the RU or DU, it can be done in the following way:

[0318] AI-related data can be sent from RU and / or DU to CU, then CU sends it to DPF, and DPF forwards it to DAF;

[0319] AI-related data can be sent from DAF to DPF, DPF to CU, and then CU to RU and / or DU;

[0320] AI-related data can be sent from RU and / or DU to CU, and then CU sends it to DAF;

[0321] AI-related data can be sent from DAF to CU, and then from CU to RU and / or DU;

[0322] AI-related data can be sent from RU and / or DU to DPF, and then forwarded by DPF to DAF;

[0323] AI-related data can be sent from DAF to DPF, and then from DPF to RU and / or DU;

[0324] AI-related data can be sent directly to the DAF from the RU and / or DU; or...

[0325] AI-related data can be sent directly from DAF to RU and / or DU.

[0326] Based on the above description, in some embodiments, the transmission of data plane data with the third node includes transmitting data plane data with the third node through a fourth node.

[0327] The fourth node includes at least one of the following: DPF, AMF, or Mobility Management Entity (MME).

[0328] In some embodiments, when the second node adopts a separate structure, the second node includes at least one of RU, DU, and CU, and transmits data plane data with the third node, including RU and / or DU transmitting data plane data with the third node.

[0329] In some embodiments, when the second node adopts a split structure and introduces a DPF, the second node includes at least one of RU, DU, and CU. Taking the transmission of third data to the third node through the fourth node as an example, it can be that RU and / or DU transmit data plane data to CU, and CU transmits data plane data to the third node through the fourth node; or, RU and / or DU transmit data plane data to the third node through the fourth node.

[0330] For example, as shown in Figure 18, which is a schematic diagram of another data plane transmission architecture according to some embodiments, taking data plane data transmission between the DPF, RU, and SF as an example, the RU can encapsulate the data plane data into GTP packets and then deliver them to the core network device DPF. In some embodiments, the DPF can encapsulate the data packet into a GTP tunnel between the DPF and SF according to the data type or destination node identifier in the GTP header of the data packet, and then send it to one or more SFs.

[0331] It should be noted that the GTP tunnel between DPF and SF is optional. If the data packet transmitted by RU is already an IP packet with the destination address of SF, DPF can directly route the IP packet to SF after receiving the data packet without encapsulating it into a GTP tunnel.

[0332] To support data analysis and processing in any topology of future wireless communication networks, base stations (including CUs and / or DUs), core networks, or AFs / ASs all support Data Plane Functions (DAFs), enabling data acquisition, data storage, data processing, model training, model inference, and model monitoring. As shown in Figure 18, the DAF can be located in the DU, CU, RAN, CN, AS, or AF. In addition, CUs, DUs, core networks, or AFs / ASs can be configured with Data Plane Functions (DPFs), which separate the data plane acquisition function from the DAF. As shown in Figure 18, xNBs can directly interact with neighboring xNBs, core networks, or ASs / AFs via the DAF, or complete data plane data acquisition and management through the DPF. Subsequently, the DAF performs AI model training and / or AI model inference, as well as AI analytics generation.

[0333] In some embodiments, data acquisition on the data plane includes not only the collection of AI training data, AI analysis data, AI models, and AI model performance data, but also the transmission of intermediate computation results of AI models used for federated learning. Data consumers can collect data from data producers one-time based on a request-response model, periodically push data between data consumers and data producers based on a subscription notification model, or trigger data acquisition based on specific events.

[0334] To support the acquisition and processing of sensing data in future wireless communication networks, base stations, core networks, or AF / AS can all support SF (Sensing Detection and Sensing) to perform functions such as sensing data acquisition, sensing data storage, or sensing data processing. For base stations, they can be further divided into RU (Real Estate Root), DU (Distribution Unit), and CU (Collection Unit). Here, RU, DU, and / or CU can all support SF functionality. RU may be co-located with DU or deployed separately. As shown in Figure 19, SF can be located at RU, DU, xNB, CN, AS, or AF. Here, RU, DU, and / or xNB themselves can have sensing functions, perform sensing operations, and acquire raw sensing data. AF or AS may acquire sensing data from third-party sensors. From the base station's perspective, the sensing data from RU or DU can be processed directly at the RU or DU side to obtain sensing results. Furthermore, the sensing data from RU or DU can also be sent to CU, core network equipment, or AF / AS for further processing. Similarly, the sensing data from CU or base station can also be processed directly at CU or base station to obtain sensing results. Furthermore, the sensing data from RU, DU, CU, or base station can also be sent to core network equipment or AF / AS for further processing.

[0335] In addition, the base station, core network, or AF / AS can be configured to include a DPF, separating the sensing data acquisition and transmission function from the SF. Figure 19 shows a schematic diagram of another sensing data plane transmission architecture according to some embodiments. The xNB can interact with the xNB, core network, or AS / AF directly through the SF, or it can complete the acquisition and transmission of sensing data through the DPF. Subsequently, the SF performs sensing data analysis and derives sensing results or intermediate results. Furthermore, the RU or DU can also interact with the xNB, core network, or AS / AF directly through the SF, or it can complete data plane acquisition and transmission through the DPF. Subsequently, the SF performs sensing data analysis and derives sensing results or intermediate results.

[0336] In some embodiments, perception data acquisition includes not only the collection of perception data from various perception scenarios, but also the transmission of perception analysis results. Data consumers can collect data from data producers one-time based on a request-response model, periodically push data between data consumers and data producers based on a subscription notification model, or trigger data collection based on specific events.

[0337] Based on the above description, in some embodiments, the second node and / or the third node support sensing functions, which include at least one of the following:

[0338] Sensor data acquisition;

[0339] Sensing data storage; or

[0340] Sensing data processing.

[0341] In some embodiments, the second node and / or the third node supports data analysis functions, which include at least one of the following:

[0342] AI data collection;

[0343] AI data storage;

[0344] AI data processing;

[0345] AI model training;

[0346] AI model inference; or

[0347] AI model monitoring.

[0348] In some embodiments, the second node and / or the third node support data plane functionality, which is used for data plane data acquisition and / or data plane data processing.

[0349] AI models need to support functions such as data acquisition, data storage, data processing, AI model training, AI model monitoring, and AI model inference. From the base station's perspective, the base station can obtain AI-related data from neighboring base stations, the core network, OAM, application servers (AS), or AF for its own model training. In some embodiments, the base station can perform AI inference and generate AI analytics based on the AI ​​model. Furthermore, the AI ​​model used by the base station can be trained through core network equipment, AS / AF, or OAM, and then sent to the base station after training. On the other hand, the base station can provide AI training data and AI analytics according to the needs of the UE, xNB, core network, OAM, or AS / AF. For scenarios where the AI ​​model used by the base station is trained by neighboring base stations, the core network, OAM, or AS / AF, the base station may also need to further provide performance testing information of the AI ​​model to neighboring base stations, the core network, OAM, or AS / AF.

[0350] Based on this, in some embodiments, after the second node receives data plane data from the third node, it trains the AI ​​model of the second node based on the data plane data.

[0351] In some embodiments, the second node receives data plane data from the third node, which is used to indicate the AI ​​model that the second node should use.

[0352] In some embodiments, after the second node uses the AI ​​model indicated by the data plane data, it sends performance testing information for the AI ​​model to the third node.

[0353] In scenarios where the CU / DU are separated, the CU can obtain AI-related data from the DU for its own model training, and the DU can also obtain AI-related data from the CU for its own model training. In some embodiments, both the CU and DU can perform AI inference and generate AI analytics based on the AI ​​model. Furthermore, the AI ​​model used by the DU can be trained by the CU, and the trained AI model is then sent to the DU for use. On the other hand, the CU or DU can provide AI training data and AI analytics according to their needs. In scenarios where the AI ​​model used by the DU is trained by the CU, the DU may also need to further provide performance evaluation information of the AI ​​model to the CU.

[0354] Based on this, in some embodiments, the second node includes a CU and a DU, wherein the CU is used to obtain AI training data from the DU and to train the AI ​​model of the second node based on the AI ​​training data; or, the DU is used to obtain AI training data from the CU and to train the AI ​​model of the second node based on the AI ​​training data.

[0355] To support efficient data acquisition, the collectable data and data transmission methods need to be pre-configured. For example, xNBs and neighboring xNBs, CNs, or AFs / ASs need to inform each other what data they can provide, which AI models they support, AI analytics, whether they support AI model training, what various sensing capabilities they possess, what data they can provide, and what sensing scenarios they support.

[0356] Based on this, in some embodiments, the second node sends second information to the third node, the second information being used to indicate at least one of the following:

[0357] The second node possesses perceptual capabilities;

[0358] The second node can provide sensing data;

[0359] The second node supports the following perception scenarios;

[0360] The second node can provide data plane data;

[0361] The second node supports AI models;

[0362] The second node supports AI analysis; or

[0363] Does the second node support the training of AI models?

[0364] For the transmission of sensing data and / or data plane data, traditional methods can be used, such as F1 tunnel (DU and CU), Xn tunnel (between xNBs), and NG tunnel (between base station and CN). Furthermore, based on the characteristics of data plane data and / or sensing data, new data tunnels can be designed between xNBs and CNs, or between CUs and DUs, or between CN network elements to improve the efficiency of sensing data and / or data plane data transmission. Additionally, for the transmission of raw data plane data and / or raw sensing data, or AI models, compression can be performed to reduce the amount of data transmitted. To ensure the security of data transmission, further improvements are needed in data security and integrity protection.

[0365] The foregoing primarily describes the solution provided in this disclosure from the perspective of the interaction between various nodes. It is understood that each node, such as the first node or the second node, includes corresponding hardware structures and / or software modules to perform the aforementioned functions. Those skilled in the art should readily recognize that, based on the algorithmic steps of the examples described in conjunction with the embodiments disclosed herein, 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.

[0366] This disclosure embodiment can divide the first node or the second node 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.

[0367] Figure 20 is a block diagram of a communication device according to some embodiments. As shown in Figure 20, the communication device 30 includes a communication unit 301.

[0368] The communication device 30 can be the first node or a chip within the first node. When the communication device 30 is used to implement the functions of the first node in the above embodiments, each unit is used to implement the following functions.

[0369] The communication unit 301 is used to transmit data plane data based on the first wireless bearer and the second node, and the transmission includes receiving or sending.

[0370] In some embodiments, the communication unit 301 is used to transmit data plane data with the second node based on RRC signaling, or to transmit RRC signaling with the second node, wherein the NAS message in the RRC signaling carries data plane data.

[0371] In some embodiments, the communication unit 301 is further configured to send first information to the second node, the first information indicating at least one of the following: the perception capability of the first node; the perception data that the first node can provide; the perception scenarios supported by the first node; the data plane data that the first node can provide; the AI ​​model supported by the first node; the AI ​​analysis supported by the first node; or, whether the first node supports the training of the AI ​​model.

[0372] Figure 21 is a block diagram of another communication device according to some embodiments. As shown in Figure 21, the communication device 40 includes a communication unit 401.

[0373] The communication device 40 can be the second node or a chip within the second node. When the communication device 40 is used to implement the functions of the second node in the above embodiments, each unit is used to implement the following functions.

[0374] The communication unit 401 is used to transmit data plane data with the third node, including receiving or sending.

[0375] In some embodiments, the communication unit 401 is further configured to receive data plane data transmitted by the first node based on the first radio bearer; or to transmit data plane data to the first node based on the first radio bearer.

[0376] In some embodiments, the communication unit 401 is used to send GTP data packets to a third node, or to receive GTP data packets from a third node. The GTP data packets are obtained by encapsulating the data plane data of the first radio bearer with a corresponding GTP tunnel.

[0377] In some embodiments, the communication unit 401 is configured to send DPAP data packets to a third node, or to receive DPAP data packets from a third node, wherein the DPAP data packets are obtained by encapsulating the data plane data of the first radio bearer with a corresponding DPAP tunnel.

[0378] In some embodiments, the communication unit 401 is used to transmit data plane data with the third node through the fourth node.

[0379] In some embodiments, the communication unit 401 is further configured to send second information to the third node, the second information indicating at least one of the following:

[0380] The second node possesses perceptual capabilities;

[0381] The second node can provide sensing data;

[0382] The second node supports the following perception scenarios;

[0383] The second node can provide data plane data;

[0384] The second node supports AI models;

[0385] The second node supports AI analysis; or

[0386] Does the second node support the training of AI models?

[0387] It should be noted that the units in Figure 20 or Figure 21 can also be called modules; for example, a communication unit can be called a communication module. Furthermore, in the embodiments shown in Figure 20 or Figure 21, the names of the various units may not be those shown in the figures; for example, a communication unit can also be called a transmission unit.

[0388] If the units in Figure 20 or Figure 21 are implemented as software functional modules and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solutions of the embodiments of this disclosure, or the parts that contribute to related technologies, or all or part of the technical solutions, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) or processor to execute all or part of the steps of the methods of the various embodiments of this disclosure. Storage media for storing computer software products include various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0389] When the communication device 30 or communication device 40 implements the functions of the integrated module in hardware, this disclosure provides a block diagram of a communication device. As shown in FIG22, the communication device 50 includes: a processor 502, a communication interface 503, and a bus 504. In some embodiments, the communication device 50 may further include a memory 501.

[0390] Processor 502 may implement or execute various exemplary logic blocks, modules, and circuits described in connection with embodiments of this disclosure. Processor 502 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 connection with embodiments of this disclosure. Processor 502 may also be a combination that implements computing functions, for example, including one or more microprocessor combinations, a combination of a digital signal processor (DSP) and a microprocessor, etc.

[0391] The communication interface 503 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.

[0392] The memory 501 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 medium or other magnetic storage device, 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.

[0393] In some embodiments, the memory 501 may exist independently of the processor 502. The memory 501 may be connected to the processor 502 via a bus 504 and is used to store instructions or program code. When the processor 502 calls and executes the instructions or program code stored in the memory 501, it can implement the data transmission method provided in the embodiments of this disclosure.

[0394] In other embodiments, memory 501 may also be integrated with processor 502.

[0395] Bus 504 can be an extended industry standard architecture (EISA) bus, etc. Bus 504 can be divided into address bus, data bus, control bus, etc. For ease of representation, only one thick line is used in Figure 22, but this does not mean that there is only one bus or one type of bus.

[0396] Through the above description of the implementation methods, those skilled in the art can clearly understand that, for the sake of convenience and brevity, only the division of the above functional modules is used as an example. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the first node or the second node can be divided into different functional modules to complete all or part of the functions described above.

[0397] This disclosure also provides a computer-readable storage medium. All or part of the processes in the above method embodiments can be executed by computer instructions instructing related hardware. The program can be stored in the computer-readable storage medium, and when executed, it can include the processes of the above method embodiments. The computer-readable storage medium can also be an external storage device for the first or second node, such as a pluggable hard drive, smart media card (SMC), secure digital (SD) card, or flash card equipped on the first or second node. In some embodiments, the computer-readable storage medium can also include both internal storage units of the first or second node and external storage devices. The computer-readable storage medium is used to store the computer program and other programs and data required by the first or second node. The computer-readable storage medium can also be used to temporarily store data that has been output or will be output.

[0398] This disclosure also provides a computer program product comprising a computer program that, when run on a computer, causes the computer to perform any of the data transmission methods provided in the above embodiments.

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

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

[0401] The above are merely specific embodiments 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 data transmission method applied to a first node, the method comprising: Data plane data is transmitted between the first wireless bearer and the second node, and the transmission includes receiving or sending.

2. The method according to claim 1, wherein, The first radio bearer is not associated with the Protocol Data Unit (PDU) session, and different first radio bearers can correspond to different Quality of Service (QoS) parameter requirements.

3. The method according to claim 1, wherein, The data plane data includes at least one of the following: Artificial intelligence (AI) data labeling; AI models; AI training data; AI inference data; AI data analysis; AI model performance data; Sensing data identification; Communication-sensing data; Environmental sensing data; or Data perceived by the target object.

4. The method according to claim 1, wherein, The air interface protocol stack corresponding to the first wireless bearer includes at least one of the following: Data plane adaptation protocol DPAP layer; Packet Data Convergence Protocol (PDCP) layer; Radio Link Control (RLC) layer; or Media Access Control (MAC) layer.

5. The method according to claim 4, wherein, The DPAP layer is used for at least one of the following: Transmit the data plane data; Map the quality of service flow or service flow of the data plane data to the first wireless bearer; Encapsulate the DPAP header; or Remove the DPAP header.

6. The method according to claim 5, wherein, The DPAP header includes at least one of the following: QoS indication; Data type indicator; Data identification; Source node identifier; At least one target node identifier; Source port number; Target port number; Protocol identifier; or Timestamp.

7. The method according to claim 6, wherein, The QoS indication includes at least one of the following: Data Quality Index (DQI); or Data stream identifier.

8. The method according to claim 6, wherein, The data type indicator is used to indicate at least one of the following types: AI data; Sensing data; or Other data.

9. The method according to claim 6, wherein, The protocol identifier is used to indicate at least one of the following protocols: Hypertext Transfer Protocol; File transfer protocol; g Remote Procedure Call (RPC); Real-time web communication; Message Queuing Telemetry Transport Protocol; Network sockets; or Restricted application protocol.

10. The method according to claim 6, wherein, The timestamp is used to indicate at least one of the following: Data generation time; or Data latency budget.

11. The method according to claim 5, wherein, The DPAP header includes at least one of the following: AI data identification; AI models; AI training data; AI inference data; AI data analysis data; or AI model performance data.

12. The method according to claim 5, wherein, The DPAP header includes at least one of the following: Sensing data identification; Communication-sensing data; Environmental sensing data; or Data perceived by the target object.

13. The method according to claim 5, wherein, The DPAP header includes at least one of the following: Data packet transmission sequence number; Request confirmation instructions; or Data packet reception confirmation sequence number.

14. The method according to claim 4, wherein, The data plane data is either based on Internet Protocol (IP) or based on non-IP data.

15. The method according to claim 14, wherein, When the data plane data is IP-based, at least one of the following protocol stacks exists above the DPAP layer: Transmission Control Protocol (TCP / IP) stack; User Datagram Protocol (UDP / IP) stack; Fast UDP internet connection using the QUIC / UDP / IP protocol stack; or, When the data plane data is non-IP based, the application protocol layer can be above the DPAP layer.

16. The method according to claim 1, wherein, The transmission of data plane data with the second node includes: The data plane data is transmitted with the second node based on Radio Resource Control (RRC) signaling, or the data plane data is transmitted with the second node via RRC signaling, wherein the data plane data is carried in the Non-Access Stratum (NAS) message of the RRC signaling.

17. The method according to claim 1, wherein, The first radio bearer is a Uu interface signaling radio bearer (SRB), a data radio bearer (DRB), or a data plane radio bearer (DPRB) between the first node and the second node.

18. The method according to claim 1, wherein, At least one of the first node or the second node supports a sensing function, which includes at least one of the following: Sensor data acquisition; Sensing data storage; or Sensing data processing.

19. The method according to claim 1, wherein, At least one of the first node or the second node supports data analysis functionality, which includes at least one of the following: AI data collection; AI data storage; AI data processing; AI model training; AI reasoning; or AI model performance monitoring.

20. The method according to claim 1, wherein, At least one of the first node or the second node supports data plane functionality, which includes at least one of data plane data acquisition or data plane data processing.

21. The method according to claim 1, further comprising: Send a first message to the second node, the first message indicating at least one of the following: The first node possesses sensing capabilities; The sensing data that the first node can provide; The perception scenarios supported by the first node; The first node can provide data plane data; The AI ​​models supported by the first node; AI analysis supported by the first node; or Does the first node support the training of AI models? 22. The method according to claim 1, wherein, The first node is a terminal, and the second node is an access network device; or... The first node is the terminal, and the second node is a core network device; or... The first node is the terminal, and the second node is an application server or application function.

23. A data transmission method, wherein, Applied to the second node, the method includes: Data plane data is transmitted with a third node, the transmission including receiving or sending.

24. The method of claim 23, further comprising: Receive the data plane data transmitted by the first node based on the first radio bearer; or, The data plane data is sent to the first node based on the first wireless bearer.

25. The method according to claim 24, wherein, The first radio bearer is not associated with the PDU session, and different first radio bearers correspond to different QoS parameter requirements.

26. The method according to claim 23, wherein, Data plane data is transmitted with the third node based on at least one of the following protocols: Next-generation application protocol NGAP; General Packet Radio Service Tunneling Protocol (GTP); IP; QUIC protocol; or DPAP.

27. The method according to claim 26, wherein, Data plane data transmission with the third node based on GTP includes: Sending GTP data packets to the third node, or receiving GTP data packets from the third node, wherein the GTP data packets are obtained by encapsulating the data plane data of the first radio bearer with corresponding GTP tunnels.

28. The method according to claim 27, wherein, The GTP header of the GTP data packet includes at least one of the following: QoS indication; Data type indicator; Data identification; Source node identifier; At least one target node identifier; Source port number; Target port number; Protocol identifier; or Timestamp.

29. The method according to claim 26 or 27, wherein, The protocol stack corresponding to GTP includes at least one of the following: DPAP; GTP; UDP; or IP.

30. The method according to claim 26, wherein, Data plane data transmission with the third node based on DPAP includes: Send DPAP data packets to the third node, or receive DPAP data packets from the third node, wherein the DPAP data packets are obtained by encapsulating the data plane data of the first radio bearer with the corresponding DPAP tunnel.

31. The method according to claim 30, wherein, The DPAP header of the DPAP packet includes at least one of the following: QoS indication; Data type indicator; Data identification; Source node identifier; At least one target node identifier; Source port number; Target port number; Protocol identifier; or Timestamp.

32. The method according to claim 26 or 31, wherein, The protocol stack corresponding to DPAP includes at least one of the following: DPAP; UDP; Stream Control Transfer Protocol (SCTP); or IP.

33. The method according to claim 23, wherein, The second node includes at least one of a remote unit RU, a distributed unit DU, a centralized unit CU, and a base station.

34. The method according to claim 23, wherein, The transmission of data plane data with the third node includes: Data plane data is transmitted between the fourth node and the third node.

35. The method according to claim 34, wherein, The fourth node includes at least one of the following: Data Plane Function (DPF), Access Mobility Management Function (AMF), and Mobility Management Entity (MME).

36. The method according to claim 34, wherein, The second node includes at least one of RU, DU, and CU; The transmission of data plane data between the fourth node and the third node includes: The RU and / or the DU send the data plane data to the CU, and the CU sends the data plane data to the third node through the fourth node; or, The RU and / or the DU send the data plane data to the third node through the fourth node.

37. The method according to claim 23, wherein, At least one of the second node or the third node supports a sensing function, which includes at least one of the following: Sensor data acquisition; Sensing data storage; or Sensing data processing.

38. The method according to claim 23, wherein, At least one of the second node or the third node supports data analysis functions, which include at least one of the following: AI data collection; AI data storage; AI data processing; AI model training; AI model inference; or AI model monitoring.

39. The method of claim 23, further comprising: Send a second message to the third node, the second message indicating at least one of the following: The second node possesses perception capabilities; The second node can provide sensing data; The second node supports the following perception scenarios; The second node can provide data plane data; The AI ​​models supported by the second node; The second node supports AI analysis; or Does the second node support the training of AI models? 40. The method according to claim 23, wherein, The second node is an access network device, and the third node is a core network device; or, The second node is an access network device, and the third node is one of the following: an application server, application functions, and data analysis functions; or, The second node is a core network device, and the third node is an access network device; or, The second node is an access network device, and the third node is an access network device.

41. The method according to claim 24, wherein, The first node is a terminal.

42. A communication device, comprising: Memory and processor; The memory and the 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 according to any one of claims 1 to 41.

43. A computer-readable storage medium, wherein, The computer-readable storage medium stores computer instructions that, when executed on a computer, cause the computer to perform the method according to any one of claims 1 to 41.

44. A computer program product, wherein, The computer program product includes computer instructions that, when executed on a computer, cause the computer to perform the method according to any one of claims 1 to 41.

Images