Data transmission method

Abstract

A data transmission method, executed in a first network node of a radio access network (RAN) and comprising: receiving a first connection establishment request message related to a first data transport bearer, the first connection establishment request message comprising identifier information of a service type or a function type not associated with a user equipment (UE), or identifier information of a plurality of UEs, the first data transport bearer being used for transmitting data between the first network node and a second network node of a core network, and the data being data related to the service type or function type, or data related to the plurality of UEs in the RAN; and sending a first connection establishment request response message related to the first data transport bearer, so as to establish the first data transport bearer between the first network node of the RAN and the second network node of the core network.

Description

Data transmission method Technical Field

[0001] The present application relates to the field of wireless communication technology, and in particular to a data transmission method. Background Art

[0002] Since 3G, mobile communication networks based on Third Generation Partnership Project (3GPP) standards have evolved from third-generation mobile communications, dominated by Wideband Code Division Multiple Access (WCDMA), to fourth-generation mobile communications, dominated by Long Term Evolution (LTE), and finally to the current fifth-generation mobile communication system architecture, characterized by New Radio (NR). These systems are primarily divided into two parts: the Radio Access Network (RAN) and the Core Network (CN). However, the standard interfaces between the RAN and CN vary, demonstrating the continuous evolution of mobile communication technology. Figure 1 shows a 5G mobile communication system architecture model, which primarily includes user equipment (UE), the Radio Access Network (RAN), and the Core Network (5G Core Network (5GC). The Access and Mobility Management Function (AMF) and the User Plane Function (UPF) are two network nodes in the 5G Core Network (5GC). The RAN and AMF are connected via the N2 interface, and the RAN and UPF are connected via the N3 interface. Since the gNB is a key logical network node in the RAN and the interface node connecting the RAN with the AMF and UPF 30d, the N2 and N3 interfaces are also the interfaces between the gNB and the AMF and UPF 30d, respectively. The N2 and N3 interfaces are collectively referred to as the NG interface, i.e., the interface between the RAN and the 5GC. The NG interface is functionally divided into the control plane interface (NG-C) and the user plane interface (NG-U), corresponding to the N2 and N3 interfaces, respectively.

[0003] The NG-C protocol stack is shown in Figure 2 below. The transport layer's data link layer, physical layer, Internet Protocol (IP), and stream control transmission protocol (SCTP) are all based on existing technologies, while the application layer's NG application protocol (NGAP) is the primary protocol that embodies NG-C's capabilities.

[0004] The main capabilities provided by NGAP are:

[0005] 1. The process of establishing, maintaining, and releasing a Protocol Data Unit (PDU) session. A PDU Session is used to define the connection between the UE and the data network (DN) that provides the PDU connection service. It is used to associate all information and resources related to the PDU connection (including transmission) service.

[0006] 2. Execute the handover process between the same Radio Access Technology (RAT) and different RATs;

[0007] 3. Differentiate the signaling management specific to each UE at the protocol level;

[0008] 4. Transmit Non-Access Signalling (NAS) messages between the UE and the AMF;

[0009] 5. Resource reservation mechanism related to packet flow.

[0010] In particular, the capabilities provided by NGAP also include the transmission of some special service data, such as the transparent transmission of New Radio Positioning Protocol A (NR Positioning Protocol A, NRPPa, defined in 3GPP TS 38.455) messages, some of which include data related to positioning services.

[0011] The NG-U protocol stack is shown in Figure 3 below. The physical layer, data link layer, IP, User Datagram Protocol (UDP), and General Packet Radio Service Tunnelling Protocol-user plane (GTP-U) protocols are all based on existing technologies. The PDU Session User Plane Protocol (PDU) is a unique protocol associated with the PDU Session that provides control information elements (CIEs) for the user plane PDUs, such as the QoS flow identifier (QFI) and reflective QoS indicator (RQI). The main functions of NG-U are: supporting non-guaranteed delivery of PDU Session user plane PDUs between the RAN and the UPF 30d.

[0012] Figure 4 shows the user plane protocol stack for the PDU Session in a 5G mobile communication system. The PDU Session is related to the PDU Session user plane transmission between the UE and the DN and is related to UE services. NG-U, the portion of the N3 user plane corresponding to the NG interface, is part of the PDU Session user plane transmission between the UE and the DN. Therefore, NG-U is usually related to UE services. The PDU Session user plane further includes the 5G-AN protocol layer, which corresponds to the radio interface (Uu interface) between the UE and the gNB. The protocol stack for the Uu interface is shown in Figure 5 below. For details on the Service Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP), Radio Link Control (RLC), Medium Access Control (MAC), and physical layer PHY protocol stack, please refer to the relevant 3GPP standard protocols. Technical issues:

[0013] With the development of technology and business requirements, there will be more and more demands for data interaction between RAN network nodes and CN network nodes. For example:

[0014] 1. RAN Artificial Intelligence (AI) Functions: The interaction between the RAN's AI functions and / or the CN's AI functions, particularly data collection related to AI functions, including data collection and distribution related to inference, model monitoring, and model training. The objectives of the SA2 Rel-19 AI Project Report include studying the interaction and coordination between the CN and RAN to support an AI-enabled RAN.

[0015] 2. Communication Awareness Service: Communication awareness functions are usually performed by RAN network nodes. However, as a service provided by the mobile communication network, awareness service is usually managed by the CN. Therefore, a large amount of service data-related interaction occurs between the RAN and CN.

[0016] 3. Special broadcast or multicast services: This is especially true for bidirectional multicast services based on unicast mode. Currently, 5G-supported broadcast or multicast services are typically only available for downlink services. A typical application is shown in Figure 6. UE1 and UE2 provide hot standby functionality at the radio access network (RAN) layer for highly reliable bidirectional real-time services. While the downlink is similar to multicast, the uplink represents a new service type. Therefore, new service data interaction requirements arise between the RAN and CN.

[0017] Typically, these services or functional requirements involve data exchange between RAN and CN nodes, including both user equipment (UE)-related and non-UE-related information. This non-UE-related information may involve cells, RAN nodes, or specific services. However, current 5G mobile communication systems are still unable to effectively support these service requirements, especially those involving non-UE-related data.

[0018] Specifically, on the one hand, in 5G and earlier mobile communication systems, the RAN node RAN (gNB) does not support the user plane data transmission bearer technical solution for non-UE-related or multiple UE-related and bidirectional business data; the interface between the RAN node (gNB) and the CN node also does not support the user plane data transmission bearer technical solution for non-UE-related or multiple UE-related and bidirectional business data. Furthermore, the user plane-based data transmission bearer technical solution is not supported between the nodes within the core network and between the core network node and the data network (DN) to exchange non-UE-related or multiple UE-related and bidirectional business data; on the other hand, with the continuous increase in business demands and types, there is also a need to further enhance the control plane message solution that supports non-UE or UE-associated business data transmission based on the existing interface between the RAN node (gNB) and the CN node to support more types of business data, especially to provide a general and scalable control plane message solution for business data transmission.

[0019] The demand for data interaction related to the above services or functions, as well as related problems, also exist between RAN nodes. In the 5G mobile communication system, RAN nodes are connected through the Xn interface. The Xn interface is also functionally divided into the control plane interface (Xn Interface Control Plane, Xn-C) and the user plane interface (Xn-U). The transport layer protocol of Xn-C is exactly the same as that of NG-C, and the application layer protocol of Xn-C is XnAP (Xn Application Protocol); while the transport layer protocol stack of Xn-U is exactly the same as that of NG-G, that is, it includes GTP-U, UDP, IP, data link layer (Data link layer) and physical layer (Physical layer).

[0020] Furthermore, the data exchange requirements and related issues related to the aforementioned services or functions also exist between different nodes within the RAN. In the 5G mobile communication system, the gNB node in the RAN can be further divided into two network nodes: the gNB-CU (gNB Central Unit) and the gNB-DU (gNB Distributed Unit). The gNB-CU and gNB-DU are connected via the F1 interface. The F1 interface is functionally divided into the control plane interface (F1-C) and the user plane interface (F1-U). The transport layer protocol of F1-C is identical to that of NG-C, and the application layer protocol of F1-C is F1AP (F1 Application Protocol). The transport layer protocol stack of F1-U is identical to that of NG-G, namely GTP-U / UDP / IP / data link layer / physical layer.

[0021] Summary of the Invention

[0022] An object of the present disclosure is to provide a data transmission method, a user equipment, and a base station.

[0023] In a first aspect, the present invention provides a data transmission method, executed in a first network node of a radio access network (RAN), comprising:

[0024] receiving a first connection establishment request message related to a first data transmission bearer, used to establish the first data transmission bearer, wherein the first connection establishment request message includes identification information of a service type or function type associated with a non-user equipment UE, or identification information of multiple UEs, and the first data transmission bearer is used to transmit data between the first network node and the second network node, the data being data related to the service type or function type, or data related to the multiple UEs in the radio access network; and

[0025] A first connection establishment request response message related to the first data transmission bearer is sent to establish the first data transmission bearer between a first network node of the radio access network RAN ​​and the second network node.

[0026] In a second aspect, an embodiment of the present invention provides a network node, comprising a processor and a memory, wherein the processor is configured to call and execute a computer program stored in the memory so that a device equipped with the processor performs the disclosed method.

[0027] In a third aspect, an embodiment of the present invention provides a data transmission method, executed in a data transmission system, characterized by comprising:

[0028] The third network node sends a first connection establishment request message related to a first data transmission bearer to the first network node, so as to establish the first data transmission bearer between the first network node and the second network node, wherein the first connection establishment request message includes identification information of a service type or a function type associated with a non-UE, or identification information of multiple UEs; and the first network node sends a first connection establishment request response message related to the first data transmission bearer to the third network node;

[0029] The third network node sends a second connection establishment request message related to the first data transmission bearer, the second data transmission bearer, and / or the third data transmission bearer to the fourth network node, wherein the second data transmission bearer is used to represent a bearer between the second network node and the fifth network node, the third data transmission bearer is used to represent a bearer between the second network node and the sixth network node, and the first data transmission bearer, the second data transmission bearer, and the third data transmission bearer are all used to transmit data related to a service type or a function type associated with the non-UE, or data of the multiple UEs;

[0030] The fourth network node sends a third connection establishment request message related to the first data transmission bearer to the third network node;

[0031] The fourth network node sends a fourth connection establishment request message related to the first data transmission bearer, the second data transmission bearer, and / or the third data transmission bearer to the second network node to establish the first data transmission bearer, the second data transmission bearer, and / or the third data transmission bearer.

[0032] In a fourth aspect, the present invention provides a data transmission method, executed in a first network node of a radio access network (RAN), comprising:

[0033] Receive or send a protocol transmission message; wherein the protocol transmission message carries a protocol data unit (PDU); the protocol transmission message and the protocol data unit type both correspond to the service type or function type.

[0034] In a fifth aspect, an embodiment of the present invention provides a network node, comprising a processor and a memory, wherein the processor is configured to call and execute a computer program stored in the memory so that a device equipped with the processor performs the disclosed method.

[0035] In a sixth aspect, an embodiment of the present invention provides a data transmission system, characterized by comprising:

[0036] A first network node, a second network node, a third network node, a fourth network node, and a fifth network node, wherein:

[0037] The first network node is configured to receive a first connection establishment request message related to a first data transmission bearer, where the first data transmission bearer is used to represent a bearer between the first network node and the second network node;

[0038] The second network node is configured to receive a fourth connection establishment request message related to the first data transmission bearer, a second data transmission bearer, and / or a third data transmission bearer, wherein the second data transmission bearer is used to represent a bearer between the second network node and the fifth network node, and the third data transmission bearer is used to represent a bearer between the second network node and the sixth network node;

[0039] The third network node sends a first connection establishment request message related to the first data transmission bearer to the first network node, so as to establish the first data transmission bearer between the first network node and the second network node, wherein the first connection establishment request message includes identification information of a service type or a function type associated with the non-UE, or identification information of multiple UEs; the first network node sends a first connection establishment request response message related to the first data transmission bearer to the third network node; and the third network node sends a second connection establishment request message related to the first data transmission bearer, the second data transmission bearer, and / or the third data transmission bearer to the fourth network node, wherein the first data transmission bearer, the second data transmission bearer, and the third data transmission bearer are all used to transmit data related to the service type or function type associated with the non-UE, or data of the multiple UEs;

[0040] the fourth network node is configured to send a third connection establishment request message related to the first data transmission bearer to the third network node, send a fourth connection establishment request message related to the first data transmission bearer, the second data transmission bearer, and / or the third data transmission bearer to the second network node to establish the first data transmission bearer, the second data transmission bearer, and / or the third data transmission bearer, and send a fifth connection establishment request message related to the second data transmission bearer to the fifth network node to establish the second data transmission bearer;

[0041] The fifth network node is configured to receive a fifth connection establishment request message related to the second data transmission bearer.

[0042] The disclosed method can be programmed as computer-executable instructions stored in a non-transitory computer-readable medium. The non-transitory computer-readable medium, when loaded into a computer, instructs the processor of the computer to execute the disclosed method.

[0043] The non-transitory computer-readable medium may include at least one of the group consisting of a hard disk, a CD-ROM, an optical storage device, a magnetic storage device, a read-only memory, a programmable read-only memory, an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), and a flash memory.

[0044] The disclosed method can be programmed as a computer program product, which causes a computer to perform the disclosed method.

[0045] The disclosed method may be programmed as a computer program, which causes a computer to perform the disclosed method.

[0046] Technical effects:

[0047] Some embodiments of the present invention implement a first data transmission bearer and a second data transmission bearer between a network node of a radio access network RAN ​​and a core network service management function CNSMF node. The first data transmission bearer and the second data transmission bearer are used to transmit data destined for or originating from a network node (non-UE) of the radio access network RAN. This can provide a mechanism for establishing a non-UE data transmission bearer and for transmitting non-UE data between a core network network node and a network node of the radio access network RAN ​​based on the data transmission bearer on the user plane. Such a mechanism can be applied to, for example, AI data transmission, wireless perception service data, NRPPa (NG-RAN; NR Positioning Protocol A) data transmission defined in 3GPP TS 38.455, or some newly defined data transmission.

[0048] Some embodiments of the present invention implement a first data transmission bearer and a third data transmission bearer between a network node of the radio access network (RAN) and a network node of a data network. The first data transmission bearer and the third data transmission bearer are used to transmit data destined for or originating from a network node (non-UE) of the radio access network (RAN). This can provide a mechanism for establishing a non-UE data transmission bearer and for transmitting non-UE data between a data network network node and a network node of the radio access network (RAN) using this data transmission bearer based on the user plane. Such a mechanism can provide more third-party applications based on the Internet with the ability to access specific functions and services of the network nodes of the radio access network.

[0049] Some embodiments of the present invention implement a first data transmission bearer and a third data transmission bearer between multiple user equipment (UE) of the radio access network (RAN) and a network node of the data network. The first data transmission bearer and the third data transmission bearer are used to transmit uplink and downlink bidirectional data multicast for or related to the multiple user equipment (UE) of the radio access network (RAN). This can provide a multi-UE-based downlink data multicast and a multi-UE radio link backup mechanism for uplink selection.

[0050] Some embodiments of the present invention implement data exchange between a network node of a radio access network (RAN) and an access and mobility management function (AMF) of a core network based on control plane messages, and then exchange data with a core network node related to a service or function through the AMF, thereby implementing a specific service or function in a mobile communication system. The data exchanged is related to artificial intelligence, a radio sensing function (RS) of the RAN, or a core network service management function (CNSMF). BRIEF DESCRIPTION OF THE DRAWINGS

[0051] One or more embodiments are exemplified by the figures in the corresponding drawings. These exemplified descriptions do not constitute limitations on the embodiments. Elements with the same reference numerals in the drawings represent similar elements. Unless otherwise stated, the figures in the drawings do not constitute proportional limitations. The division of the following embodiments is for the convenience of description and should not constitute any limitation on the specific implementation of the present invention. The various embodiments can be combined and referenced with each other under the premise of no contradiction. In particular, the user plane connection can also be a data transmission bearer.

[0052] The schematic diagram of Figure 1 shows a 5G mobile communication system architecture model.

[0053] FIG2 is a schematic diagram showing the protocol stack of NG-C.

[0054] FIG3 is a schematic diagram showing the protocol stack of NG-U.

[0055] FIG4 is a schematic diagram showing the user plane protocol stack of a PDU Session in a 5G mobile communication system.

[0056] FIG5 is a schematic diagram showing the protocol stack of the Uu interface.

[0057] FIG6 is a schematic diagram showing a bidirectional multicast service based on a unicast mode.

[0058] FIG7 is a schematic diagram showing a telecommunication system for executing the method disclosed in an embodiment of the present invention.

[0059] FIG8 is a schematic diagram illustrating a data transmission method according to an embodiment of the present invention.

[0060] FIG9 is a schematic diagram illustrating a data transmission method according to another embodiment of the present invention.

[0061] FIG10 is a schematic diagram showing a data transmission method according to another embodiment of the present invention.

[0062] FIG11 is a schematic diagram showing a data transmission method according to another embodiment of the present invention.

[0063] FIG12 is a schematic diagram showing a data transmission method according to another embodiment of the present invention.

[0064] The schematic diagram of Figure 13 shows data interaction between RAN and NWDAF through the AMF network node.

[0065] The schematic diagram of Figure 14 shows the interface N-AI between AMF and NWDAF.

[0066] FIG15 is a schematic diagram showing downlink UE associated AI-P transmission (DOWNLINK UE ASSOCIATED AI-P TRANSPORT).

[0067] FIG16 is a schematic diagram showing uplink UE associated AI-P transmission (UPLINK UE ASSOCIATED AI-P TRANSPORT).

[0068] FIG17 is a schematic diagram showing downlink non-UE associated AI-P transmission (DOWNLINK NON UE ASSOCIATED AI-P TRANSPORT).

[0069] FIG18 is a schematic diagram showing uplink non-UE associated AI-P transmission (UPLINK NON UE ASSOCIATED AI-P TRANSPORT).

[0070] The schematic diagram of Figure 19 shows that RAN exchanges data through the AMF network node and the Radio Sensing Management Function (RSMF) node.

[0071] FIG20 is a schematic diagram showing an N-RS interface.

[0072] FIG21 is a schematic diagram showing downlink UE associated RS-P transmission (DOWNLINK UE ASSOCIATED RS-P TRANSPORT).

[0073] FIG22 is a schematic diagram showing uplink UE associated RS-P transmission (UPLINK UE ASSOCIATED RS-P TRANSPORT).

[0074] FIG23 is a schematic diagram showing downlink non-UE associated RS-P transmission (DOWNLINK NON UE ASSOCIATED RS-P TRANSPORT).

[0075] FIG24 is a schematic diagram showing uplink non-UE-associated RS-P transmission (UPLINK NON UE ASSOCIATED RS-P TRANSPORT).

[0076] The schematic diagram of Figure 25 shows data interaction between the RAN and the core network service management function (CN Service Management Function, CNSMF) through the AMF network node.

[0077] Figure 26 is a schematic diagram showing the N-CNS interface.

[0078] FIG27 is a schematic diagram showing downlink UE associated common service data transport.

[0079] FIG28 is a schematic diagram showing uplink UE associated common service data transport (UPLINK UE ASSOCIATED common service data TRANSPORT).

[0080] FIG29 is a schematic diagram showing downlink non-UE associated common service data transmission (DOWNLINK NON UE ASSOCIATED COMMON SERVICE DATA TRANSPORT).

[0081] FIG30 is a schematic diagram showing uplink non-UE-associated common service data transmission (UPLINK NON UE ASSOCIATED COMMON SERVICE DATA TRANSPORT).

[0082] The schematic diagram of Figure 31 shows data interaction between RAN and CNSMF through the UPF network node.

[0083] FIG32 is a schematic diagram showing a user plane connection based on the Transmission Control Protocol (TCP) on the N-SP interface.

[0084] FIG33 is a schematic diagram showing a user plane connection based on GTP-U on the N-SP interface.

[0085] The schematic diagram of Figure 34 shows the relevant signaling and processes for establishing the user plane connection between the NG-U (N3) and N-SP interfaces.

[0086] The schematic diagram of Figure 35 shows the relevant signaling and processes for establishing the user plane connection between the NG-U (N3) and N-SP interfaces.

[0087] FIG36 is a schematic diagram showing data interaction between the RAN and the data network (DN).

[0088] Figure 37 is a schematic diagram showing the protocol stack for the user plane connection between the RAN and the DN.

[0089] The schematic diagram of Figure 38 shows the signaling process related to the NG-U (N3) user plane connection in establishing the RAN and DN user plane connection.

[0090] The schematic diagram of Figure 39 shows the signaling process related to the NG-U (N3) user plane connection in establishing the RAN and DN user plane connection.

[0091] Figure 40 is a schematic diagram showing group UE services between multiple UEs and DN.

[0092] FIG41 is a schematic diagram showing the relevant signaling and process for establishing a user plane connection for group UE services.

[0093] FIG42 is a schematic diagram showing the relevant signaling and process for establishing a user plane connection for group UE services.

[0094]

[0095] The schematic diagram of Figure 43 shows the mapping of QoS flows related to the RAN and UPF user plane (RAN-UPF UP) connection and data radio bearers (DRBs) related to the Uu DRB.

[0096] FIG44 is a schematic diagram showing that an Xn interface (including Xn-C and Xn-U) is established between RAN nodes.

[0097] Figure 45 is a schematic diagram showing the control plane signaling flow and messages between RAN nodes.

[0098] Figure 46 is a schematic diagram showing that multiple RAN nodes establish a user plane connection associated with a certain service or function through the NG-U interface (i.e., N3) between them and the UPF 30d of the core network.

[0099] Figure 47 is a schematic diagram showing the signaling process and messages exchanged between multiple RAN nodes through the core network.

[0100] Figure 48 is a schematic diagram showing that the F1 interface (including F1-C and F1-U) is established between the gNB-CU and gNB-DU.

[0101] Figure 49 is a schematic diagram showing the control plane signaling procedures and messages between the gNB-CU and gNB-DU.

[0102] FIG50 is a schematic diagram showing a chip of the present invention. DETAILED DESCRIPTION

[0103] In order to make the purpose, technical solutions and advantages of this application more clear, some embodiments of this application are further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described here are only used to explain this application and are not used to limit this application.

[0104] To support a variety of new services, control plane or user plane functions are added to the interface between RAN and CN. Specifically:

[0105] On the control plane, add corresponding control plane processes for new services;

[0106] On the user plane, add new user plane connection types for new services, and add new control plane processes or enhance existing control processes to support the establishment of new user plane connection types;

[0107] In particular, the user plane connection mentioned in the present invention may also be a data transmission bearer, a user plane bearer, a GTP-U connection, a GTP-U transport bearer, a data radio bearer, etc.

[0108] The data transmission method may be performed in the telecommunications system shown in FIG7 . The network functions described in this embodiment of the present invention, such as NWDAF 30a, AMF 30b, SMF 30c, UPF 30d, RSMF 10e, RSMF 10f, and DN 40, may be executed in one or more network nodes, such as the network entity device 30. The RAN 20 in this embodiment of the present invention may include an embodiment of the base station 20a.

[0109] Referring to Figure 7 , a telecommunications system including UE 10a, UE 10b, base station (BS) 20a, and network entity device 30 performs the disclosed method according to one embodiment of the present invention. Figure 7 is illustrative and non-limiting, and the system may include more UEs, BSs, and CN entities. Connections between devices and device components are shown as lines and arrows in the figure. User equipment 10a may include a processor 11a, a memory 12a, and a transceiver 13a. User equipment 10b may include a processor 11b, a memory 12b, and a transceiver 13b. Base station 20a may include a processor 21a, a memory 22a, and a transceiver 23a. Network entity device 30 may include a processor 31, a memory 32, and a transceiver 33. Each of processors 11a, 11b, 21a, and 31 may be configured to implement the functions, procedures, and / or methods described herein. The various layers of the radio interface protocol may be implemented in processors 11a, 11b, 21a, and 31. Each of the memories 12a, 12b, 22a, and 32 is operable to store various programs and information to operate the connected processor. Each of the transceivers 13a, 13b, 23a, and 33 is operatively coupled to the connected processor to transmit and / or receive radio signals or wired signals. The UE 10a can communicate with the UE 10b via a side link. The base station 20a can be an eNB, gNB, or other type of radio node and can configure radio resources for the UEs 10a and 10b.

[0110] Each of the processors 11a, 11b, 21a, and 31 may include an application-specific integrated circuit (ASIC), other chipsets, logic circuits, and / or data processing devices. Each of the memories 12a, 12b, 22a, and 32 may include a read-only memory (ROM), a random access memory (RAM), flash memory, a storage card, a storage medium, and / or other storage devices. Each of the transceivers 13a, 13b, 23a, and 33 may include a baseband circuit and a radio frequency (RF) circuit to process radio frequency signals. When this embodiment is implemented in software, the techniques described herein may be implemented using modules, programs, functions, entities, and the like that perform the functions described herein. These modules may be stored in a memory and executed by a processor. The memory may be implemented within the processor or externally, wherein the memory may be communicatively coupled to the processor in various ways known in the art.

[0111] The network entity device 30 may be a node in a CN. The CN may include an LTE CN or a 5G core (5GC), which includes a user plane function (UPF), a session management function (SMF), an access and mobility management function (AMF), a unified data management (UDM), a policy control function (PCF), a control plane (CP) / user plane (UP) separation (CUPS), an authentication server (AUSF), a network slice selection function (NSSF), and a network exposure function (NEF). The network functions described in the embodiments of the present invention, such as the NWDAF 30a, AMF 30b, SMF 30c, UPF 30d, RSMF 10e, RSMF 10f, and DN 40, may be executed in one or more of the network entity devices 30.

[0112] In embodiments of the present invention, a base station may be an entity for transmitting or receiving information, such as a gNB. A base station may also be an eNodeB, a transmission reception point (TRP), a NodeB in next-generation communications, or an access point in a wireless local area network (e.g., Wi-Fi).

[0113] A user end (UE) is an entity used to send or receive information at the user end, such as a mobile phone. A UE can also be called a terminal, mobile station, or mobile terminal. A UE can be a mobile phone, PAD, VR / AR device, industrial control wireless terminal, autonomous driving wireless terminal, telemedicine wireless terminal, smart grid wireless terminal, traffic safety wireless terminal, smart city wireless terminal, or smart home wireless terminal.

[0114] In addition, terminals and base stations can be deployed on land, including indoors, outdoors, handheld, and vehicle-mounted, as well as on water, in the air, on airplanes, drones, or satellites.

[0115] Examples of UEs described herein (e.g., UE 10, UE1, UE2, to UEn) may include one of the UE 10a or UE 10b. Examples of base stations described herein may include the base station 20a. Uplink (UL) transmission of control signals or data may be a transmission operation from a UE to a base station. Downlink (DL) transmission of control signals or data may be a transmission operation from a base station to a UE. DL control signals may include downlink control information (DCI) or radio resource control (RRC) signals from a base station to a UE.

[0116] Referring to FIG8 , a data transmission method is performed in a first network node of a radio access network (RAN). For example, the first network node receives or sends a protocol transmission message, wherein the protocol transmission message carries a protocol data unit (PDU), and the protocol transmission message and the protocol data unit type correspond to a service type or a function type (A010).

[0117] In some embodiments of the present invention, the protocol transmission message includes a message type element, and the message type element is used to indicate a service type or function type corresponding to the protocol transmission message.

[0118] In some embodiments of the present invention, the protocol transmission message includes a message type element and a service type element, and the service type element is used to indicate the service type or function type corresponding to the protocol transmission message.

[0119] In some embodiments of the present invention, the protocol transmission message is a user equipment UE-associated or non-UE-associated protocol transmission message, wherein the UE-associated or non-UE-associated protocol transmission message is indicated by a message type element in the protocol transmission message.

[0120] In some embodiments of the present invention, the received or sent protocol transmission message is indicated by the message type element in the protocol transmission message.

[0121] In some embodiments of the present invention, the UE-associated protocol transmission message further includes identification information of the UE in the first network node and identification information of the UE in the network node for access and mobility management.

[0122] In some embodiments of the present invention, the protocol transmission message further includes routing identification information, wherein the routing identification information is used to identify a network node for service management in the core network corresponding to the service type or function type.

[0123] In some embodiments of the present invention, the first network node is a base station of the radio access network RAN;

[0124] The network node for access and mobility management is an Access and Mobility Management Function (AMF); and

[0125] The network node used for service management is the Core Network Service Management Function CNSMF.

[0126] Referring to Figure 9, please note that although RAN 20 is described as an example in the description, the wireless communication method can be performed by a base station, such as a gNB, an eNB, a base station integrating eNB and gNB, or a base station beyond 5G technology. UE10 may include an embodiment of UE 10a or UE 10b. In step A001, a first network node of a radio access network RAN ​​receives a first connection establishment request message related to a first data transmission bearer, for establishing the first data transmission bearer, wherein the first connection establishment request message includes identification information of a service type or function type associated with a non-user equipment UE, or identification information of multiple UEs, and the first data transmission bearer is used to transmit data between the first network node and a second network node, the data being data related to the service type or function type, or data related to the multiple UEs in the radio access network.

[0127] In step A002, the first network node of the radio access network RAN ​​sends a first connection establishment request response message related to the first data transmission bearer to establish the first data transmission bearer between the first network node of the radio access network RAN ​​and the second network node of the core network.

[0128] In some embodiments of the present invention, the first network node is a base station or a base station distributed unit (Distributed Unit, DU) of the radio access network RAN; the second network node is a user plane function UPF of the core network, a base station of the radio access network RAN, or a base station centralized unit (Centralized Unit, CU) of the radio access network RAN.

[0129] In some embodiments of the present invention, the first data transmission bearer is a user plane transmission bearer, and may also be a transmission bearer based on the General Packet Radio Tunneling Protocol-User Plane GTP-U protocol.

[0130] In some embodiments of the present invention, the first connection establishment request message further includes at least one of the following information:

[0131] the identification or address information of the first network node;

[0132] The identifier or address information of the second network node of the base station of the core network or the radio access network RAN;

[0133] endpoint information of the second network node of the transport bearer related to the first data transport bearer; and

[0134] The first data transmission carries relevant data rate and quality of service (QoS) requirement information.

[0135] In some embodiments of the present invention, the first connection establishment request response message includes at least one of the following information:

[0136] the identification or address information of the first network node;

[0137] The identification or address information of the second network node; and

[0138] The endpoint information of the first network node of the transmission bearer related to the first data transmission bearer.

[0139] 10 , a data transmission method is performed in a data transmission system.

[0140] Step A020: The third network node (e.g., AMF) sends a first connection establishment request message related to the first data transmission bearer to the first network node (e.g., gNB) to establish the first data transmission bearer between the first network node (e.g., gNB) and the second network node (e.g., UPF), wherein the first connection establishment request message includes identification information of a service type or function type associated with a non-UE, or identification information of multiple UEs; the first network node (e.g., gNB) sends a first connection establishment request response message related to the first data transmission bearer to the third network node (e.g., AMF).

[0141] Step A021: The first network node (e.g., gNB) sends a first connection establishment response message to the third network node (e.g., AMF).

[0142] Step A022: The third network node (e.g., AMF) sends a second connection establishment request message related to the first data transmission bearer, the second data transmission bearer, and / or the third data transmission bearer to the fourth network node (e.g., SMF), wherein the second data transmission bearer is used to characterize the bearer between the second network node (e.g., UPF) and the fifth network node (e.g., CNSMF), and the third data transmission bearer is used to characterize the bearer between the second network node (e.g., UPF) and the sixth network node (e.g., DN). The first data transmission bearer, the second data transmission bearer, and the third data transmission bearer are all used to transmit data related to the service type or function type associated with the non-UE, or data of the multiple UEs.

[0143] Step A023: The fourth network node (e.g., SMF) sends a second connection establishment response message related to the first data transmission bearer, the second data transmission bearer, and / or the third data transmission bearer to the third network node (e.g., AMF). The second connection establishment response message may be combined with the third connection establishment request message into one message.

[0144] Step A024a: The fourth network node (e.g., SMF) sends a third connection establishment request message related to the first data transmission bearer to the third network node (e.g., AMF).

[0145] Step A025a: The third network node (e.g., AMF) sends a third connection establishment response message related to the first data transmission bearer to the fourth network node (e.g., SMF).

[0146] Step A024b: The fourth network node (e.g., SMF) sends a fourth connection establishment request message related to the first data transmission bearer, the second data transmission bearer, and / or the third data transmission bearer to the second network node (e.g., UPF) to establish the first data transmission bearer, the second data transmission bearer, and / or the third data transmission bearer.

[0147] Step A025b: The second network node (eg, UPF) sends a fourth connection establishment response message related to the first data transmission bearer, the second data transmission bearer, and / or the third data transmission bearer to the fourth network node (eg, SMF).

[0148] 11 , in some embodiments of the present invention, the data transmission method further includes:

[0149] Step A026: The fourth network node (eg, SMF) sends a fifth connection establishment request message related to the second data transmission bearer to the fifth network node (eg, CNSMF) to establish the second data transmission bearer.

[0150] Step A027: The fifth network node (eg, CNSMF) sends a fifth connection establishment response message related to the second data transmission bearer to the fourth network node (eg, SMF).

[0151] In some embodiments of the present invention, the second connection establishment request message, the third connection establishment request message, the fourth connection establishment request message, and the fifth connection establishment request message include identification information of the service type or function type, or identification information of the multiple UEs.

[0152] 12 , in some embodiments of the present invention, the data transmission method further includes:

[0153] Step A028: The fourth network node sends a fourth connection establishment completion message related to the first data transmission bearer, the second data transmission bearer, and / or the third data transmission bearer to the second network node to complete the establishment of the first data transmission bearer, the second data transmission bearer, and / or the third data transmission bearer.

[0154] In some embodiments of the present invention, the first network node is a base station of the radio access network RAN;

[0155] The second network node is a user plane function UPF;

[0156] The third network node is an access and mobility management function AMF;

[0157] The fourth network node is a session management function SMF;

[0158] The fifth network node is a core network service management function CNSMF;

[0159] The sixth network node is a network node of the data network DN.

[0160] In some embodiments of the present invention, the first data transmission bearer is a user plane transmission bearer; wherein the user plane transmission bearer is a transmission bearer based on the General Packet Radio Tunneling Protocol-User Plane GTP-U protocol.

[0161] In some embodiments of the present invention, the second data transmission bearer is a user plane transmission bearer; wherein, the user plane transmission bearer is a transmission bearer based on the GTP-U protocol, a transmission bearer based on the Transmission Control Protocol TCP protocol, or a transmission bearer based on the HTTP protocol.

[0162] In some embodiments of the present invention, the third data transmission bearer is a user plane transmission bearer; wherein, the user plane transmission bearer is a transmission bearer based on the GTP-U protocol, a transmission bearer based on the TCP protocol, a transmission bearer based on the User Datagram Protocol (UDP) protocol, or a transmission bearer based on the Hypertext Transfer Protocol (HTTP) protocol.

[0163] In some embodiments of the present invention, the second connection establishment request message (e.g., RAN-UPF UP connection and UPF-CNSMF UP connection establishment request message) includes at least one of the following: an identifier or address information of a network node (e.g., gNB) of the radio access network RAN, an identifier or address information of the access and mobility management function AMF, an identifier or address information of the session management function SMF, an identifier or address information of the CNSMF network node, an identifier or address information of the user plane function UPF, an identifier or address information related to the data network DN, and service-related information of the first data transmission bearer, the second data transmission bearer, and / or the third data transmission bearer.

[0164] In some embodiments of the present invention, the third connection establishment request message (e.g., RAN-UPF UP connection and UPF-CNSMF UP connection establishment request message) (e.g., step 5a of corresponding embodiment 4 or 5 or step 3a of embodiment 6) includes at least one of the following: the identification or address information of the network node (e.g., gNB) of the radio access network RAN, the identification or address information of the access and mobility management function AMF, the identification or address information of the session management function SMF, the identification or address information of the UPF, the endpoint information of the UPF carried by the first data transmission and / or service-related information.

[0165] In some embodiments of the present invention, the fourth connection establishment request message (e.g., RAN-UPF UP connection and UPF-CNSMF UP connection establishment request message) includes at least one of the following: an identifier or address information of a network node (e.g., gNB) of the radio access network RAN, an identifier or address information of the core network service management function CNSMF, an identifier or address information of the access and mobility management function AMF, an identifier or address information of the session management function SMF, an identifier or address information of the UPF, an identifier or address information related to the data network DN, endpoint information of the base station of the first data transmission bearer, endpoint information of the CNSMF of the second data transmission bearer, endpoint information of the DN of the third data transmission bearer and / or information related to the service of the data transmission bearer.

[0166] In some embodiments of the present invention, the first connection establishment request message (e.g., RAN-UPF UP connection and UPF-CNSMF UP connection establishment request message) includes at least one of the following: an identifier or address information of a network node (e.g., gNB) of the radio access network RAN, an identifier or address information of the access and mobility management function AMF, an identifier or address information of the session management function SMF, an identifier or address information of the user plane function UPF, endpoint information of the UPF of the first data transmission bearer and / or information related to the service of the data transmission bearer.

[0167] In some embodiments of the present invention, the fifth connection establishment request message (e.g., RAN-UPF UP connection and UPF-CNSMF UP connection establishment request message) includes at least one of the following: an identifier or address information of a network node (e.g., gNB) of the radio access network RAN, an identifier or address information of the access and mobility management function AMF, an identifier or address information of the UPF, an identifier or address information of the session management function SMF, an identifier or address information of the core network service management function CNSMF, endpoint information of the UPF of the second data transmission bearer and / or information related to the service of the data transmission bearer.

[0168] In some embodiments of the present invention, the information related to the service carried by the data transmission includes at least one of the following: service type or function type, service data rate, and information related to service quality of service QoS.

[0169] In some embodiments of the present invention, the second connection establishment response message includes at least one of the following: an identifier or address information of a network node (e.g., gNB) of the radio access network RAN, an identifier or address information of the access and mobility management function AMF, an identifier or address information of the session management function SMF, an identifier or address information of the UPF, endpoint information of the UPF carried by the first data transmission and / or information related to the service carried by the data transmission.

[0170] In some embodiments of the present invention, the third connection establishment response message includes at least: endpoint information of the base station carried by the first data transmission.

[0171] In some embodiments of the present invention, the fourth connection establishment response message includes at least: endpoint information of the UPF carried by the first data transmission, endpoint information of the UPF carried by the second data transmission, and / or endpoint information of the UPF carried by the third data transmission.

[0172] In some embodiments of the present invention, the first connection establishment response message includes at least: endpoint information of the base station carried by the first data transmission.

[0173] In some embodiments of the present invention, the fifth connection establishment response message includes at least: endpoint information of the CNSMF bearer of the second data transmission.

[0174] In some embodiments of the present invention, the fourth connection establishment completion message includes at least: endpoint information of the base station carried by the first data transmission, endpoint information of the CNSMF carried by the second data transmission, and / or endpoint information of the DN carried by the third data transmission.

[0175] In some embodiments of the present invention, in the downlink direction, data related to at least two UEs are first mapped by the RAN to a data radio bearer (DRB) of the Uu interface of at least two UEs, and then the data related to at least two UEs are transmitted through the data radio bearer DRB; wherein the data related to at least two UEs are transmitted through the first data transmission bearer.

[0176] In some embodiments of the present invention, in the uplink direction, the first network node selects one UE of at least two UEs, maps the data radio bearer and data of the Uu interface of the selected UE to the first data transmission bearer, and then transmits the data of the selected UE through the first data transmission bearer.

[0177] In some embodiments of the present invention, in the uplink direction, the data transmission method further includes:

[0178] The first network node selects one of the at least two UEs, and maps at least one data radio bearer (DRB) of the selected UE to at least one quality of service (QoS) flow associated with the first data transmission bearer; and

[0179] The service data unit SDU carried by the at least one DRB is sent to the corresponding quality of service flow QoS flow.

[0180] In some embodiments of the present invention, the first network node measures uplink transmission quality of at least two UEs to obtain a measurement result.

[0181] In some embodiments of the present invention, for the selected UE, when the measurement result is lower than a predetermined value, the first network node triggers a process of reselecting the UE, wherein the process of triggering the reselection of the UE is to reselect a UE corresponding to the best measurement result and map the data carried by at least two DRBs of the UE to the quality of service flow QoS flow corresponding to the DRB.

[0182] Examples of the method are illustrated below.

[0183] Example 1: AI-related data exchange between RAN and CN based on control plane messages

[0184] As shown in Figure 13, the RAN 20 has an AI function. The CN includes an AI function network node. In this embodiment, the AI ​​function network node of the CN can be a network data analysis function (Network Data Analytics Function, NWDAF) network node, or an AI function network node for a specific service, such as a location management function (Location Management Function, LMF) that supports the AI ​​function. This embodiment is described using the NWDAF as an example, but the principles of the methods and processes therein are also applicable to other AI function network nodes.

[0185] The RAN 20 exchanges data with the NWDAF through the AMF 30b network node. The data flow is shown as the dotted line 201 in Figure 13. This embodiment of the present invention mainly relates to the N2 interface between the RAN 20 and the AMF 30b, that is, defining dedicated procedures on the NG-C interface to meet data interaction requirements. As for the interface N-AI interface protocol and data interaction process between the AMF 30b and the NWDAF, the existing 5GC NL1 interface protocol and data interaction process can be referenced for enhancement and adaptive modification (as shown in the N-AI interface of Figure 14).

[0186] Furthermore, as shown in Figure 13, RAN 20 exchanges AI-related data with NWDAF 30a based on the AI-P (AI Protocol). The AI-P protocol can be an existing data transmission protocol or an enhanced and modified version of an existing protocol, such as NRPPa (NG-RAN; NR Positioning Protocol A) defined in 3GPP TS 38.455, or a newly defined data transmission protocol. This embodiment of the present invention primarily supports the transmission of AI-related data between RAN 20 and NWDAF 30a by enhancing the NGAP protocol over the NG-C interface, namely, adding functionality related to the transmission of AI-P protocol packets.

[0187] The embodiments of the present invention define a dedicated process for transmitting AI-related data on the NG interface of 5G or the interface between the RAN and CN nodes of future mobile communication systems.

[0188] As an embodiment, the present invention adds AI-related data to the NGAP protocol of the 5G NG-C interface, namely the transmission process of AI-P protocol data packets, including: the uplink and / or downlink transmission process of AI data associated with the UE, using UE-associated signaling; and the uplink and / or downlink transmission process of AI data not associated with the UE, using non-UE-associated signaling. Specific examples are described below.

[0189] Referring to Figure 15, Figure 15 shows a downlink UE associated AI-P transmission (DOWNLINK UE ASSOCIATED AI-P TRANSPORT) method. In this embodiment, AMF 30b initiates downlink UE associated AI-P data transmission by sending a downlink UE associated AI-P transmission (DOWNLINK UE ASSOCIATED AI-P TRANSPORT) message to RAN 20.

[0190] Referring to Figure 16, Figure 16 shows a method for uplink UE associated AI-P transmission (UPLINK UE ASSOCIATED AI-P TRANSPORT). In this embodiment, RAN 20 initiates uplink UE associated AI-P data transmission by sending an uplink UE associated AI-P transmission (UPLINK UE ASSOCIATED AI-P TRANSPORT) message to AMF 30b.

[0191] Based on the existing NGAP protocol framework, the functional definition and content of the DOWNLINK UE ASSOCIATED AI-P TRANSPORT and UPLINK UE ASSOCIATED AI-P TRANSPORT messages are as follows:

[0192] The description of the information element is as follows:

[0193] 1. Message Type (i.e., message type element): Specific message type values ​​need to be defined for DOWNLINK UE ASSOCIATED AI-P TRANSPORT and UPLINK UE ASSOCIATED AI-P TRANSPORT;

[0194] 2.AMF UE NGAP ID: uniquely identifies the UE association on the NG interface. Please refer to 3GPP protocol TS 38.401;

[0195] 3.RAN UE NGAP ID: uniquely identifies the UE association within the RAN;

[0196] 4. Routing ID: used to identify the AI ​​function network node in CN (5GC), such as a NWDAF node;

[0197] 5. AI-P-PDU: This information element includes a RAN-NWDAF or NWDAF-RAN AI-related protocol data unit, namely, AI-P PDU. The AMF will directly forward this message between the RAN 20 and the NWDAF 30a.

[0198] Referring to Figure 17, Figure 17 shows a method for downlink non-UE associated AI-P transmission (DOWNLINK NON UE ASSOCIATED AI-P TRANSPORT). In this embodiment, AMF 30b initiates downlink non-UE associated AI-P transmission by sending a downlink non-UE associated AI-P transmission (DOWNLINK NON UE ASSOCIATED AI-P TRANSPORT) message to RAN 20.

[0199] Uplink non-UE-associated AI-P transport

[0200] Referring to Figure 18, Figure 18 shows an uplink non-UE associated AI-P transmission (UPLINK NON UE ASSOCIATED AI-P TRANSPORT) method. In this embodiment, RAN 20 initiates uplink non-UE associated AI-P transmission by sending an uplink non-UE associated AI-P transmission (UPLINK NON UE ASSOCIATED AI-P TRANSPORT) message to AMF 30b.

[0201] Based on the existing NGAP protocol framework, the functional definition and content of the DOWNLINK NON UE ASSOCIATED AI-P TRANSPORT and UPLINK NON UE ASSOCIATED AI-P TRANSPORT messages are as follows:

[0202] The description of the information element is as follows:

[0203] 1. Message Type (i.e., message type element): Specific message type values ​​need to be defined for DOWNLINK NON UE ASSOCIATED AI-P TRANSPORT and UPLINK NON UE ASSOCIATED AI-P TRANSPORT;

[0204] 2. Routing ID: used to identify the AI ​​function network node in CN (5GC), such as a NWDAF node;

[0205] 3. AI-P-PDU: This information element includes a RAN–NWDAF or NWDAF–RAN AI-related protocol data unit, namely, AI-P PDU. The AMF 30b will forward the message directly between the RAN 20 and the NWDAF 30a.

[0206] In another implementation, data related to an AI service or function is exchanged between two RAN nodes based on control plane messages. These RAN nodes have AI services or functions, or another node that has AI services or functions is associated with the RAN node to support the RAN node in performing the AI ​​service or function. For example, the another node that has AI services or functions is a child node of the RAN node serving as the AI ​​service or function.

[0207] Taking 5G RAN (i.e., RAN nodes of 5G mobile communication systems, such as gNBs) as an example, in order to support data exchange related to AI services or functions between RAN nodes based on control plane messages, the transmission process and messages of AI data are added to the XnAP protocol of the Xn-C interface. The AI ​​data can be the PDU of the AI-P protocol or the payload of AI data. Specifically, the control plane message includes at least one of the following information:

[0208] ● Message Type (i.e., message type element): includes at least UE-associated AI-P TRANSPORT and non-UE-associated AI-P TRANSPORT

[0209] UE identity on the Xn interface: This is the identifier used by the two RAN nodes to uniquely identify the UE on the Xn interface. Refer to 3GPP TS 38.401.

[0210] Route ID: If the AI ​​service or function is located on another node, the RAN uses this identifier to identify and route AI data to that node.

[0211] ●AI data: This data can be AI-P PDU or ordinary payload.

[0212] In particular, if the Xn-C interface is not established between the two RAN nodes, the above message can also be forwarded through the AMF 30b of the core network, that is, the first RAN node (referred to as RAN1) sends the AI ​​data to the AMF 30b through the AI ​​data uplink transmission process on the above-mentioned NGAP interface, and then the AMF 30b sends the AI ​​data to the other second RAN node (referred to as RAN2) through the AI ​​data downlink transmission process on the above-mentioned NGAP interface.

[0213] In another implementation, data exchange related to AI services or functions is performed between internal nodes of the RAN based on control plane messages. These internal RAN nodes have AI services or functions. Taking the gNB-CU and gNB-DU of the 5G RAN (i.e., the RAN nodes of the 5G mobile communication system, such as gNB) as an example, in order to support data exchange related to AI services or functions between the gNB-CU and gNB-DU based on control plane messages, the transmission process and messages of AI data are added to the F1AP protocol of the F1-C interface, where the AI ​​data can be the PDU of the AI-P protocol or the payload of AI data. Specifically, the control plane message includes at least one of the following information:

[0214] ● Message Type (i.e., message type element): includes at least UE-associated AI-P TRANSPORT and non-UE-associated AI-P TRANSPORT

[0215] UE identity on the F1 interface: The gNB-CU and gNB-DU uniquely identify the UE on the F1 interface. For details, refer to 3GPP TS 38.401.

[0216] Routing ID: If the AI ​​service or function is located on another node, the gNB-CU and gNB-DU use this ID to identify and route AI data to that node.

[0217] ●AI data: This data can be AI-P PDU or ordinary payload.

[0218] Example 2: Data exchange between RAN and CN related to wireless sensing services based on control plane messages

[0219] As shown in Figure 19, Figure 19 illustrates the process of data interaction between RAN 20 and a Radio Sensing Management Function (RSMF) node via an AMF network node 30b. In this embodiment, RAN 20 also has a Radio Sensing RS (Radio Sensing) function. The CN also includes a CN RS function network node, such as a Radio Sensing Management Function (RSMF) network node 30e. Data is exchanged between RAN 20 and RSMF 30e via AMF 30b network node 30b, with the data flow shown as dashed line 202 in Figure 19. This embodiment of the present invention primarily involves defining dedicated procedures on the N2 interface, or NG-C interface, between RAN 20 and AMF 30b to support such data interaction. The N-RS interface protocol and its data interaction process between AMF 30b and RSMF can be enhanced and adaptively modified with reference to the existing 5GC NL1 interface protocol and data interaction process (as shown in the N-RS interface of Figure 20).

[0220] Furthermore, as shown in FIG20 , RAN 20 exchanges RS-related data with RSMF 30e based on the RS-P (Radio Sensing Protocol). The RS-P protocol can be an existing data transmission protocol, or an enhanced and modified version of an existing protocol, such as NRPPa (NG-RAN; NR Positioning Protocol A) defined in 3GPP TS 38.455, or a newly defined data transmission protocol, such as a new protocol enhanced and modified with reference to the NRPPa protocol. The embodiments of the present invention primarily support the transmission of RS-related data between RAN 20 and RSMF by enhancing the NGAP protocol on the NG-C interface, i.e., adding functions related to the transmission of RS-P protocol data packets.

[0221] The embodiment of the present invention defines a dedicated process for transmitting RS-related data on the NG interface of the CN of 5G or the interface between the RAN and CN nodes of a future mobile communication system.

[0222] This embodiment of the present invention adds RS-related data, namely the transmission process of RS-P protocol packets, to the NGAP protocol of the NG-C interface of the 5G CN. This includes: uplink and / or downlink transmission of RS data associated with a UE, using UE-associated signaling; and uplink and / or downlink transmission of RS data not associated with a UE, using non-UE-associated signaling. Specific examples are described below.

[0223] Referring to Figure 21, Figure 21 shows a downlink UE associated RS-P transmission (DOWNLINK UE ASSOCIATED RS-P TRANSPORT) method. In this embodiment, AMF 30b initiates downlink UE associated RS-P transmission by sending a downlink UE associated RS-P transmission (DOWNLINK UE ASSOCIATED RS-P TRANSPORT) message to RAN 20.

[0224] Referring to Figure 22, Figure 22 shows the uplink UE associated RS-P transmission (UPLINK UE ASSOCIATED RS-P TRANSPORT) method. In this embodiment, RAN 20 initiates uplink UE associated RS-P transmission by sending an uplink UE associated RS-P transmission (UPLINK UE ASSOCIATED RS-P TRANSPORT) message to AMF 30b.

[0225] Based on the existing NGAP protocol framework, the functional definition and content of the DOWNLINK UE ASSOCIATED RS-P TRANSPORT and UPLINK UE ASSOCIATED RS-P TRANSPORT messages are as follows:

[0226] The description of the information element is as follows:

[0227] 1. Message Type (i.e., message type element): Specific message type values ​​need to be defined for DOWNLINK UE ASSOCIATED RS-P TRANSPORT and UPLINK UE ASSOCIATED RS-P TRANSPORT;

[0228] 2.AMF UE NGAP ID: uniquely identifies the UE association on the NG interface. Please refer to 3GPP protocol TS 38.401;

[0229] 3.RAN UE NGAP ID: uniquely identifies the UE association within the RAN;

[0230] 4. Routing ID: used to identify the RS functional network node in CN (5GC), such as a RSMF node;

[0231] 5. RS-P-PDU: This information element includes an RS-related protocol data unit from RAN to RSMF or from RSMF to RAN, namely RS-P PDU. The AMF will forward this message directly between RAN and RSMF.

[0232] Referring to Figure 23, Figure 23 shows a downlink non-UE associated RS-P transmission (DOWNLINK NON UE ASSOCIATED RS-P TRANSPORT) method. In this embodiment, AMF 30b initiates downlink non-UE associated RS-P transmission by sending a downlink non-UE associated RS-P transmission (DOWNLINK NON UE ASSOCIATED RS-P TRANSPORT) message to RAN 20.

[0233] Referring to Figure 24, Figure 24 shows the uplink non-UE associated RS-P transmission (UPLINK NON UE ASSOCIATED RS-P TRANSPORT) method. In this embodiment, RAN 20 initiates uplink non-UE associated RS-P transmission by sending an uplink non-UE associated RS-P transmission (UPLINK NON UE ASSOCIATED RS-P TRANSPORT) message to AMF 30b.

[0234] Based on the existing NGAP protocol framework, the functional definition and content of the DOWNLINK NON UE ASSOCIATED RS-P TRANSPORT and UPLINK NON UE ASSOCIATED RS-P TRANSPORT messages are as follows:

[0235] The description of the information element is as follows:

[0236] 1. Message Type (i.e., message type element): Specific message type values ​​need to be defined for DOWNLINK NON UE ASSOCIATED RS-P TRANSPORT and UPLINK NON UE ASSOCIATED RS-P TRANSPORT;

[0237] 2. Routing ID: used to identify the RS functional network node in CN (5GC), such as a RSMF node;

[0238] 3. RS-P-PDU: This information element includes an RS-related protocol data unit from RAN 20 to RSMF or from RSMF to RAN 20, namely RS-P PDU. AMF 30b will forward and transmit this message directly between RAN 20 and RSMF.

[0239] In another implementation, data related to a Radio Sensing (RS) service or function is exchanged between two RAN nodes based on control plane messages. These RAN nodes may have a radio sensing service or function, or another node with a radio sensing service or function may be associated with the RAN node to support the RAN node in performing the radio sensing service or function. For example, a child node of the RAN node that performs the radio sensing service or function may be associated with, connected to, or interact with the RAN node.

[0240] Taking 5G RAN (i.e., RAN nodes of 5G mobile communication systems, such as gNBs) as an example, in order to support data exchange related to radio sensing services or functions between RAN nodes based on control plane messages, the transmission process of radio sensing data (RS data) is added to the XnAP protocol of the Xn-C interface. The RS data can be the PDU of the RS-P protocol or the payload of the RS data. Specifically, the control plane message includes at least one of the following information:

[0241] ● Message Type (i.e., message type element): includes at least UE-associated RS-P TRANSPORT and non-UE-associated RS-P TRANSPORT

[0242] UE identity on the Xn interface: This is the identifier used by the two RAN nodes to uniquely identify the UE on the Xn interface. Refer to 3GPP TS 38.401.

[0243] ● Routing ID: If the RS service or function is located at another node, the RAN uses this ID to identify and route RS data to the RS service or function node.

[0244] ● RS data: This data can be RS-P PDU or ordinary payload.

[0245] In particular, if no Xn-C interface is established between the two RAN nodes, the above message can also be forwarded through the AMF node of the core network, that is, the first RAN node sends the RS data to the AMF node through the RS data uplink transmission process on the above NGAP interface, and then the AMF sends the RS data to the other second RAN node through the RS data downlink transmission process on the above NGAP interface.

[0246] In another implementation, data exchange related to wireless sensing RS services or functions is performed between internal nodes of the RAN based on control plane messages. These internal RAN nodes have RS services or functions. Taking the gNB-CU and gNB-DU of the 5G RAN (i.e., the RAN nodes of the 5G mobile communication system, such as gNB) as an example, in order to support data exchange related to RS services or functions between the gNB-CU and gNB-DU based on control plane messages, the transmission process and messages of RS data are added to the F1AP protocol of the F1-C interface, where the RS data can be a PDU of the RS-P protocol or a payload of RS data. Specifically, the control plane message includes at least one of the following information:

[0247] ● Message Type (i.e., message type element): includes at least UE-associated RS-P TRANSPORT and non-UE-associated RS-P TRANSPORT

[0248] UE identity on the F1 interface: The gNB-CU and gNB-DU uniquely identify the UE on the F1 interface. For details, refer to 3GPP TS 38.401.

[0249] Routing ID: If the RS service or function is located at another node, the gNB-CU and gNB-DU use this ID to identify and route RS data to that RS service or function node.

[0250] ● RS data: This data can be RS-P PDU or ordinary payload.

[0251] Example 3: Service data interaction between RAN and CN based on control plane messages supporting service expansion capabilities

[0252] As shown in Figure 25 , the RAN 20 also has one or more services or functions, and the CN also includes one or more CN service or function network nodes, such as a core network service management function (CN Service Management Function, CNSMF) network node. The RAN 20 exchanges data with the CNSMF 30g through the AMF 30b network node, as shown by the dotted line 203 in Figure 25 . This embodiment mainly involves defining dedicated procedures on the N2 interface, i.e., the NG-C interface, between the RAN 20 and the AMF 30b to support the data interaction. As for the N-CNS interface protocol and its data interaction process between the AMF 30b and the CNSMF, the existing 5GC NL1 interface protocol and data interaction process can be referenced for enhancement and adaptive modification (as shown in the N-CNS interface of Figure 26 ).

[0253] Furthermore, as shown in FIG26 , RAN 20 exchanges service-related data with CNSMF 30g via the CNS-P (CN Service Protocol). The CNS-P protocol can be an existing data transmission protocol, or an enhanced and modified version of an existing protocol, such as NRPPa (NG-RAN; NR Positioning Protocol A), i.e., 3GPP TS 38.455, or a newly defined data transmission protocol, such as a new protocol enhanced and modified with reference to the NRPPa protocol. This embodiment of the present invention primarily relates to supporting the transmission of service-related data between RAN 20 and CNSMF 30g by enhancing the NGAP protocol on the NG-C interface, i.e., adding functionality related to the transmission of CNS-P protocol data packets.

[0254] In particular, the aforementioned services or functions, the service or function network node CNSMF, the interface N-CNS between the AMF 30b and the CNSMF, and the CNS-P protocol for carrying service data between the RAN 20 and the CNSMF 30g all refer to a higher-level, logical, and virtual concept. When corresponding to one or more specific services or functions, the corresponding specific concepts and their definitions may be the same or different. For example, a certain service here may be a positioning service, an AI function, a wireless sensing service, or other future services. The corresponding core network function network node may be the LMF, NWDAF, or the RSMF described above, or other functional network nodes. The corresponding N-CNS interface may be N-L1, or the N-AI or N-RS interface described above, or other interfaces. The corresponding CNS-P protocol may be NRPPa, or the AI-P or RS-P protocol described above, or other protocols. The network nodes of the CN corresponding to the multiple services or functions may be independent and separate, or the network nodes of any two or more of the services or functions may be combined.

[0255] The embodiments of the present invention define a common process for transmitting service-related data on the NG interface of 5G or the interface between the RAN and CN nodes of future mobile communication systems.

[0256] This embodiment of the present invention adds general / multi-purpose service-related data, namely the transmission process of CNS-P protocol packets, to the NGAP protocol of the 5G NG-C interface. This includes the uplink and / or downlink transmission of general / multi-purpose service data associated with a UE, using UE-associated signaling, and the uplink and / or downlink transmission of general / multi-purpose service data not associated with a UE, using non-UE-associated signaling. Specific examples are described below.

[0257] Referring to Figure 27, Figure 27 shows a downlink UE associated common service data transmission method. In this embodiment, AMF 30b initiates the process by sending a downlink UE associated common service data transmission message to RAN 20.

[0258] Referring to Figure 28, Figure 28 shows an uplink UE associated common service data transmission method. In this embodiment, RAN 20 initiates uplink UE associated common service data transmission by sending an uplink UE associated common service data transmission message to AMF 30b.

[0259] Based on the existing NGAP protocol framework, the functional definition and content of the DOWNLINK UE ASSOCIATED COMMON SERVICE DATA TRANSPORT and UPLINK UE ASSOCIATED COMMON SERVICE DATA TRANSPORT messages are as follows:

[0260] The description of the information element is as follows:

[0261] 1. Message Type (i.e., message type element): Specific message type values ​​need to be defined for DOWNLINK UE ASSOCIATED COMMON SERVICE DATA TRANSPORT and UPLINK UE ASSOCIATED COMMON SERVICE DATA TRANSPORT;

[0262] 2. Service Type (i.e., service type element): used to identify the service type or function type of the transmission. Different service type identifiers or type values ​​can be defined for different service types or function types.

[0263] 6.AMF UE NGAP ID: uniquely identifies the UE association on the NG interface. Please refer to 3GPP protocol TS 38.401.

[0264] 7.RAN UE NGAP ID: uniquely identifies the UE association within the RAN;

[0265] 8. Routing ID: used to identify the network node of a service or function in CN (5GC), such as the CNSMF node of a certain service;

[0266] 9. CNS-P-PDU: This information element contains a protocol data unit (CNS-P PDU) for service data from the RAN to the CNSMF or vice versa. The AMF forwards this message directly between the RAN and the CNSMF without performing any translation. In particular, this information element must match the service type. If different service types use different CNS-P protocols, the CNS-P PDU must correspond to the service type.

[0267] Referring to Figure 29, Figure 29 shows a downlink non-UE associated common service data transmission (DOWNLINK NON UE ASSOCIATED COMMON SERVICE DATA TRANSPORT) method. In this embodiment, AMF 30b initiates downlink non-UE associated common service data transmission by sending a downlink non-UE associated common service data transmission (DOWNLINK NON UE ASSOCIATED COMMON SERVICE DATA TRANSPORT) message to RAN 20.

[0268] Referring to Figure 30, Figure 30 shows an uplink non-UE associated common service data transmission (UPLINK NON UE ASSOCIATED COMMON SERVICE DATA TRANSPORT) method. In this embodiment, RAN 20 initiates uplink non-UE associated common service data transmission by sending an uplink non-UE associated common service data transmission (UPLINK NON UE ASSOCIATED COMMON SERVICE DATA TRANSPORT) message to AMF 30b.

[0269] Based on the existing NGAP protocol framework, the functional definition and content of the DOWNLINK NON UE ASSOCIATED COMMON SERVICE DATA TRANSPORT and UPLINK NON UE ASSOCIATED COMMON SERVICE DATA TRANSPORT messages are as follows:

[0270] The description of the information element is as follows:

[0271] 1. Message Type (i.e., message type element): Specific message type values ​​need to be defined for DOWNLINK NON UE ASSOCIATED COMMON SERVICE DATA TRANSPORT and UPLINK NON UE ASSOCIATED COMMON SERVICE DATA TRANSPORT;

[0272] 2. Service Type (i.e., service type element): used to identify the service type or function type of the transmission. Different service type identifiers or type values ​​can be defined for different service types or function types.

[0273] 3. Routing ID: used to identify the network node of a service or function in CN (5GC), such as the CNSMF node of a certain service;

[0274] 4. CNS-P-PDU: This information element contains a protocol data unit (CNS-P PDU) related to service data from the RAN 20 to the CNSMF or vice versa. The AMF 30b forwards this message directly between the RAN 20 and the CNSMF 30g without translation. Specifically, this information element must match the service type. For example, if different service types use different CNS-P protocols, the CNS-P PDU must correspond to the service type.

[0275] In another implementation, data related to one or more services or functions is exchanged between two RAN nodes based on control plane messages. These RAN nodes have one or more services or functions, or another node that has one or more services or functions is associated with the RAN node to support the RAN node in performing one or more services or functions. For example, a node that is a child node of one or more services or functions of the RAN node is associated with, connected to, or interacts with the RAN node.

[0276] Taking 5G RAN (i.e., the RAN node of the 5G mobile communication system, such as gNB) as an example, in order to support data interaction related to one or more services or functions between RAN nodes based on control plane messages, the transmission process and message of one or more service or function data (service data) are added to the XnAP protocol of the Xn-C interface, where the service data can be the PDU of the Service-P protocol or the payload of the service data. The Service-P protocol is similar to the above-mentioned CNS-P protocol. Specifically, the control plane message includes at least one of the following information:

[0277] ● Message Type (i.e., message type element): includes at least UE-associated common service data transmission message (UE-ASSOCIATED COMMON SERVICE DATA TRANSPORT) and non-UE-associated common service data transmission message (NON-UE-ASSOCIATED COMMON SERVICE DATA TRANSPORT);

[0278] ● Service Type (i.e., service type element): used to identify the service type or function type of the transmission. Different service type identifiers or type values ​​can be defined for different service types or function types.

[0279] UE identity on the Xn interface: This is the identifier used by the two RAN nodes to uniquely identify the UE on the Xn interface. Refer to 3GPP TS 38.401.

[0280] Routing ID: If the service or function is located at another node, the RAN uses this ID to identify and route service data to the node that supports the service or function.

[0281] ●Service data: This data can be a Service-P PDU or a normal payload.

[0282] In particular, if no Xn-C interface is established between the two RAN nodes, the above message can also be forwarded through the AMF node of the core network, that is, the first RAN node sends the service data (Service data) to the AMF node through the general service data uplink transmission process on the above NGAP interface, and then the AMF sends the service data (Service data) to the other second RAN node through the general service data downlink transmission process on the above NGAP interface.

[0283] In another implementation, data exchange related to one or more services or functions is performed between internal nodes of the RAN based on control plane messages. These internal RAN nodes have one or more services or functions. Taking the gNB-CU and gNB-DU of the 5G RAN (i.e., the RAN nodes of the 5G mobile communication system, such as gNB) as an example, in order to support the exchange of data related to one or more services or functions between the gNB-CU and gNB-DU based on control plane messages, the transmission process and messages of one or more service or function data (Service data) are added to the F1AP protocol of the F1-C interface, where the service data can be a PDU of the Service-P protocol or a payload of the service data. Specifically, the control plane message includes at least one of the following information:

[0284] ● Message Type (i.e., message type element): includes at least UE-associated uplink / downlink common service data transmission message (UPLINK / DOWNLINK UE ASSOCIATED COMMON SERVICE DATA TRANSPORT) and non-UE-associated uplink / downlink common service data transmission message (UPLINK / DOWNLINK NON UE ASSOCIATED COMMON SERVICE DATA TRANSPORT);

[0285] UE identity on the F1 interface: The gNB-CU and gNB-DU uniquely identify the UE on the F1 interface. For details, refer to 3GPP TS 38.401.

[0286] Routing ID: If the service or function is located at another node, the RAN uses this ID to identify and route service data to the node that contains the service or function.

[0287] ●Service data: This data can be a Service-P PDU or a normal payload.

[0288] The following describes the data interaction between the RAN and CN based on the user plane connection.

[0289] Example 4: User plane connection between network nodes for services or functions of RAN and CN

[0290] Generally, a service or function involves network nodes in the RAN and CN, and these RAN and CN network nodes exchange large amounts of data and / or data in real time. Therefore, it is necessary to establish user plane connections, i.e., connection-oriented communication links, between the RAN 20 and the CN's UPF network node 30d, and between the UPF 30d and the CN's service or function network node to meet data exchange requirements. In this embodiment, in the CN, the network node for this service or function is the Core Network Service Management Function (CNSMF). Accordingly, in the RAN 20, this service or function can be part of the RAN 20 network node or another network node. In this embodiment, the service or function is part of the RAN 20 network node, i.e., RAN 20 (service or function). In particular, these services or functions are non-UE-associated, meaning that their establishment is not associated with a specific UE, but rather with a cell, base station (such as a gNB in ​​NR), or a specific function or service. These services or functions may involve multiple cells or base stations. Data corresponding to non-UE-associated services or functions are called non-UE-associated data, even though these data may come from a certain UE or be related to a certain UE.

[0291] Please refer to Figure 31, which illustrates data exchange between the RAN 20 and the CNSMF via the UPF network node. In this embodiment, the RAN 20 supports a certain service or function, and the CN includes a CN service management function network node, the CNSMF, which also supports the service or function. The RAN 20 exchanges data with the CNSMF via the UPF network node 30d. The data flow is shown by dashed line 204 in Figure 31. This embodiment involves establishing dedicated user plane connections over the N3 interface between the RAN 20 and the UPF 30d, and the N-SP interface between the UPF 30d and the CNSMF, namely, the NG-U and N-SP interfaces, to support this data exchange. The N-SP interface is a newly defined interface.

[0292] Furthermore, as shown in Figures 32 and 33, the RAN 20 exchanges service-related data with the CNSMF based on the SP (Service Protocol). The SP protocol is related to the corresponding service and function. To meet the different requirements of different services and functions, different SP protocols can be used, including existing data transmission protocols or newly defined data transmission protocols. This embodiment of the present invention involves establishing a dedicated user plane connection on the NG-U and N-SP interfaces to support the transmission of service-related data between the RAN 20 and the CNSMF. The user plane connection on the NG-G interface is based on the GTP-U protocol. SP protocol data packets are transmitted between the RAN 20 and the UPF 30d as GTP-U SDUs (Service Data Packets) via GTP-U PDUs. Regarding the N-SP interface protocol between the UPF 30d and the CNSMF, this embodiment provides a user plane connection based on the Transmission Control Protocol (TCP) as shown in Figure 32 and a user plane connection based on GTP-U as shown in Figure 33.

[0293] Specifically, the transmission process of the user plane SP protocol data packet from the RAN 20 to the CNSMF is as follows:

[0294] 1. RAN 20 sends the SP protocol data packet to UPF 30d through the NG-U interface;

[0295] 2. UPF 30d receives the SVP protocol data packet from the NG-U interface and forwards it to the CNSMF through the N-SP interface;

[0296] 3. CNSMF receives SP protocol data packets through the N-SP interface;

[0297] The transmission process of the user plane SP protocol data packet from the CNSMF to the RAN 20 is the opposite of the above process.

[0298] In order to establish the user plane connection between the NG-U (N3) and N-SP interfaces, it is necessary to design relevant control plane signaling processes in the control plane interface protocol between relevant network nodes, including enhancements and modifications to the NGAP protocol of the NG-C (N2) interface, involving network nodes such as RAN, UPF, CNSMF, AMF and SMF.

[0299] Figure 34 is a schematic diagram of the relevant signaling process, in which the processes and their numbers do not limit their order. In addition, the control plane signaling process can also include only one or more processes. The main processes are described as follows:

[0300] 1a: The RAN 20 (gNB) sends a first service establishment request message (RAN-CNSMF service establishment request message) between the network node of the radio access network RAN ​​20 and the core network service management function CNSMF to the AMF 30b. The message includes at least one of the following information: the identifier or address information of the network node of the radio access network RAN ​​20 (e.g., gNB), the identifier or address information of the access and mobility management function AMF, the identifier or address information of the core network service management function CNSMF, and RAN-CNSMF service-related information (e.g., service type or function type, and / or service data rate).

[0301] In the example of Figure 8, the third network node (e.g., AMF 30b) receives a service establishment request message related to the first data transmission bearer, the second data transmission bearer, and / or the third data transmission bearer from the first network node (e.g., gNB) or the fifth network node (e.g., CNSMF) (e.g., step 1a of the corresponding embodiment 4) (e.g., step 1b of the corresponding embodiment 4), wherein the service establishment request message includes identification information of the service type or function type, or identification information of the multiple UEs.

[0302] 2a: AMF 30b sends a RAN-CNSMF service establishment response message to the RAN 20 node.

[0303] 1b: The CNSMF 30g sends a second service establishment request message (RAN-CNSMF service establishment request message) between the network node of the radio access network RAN ​​20 and the core network service management function CNSMF to the AMF 30b. The message includes at least one of the following information: the identifier or address information of the network node of the radio access network RAN ​​20 (e.g., gNB), the identifier or address information of the access and mobility management function AMF, the identifier or address information of the core network service management function CNSMF, and service-related information related to the user plane (RAN-CNSMF UP) connection between the RAN 20 and the CNSMF (e.g., service type or function type, and / or service data rate).

[0304] 2b: AMF 30b sends a RAN-CNSMF service establishment response message to CNSMF 30g.

[0305] 3: The AMF 30b sends a connection establishment request message between the network node of the radio access network RAN ​​20 and the core network service management function CNSMF to the SMF 30c (as an example of the second connection establishment request message, such as a RAN-UPF UP connection and a UPF-CNSMF UP connection establishment request message). The RAN-CNSMF UP connection refers to the user plane connection of the NG-U and / or N-SP interface mentioned above. This message includes at least one of the following information: the identifier or address information of the network node of the radio access network RAN ​​20 (such as a gNB), the identifier or address information of the access and mobility management function AMF, the identifier or address information of the session management function SMF, the identifier or address information of the CNSMF network node, and service-related information related to the user plane (RAN-CNSMF UP) connection between RAN 20 and CNSMF (such as service type or function type, and / or service data rate).

[0306] 5: SMF 30c sends a RAN-CNSMF UP connection establishment response message (as an example of the second connection establishment response message) and a connection establishment request message between the network node of the radio access network RAN ​​20 and the core network user plane function UPF node (as an example of the third connection establishment request message, such as a RAN-UPF UP connection establishment request message) to AMF 30b.

[0307] 35 , in another embodiment, step 5 can be divided into two steps, including steps 4 and 5a.

[0308] 4: SMF 30c sends a RAN-CNSMF UP connection establishment response message to AMF 30b (as an example of the second connection establishment response message).

[0309] 5a: The SMF 30c sends a connection establishment request message (e.g., a RAN-UPF UP connection establishment request message) between the network node of the radio access network RAN ​​20 and the core network user plane function (UPF) node to the AMF 30b. The message includes at least one of the following information: the identifier or address information of the network node (e.g., gNB) of the radio access network RAN ​​20, the identifier or address information related to the access and mobility function (AMF), the identifier or address information of the session management function (SMF), the identifier or address information of the UPF, and information related to resources connected between the RAN and UPF user plane (RAN-UPF UP) over the NG-U interface. The information related to resources connected between the RAN and UPF user plane (RAN-UPF UP) over the NG-U interface includes at least one of the following information: UPF endpoint information of the transport bearer, service type or function type, service data rate, and information related to service quality of service (QoS). As an embodiment, the RAN and UPF user plane (RAN-UPF UP) connection establishment request message can be an existing PDU session resource establishment request message PDU Session Resource Setup Request, and include at least one of the following enhancements and modifications: defining a new PDU session type PDU session Type for the RAN-CNSMF service; QoS flow configuration-related configuration information is optional because the RAN and UPF user plane (RAN-UPF UP) connection does not need to be mapped to the DRB; the UE-related identifier or address information is replaced by the identifier or address information of the network node (e.g., gNB) of the radio access network RAN ​​20.

[0310] 6a: AMF 30b sends a RAN-UPF UP connection establishment response message (as an example of the third connection establishment response message) to SMF 30c. This message includes at least one of the following information: the identifier or address information of a network node (e.g., a gNB) of the radio access network RAN ​​20, the identifier or address information related to the access and mobility management function (AMF), the identifier or address information of the session management function (SMF), the identifier or address information of the UPF, and information related to resources connected to the RAN-UPF UP over the NG-U interface. The information related to resources connected to the RAN-UPF UP over the NG-U interface includes at least information about the RAN 20 (gNB) endpoint that transmits the bearer. As an embodiment, the RAN and UPF user plane (RAN-UPF UP) connection establishment response message can be an existing PDU session resource establishment response message PDU Session Resource Setup Response, wherein the QoS flow configuration-related configuration information is optional because the RAN and UPF user plane (RAN-UPF UP) connection does not need to be mapped to the DRB; the UE-related identifier or address information is replaced by the identifier or address information of the network node (e.g., gNB) of the radio access network RAN ​​20.

[0311] 5b: The SMF 30c sends a connection establishment request message between the network node of the radio access network RAN ​​20 and the core network service management function CNSMF to the UPF 30d (as an example of the fourth connection establishment request message, such as a RAN-UPF UP connection and a UPF-CNSMF UP connection establishment request message). The message includes at least one of the following information: the identifier or address information of the network node (such as a gNB) of the radio access network RAN ​​20, the identifier or address information of the core network service management function CNSMF, the identifier or address information related to the access and mobility management function AMF, the identifier or address information of the session management function SMF, the identifier or address information of the UPF, information related to resources of the RAN and UPF user plane (RAN-UPF UP) connection on the NG-U interface, and information related to resources of the UPF-CNSMF connection on the N-SP interface. The resource-related information for the RAN-UPF user plane (RAN-UPF UP) connection over the NG-U interface includes at least one of the following: RAN 20 endpoint information for the transport bearer, service type or function type, service data rate, and service quality of service (QoS)-related information; the resource-related information for the UPF-CNSMF connection over the N-SP interface includes at least one of the following: CNSMF endpoint information for the transport bearer, service type or function type, service data rate, and service quality of service (QoS)-related information. In one embodiment, the RAN-UPF user plane (RAN-UPF UP) connection establishment request message may be an existing PDU Session Resource Setup Request message, and include at least one of the following enhancements and modifications: defining a new PDU session type (PDU session Type) for the UPF-CNSMF service; QoS flow configuration-related configuration information is optional because the RAN-UPF user plane (RAN-UPF UP) connection does not need to be mapped to a DRB; and replacing UE-related identifiers or address information with non-UE-related identifiers or address information (e.g., identifiers or address information of a node (gNB), cell, function, or service).

[0312] 6b: The UPF 30d sends a RAN and UPF user plane (RAN-UPF UP) connection and UPF-CNSMF UP connection establishment response message to the SMF 30c (as an example of the fourth connection establishment response message). The message includes at least one of the following information: the identifier or address information of the network node (e.g., gNB) of the radio access network RAN ​​20, the identifier or address information of the core network service management function CNSMF, the identifier or address information related to the access and mobility management function AMF, the identifier or address information of the session management function SMF, the identifier or address information of the UPF, information related to resources of the RAN and UPF user plane (RAN-UPF UP) connection on the NG-U interface, and information related to resources of the UPF-CNSMF connection on the N-SP interface. In which, the resource-related information of the RAN and UPF user plane (RAN-UPF UP) connected on the NG-U interface includes at least the endpoint information of the UPF of the transmission bearer of the NG-U interface; the resource-related information of the UPF-CNSMF connected on the N-SP interface includes at least the endpoint information of the UPF of the transmission bearer of the N-SP interface; as an embodiment, the RAN and UPF user plane (RAN-UPF UP) connection establishment response message can be an existing PDU session resource establishment response message PDU Session Resource Setup Response, wherein the QoS flow configuration-related configuration information is optional because the RAN and UPF user plane (RAN-UPF UP) connection does not need to be mapped to the DRB; the UE-related identifier or address information is replaced by the identifier or address information of the network node (e.g., gNB) of the radio access network RAN ​​20; the UE-related identifier or address information is replaced by non-UE-related identifier or address information (such as the identifier or address information of the node (gNB), cell, function or service, etc.).

[0313] 5c: SMF 30c sends a connection establishment request message (e.g., a UPF-CNSMF UP connection establishment request message) between the core network user plane network node UPF and the core network service management function CNSMF to CNSMF 30g. The message includes at least one of the following information: the identifier or address information of the network node (e.g., gNB) of the radio access network RAN ​​20, the identifier or address information of the UPF, the identifier or address information of the session management function SMF, the identifier or address information of the core network service management function CNSMF, and information related to resources of the UPF-CNSMF UP connection on the N-SP interface. The information related to resources of the UPF-CNSMF UP connection on the N-SP interface includes at least one of the following information: endpoint information of the UPF that transmits the bearer, service type or function type, service data rate, and information related to service quality of service (QoS).

[0314] 6c: CNSMF 30g sends a UPF-CNSMF UP Connection Establishment Response message (as an example of the fifth connection establishment response message) to SMF 30c. This message includes at least one of the following information: the identifier or address information of a network node (e.g., gNB) of the radio access network RAN ​​20, the identifier or address information of the UPF, the identifier or address information of the session management function (SMF), the identifier or address information of the core network service management function (CNSMF), and resource-related information of the UPF-CNSMF UP connection on the N-SP interface. The resource-related information of the UPF-CNSMF UP connection on the N-SP interface includes at least CNSMF endpoint information for the transport bearer.

[0315] 7: AMF 30b sends a connection establishment request message (e.g., a RAN-UPF UP connection establishment request message) to RAN 20 (gNB) between the network node of the radio access network RAN ​​20 and the core network user plane function network node UPF 30d. The message includes at least one of the following information: identifier or address information related to the network node of the radio access network RAN ​​20 (e.g., gNB), identifier or address information related to the access and mobility management function AMF, identifier or address information of the session management function SMF, identifier or address information of the UPF, and information related to resources connected to the RAN and UPF user plane (RAN-UPF UP) over the NG-U interface. The information related to resources connected to the RAN and UPF user plane (RAN-UPF UP) over the NG-U interface includes at least one of the following information: UPF endpoint information for the transport bearer, service type or function type, service data rate, and service quality of service (QoS) information. As an embodiment, the RAN and UPF user plane (RAN-UPF UP) connection establishment request message can be the existing PDU session resource establishment request message PDU Session Resource Setup Request, and is enhanced and modified according to the requirements of the RAN-CNSMF UP service, wherein the enhancement and modification include at least one of the following: defining a new PDU session type PDU session Type for the RAN-CNSMF service; QoS flow configuration-related configuration information is optional because the RAN and UPF user plane (RAN-UPF UP) connection does not need to be mapped to the DRB; replacing the UE-related identifier or address information with the identifier or address information of the network node (e.g., gNB) of the radio access network RAN ​​20.

[0316] 8: The RAN 20 (gNB) sends a RAN-UPF UP connection establishment response message to the AMF 30b (as an example of a first connection establishment response message). This message includes at least one of the following information: the identifier or address information of a network node (e.g., a gNB) of the radio access network RAN ​​20, the identifier or address information related to the access and mobility management function (AMF), the identifier or address information of the session management function (SMF), the identifier or address information of the UPF, and information related to resources connected to the RAN-UPF UP over the NG-U interface. The information related to resources connected to the RAN-UPF UP over the NG-U interface includes at least information about the RAN 20 (gNB) endpoint that transmits the bearer. As an embodiment, the RAN and UPF user plane (RAN-UPF UP) connection establishment response message can be an existing PDU session resource establishment response message PDU Session Resource Setup Response, wherein the QoS flow configuration-related configuration information is optional because the RAN and UPF user plane (RAN-UPF UP) connection does not need to be mapped to the DRB; the UE-related identifier or address information is replaced by the identifier or address information of the network node (e.g., gNB) of the radio access network RAN ​​20.

[0317] 9: SMF 30c sends a user plane connection establishment completion message to UPF 30d (as an example of the fourth connection establishment completion message), which includes at least the endpoint information of RAN 20 (gNB) for the transport bearer connected to the RAN and UPF user plane (RAN-UPF UP) on the NG-U interface, and / or the endpoint information of CNSMF for the transport bearer connected to the UPF-CNSMF UP on the N-SP interface.

[0318] In another embodiment, AMF and SMF are a network node, then the message sending and receiving and process processing between AMF and SMF in the above process are completed by the internal implementation of the network node, and the flow message sending and receiving and process processing between the two nodes AMF and SMF and other network nodes are implemented by the network node and other network nodes.

[0319] Specifically, for different services and functions, the core network service management function CNSMF node, SP protocol, and N-SP interface may be the same or different. For example, for AI-related services and functions, the core network service management function CNSMF node may be the existing network data analysis function (NetWork Data Analytics Function, NWDAF), and its corresponding N-SP interface and SP protocol can be designed with reference to the existing NL1 interface and NRPPa protocol respectively. For wireless sensing services, the core network service management function CNSMF node needs to be redefined and introduced, such as the Radio Sensing Management Function (RSMF), and its corresponding N-SP interface and SP protocol can be designed with reference to the existing NL1 interface and NRPPa protocol respectively.

[0320] Example 5: User plane connection between network nodes for services or functions of RAN and DN

[0321] Typically, a service or function involves network nodes in the RAN 20 (gNB) and the DN (Data Network). Large amounts of data and / or real-time data exchange occurs between the RAN 20 and DN network nodes, such as radio awareness services, referred to herein as RAN-DN services. User plane connections, i.e., connection-oriented communication links, are established between the RAN 20 and the CN's UPF network node 30d, and between the UPF 30d and the DN 40 network node to support these data exchange requirements.

[0322] As shown in Figure 36, data flow 205 represents data interaction on the user plane connection of the RAN-DN service. This embodiment involves establishing a dedicated user plane connection on the N3 interface between the RAN 20 and the UPF 30d, namely the NG-U, to support the data interaction requirements.

[0323] Figure 37 shows a protocol stack model for the user plane connection between the RAN 20 and the DN. The user plane connection of the NG-G interface is based on the GTP-U protocol. In particular, these services or functions are non-UE-associated, meaning that the establishment of these services and functions is not associated with a specific UE, but rather with a cell, base station (such as NR's gNB), or a specific function or service, which may involve multiple cells or base stations. The data corresponding to non-UE-associated services or functions is called non-UE-associated data, even though this data may originate from or be related to a specific UE.

[0324] Specifically, the transmission process of an application layer data packet from RAN 20 to DN 40 is as follows:

[0325] 1. RAN 20 sends the application layer data packet to UPF 30d through the NG-U interface;

[0326] 2. UPF 30d receives application layer data packets from the NG-U interface and forwards them to DN via N6;

[0327] 3.DN receives application layer data packets through the N6 interface;

[0328] The transmission process of the user plane application layer data packet from the DN to the RAN 20 is the opposite of the above process, where the N6 interface is the interface in the existing 5GC.

[0329] In order to establish the NG-U (N3) user plane connection between RAN 20 and DN user plane connection, it is necessary to enhance and modify the control plane process of the NGAP protocol of the NG-C (N2) interface, involving network nodes such as RAN, UPF, AMF and SMF.

[0330] Figure 38 is a schematic diagram of the control plane flow of the NGAP protocol for enhancing and modifying the NG-C (N2) interface. The processes and their numbers do not limit their order. In addition, the control plane signaling process may also include only one or more of the processes. The main processes are described as follows:

[0331] 1a: RAN 20 (gNB) sends an RN-DN service establishment request message to AMF 30b. The message includes at least one of the following information: the identifier or address information of the network node (e.g., gNB) of the radio access network RAN, the identifier or address information related to the access and mobility management function (AMF), and service-related information (e.g., service type or function type, and / or service data rate).

[0332] 2a: AMF 30b sends an RN-DN service establishment response message to the RAN 20 node.

[0333] 3: AMF 30b sends a connection establishment request message between the network node of the radio access network RAN ​​and the user plane function UPF to SMF 30c (as an example of the second connection establishment request message, for example, a user plane (RAN-UPF UP) connection establishment request message between RAN 20 and UPF 30d). The RAN-DN UP connection refers to the user plane connection of the NG-U described above. This message includes at least one of the following information: an identifier or address information of the network node of the radio access network RAN ​​(for example, a gNB), an identifier or address information related to the access and mobility management function AMF, an identifier or address information of the session management function SMF, and service-related information related to the RAN-DN UP connection (such as service type or function type, and / or service data rate).

[0334] 5: SMF 30c sends a RAN-DN UP connection establishment response message (as an example of the second connection establishment response message) and a connection establishment request message between the network node of the radio access network RAN ​​and the user plane function UPF (as an example of the third connection establishment request message, such as the user plane (RAN-UPF UP) connection establishment request message between RAN 20 and UPF 30d) to AMF 30b.

[0335] 39 , in another embodiment, step 5 can be divided into two steps, including steps 4 and 5a.

[0336] 4: SMF 30c sends a RAN-DN UP connection establishment response message to AMF 30b (as an example of the second connection establishment response message).

[0337] 5a: The SMF 30c sends a connection establishment request message between the network node of the radio access network RAN ​​and the user plane function UPF (e.g., a RAN-UPF UP connection establishment request message between the RAN 20 and UPF 30d, as an example of the third connection establishment request message). The message includes at least one of the following information: the identifier or address information of the network node of the radio access network RAN ​​(e.g., a gNB), the identifier or address information related to the access and mobility management function AMF, the identifier or address information of the session management function SMF, the identifier or address information of the UPF, and information related to resources connected between the RAN 20 and UPF 30d (RAN-UPF UP) user plane on the NG-U interface. The information related to resources connected between the RAN 20 and UPF 30d (RAN-UPF UP) user plane on the NG-U interface includes at least one of the following information: UPF endpoint information of the transport bearer, service type or function type, service data rate, and service quality of service (QoS) related information. As an embodiment, the RAN 20 and UPF 30d user plane (RAN-UPF UP) connection establishment request message can be an existing PDU session resource establishment request message PDU Session Resource Setup Request, and include at least one of the following enhancements and modifications: defining a new PDU session type PDU session Type for RAN-DN services; QoS flow configuration-related configuration information is optional because the RAN 20 and UPF 30d user plane (RAN-UPF UP) connection does not need to be mapped to DRB; replacing the UE-related identifier or address information with the identifier or address information of the network node (e.g., gNB) of the radio access network RAN.

[0338] 6a: AMF 30b sends a RAN 20 and UPF 30d user plane (RAN-UPF UP) connection establishment response message to SMF 30c (as an example of the third connection establishment response message). This message includes at least one of the following information: the identifier or address information of a network node (e.g., a gNB) of the radio access network RAN, the identifier or address information related to the access and mobility function (AMF), the identifier or address information of the session management function (SMF), the identifier or address information of the UPF, and information related to resources connected to the user plane of the RAN 20 and UPF 30d (RAN-UPF UP) over the NG-U interface. The information related to resources connected to the user plane of the RAN 20 and UPF 30d (RAN-UPF UP) over the NG-U interface includes at least information about the RAN (gNB) endpoint that transmits the bearer. As an embodiment, the RAN and UPF user plane (RAN-UPF UP) connection establishment response message can be an existing PDU session resource establishment response message PDU Session Resource Setup Response, wherein the QoS flow configuration related configuration information is optional because the RAN and UPF user plane (RAN-UPF UP) connection does not need to be mapped to the DRB; the UE-related identifier or address information is replaced by the identifier or address information of the network node (e.g., gNB) of the radio access network RAN.

[0339] 5b: The SMF 30c sends a connection establishment request message (e.g., a RAN-UPF UP connection establishment request message) between the network node of the radio access network RAN ​​and the user plane function (UPF) to the UPF 30d. The message includes at least one of the following information: identifier or address information of the network node of the radio access network RAN ​​(e.g., a gNB), identifier or address information related to the access and mobility function (AMF), identifier or address information of the session management function (SMF), identifier or address information of the UPF, and information related to resources connected to the RAN-UPF UP interface over the NG-U interface. The information related to resources connected to the RAN-UPF UP interface over the NG-U interface includes at least one of the following information: RAN (gNB) endpoint information for the transport bearer, service type or function type, service data rate, and service quality of service (QoS) information. As an embodiment, the RAN and UPF user plane (RAN-UPF UP) connection establishment request message can be an existing PDU session resource establishment request message PDU Session Resource Setup Request, and include at least one of the following enhancements and modifications: defining a new PDU session type PDU session Type for RAN-DN services; QoS flow configuration-related configuration information is optional because the RAN and UPF user plane (RAN-UPF UP) connection does not need to be mapped to DRB; the UE-related identifier or address information is replaced with the identifier or address information of the network node (e.g., gNB) of the radio access network RAN.

[0340] 6b: The UPF 30d sends a RAN-UPF UP connection establishment response message to the SMF 30c (as an example of the fourth connection establishment response message). This message includes at least one of the following information: the identifier or address information of a network node (e.g., a gNB) of the radio access network RAN, the identifier or address information related to the access and mobility function (AMF), the identifier or address information of the session management function (SMF), the identifier or address information of the UPF, and information related to resources connected to the RAN-UPF UP over the NG-U interface. The information related to resources connected to the RAN-UPF UP over the NG-U interface includes at least the UPF endpoint information for the transport bearer of the NG-U interface. As an embodiment, the RAN and UPF user plane (RAN-UPF UP) connection establishment response message can be an existing PDU session resource establishment response message PDU Session Resource Setup Response, wherein the QoS flow configuration related configuration information is optional because the RAN and UPF user plane (RAN-UPF UP) connection does not need to be mapped to the DRB; the UE-related identifier or address information is replaced with non-UE-related identifier or address information (such as the identifier or address information of the node (gNB), cell, function or service, etc.).

[0341] 7: The AMF 30b sends a connection establishment request message between the network node of the radio access network RAN ​​and the user plane function UPF (e.g., a RAN-UPF UP connection establishment request message, as an example of the first connection establishment request message). The message includes at least one of the following information: the identifier or address information of the network node of the radio access network RAN ​​(e.g., the gNB), the identifier or address information related to the access and mobility management function AMF, the identifier or address information of the session management function SMF, the identifier or address information of the UPF, and information related to resources connected to the RAN-UPF UP interface over the NG-U interface. The information related to resources connected to the RAN-UPF UP interface over the NG-U interface includes at least one of the following information: UPF endpoint information for the transport bearer, service type or function type, service data rate, and service quality of service (QoS) related information. As an embodiment, the RAN and UPF user plane (RAN-UPF UP) connection establishment request message can be an existing PDU session resource establishment request message PDU Session Resource Setup Request, and include at least one of the following enhancements and modifications: defining a new PDU session type PDU session Type for RAN-DN services; QoS flow configuration-related configuration information is optional because the RAN and UPF user plane (RAN-UPF UP) connection does not need to be mapped to a DRB; replacing the UE-related identifier or address information with non-UE-related identifier or address information (such as identifier or address information of a node (gNB), cell, function or service, etc.).

[0342] 8: AMF 30b sends a RAN-UPF UP connection establishment response message to SMF 30c (as an example of a first connection establishment response message). This message includes at least one of the following information: the identifier or address information of a network node (e.g., a gNB) of the radio access network RAN, the identifier or address information related to the access and mobility function (AMF), the identifier or address information of the session management function (SMF), the identifier or address information of the UPF, and information related to resources connected to the RAN-UPF UP over the NG-U interface. The information related to resources connected to the RAN-UPF UP over the NG-U interface includes at least information about the RAN (gNB) endpoint that transmits the bearer. As an embodiment, the RAN and UPF user plane (RAN-UPF UP) connection establishment response message can be an existing PDU session resource establishment response message PDU Session Resource Setup Response, wherein the QoS flow configuration related configuration information is optional because the RAN and UPF user plane (RAN-UPF UP) connection does not need to be mapped to the DRB; the UE-related identifier or address information is replaced by the identifier or address information of the network node (e.g., gNB) of the radio access network RAN.

[0343] 9: SMF 30c sends a user plane connection establishment completion message to UPF 30d (as an example of the fourth connection establishment completion message), which includes at least the endpoint information of the RAN (gNB) to which the RAN and UPF user plane (RAN-UPF UP) are connected for the transport bearer on the NG-U interface, and / or the endpoint information of the DN node to which the UPF-DN UP is connected for the transport bearer on the N6 interface.

[0344] In another embodiment, AMF and SMF are a network node, then the message sending and receiving and process processing between AMF and SMF in the above process are completed by the internal implementation of the network node, and the flow message sending and receiving and process processing between the two nodes AMF and SMF and other network nodes are implemented by the network node and other network nodes.

[0345] Example 6: User plane connection between RAN and DN for group UE services

[0346] In some application scenarios, services or functions involve two or more UEs and DN (Data Network) network nodes, i.e., group UE services. These two or more UEs back up each other in the service. For example, in the downlink direction from the DN to multiple UEs, the RAN needs to distribute service data from one to many; in the uplink direction from multiple UEs to the DN, the RAN needs to selectively forward service data from multiple UEs on a one-to-many basis.

[0347] As shown in Figure 40, data flows are represented by dashed lines 206, 207, and 208. In terms of user plane connections carrying service data, in the downlink direction, the N3 (NG-U) user plane connection from UPF 30d to RAN 20 (such as the user plane connection of data flow 206) is mapped at RAN 20 to Uu interface user plane connections from RAN 20 to two or more UEs (UE1, ..., UEn) (such as the user plane connections of data flows 207 and 208); in the uplink direction, the Uu interface user plane connections from two or more UEs (UE1, ..., UEn) to RAN 20 are selected at RAN 20 and mapped to the N3 (NG-U) user plane connection from RAN 20 to UPF 30d. As an embodiment, the N3 (NG-U) user plane connection between the RAN 20 and the UPF 30d can adopt the NG-U interface standard shown in Figure 4, that is, QoS flow and GTP-U bearer; the user plane connection of the Uu interface between the RAN and the UE can adopt the Uu interface standard shown in Figure 5, that is, DRB.

[0348] In order to establish the user plane connection of the group UE service, it is necessary to enhance and modify the control plane process of the relevant control plane protocol, involving network nodes such as UE, RAN, UPF, AMF and SMF.

[0349] Figure 41 is a schematic diagram of the relevant signaling process, in which the processes and their numbers do not limit their order. In addition, the control plane signaling process can also include only one or more processes. The main processes are described as follows:

[0350] 1: AMF 30b sends a connection establishment request message between the network node of the radio access network RAN ​​and the user plane function UPF to SMF 30c (as an example of the second connection establishment request message, such as the RAN-UPF user plane (RAN-UPF UP) connection establishment request message). This message includes at least one of the following information: the identifier or address information of the network node of the radio access network RAN ​​(e.g., gNB), the identifier or address information related to the access and mobility management function AMF, the identifier or address information of the session management function SMF, and service-related information related to the RAN-DN service (such as service type or function type, and / or service data rate). As an embodiment, the process and message can be the process and message related to PDU Session between SMF / UPF in the existing 5GC. In particular, the message may also include identifier information related to at least two user equipments UE to indicate the service type or function type related to the at least two UEs.

[0351] 3: SMF 30c sends a RAN-DN service establishment response message (as an example of the second connection establishment response message) and a connection establishment request message between the network node of the radio access network RAN ​​and the user plane function UPF (as an example of the third connection establishment request message, such as a RAN and UPF user plane (RAN-UPF UP) connection establishment request message) to AMF 30b.

[0352] 42 , in another embodiment, step 3 can be divided into two steps, including steps 2 and 3a.

[0353] 2: SMF 30c sends a RAN-DN service establishment response message to AMF 30b (as an example of the second connection establishment response message).

[0354] 3a: The SMF 30c sends a connection establishment request message between the network node of the radio access network RAN ​​and the user plane function UPF (e.g., a RAN-UPF UP connection establishment request message, as an example of the third connection establishment request message). The message includes at least one of the following information: identification or address information of the network node of the radio access network RAN ​​(e.g., gNB), identification or address information related to the access and mobility management function AMF, identification or address information of the session management function SMF, identification or address information of the UPF, information related to resources of the RAN-UPF UP connection over the NG-U interface, identification information of at least two UEs, and information related to resources over the Uu interface. The information related to resources of the RAN-UPF UP connection over the NG-U interface includes at least one of the following information: endpoint information of the UPF of the transport bearer, service type or function type, service data rate, and information related to service quality of service (QoS). As an embodiment, the RAN and UPF user plane (RAN-UPF UP) connection establishment request message can be the existing PDU session resource establishment request message PDU Session Resource Setup Request, and at least one of the following enhancements and modifications is performed: defining a new PDU session Type for the RAN-DN service; at least two UE-related identification information and resource-related information on the Uu interface.

[0355] 4a: AMF 30b sends a RAN-UPF UP Connection Establishment Response message (as an example of the third connection establishment response message) to SMF 30c. This message includes at least one of the following information: the identifier or address information of a network node (e.g., a gNB) of the radio access network (RAN), the identifier or address information related to the access and mobility function (AMF), the identifier or address information of the session management function (SMF), the identifier or address information of the UPF, and information related to resources connected to the RAN-UPF UP over the NG-U interface. The information related to resources connected to the RAN-UPF UP over the NG-U interface includes at least information about the RAN (gNB) endpoint for the transport bearer. As an example, the RAN-UPF UP Connection Establishment Response message can be the existing PDU Session Resource Setup Response message.

[0356] 3b / 4b: Request and response messages for establishing a RAN and UPF user plane (RAN-UPF UP) connection between the SMF / UPF, respectively. As an embodiment, the process and message may be a process and message related to the PDU Session between the SMF / UPF in the existing 5GC.

[0357] 3b: The SMF 30c sends a connection establishment request message (e.g., a RAN-UPF user plane connection establishment request message, as an example of the fourth connection establishment request message) between the network node of the radio access network RAN ​​and the user plane function UPF to the UPF 30d. The message includes at least one of the following information: identifier or address information of the network node of the radio access network RAN ​​(e.g., gNB), identifier or address information related to the access and mobility management function AMF, identifier or address information of the session management function SMF, identifier or address information of the UPF, and information related to resources connected to the RAN-UPF user plane (RAN-UPF UP) over the NG-U interface. The information related to resources connected to the RAN-UPF user plane (RAN-UPF UP) over the NG-U interface includes at least one of the following information: RAN (gNB) endpoint information for the transport bearer, service type or function type, service data rate, and service quality of service (QoS) related information. As an embodiment, the RAN and UPF user plane (RAN-UPF UP) connection establishment request message can be an existing PDU session resource establishment request message PDU Session Resource Setup Request, and include at least one of the following enhancements and modifications: defining a new PDU session type PDU session Type for RAN-DN services; QoS flow configuration-related configuration information is optional because the RAN and UPF user plane (RAN-UPF UP) connection does not need to be mapped to DRB; the UE-related identifier or address information is replaced with the identifier or address information of the network node (e.g., gNB) of the radio access network RAN.

[0358] 4b: The UPF 30d sends a RAN-UPF UP connection establishment response message to the SMF 30c (as an example of the fourth connection establishment response message). This message includes at least one of the following information: the identifier or address information of a network node (e.g., a gNB) of the radio access network RAN, the identifier or address information related to the access and mobility management function (AMF), the identifier or address information of the session management function (SMF), the identifier or address information of the UPF, and information related to resources connected to the RAN-UPF UP over the NG-U interface. The information related to resources connected to the RAN-UPF UP over the NG-U interface includes at least the UPF endpoint information for the transport bearer of the NG-U interface. As an embodiment, the RAN and UPF user plane (RAN-UPF UP) connection establishment response message can be an existing PDU session resource establishment response message PDU Session Resource Setup Response, wherein the QoS flow configuration related configuration information is optional because the RAN and UPF user plane (RAN-UPF UP) connection does not need to be mapped to the DRB; the UE-related identifier or address information is replaced with non-UE-related identifier or address information (such as the identifier or address information of the node (gNB), cell, function or service, etc.).

[0359] 5: The AMF 30b sends a connection establishment request message between the network node of the radio access network RAN ​​and the user plane function UPF (e.g., a RAN-UPF UP connection establishment request message, as an example of the first connection establishment request message). The message includes at least one of the following information: identifier or address information of the network node of the radio access network RAN ​​(e.g., gNB), identifier or address information related to the access and mobility management function AMF, identifier or address information of the session management function SMF, identifier or address information of the UPF, information related to resources connected to the RAN-UPF UP over the NG-U interface, identifier information of at least two UEs, and information related to resources on the Uu interface. The information related to resources connected to the RAN-UPF UP over the NG-U interface includes at least one of the following information: UPF endpoint information for the transport bearer, service type or function type, service data rate, and service quality of service (QoS) information. As an embodiment, the RAN and UPF user plane (RAN-UPF UP) connection establishment request message can be the existing PDU session resource establishment request message PDU Session Resource Setup Request, and at least one of the following enhancements and modifications is performed: defining a new PDU session Type for the RAN-DN service; at least two UE-related identification information and resource-related information on the Uu interface.

[0360] 6: After receiving the RAN-UPF UP Connection Establishment Request message, the RAN 20 (gNB) maps the UP connection to at least two UE-related DRBs in the request message. The AMF 30b sends a RAN-UPF UP Connection Establishment Response message (as an example of a first connection establishment response message) to the SMF 30c. This message includes at least one of the following information: the identifier or address information of a network node (e.g., a gNB) in the radio access network (RAN), the identifier or address information related to the access and mobility function (AMF), the identifier or address information of the session management function (SMF), the identifier or address information of the UPF, and information related to resources connected to the RAN-UPF UP over the NG-U interface. The information related to resources connected to the RAN-UPF UP over the NG-U interface includes at least information about the RAN (gNB) endpoint that transmits the bearer. As an embodiment, the RAN and UPF user plane (RAN-UPF UP) connection establishment response message may be an existing PDU session resource establishment response message PDU Session Resource Setup Response.

[0361] A data radio bearer (DRB) establishment request message (DRB request message) is sent to the multiple user equipments (UEs) of the radio access network RAN ​​20 through a network node of the radio access network RAN ​​20 .

[0362] 7a and 7b: Based on the information in process 5 and / or 6, RAN 20 sends Uu DRB setup request messages to two or more UEs (UE1, ..., UEn) respectively. As an embodiment, the Uu DRB setup request message may be an existing radio resource control configuration message RRCReconfiguration.

[0363] 8a and 8b: Two or more UEs (UE1, ..., UEn) respectively send Uu DRB setup response messages to the RAN 20. As an embodiment, the Uu DRB setup response message may be an existing radio resource control configuration complete message RRCReconfigurationComplete.

[0364] 9: SMF 30c sends a user plane connection establishment completion message to UPF 30d (as an example of the fourth connection establishment completion message), which includes at least the endpoint information of the RAN (gNB) to which the RAN and UPF user plane (RAN-UPF UP) are connected for the transport bearer on the NG-U interface, and / or the endpoint information of the DN node to which the UPF-DN UP is connected for the transport bearer on the N6 interface.

[0365] In another embodiment, AMF and SMF are a network node, then the message sending and receiving and process processing between AMF and SMF in the above process are completed by the internal implementation of the network node, and the flow message sending and receiving and process processing between the two nodes AMF and SMF and other network nodes are implemented by the network node and other network nodes.

[0366] In particular, when the above-mentioned RAN and UPF user plane (RAN-UPF UP) connection and the Uu DRBs of two or more UEs are established, in the RAN 20, the following mapping relationship between the RAN and UPF user plane (RAN-UPF UP) connection and the Uu DRBs of two or more UEs will be established according to the information in process 1:

[0367] 1. In the downlink direction, the RAN-UPF UP connection is simultaneously mapped to the Uu DRBs of two or more UEs (UE1, ..., UEn);

[0368] 2. In the uplink direction, one Uu DRB of two or more UEs (UE1, ..., UEn) is selected and mapped to the established RAN-UPF UP connection.

[0369] In particular, corresponding to the Uu interface user plane protocol shown in FIG5 , as shown in FIG43 , the middle line 209 represents the mapping relationship established above, which is further described as follows:

[0370] 1. In the downlink direction, the QoS flow associated with the RAN and UPF user plane (RAN-UPF UP) connection is simultaneously mapped to a DRB associated with a Uu DRB for two or more UEs (UE1, ..., UEn) at the SDAP protocol layer in RAN 20. Specifically, when a service data packet (SDU) is received from a QoS flow in RAN 20, two or more identical copies of the data packet are generated through a replication operation and then sent to the DRBs corresponding to the two or more UEs.

[0371] 2. In the uplink direction, one data radio bearer (DRB) associated with a Uu DRB for each of two or more UEs (UE1, ..., UEn) is selected in the RAN 20 and mapped to a quality of service (QoS) flow associated with the RAN and UPF user plane (RAN-UPF UP) connection; that is, at a certain moment, one DRB is selected from the DRBs of the two or more UEs (UE1, ..., UEn) and mapped to the QoS flow. Specifically, when the DRB is selected to be mapped to the corresponding QoS flow, the service data unit (SDU) received from the DRB is sent to the corresponding QoS flow, and the SDU received from other DRBs is discarded or discarded after meeting a predetermined condition, such as being discarded after being buffered for a certain period of time.

[0372] In particular, for the uplink direction, the data packet reception status of the DRBs of the two or more UEs is measured in real time in the RAN 20, where the measurement parameters may be one or more of the following: Block Error Rate (BLER), Packet Error Rate (PER), Protocol Data Unit Set Error Rate (PSER), and uplink wireless signal quality corresponding to the DRB. Furthermore, for a DRB currently selected to be mapped to the corresponding quality of service flow QoS flow, if the measurement result is lower than a predetermined value, a process of reselecting the DRB will be triggered, and a DRB with the best measurement result will be reselected to be mapped to the corresponding quality of service flow QoS flow.

[0373] In particular, the above embodiment 6 can also be applied to dual-stack or multi-stack UEs, that is, the above processes and technologies involving two or more UEs are correspondingly applied to the dual-stack or multi-stack of one UE.

[0374] Example 7: User plane connection for services or functions between RAN nodes

[0375] Generally, a service or function involves two or more RAN network nodes, with high-volume and / or real-time data exchange between these nodes. These RAN nodes may perform a service or function, or a node performing another service or function may be associated with the RAN node to support the RAN node in performing the service or function. For example, a node may be associated with, connected to, or interact with the RAN node as a child node of a service or function of the RAN node. Therefore, it is necessary to establish a user plane connection, i.e., a connection-oriented communication link, between the two RAN network nodes to meet data exchange requirements.

[0376] Taking 5G RAN (i.e., RAN nodes of a 5G mobile communication system, such as gNBs) as an example, in order to support data exchange related to a certain service or function between RAN nodes based on user plane connections, a dedicated user plane connection is established between RAN nodes to support such data exchange.

[0377] As shown in Figure 44, if an Xn interface, including Xn-C and Xn-U, is established between RAN nodes, a user plane connection associated with a certain service or function is established directly on the Xn-U interface. As shown in Figure 3, this user plane connection is usually a data transmission bearer based on the GTP-U protocol. In order to establish this user plane connection, it is necessary to design corresponding control plane signaling processes and messages in the XnAP protocol of the Xn-C interface. As shown in Figure 45, the control plane signaling process and messages include:

[0378] 1: RAN1 (gNB) sends an Xn UP connection establishment request message to RAN2 (gNB) (e.g., an Xn UP UP connection establishment request message, as an example of the first connection establishment request message). The Xn UP connection establishment request message includes at least one of the following information: identification or address information related to the radio access network RAN1 and / or RAN2 node (e.g., gNB), and resource-related information on the Xn-U interface of the user plane (Xn UP) connection between RAN1 and RAN2. The resource-related information on the Xn-U interface of the Xn UP connection includes at least one of the following information: endpoint information of RAN1 (gNB) transmitting the bearer, service type or function type, service data rate, and service quality of service (QoS) related information.

[0379] 2: RAN2 (gNB) sends an Xn UP Connection Establishment Response message to RAN1 (as an example of a first connection establishment response message). This message includes at least one of the following information: identification or address information of the radio access network RAN2 and / or a RAN1 node (e.g., a gNB), and resource-related information about the Xn-U interface connection between the RAN1 and RAN2 user planes (Xn UP). The resource-related information about the Xn-U interface connection between the RAN1 and RAN2 user planes (Xn UP) includes at least information about the RAN2 (gNB) endpoint that transmits the bearer.

[0380] As shown in Figure 46, if an Xn interface is not or cannot be established between RAN nodes, a user plane connection associated with a specific service or function can be established over the NG-U interface (i.e., N3) between the two RAN nodes and the core network's UPF 30d. RAN1 and RAN2 will send data related to this service or function to the UPF 30d via their respective user plane connections with the UPF 30d, and receive data related to the service or function forwarded by the UPF 30d from the other RAN node. As shown in Figure 3, this user plane connection is typically a data transmission bearer based on the GTP-U protocol. To establish this user plane connection, relevant control plane signaling processes and messages must be designed within the control plane interface protocols between the relevant network nodes, including the NGAP protocol for the NG-C (N2) interface. This involves network nodes such as the RAN, UPF 30d, AMF 30b, and SMF 30c.

[0381] Figure 47 is a schematic diagram of the signaling process flow between multiple RAN nodes through the core network. The processes and their numbers do not limit their order. In addition, the control plane signaling process can also include only one or more of the processes. The main processes are described as follows:

[0382] 1a or 1b: RAN1 (gNB) or RAN2 (gNB) sends a RAN1-RAN2 service setup request message to AMF 30b. The message includes at least one of the following information: the identifier or address information of the RAN1 and / or RAN2 node (e.g., gNB) of the radio access network RAN, the identifier or address information related to the access and mobility management function AMF 30b, and service-related information (e.g., service type or function type, and / or service data rate).

[0383] 2a or 2b: AMF 30b sends an RN-DN service establishment response message to the RAN2 and / or RAN1 node.

[0384] 3: AMF 30b sends a connection establishment request message between the RAN1 and RAN2 nodes of the radio access network RAN ​​to SMF 30c (as an example of the second connection establishment request message, for example, a RAN1 and RAN2 user plane (RAN1-RAN2 UP) connection establishment request message). The connection establishment request message includes at least one of the following information: identifiers or address information of the RAN1 and RAN2 nodes (for example, gNB) of the radio access network RAN, identifiers or address information related to the access and mobility management function AMF 30b, identifiers or address information of the session management function SMF 30c, and service-related information related to the RAN1-RAN2 UP connection (such as service type or function type, and / or service data rate).

[0385] 4: SMF 30c sends a RAN1-RAN2 UP connection establishment response message to AMF 30b (as an example of the second connection establishment response message).

[0386] 5: The SMF 30c sends a connection establishment request message (as an example of the fourth connection establishment request message, for example, a RAN-UPF user plane (RAN-UPF UP) connection establishment request message) between the RAN1 and / or RAN2 nodes of the radio access network RAN ​​and the user plane function UPF 30d to the UPF 30d. The connection establishment request message includes at least one of the following information: identifiers or address information of the RAN1 and / or RAN2 nodes (for example, gNBs) of the radio access network RAN, identifiers or address information related to the access and mobility management function AMF 30b, identifiers or address information of the session management function SMF 30c, identifiers or address information of the UPF 30d, and information related to resources of the user plane (RAN-UPF UP) connection between RAN1 and / or RAN2 and UPF 30d on the NG-U interface. Among them, the resource-related information of the RAN1 and / or RAN2 and UPF 30d user plane (RAN-UPF UP) connected on the NG-U interface includes at least one of the following information: endpoint information of the RAN1 and / or RAN2 (gNB) that transmits the bearer, service type or function type, service data rate, and service service quality QoS related information.

[0387] 6: The UPF 30d sends a RAN1 and / or RAN2 and UPF 30d user plane (RAN-UPF UP) connection establishment response message to the SMF 30c (as an example of the fourth connection establishment response message). The connection establishment response message includes at least one of the following information: identifiers or address information of the RAN1 and / or RAN2 nodes (e.g., gNBs) of the radio access network RAN, identifiers or address information related to the access and mobility management function (AMF) 30b, identifiers or address information of the session management function (SMF) 30c, identifiers or address information of the UPF 30d, and information related to resources connected to the NG-U interface between the user plane of RAN1 and / or RAN2 and the UPF 30d (RAN-UPF UP). The information related to resources connected to the user plane of RAN1 and / or RAN2 and the UPF 30d (RAN-UPF UP) over the NG-U interface includes at least endpoint information of the UPF 30d for transport bearers on the NG-U interface of RAN1 and / or RAN2.

[0388] 7a or 7b: The AMF 30b sends a connection establishment request message between the RAN1 or RAN2 node of the radio access network RAN ​​and the user plane function UPF 30d to RAN1 or RAN2 (gNB) (as an example of the first connection establishment request message, for example, a RAN and UPF user plane (RAN-UPF UP) connection establishment request message). The message includes at least one of the following information: the identifier or address information of the RAN1 or RAN2 node (for example, a gNB) of the radio access network RAN, the identifier or address information related to the access and mobility management function AMF 30b, the identifier or address information of the session management function SMF 30c, the identifier or address information of the UPF 30d, and information related to resources of the user plane connection between RAN1 or RAN2 and UPF 30d (RAN-UPF UP) on the NG-U interface. The resource-related information for the RAN1 or RAN2 and UPF 30d user plane (RAN-UPF UP) connection over the NG-U interface includes at least one of the following: UPF 30d endpoint information for the transport bearer on the NG-U interface with RAN1 or RAN2, service type or function type, service data rate, and service quality of service (QoS) related information. In one embodiment, the RAN-UPF UP connection establishment request message may be an existing PDU Session Resource Setup Request message, and include at least one of the following enhancements and modifications: defining a new PDU session type (PDU session Type) for RAN-DN services; QoS flow configuration related information is optional because the RAN-UPF UP connection does not need to be mapped to a DRB; and replacing UE-related identifiers or address information with non-UE-related identifiers or address information (e.g., identifiers or address information of a node (gNB), cell, function, or service).

[0389] 8a or 8b: RAN1 or RAN2 (gNB) sends a RAN and UPF user plane (RAN-UPF UP) connection establishment response message to AMF 30b (as an example of a first connection establishment response message). The connection establishment response message includes at least one of the following information: the identifier or address information of the RAN1 or RAN2 (gNB) node (e.g., gNB) of the radio access network RAN, the identifier or address information related to the access and mobility management function (AMF) 30b, the identifier or address information of the session management function (SMF) 30c, the identifier or address information of the UPF 30d, and information related to resources connected to the NG-U interface between the RAN1 or RAN2 (gNB) and the UPF user plane (RAN-UPF UP). The information related to resources connected to the NG-U interface between the RAN1 or RAN2 (gNB) and the UPF 30d (RAN-UPF UP) includes at least the RAN1 or RAN2 (gNB) endpoint information for transport bearers on the NG-U interface of RAN1 or RAN2. As an embodiment, the RAN and UPF user plane (RAN-UPF UP) connection establishment response message can be an existing PDU session resource establishment response message PDU Session Resource Setup Response, wherein the UE-related identifier or address information is replaced by the identifier or address information of the network node (e.g., gNB) of the radio access network RAN.

[0390] 9: SMF 30c sends a connection establishment completion message between the RAN1 and / or RAN2 nodes of the radio access network RAN ​​and the user plane function UPF 30d to UPF 30d (as an example of the fourth connection establishment completion message), which includes at least the endpoint information of RAN1 and / or RAN2 (gNB) of the transmission bearer connected to the user plane of UPF 30d (RAN-UPF UP) on the NG-U interface.

[0391] Example 8: User plane connection for services or functions between nodes within the RAN

[0392] Typically, a service or function involves two or more network nodes within a RAN, with high-volume and / or real-time data exchange between these nodes. These RAN network nodes perform a specific service or function. Therefore, it is necessary to establish a user plane connection—a connection-oriented communication link—between the two RAN network nodes to meet data exchange requirements.

[0393] Taking the 5G RAN (i.e., the RAN node of the 5G mobile communication system, such as the gNB) as an example, in order to support data exchange related to a certain service or function between the gNB-CU and gNB-DU in the RAN based on the user plane connection, a dedicated user plane connection is established between the gNB-CU and gNB-DU to support such data exchange.

[0394] As shown in Figure 48, a user plane connection associated with a certain service or function is established on the F1-U interface. As shown in Figure 3, this user plane connection is usually a data transmission bearer based on the GTP-U protocol. In order to establish this user plane connection, it is necessary to design corresponding control plane signaling processes and messages in the F1AP protocol of the F1-C interface. As shown in Figure 49, the control plane signaling process and messages include:

[0395] 1: The gNB-CU sends an F1 UP connection establishment request message to the gNB-DU (e.g., an F1 UP connection establishment request message as an example of the first connection establishment request message). The F1 UP connection establishment request message includes at least one of the following information: identification or address information of the gNB-CU and / or gNB-DU nodes of the radio access network (RAN), and resource-related information on the F1-U interface for the user plane (F1 UP) connection between the gNB-CU and gNB-DU. The resource-related information on the F1-U interface for the F1 UP connection includes at least one of the following information: endpoint information of the gNB-CU transmitting the bearer, service type or function type, service data rate, and service quality of service (QoS) related information.

[0396] 2: The gNB-DU sends an F1 UP Connection Establishment Response message to the gNB-CU (as an example of a first connection establishment response message). The F1 UP Connection Establishment Response message includes at least one of the following information: identifiers or addresses of the gNB-CU and / or gNB-DU nodes in the radio access network, and resource-related information on the F1-U interface for the user plane (F1 UP) connection between the gNB-CU and gNB-DU. The resource-related information on the F1-U interface for the F1 UP connection includes at least endpoint information of the gNB-DU transmitting the bearer.

[0397] Referring to Figure 50, the embodiment of the present application also provides a chip 700, which may correspond to the corresponding process implemented by the user equipment (e.g., UE 10a, UE 10b, UE 10, UE1, UE2, to UEn) or network node (e.g., RAN20, NWDAF 30a, AMF 30b, SMF 30c, UPF 30d, RSMF 10e, RSMF 10f) or DN 40 entity in the embodiment of the present application, and the chip 700 can implement the corresponding process implemented by the above-mentioned user equipment (e.g., UE 10a, UE 10b, UE 10, UE1, UE2, to UEn) or network node (e.g., RAN20, NWDAF 30a, AMF 30b, SMF 30c, UPF 30d, RSMF 10e, RSMF 10f) or DN 40 entity in each method of the embodiment of the present application. The chip 700 includes a processor 701 , which can call and run a computer program from a memory to implement the method in the embodiment of the present application.

[0398] Optionally, the chip 700 may further include a memory 702. The processor 701 may call and execute a computer program from the memory 702 to implement the method in the embodiment of the present application.

[0399] The memory 702 may be a separate device independent of the processor 701 , or may be integrated into the processor 701 .

[0400] Optionally, the chip 700 may further include an input interface 703. The processor 701 may control the input interface 703 to communicate with other devices or chips, and specifically, may obtain messages or data sent by other devices or chips.

[0401] Optionally, the chip 700 may further include an output interface 704. The processor 701 may control the output interface 704 to communicate with other devices or chips, and specifically, may output information or data to other devices or chips.

[0402] Those skilled in the art will appreciate that the above-mentioned embodiments are specific embodiments for implementing the present application, and that in actual applications, various changes may be made thereto in form and detail without departing from the spirit and scope of the present application.

Claims

1. A data transmission method, executed in a first network node of a radio access network RAN, characterized in that: Include: receiving a first connection establishment request message related to a first data transmission bearer, used to establish the first data transmission bearer, wherein the first connection establishment request message includes identification information of a service type or a function type associated with a non-user equipment UE, or identification information of multiple UEs, and the first data transmission bearer is used to transmit data between the first network node and the second network node, and the data is data related to the service type or the function type, or data related to the multiple UEs in the radio access network; and A first connection establishment request response message related to the first data transmission bearer is sent to establish the first data transmission bearer between a first network node of the radio access network RAN ​​and the second network node.

2. The data transmission method according to claim 1, characterized in that: The first network node is a base station or a base station distribution unit DU of the radio access network RAN; The second network node is a user plane function UPF of a core network, a base station of a radio access network RAN, or a base station centralized unit CU of the radio access network RAN.

3. The data transmission method according to claim 1, characterized in that: The first data transmission bearer is a user plane transmission bearer and is a transmission bearer based on a General Packet Radio Service Tunneling Protocol-User Plane GTP-U protocol.

4. The data transmission method according to claim 1, characterized in that: The first connection establishment request message further includes at least one of the following information: The identifier or address information of the first network node; An identifier or address information of a second network node of the core network or the radio access network; endpoint information of the second network node of the transport bearer associated with the first data transport bearer; and The first data transmission carries relevant data rate and quality of service QoS requirement information.

5. The data transmission method according to claim 1, characterized in that: The first connection establishment request response message includes at least one of the following information: The identifier or address information of the first network node; The identification or address information of the second network node; and The endpoint information of the first network node of the transmission bearer related to the first data transmission bearer.

6. A data transmission method, executed in a data transmission system, characterized in that: Include: The third network node sends a first connection establishment request message related to the first data transmission bearer to the first network node, so as to establish the first data transmission bearer between the first network node and the second network node, wherein the first connection establishment request message includes identification information of a service type or a function type associated with a non-UE, or identification information of multiple UEs. The first network node sends a first connection establishment request response message associated with the first data transmission bearer to the third network node; The third network node sends a second connection establishment request message related to the first data transmission bearer, the second data transmission bearer, and / or the third data transmission bearer to the fourth network node, wherein the second data transmission bearer is used to represent a bearer between the second network node and the fifth network node, the third data transmission bearer is used to represent a bearer between the second network node and the sixth network node, and the first data transmission bearer, the second data transmission bearer, and the third data transmission bearer are all used to transmit data related to a service type or a function type associated with the non-UE, or data of the multiple UEs; The fourth network node sends a third connection establishment request message associated with the first data transmission bearer to the third network node; and The fourth network node sends a fourth connection establishment request message related to the first data transmission bearer, the second data transmission bearer, and / or the third data transmission bearer to the second network node to establish the first data transmission bearer, the second data transmission bearer, and / or the third data transmission bearer.

7. The data transmission method according to claim 6, characterized in that: Further including: The fourth network node sends a fifth connection establishment request message related to the second data transmission bearer to the fifth network node to establish the second data transmission bearer.

8. The data transmission method according to claim 7, characterized in that: Further including: The first network node sends a first connection establishment response message to the third network node; The fourth network node sends a second connection establishment response message related to the first data transmission bearer, the second data transmission bearer, and / or the third data transmission bearer to the third network node; The third network node sends a third connection establishment response message related to the first data transmission bearer to the fourth network node; The second network node sends a fourth connection establishment response message related to the first data transmission bearer, the second data transmission bearer, and / or the third data transmission bearer to the fourth network node; and The fifth network node sends a fifth connection establishment response message associated with the second data transmission bearer to the fourth network node.

9. The data transmission method according to claim 6, characterized in that: Further including: The fourth network node sends a fourth connection establishment completion message related to the first data transmission bearer, the second data transmission bearer, and / or the third data transmission bearer to the second network node to complete the establishment of the first data transmission bearer, the second data transmission bearer, and / or the third data transmission bearer.

10. The data transmission method according to claim 6, characterized in that: The first network node is a base station of the radio access network RAN; The second network node is a user plane function UPF; The third network node is an access and mobility management function AMF; The fourth network node is a session management function SMF; The fifth network node is a core network service management function CNSMF; and / or The sixth network node is a network node of the data network DN.

11. The data transmission method according to claim 6, characterized in that: Further including: The third network node receives a service establishment request message related to the first data transmission bearer, the second data transmission bearer, and / or the third data transmission bearer from the first network node or the fifth network node, wherein the service establishment request message includes identification information of the service type or function type, or identification information of the multiple UEs.

12. The data transmission method according to claim 7, characterized in that: The second connection establishment request message, the third connection establishment request message, the fourth connection establishment request message, and the fifth connection establishment request message include identification information of the service type or function type, or identification information of the multiple UEs.

13. The data transmission method according to claim 6, characterized in that: The first data transmission bearer is a user plane transmission bearer; wherein the user plane transmission bearer is a transmission bearer based on the General Packet Radio Service Tunneling Protocol-User Plane GTP-U protocol.

14. The data transmission method according to claim 6, characterized in that: The second data transmission bearer is a user plane transmission bearer; wherein the user plane transmission bearer is a transmission bearer based on the GTP-U protocol, a transmission bearer based on the transmission control protocol TCP protocol, or a transmission bearer based on the HTTP protocol.

15. The data transmission method according to claim 6, characterized in that: The third data transmission bearer is a user plane transmission bearer; wherein the user plane transmission bearer is a transmission bearer based on the GTP-U protocol, a transmission bearer based on the TCP protocol, a transmission bearer based on the User Datagram Protocol UDP protocol, or a transmission bearer based on the Hypertext Transfer Protocol Secure HTTP protocol.

16. The data transmission method according to claim 10, characterized in that: The second connection establishment request message includes at least one of the following: an identifier or address information related to a network node of the radio access network RAN, an identifier or address information related to the access and mobility management function AMF, an identifier or address information of the session management function SMF, an identifier or address information related to a network node of the CNSMF, an identifier or address information of the user plane function UPF, an identifier or address information related to the data network DN, and service-related information of the first data transmission bearer, the second data transmission bearer, and / or the third data transmission bearer; The third connection establishment request message includes at least one of the following: an identifier or address information related to a network node of the radio access network RAN, an identifier or address information related to the access and mobility management function AMF, an identifier or address information of the session management function SMF, an identifier or address information of the UPF, endpoint information of the UPF of the first data transmission bearer and / or information related to the service; The fourth connection establishment request message includes at least one of the following: an identifier or address information related to a network node of the radio access network RAN, an identifier or address information of the core network service management function CNSMF, an identifier or address information related to the access and mobility management function AMF, an identifier or address information of the session management function SMF, an identifier or address information of the UPF, an identifier or address information related to the data network DN, endpoint information of a base station of the first data transmission bearer, endpoint information of the CNSMF of the second data transmission bearer, endpoint information of the DN of the third data transmission bearer and / or information related to the service of the data transmission bearer; The first connection establishment request message includes at least one of the following: an identifier or address information related to a network node of the radio access network RAN, an identifier or address information related to the access and mobility management function AMF, an identifier or address information of the session management function SMF, an identifier or address information of the user plane function UPF, endpoint information of the UPF of the first data transmission bearer and / or information related to the service; and The fifth connection establishment request message includes at least one of the following: an identifier or address information related to a network node of the radio access network RAN, an identifier or address information related to the access and mobility management function AMF, an identifier or address information of the UPF, an identifier or address information of the session management function SMF, an identifier or address information of the core network service management function CNSMF, endpoint information of the UPF carried by the second data transmission and / or information related to the service carried by the data transmission.

17. The data transmission method according to claim 16, characterized in that: The information related to the service carried by the data transmission includes at least one of the following: service type or function type, service data rate, and information related to service quality of service QoS.

18. The data transmission method according to claim 8, characterized in that: The second connection establishment response message includes at least one of the following: identification or address information related to a network node of the radio access network RAN, identification or address information related to the access and mobility management function AMF, identification or address information of the session management function SMF, identification or address information of the UPF, endpoint information of the UPF of the first data transmission bearer and / or information related to the service of the data transmission bearer; The third connection establishment response message includes at least: endpoint information of the base station carried by the first data transmission; The fourth connection establishment response message includes at least: endpoint information of the UPF of the first data transmission bearer, endpoint information of the UPF of the second data transmission bearer, and / or endpoint information of the UPF of the third data transmission bearer; The first connection establishment response message includes at least: endpoint information of the base station carried by the first data transmission; and / or The fifth connection establishment response message includes at least: endpoint information of the CNSMF carried by the second data transmission.

19. The data transmission method according to claim 9, characterized in that: The fourth connection establishment completion message includes at least: endpoint information of the base station carried by the first data transmission, endpoint information of the CNSMF carried by the second data transmission, and / or endpoint information of the DN carried by the third data transmission.

20. The data transmission method according to claim 6, characterized in that: In the downlink direction, it also includes: Data related to at least two UEs are mapped by the RAN to data radio bearers (DRBs) of the Uu interfaces of the at least two UEs; and Data related to at least two UEs is transmitted via the data radio bearer DRB; wherein the data related to at least two UEs is transmitted via the first data transmission bearer; and / or In the uplink direction, the first network node selects one UE among at least two UEs, maps the data radio bearer and data of the Uu interface of the selected UE to the first data transmission bearer, and transmits the data of the selected UE through the first data transmission bearer.

21. The data transmission method according to claim 20, characterized in that: In the uplink direction, it also includes: The first network node selects one of the at least two UEs, and maps at least one data radio bearer DRB of the selected UE to at least one quality of service flow QoS flow associated with the first data transmission bearer; and The service data unit SDU carried by the at least one DRB is sent to the corresponding quality of service flow QoS flow.

22. The data transmission method according to claim 21, characterized in that: The first network node measures the transmission quality of uplinks of at least two UEs to obtain a measurement result.

23. The data transmission method according to claim 22, characterized in that: For the selected UE, when the measurement result is lower than a predetermined value, the first network node triggers a process of reselecting the UE, wherein the process of triggering the reselection of the UE is to reselect a UE corresponding to the best measurement result and map the data carried by at least two DRBs of the UE to the service quality flow QoS flow corresponding to the DRB.

24. A data transmission method, executed in a first network node of a radio access network RAN, characterized in that: Include: Receive or send a protocol transmission message; wherein the protocol transmission message carries a protocol data unit (PDU), and the protocol transmission message and the protocol data unit type both correspond to the service type or function type.

25. The data transmission method according to claim 24, characterized in that: The protocol transmission message includes a message type element, and the message type element is used to indicate the service type or function type corresponding to the protocol transmission message.

26. The data transmission method according to claim 24, characterized in that: The protocol transmission message includes a message type element and a service type element, and the service type element is used to indicate the service type or function type corresponding to the protocol transmission message.

27. The data transmission method according to claim 26, characterized in that: The protocol transmission message is a user equipment UE-associated or non-UE-associated protocol transmission message, wherein the UE-associated or non-UE-associated protocol transmission message is indicated by a message type element in the protocol transmission message.

28. The data transmission method according to claim 26, characterized in that: The received or sent protocol transmission message is indicated by the message type element in the protocol transmission message.

29. The data transmission method according to claim 27, characterized in that: The UE-associated protocol transmission message also includes identification information of the UE in the first network node and identification information of the UE in the network node used for access and mobility management.

30. The data transmission method according to claim 24, characterized in that: The protocol transmission message also includes routing identification information, wherein the routing identification information is used to identify a network node for service management in a core network corresponding to the service type or function type.

31. The data transmission method according to claim 30, characterized in that: The first network node is a base station of the radio access network RAN; The network node for access and mobility management is an access and mobility management function AMF; and The network node used for service management is the core network service management function CNSMF.

32. A network node, characterized in that: include: A processor configured to call and execute a computer program stored in a memory so that a device equipped with the processor executes the method of any one of claims 1 to 31.

33. A chip, characterized in that: include: A processor configured to call and execute a computer program stored in a memory so that a device equipped with the processor executes the method of any one of claims 1 to 31.

34. A computer-readable storage medium, characterized in that A computer program is stored therein, wherein the computer program enables a computer to execute the method of any one of claims 1 to 31.

35. A computer program product, characterized in that Comprising a computer program, wherein the computer program causes a computer to execute the method of any one of claims 1 to 31.

36. A data transmission system, characterized in that: Include: A first network node, a second network node, a third network node, a fourth network node, and a fifth network node, wherein: The first network node is used to receive a first connection establishment request message related to a first data transmission bearer, wherein: The first data transmission bearer is used to represent a bearer between the first network node and the second network node; The second network node is used to receive a fourth connection establishment request message related to the first data transmission bearer, the second data transmission bearer, and / or the third data transmission bearer; wherein the second data transmission bearer is used to represent the bearer between the second network node and the fifth network node, and the third data transmission bearer is used to represent the bearer between the second network node and the sixth network node; The third network node is used to send the first connection establishment request message related to the first data transmission bearer to the first network node, so as to establish the first data transmission bearer between the first network node and the second network node, wherein the first connection establishment request message includes identification information of a service type or a function type associated with a non-UE, or identification information of multiple UEs; the first network node sends a first connection establishment request response message related to the first data transmission bearer to the third network node; the third network node sends a second connection establishment request message related to the first data transmission bearer, the second data transmission bearer, and / or the third data transmission bearer to the fourth network node, wherein the first data transmission bearer, the second data transmission bearer, and the third data transmission bearer are all used to transmit data related to a service type or a function type associated with the non-UE, or data of the multiple UEs; the fourth network node is configured to send a third connection establishment request message related to the first data transmission bearer to the third network node, send a fourth connection establishment request message related to the first data transmission bearer, the second data transmission bearer, and / or the third data transmission bearer to the second network node to establish the first data transmission bearer, the second data transmission bearer, and / or the third data transmission bearer, and send a fifth connection establishment request message related to the second data transmission bearer to the fifth network node to establish the second data transmission bearer; and The fifth network node is configured to receive a fifth connection establishment request message related to the second data transmission bearer.

Images