Data transmission method and apparatus, access network device, network element and storage medium

By establishing a user plane connection between the access network device and the first network element, the problem of data transmission being unable to meet the requirements of large data volume and high latency in the existing technology is solved, and more efficient communication performance is achieved.

WO2026232612A1PCT designated stage Publication Date: 2026-11-12GUANGDONG OPPO MOBILE TELECOMMUNICATIONS CORP LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/CN2025/094109
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Filing Date
2025-05-09
Publication Date
2026-11-12

AI Technical Summary

Technical Problem

In the current system architecture, the transmission between access network devices and specific core network elements is difficult to meet the data transmission requirements of large data volume and high latency, especially for specific services such as sensing services and positioning services, where control plane connectivity is difficult to achieve effectively.

Method used

By establishing a user plane connection between the access network equipment and the first network element, data interaction is achieved, and the user plane connection is used to transmit large amounts of data with high latency requirements.

Benefits of technology

It improves the communication performance between access network equipment and the first network element, enabling the effective transmission of large amounts of data and meeting the communication requirements with high latency.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN2025094109_12112026_PF_FP_ABST
    Figure CN2025094109_12112026_PF_FP_ABST
Patent Text Reader

Abstract

Provided in the embodiments of the present application is a data transmission method, comprising: a first network element sending first data to an access network device on the basis of a first connection; and / or the first network element receiving, on the basis of the first connection, second data sent by the access network device. Further provided in the embodiments of the present application are a data transmission apparatus, a device, a network element and a storage medium.
Need to check novelty before this filing date? Find Prior Art

Description

Data transmission methods and apparatus, access network equipment, network elements and storage media Technical Field

[0001] This application relates to the field of communication technology, and in particular to a data transmission method and apparatus, access network equipment, network element and storage medium. Background Technology

[0002] In the current system architecture, the transmission between access network devices and specific core network elements needs to be transmitted through the control plane, which makes it difficult to meet the data transmission requirements of large data volume and high latency. Summary of the Invention

[0003] This application provides a data transmission method and apparatus, access network equipment, network element, and storage medium.

[0004] Firstly, a data transmission method is provided, the method comprising:

[0005] The first network element sends the first data to the access network device based on the first connection;

[0006] And / or,

[0007] The first network element receives the second data sent by the access network device based on the first connection.

[0008] Secondly, a data transmission method is provided, the method comprising:

[0009] The second network element sends a first request message to the first network element, the first request message being used to request the first network element to configure a second connection; the first connection between the first network element and the access network device is related to the second connection;

[0010] or,

[0011] The second network element sends a fourth request message to the first network element, the fourth request message being used to request the first network element to configure a first connection;

[0012] The first connection is used to transmit first data and / or second data, wherein the first data is data sent by the first network element to the access network device, and the second data is data sent by the access network device to the first network element.

[0013] Thirdly, a data transmission method is provided, the method comprising:

[0014] The access network device receives first data sent by the first network element based on the first connection;

[0015] And / or,

[0016] The access network device sends the second data to the first network element based on the first connection.

[0017] Fourthly, a data transmission method is provided, the method comprising:

[0018] The third network element receives the fifth or sixth request information;

[0019] The fifth request information is used to request the second network element to send a first message to the access network device, the first message including information related to the second connection between the first network element and the access network element;

[0020] The sixth request information is used to request the second network element to send a sixth message to the access network device. The sixth message includes information related to the first connection between the first network element and the access network element.

[0021] Fifthly, a data transmission apparatus is provided, applied to a first network element, the apparatus comprising:

[0022] The first communication unit is configured to send first data to the access network device based on a first connection; and / or to receive second data sent by the access network device based on the first connection.

[0023] Sixthly, a data transmission apparatus is provided, applied to a second network element, the apparatus comprising:

[0024] The second communication unit is configured to send a first request message to the first network element, the first request message being used to request the first network element to configure a second connection; the first connection between the first network element and the access network device is related to the second connection.

[0025] or,

[0026] The second communication unit is configured to send a fourth request message to the first network element, the fourth request message being used to request the first network element to configure a first connection;

[0027] The first connection is used to transmit first data and / or second data, wherein the first data is data sent by the first network element to the access network device, and the second data is data sent by the access network device to the first network element.

[0028] In a seventh aspect, a data transmission apparatus is provided, applied to an access network device, the apparatus comprising:

[0029] The third communication unit is configured to receive first data sent by the first network element based on the first connection; and / or send second data to the first network element based on the first connection.

[0030] Eighthly, a data transmission apparatus is provided, applied to a third network element, the apparatus comprising:

[0031] The fourth communication unit is configured to receive either the fifth or sixth request information.

[0032] The fifth request information is used to request the second network element to send a first message to the access network device, the first message including relevant information about the second connection;

[0033] The sixth request information is used to request the second network element to send a sixth message to the access network device. The sixth message includes information related to the first connection between the first network element and the access network element.

[0034] Ninthly, a communication device is provided, the communication device comprising: a memory, a transceiver, a processor, and a bus system;

[0035] The memory is used to store programs and instructions;

[0036] The transceiver is used to receive or send information under the control of the processor;

[0037] The processor is used to execute programs in the memory;

[0038] The bus system is used to connect the memory, the transceiver, and the processor to enable communication between the memory, the transceiver, and the processor;

[0039] The processor is used to call program instructions in the memory to execute the data transmission method described above.

[0040] The chip provided in this application embodiment is used to implement the above-described data transmission method.

[0041] Specifically, the chip includes a processor for retrieving and running a computer program from memory, causing a device equipped with the chip to perform the aforementioned data transmission method.

[0042] The computer-readable storage medium provided in this application embodiment is used to store a computer program that causes a computer to execute the above-described data transmission method.

[0043] The computer program product provided in this application includes computer program instructions that cause a computer to execute the above-described data transmission method.

[0044] The computer program provided in this application embodiment, when run on a computer, causes the computer to execute the above-described data transmission method.

[0045] In the data transmission method provided in this application embodiment, a first network element can establish a first connection with an access network device and perform data interaction through the first connection. This allows for the transmission of larger data volumes and transmissions with higher latency requirements between the first network element and the access network device, thereby improving the communication performance between them to a certain extent. Attached Figure Description

[0046] Figure 1 is a schematic diagram of a system architecture provided in an embodiment of this application;

[0047] Figure 2 is a schematic diagram of a system architecture for a perception service provided in an embodiment of this application;

[0048] Figure 3 is a schematic diagram of a system architecture for a location service provided in an embodiment of this application;

[0049] Figure 4 is a schematic diagram of a location service process provided in an embodiment of this application;

[0050] Figure 5 is a flowchart illustrating a data transmission method according to an embodiment of this application;

[0051] Figure 6 is a schematic flowchart of a data transmission method provided in an embodiment of this application;

[0052] Figure 7 is a schematic flowchart of a data transmission method provided in an embodiment of this application;

[0053] Figure 8 is a schematic flowchart of a data transmission method provided in an embodiment of this application;

[0054] Figure 9 is a flowchart illustrating a data transmission method according to an embodiment of this application.

[0055] Figure 10 is a schematic diagram of a signaling interaction provided in an embodiment of this application;

[0056] Figure 11 is a schematic flowchart of a data transmission method provided in an embodiment of this application;

[0057] Figure 12 is a second schematic diagram of signaling interaction provided in an embodiment of this application;

[0058] Figure 13 is a schematic flowchart of a data transmission method provided in an embodiment of this application;

[0059] Figure 14 is a schematic diagram of a signaling interaction provided in an embodiment of this application;

[0060] Figure 15 is a flowchart illustrating a data transmission method according to an embodiment of this application.

[0061] Figure 16 is a schematic diagram of the structure of a data transmission device 1600 provided in an embodiment of this application;

[0062] Figure 17 is a structural schematic diagram of a data transmission device 1700 provided in an embodiment of this application;

[0063] Figure 18 is a structural schematic diagram of a data transmission device 1800 provided in an embodiment of this application;

[0064] Figure 19 is a structural schematic diagram of a data transmission device 1900 provided in an embodiment of this application;

[0065] Figure 20 is a schematic structural diagram of a communication device provided in an embodiment of this application;

[0066] Figure 21 is a schematic structural diagram of a chip according to an embodiment of this application;

[0067] Figure 22 is a schematic block diagram of a communication system provided in an embodiment of this application. Detailed Implementation

[0068] To make the objectives, technical solutions, and advantages of this application clearer, the embodiments of this application will be described in further detail below with reference to the accompanying drawings. The accompanying drawings are for reference only and are not intended to limit the embodiments of this invention.

[0069] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this application are used to distinguish different objects, not to describe a specific order. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or device that includes a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units not listed, or may optionally include other steps or units inherent to these processes, methods, products, or devices.

[0070] It should be noted that this application applies to mobile networks, especially future-oriented mobile networks, such as Beyond 5G (B5G) networks, 6G networks, etc.

[0071] Figure 1 illustrates a schematic diagram of a system architecture provided in this application. As shown in Figure 1, the system architecture includes: Wireless Access Network ((R)AN) equipment, User Equipment (UE), Data Network (DN) network elements, Access and Mobility Management Function (AMF) network elements, Session Management Function (SMF) network elements, Policy Control Function (PCF) network elements, Authentication Server Function (AUSF) network elements, Unified Data Management (UDM) network elements, Application Function (AF) network elements, User Plane Function (UPF) network elements, and the Network Slice Selection Function (NSSF) network elements.

[0072] In some embodiments, the above system architecture may also include network elements not shown in Figure 1, such as Location Management Function (LMF), Network Exposure Function (NEF), Home Gateway Mobile Location Center (H-GMLC), Visited Gateway Mobile Location Center (V-GMLC), and Location Services Client (LCS Client).

[0073] The AMF network element is mainly used for terminal registration, mobility management, and tracking area update processes in mobile networks. The mobility management network element can receive Non-Access Stratum (NAS) messages, complete registration management, connection management, and reachability management, allocate tracking area lists, and perform mobility management, and also transparently transmit session management messages to the SMF network element.

[0074] SMF network elements are primarily used for session management in mobile networks, such as session creation, modification, and release. Specific functions include assigning Internet Protocol (IP) addresses to users and selecting user plane network elements that provide packet forwarding capabilities.

[0075] In addition, the PCF network element includes user subscription data management, policy control, billing policy control, and Quality of Service (QoS) control. The AUSF network element is primarily used to authenticate service functions using an extensible authentication protocol (EAP) and store keys to achieve user authentication and authorization. The UDM network element is mainly used to store user data, such as subscription information and authentication / authorization information.

[0076] UPF network elements are primarily used for user plane service processing, such as service routing, packet forwarding, anchoring functions, Quality of Service (QoS) mapping and enforcement, uplink identification and routing to the data network, downlink packet buffering and downlink data arrival notification triggering, and connection to external data networks. NSSF network elements are primarily used to select the network slice serving the UE, determine the Network Slice Selection Assistance Information (NSSAI) configured for the UE, and determine the NSSAI allowed by the UE.

[0077] (R)AN equipment, also known as access network equipment, is a device that provides wireless communication functions for UEs. Access network equipment includes, but is not limited to: base stations (BS), base stations (xNodeB, xNB) in future mobile networks, next-generation base stations (gNodeB, gNB) in 5G, evolved Node B (eNB), radio network controllers (RNC), Node Bs (NB), base station controllers (BSC), base transceiver stations (BTS), femtocells, base band units (BBU), transmitting and receiving points (TRP), transmitting points (TP), mobile switching centers, etc.

[0078] The UE in this application embodiment is a device with wireless transceiver capabilities, which can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; it can also be deployed on water; and it can also be deployed in the air (e.g., on airplanes, balloons, and satellites). The UE can be a mobile phone, tablet computer, computer with wireless transceiver capabilities, VR device, AR device, wireless device in autonomous driving, wireless device in telemedicine, device in smart grid, wireless device in transportation safety, wireless device in smart city, etc.

[0079] DN network elements are mainly used to provide services to users, such as operator services, Internet access services, and third-party services.

[0080] It should be noted that the aforementioned network elements can be network components within hardware devices, software functions running on dedicated hardware, or virtualized functions instantiated on a platform (e.g., a cloud platform). These network elements can be divided into one or more services; furthermore, services that exist independently of network functions may also exist.

[0081] Referring to Figure 1, the UE can connect to the AMF network element through the N1 interface, and the (R)AN can connect to the AMF network element through the N2 interface. The UE connects to the (R)AN through the Uu interface. N3 is the connection interface between the (R)AN and the UPF network element. N4 is the connection interface between the SMF network element and the UPF, used to transmit control signaling between the SMF and UPF network elements. N5 is the connection interface between the PCF network element and the AF network element. N6 is the connection interface between the UPF network element and the DN network element. N7 is the connection interface between the SMF network element and the PCF. N8 is the connection interface between the UDM network element and the AMF network element. N9 is the connection interface between different UPF network elements, supporting cross-UPF data forwarding. N10 is the connection interface between the UDM network element and the SMF network element. N11 is the connection interface between the AMF network element and the SMF network element, used for exchanging session management signaling (such as PDU session establishment). N12 is the connection interface between the AUSF network element and the AMF network element, used to transmit UE authentication and key-related information. N13 is the connection interface between the UDM network element and the AUSF network element. N14 is the connection interface between AMF network elements, used for UE context synchronization during handover across AMF network elements. N15 is the connection interface between the AMF network element and the PCF network element. N22 is the connection interface between the NSSF and the AMF network element.

[0082] The following section introduces sensing technology.

[0083] Sensing technology refers to the technology of using sensors, signal processing, artificial intelligence and other means to detect, identify, measure and provide feedback on the physical environment or target objects.

[0084] Current cellular networks are used solely for communication. However, the radio electromagnetic signals used by cellular networks can be used for more than just wireless data transmission and communication; they also possess environmental sensing capabilities, such as user motion or gesture recognition, respiratory monitoring, terminal movement speed measurement, environmental imaging, and weather monitoring. Therefore, future cellular networks could be considered for more than just communication and data transmission; they could also be used for acquiring sensory information.

[0085] Sensing technology is deeply integrated with wireless communication to form Integrated Sensing and Communication (ISAC), realizing the function of "sensing the environment with communication signals".

[0086] Currently, discussions are underway to introduce sensing functions into B5G networks. This involves adding sensing function (SF) network elements and corresponding processes to support sensing functions in 3GPP networks.

[0087] For example, referring to the architecture diagram shown in Figure 2, an SF network element can be added to the system architecture shown in Figure 1. The SF network element can include a control plane portion (denoted as SF-C) and a user plane portion (denoted as SF-U).

[0088] It should be noted that the SF network element can be set up independently or jointly with the LMF network element, and this application embodiment does not impose any restrictions on this.

[0089] In practical applications, when an application sends a perception request for a target UE to the core network of the 3GPP network, the core network selects a suitable access network device or auxiliary UE through SF network elements or AMF network elements, triggers the ability to perform perception-related radio measurements, initiates the measurement of perception information, and generates perception results.

[0090] The main wireless sensing scenarios for integrated sensing are as follows:

[0091] 1) Base station echo sensing link (single gNB sensing): The base station sends sensing signals and receives echo signals;

[0092] 2) Inter-base station sensing link (gNB-gNB sensing): Base station B receives sensing signals sent by base station A;

[0093] 3) Air interface uplink sensing link (UE-gNB uplink sensing): The base station receives sensing signals sent by the terminal;

[0094] 4) Air interface downlink sensing link (UE-gNB downlink sensing): The terminal receives sensing signals sent by the base station;

[0095] 5) Terminal echo sensing link (single UE sensing): The terminal sends sensing signals and receives echo signals;

[0096] 6) Inter-terminal sensing link (UE-UE sensing): Terminal B receives sensing signals sent by Terminal A.

[0097] The perception task requires identifying the corresponding perception target. When the perception target is a UE, the corresponding UE can be found directly through the UE's ID or Internet Protocol (IP) address information, and the UE can be used as the sender or receiver of the perception signal. Then, other surrounding perception nodes can be selected to complete the perception task.

[0098] In the initial stage of B5G communication and sensing integration, the focus is on reusing existing air interface signals to perform sensing functions as much as possible, without introducing excessive air interface enhancements. Considering the complexity of full-duplex implementation, collaborative sensing between the UE and / or access network equipment is the preferred approach. Specifically, the sensing methods in scenarios 3), 4), 5), and 6) above may require the UE to report a large amount of sensing data to the SF network element or obtain auxiliary data from the core network element.

[0099] Currently, considering the large amount of data exchanged between the UE and the SF network element, the UE can complete the necessary interactions for sensing services with the SF network element through user plane data transmission. For example, the UE can send sensing data to the SF-U via the UPF by establishing a special PDU session.

[0100] The following section introduces deferred positioning technology.

[0101] Referring to Figure 3, which shows the system architecture diagram of the location service, and Figure 4, which shows the flowchart, the control plane data transmission between the LMF and RNA devices during the current delayed 5GC Mobile Terminated Location Request (5GC-MT-LR) process mainly includes the following steps:

[0102] S1. Delay 5GC-MT-LR steps 1-14 and execute according to the existing process. AF, LCS client or NF triggers periodic location events.

[0103] S2. The LMF executes one or more positioning procedures (UE Positioning). In this step, the LMF determines to perform NRPPa periodic measurements based on the received UE capability information and configuration. After determining to use NRPPa periodic measurements, the LMF can exchange positioning information with the NG-RAN based on the NRPPa protocol (as described in TS 38.455).

[0104] S3. Delay 5GC-MT-LR steps 18-21 and execute them according to the existing process, with the following modifications:

[0105] In steps 18-20, an NRPPa periodicity indication is added, indicating that the periodic position estimate is generated based on the NRPPa periodic measurement. (H)GMLC stores this indication.

[0106] S4a-b. The LMF executes an NRPPa periodic E-CID measurement initialization request (TS 38.455 Clause 8.2.1.2) or an NRPPa periodic measurement request (TS 38.455 Clause 8.5.1.2). The LMF configures NRPPa periodic reporting using the reporting interval and total number of times specified in step 1.

[0107] S5.AMF forwards the message to NG-RAN.

[0108] S6-7a.NG-RAN returns E-CID measurement initialization response (TS 38.455 Clause 8.2.1.2).

[0109] S6-7b.NG-RAN returned measurement response (TS 38.455 Clause 8.5.1.2).

[0110] S8-9a. The LMF periodically receives E-CID measurement reports from the NG-RAN (TS 38.455 Clause 8.2.3.2) and calculates the location results accordingly.

[0111] S8-9b.LMF periodically receives measurement reports from NG-RAN (TS 38.455 Clause 8.5.2.2) and calculates the location results accordingly.

[0112] S10.LMF calls the Nlmf_Location_EventNotify service operation (following step 28) to transmit location information to VGMLC or (H)GMLC.

[0113] S11. Delay 5GC-MT-LR step 29 and execute it according to the existing process.

[0114] S12a. Delay 5GC-MT-LR step 30a and execute it according to the existing process.

[0115] S12b-1. Delay 5GC-MT-LR step 30b-1 as per existing procedure.

[0116] S12b-2. Delay 5GC-MT-LR step 30b-2 as per existing procedure.

[0117] S12c. Delay 5GC-MT-LR step 30c and execute according to the existing process.

[0118] S8 to S12c are executed periodically.

[0119] In Figure 4, S1-S12, S4-S6 represent the LMF's reporting request to the RAN device to configure the control plane via the AMF, while S8-S9 represent the RAN node obtaining measurement data and then reporting the measurement data from the control plane via the AMF. The control plane configuration can utilize the AMF's service-based interface.

[0120] In the current integrated sensing architecture, due to the large amount of data that needs to be transmitted for sensing, the user plane connection between the UE and the SF network element can be achieved through PDU sessions. There is currently no definitive solution for configuring and establishing the user plane connection between the RAN and the SF network element. Similarly, in delayed positioning technology, the UE and the LMF network element can establish a user plane connection to transmit positioning data, but the LMF and RAN still need to interact via the control plane method of transmitting NRPP messages through the AMF.

[0121] As mentioned above, in the current system architecture, transmission between the RAN and specific network elements still requires control plane connections. Control plane connections between the RAN and specific network elements are insufficient to meet the demands of large data volumes or high latency. In particular, when the data volume of a specific service (e.g., sensing / location services) is too large or the latency requirements are high, the solution of transmitting data between the RAN and specific network elements via control plane connections is difficult to implement.

[0122] Based on this, embodiments of this application provide a data transmission method in which a first network element can establish a user plane connection with an access network device and perform data interaction through the user plane connection. In this way, the first network element and the access network device can be used for the transmission of large amounts of data and transmissions with high latency requirements, thereby improving the communication performance between the access network device and the first network element to a certain extent.

[0123] To facilitate understanding of the technical solutions of the embodiments of this application, the technical solutions of this application are described in detail below through specific embodiments. The above-mentioned related technologies are optional solutions and can be arbitrarily combined with the technical solutions of the embodiments of this application, all of which fall within the protection scope of the embodiments of this application. The embodiments of this application include at least some of the following contents.

[0124] It should be noted that the access network device in the embodiments of this application can also be called an access network node, and the two are equivalent or interchangeable.

[0125] It should also be noted that the node-level user plane connection mentioned in the embodiments of this application can also be referred to as or equivalently replaced by node-granular user plane connection, device-level user plane connection, or device-granular user plane connection.

[0126] It should also be noted that the Task / Session level user plane connection mentioned in the embodiments of this application can also be referred to as or equivalently replaced by the Task / Session granularity user plane connection.

[0127] In one embodiment of this application, referring to the flowchart of a data transmission method shown in FIG5, the data transmission method may include the following.

[0128] S510, the first network element sends first data to the access network device based on the first connection, and / or, the first network element receives second data sent by the access network device based on the first connection. Alternatively, the access network device sends first data to the first network element based on the first connection, and / or, the access network device sends second data to the first network element based on the first connection.

[0129] It should be noted that the first connection can be the connection between the access network device and the first network element. The first connection can refer to a connection that transmits data efficiently and reliably.

[0130] In some embodiments, the first connection is a user plane connection between the access network device and the first network element.

[0131] In some embodiments, the first connection is a data plane connection between the access network device and the first network element.

[0132] It should be noted that, in this embodiment, the first network element is the user plane portion of a specific service / function, and the control plane portion of this specific service / function is separately configured from the user plane portion. That is, the control plane portion and the user plane portion of the specific service / function are configured on two different entities.

[0133] In this embodiment, the first network element is used to implement the user plane portion of a specific service / function.

[0134] In some embodiments, the first network element may be one or more of the following: SF-U network element, LMF-U network element, and data collection network element.

[0135] In one example, the data transmission method provided in this application embodiment can be applied to the architecture shown in Figure 2. The first network element can be an SF-U network element. The first data and the second data can be sensing data. Specifically, the first data can be downlink sensing data, and the second data is uplink sensing data.

[0136] It should be noted that in Figure 2, the SF-C and SF-U of the SF network element are set up separately. That is to say, SF-C and SF-U are two independent physical devices.

[0137] In one example, the first network element can be the user plane portion of the LMF. The first data and the second data can be location-related data.

[0138] In this embodiment, the first network element can establish a user plane connection with the access network device and perform data interaction through the user plane connection. This allows for the transmission of larger data volumes and transmissions with higher latency requirements between the first network element and the access network device, thereby improving the communication performance between them to some extent.

[0139] In some embodiments, the first connection can be a node-level (also referred to as node-level, device-level, or device-level) user plane connection. That is, the first connection can correspond to an access network device and / or a first network element, or in other words, the first connection can be associated with an access network device and / or a first network element.

[0140] In some embodiments, the first connection may also be a user plane connection at the task / session level (also referred to as task / session granularity). That is, the first connection may correspond to a certain session (referred to as the first session in this embodiment) and / or a certain task (referred to as the first task in this embodiment).

[0141] It should be noted that the first session is any one of multiple sessions between the access network device and the first network element, and / or the first task is any one of multiple tasks between the access network device and the first network element. This application embodiment does not limit this.

[0142] In this embodiment of the application, the second network element can be configured with a first connection between the first network element and the access network device.

[0143] It should be noted that the second network element can be a control plane portion of a specific service / function. The second network element and the first network element are different device entities.

[0144] In some embodiments, the second network element may be one or more of the following: SF-C network element, LMF-C network element, and data management network element.

[0145] It should be noted that there are multiple ways to configure the second network element to connect to the first connection.

[0146] In one possible implementation (referred to as implementation 1 in this application embodiment), the second network element can be configured with a second connection. The first connection is associated with the second connection.

[0147] It should be noted that the second connection can also be a connection between the access network device and the first network element.

[0148] In some embodiments, the second connection is a user plane connection between the access network device and the first network element.

[0149] In some embodiments, the second connection is a data plane connection between the access network device and the first network element.

[0150] In another possible implementation (referred to as mode 2 in this application embodiment), the second network element can be directly configured with the first connection.

[0151] For method 1, the second network element is configured with a second connection, wherein the first connection is related to the second connection.

[0152] It should be noted that the second connection is a node-level user plane connection. That is, the second connection can correspond to the access network device and / or the first network element, or in other words, the second connection can be associated with the access network device and / or the first network element.

[0153] In one implementation (referred to as implementation 1A in this application embodiment), the first connection and the second connection are the same user plane connection, or in other words, the first connection and the second connection are the same user plane connection.

[0154] In other words, for mode 1A, the first connection can be understood as a node-level user plane connection, and the first connection can correspond to the access network device and / or the first network element.

[0155] In another implementation (referred to as Method 1B in this application embodiment), the first connection is different from the second connection, and / or the first connection can be established based on the second connection.

[0156] It should be noted that the first connection is different from the second connection. This can be understood as the first address information of the first connection being different from the second address information of the second connection.

[0157] It should also be noted that in Method 1B, the first connection can be understood as a Task / Session level user plane connection. This first connection corresponds to the first task and / or the first session.

[0158] In other words, for method 1B, the first network element can establish a second connection at the node level, and then establish a first connection at the Task / Session level based on this second connection at the node level. Method 1B can achieve isolation of user plane connections.

[0159] The following describes the specific steps for configuring the second connection using the second network element.

[0160] Referring to the flowchart shown in Figure 6, the configuration process for the second connection includes the following steps:

[0161] S610, the second network element sends a first request message to the first network element, the first request message being used to request the first network element to configure the second connection.

[0162] In some embodiments, the first request information can be understood as User Plane (UP) configuration information.

[0163] In some embodiments, the first request information may include one or more of the following:

[0164] RAN ID (Identification Information of Access Network Equipment);

[0165] The first identification information is used to identify the association between the second connection and the access network device.

[0166] It should be noted that the first identification information can also be called binding information.

[0167] In one example, the first identification information or binding information can be the RAN ID.

[0168] In one example, the first identification information or binding information can be a temporary identifier assigned to the first network element, which is referred to as the binding ID in this embodiment of the application.

[0169] In one example, the first identification information or binding information can be the connection ID of the second connection.

[0170] It should be noted that the first identification information is optional in the first request information; that is, the first request information may or may not include the first identification information. It is also possible that the RAN ID information is used as binding information, meaning that both are RAN IDs, but sent twice or only once with different IEs.

[0171] S620, the first network element sends the first response information to the second network element.

[0172] It should be understood that the first response information can be a response to the first request information. The first response information can be understood as the UP configuration response information.

[0173] In some embodiments, the first response information includes the second address information of the second connection.

[0174] It should be noted that the second address information may include one or more of the following: IP address information, port information, and fully qualified domain name (FQDN) information. This application embodiment does not limit the type of address information.

[0175] S630. The second network element sends a first message to the access network device, or the second network element sends a first message to the access network device through the third network element.

[0176] In some embodiments, the first message may include information related to the second connection. This information can be used to establish the second connection.

[0177] It should be noted that the information related to the second connection can also be understood as the configuration information of the second connection, or the second user plane information (UP information), or the second data information.

[0178] In some embodiments, the relevant information for the second connection may include one or more of the following:

[0179] Second address information for the second connection;

[0180] First identification information (binding information).

[0181] It should be noted that the first identification information is optional information in the relevant information of the second connection. That is, the relevant information of the second connection may or may not include the first identification information. It is also possible that the RAN ID information is used as binding information, that is, both are RAN IDs, and two copies are sent with different IEs or only one copy is sent.

[0182] In one possible implementation, the second network element can directly send the first message to the access network device. That is, the first message received by the access network device can come from the second network element.

[0183] It should be understood that if the second network element stores the ID of the access network device or the control plane interface information of the access network device, the second network element can send a first message to the access network device based on the ID of the access network device or the control plane interface information to establish a second connection.

[0184] In one possible implementation, the second network element can send the first message to the access network device through the third network element. That is, the first message received by the access network device can come from the third network element.

[0185] It should be noted that the third network element can be a management network element associated with the access network device. Specifically, the third network element can be a registration management network element and / or a mobility management network element. For example, the third network element can be an AMF network element in a 5G network or an MM network element in a 6G network.

[0186] Specifically, in this implementation, step S610 may include:

[0187] S630a, the second network element sends a fifth request message to the third network element. The fifth request message is used to request the third network element to send a first message to the access network device.

[0188] S630b, the third network element sends the first message to the access network equipment.

[0189] In some embodiments, the fifth request information may include one or more of the following:

[0190] Second address information for the second connection;

[0191] First identification information (i.e., binding information);

[0192] RAN ID (Identification Information) of Access Network Equipment.

[0193] In some embodiments, the third network element may determine the access network device to which the second connection is to be established based on the RAN ID. It should be understood that the third network element may manage or maintain multiple access network devices, and the third network element may determine the access network device to which the second connection is to be established based on the RAN ID in the fifth request information.

[0194] S640. The access network device sends a second message to the first network element through the second connection, or in other words, the first network element receives the second message through the second connection. The second message can be used by the first network element to determine the binding relationship of the second connection. That is, the second message can be used to determine the connection ID associated with the second connection and / or the associated RAN node.

[0195] In some embodiments, the second message includes one or more of the following:

[0196] RAN ID (Identification Information of Access Network Equipment);

[0197] First identification information (binding information).

[0198] It should be understood that after receiving the second address information, the access network device can establish a second connection with the first network element through the second address information. The access network device can then use this second connection, or in other words, use the second address information to send a second message to the first network element.

[0199] It should be noted that after the first network element receives the second message, it can determine the binding relationship of the second connection based on the second message.

[0200] In one example, when the second message includes a RAN ID, the first network element can determine that the second connection is associated with the RAN node corresponding to that RAN ID.

[0201] In one example, when the second message includes binding information, the first network element can determine that the second connection is associated with the RAN node and / or connection ID indicated by the binding information.

[0202] It should also be noted that step S640 is an optional step, meaning that step S640 can be performed or not. In Figure 6, this optional step is indicated by a dashed arrow.

[0203] It should be noted that in step S610, the second network element sends a first request message to the first network element to establish a second connection. This can be triggered by the second network element itself or by an external application network element.

[0204] In some embodiments, referring to FIG6, before step S610, the following steps are further included:

[0205] S602, the second network element receives service / data request information sent by external application network elements.

[0206] It should be noted that an external application network element can be an entity that requests services or data from other network elements in the core network. For example, an external application network element can be a Consumer Network Function (Consumer NF).

[0207] It should also be noted that the service / data request information may include target information and the corresponding service requirement.

[0208] In one example, target information may include one or more of the following: a specific geographic area, a specific UE, a specific object, a specific RAN, etc.

[0209] In one example, service requirements may include one or more of the following: sensing method, sensing accuracy, latency, etc.

[0210] S604. The second network element selects the third network element and access network equipment based on the service / data request information.

[0211] It should be noted that the second network element can obtain the ID information, control plane port information, or address information of the access network device by querying NRF / AMF, etc.

[0212] For the above-described method 1A (the first connection and the second connection are the same user plane connection), after the second connection at the node level is established, data interaction can be performed based on the second connection at the node level (i.e., step S510 is executed).

[0213] It should be noted that before the first network element and the access network device can interact with each other through the second connection based on node granularity, Task / Session needs to be configured.

[0214] In some embodiments, referring to FIG7, for mode 1A, after the second connection is established and before performing step S510, the following steps may also be included:

[0215] S710. The second network element sends a second request message to the first network element, or in other words, the first network element receives the second request message sent by the second network element. The second request message is used to request the first network element to configure the first task and / or the first session.

[0216] In some embodiments, the second request information may include one or more of the following:

[0217] RAN ID (Identification Information of Access Network Equipment);

[0218] The identification information of the first session (Session ID);

[0219] Correlation ID;

[0220] The identification information of the first task (Task ID).

[0221] In some embodiments, the second network element can obtain the Session ID and / or Task ID based on the service / data request information in step S602, or other service / data request information received before step S710. In this way, the second network element can send a second request to the first network element.

[0222] S720: The first network element sends a third message to the access network device through the second connection. The third message is used to configure the first task and / or the first session.

[0223] It should be noted that, in addition to sending third information to the access network device through the second connection, the first network element can also send third messages to the access network device through the control plane connection.

[0224] In one example, the first network element can send a third message to the second network element, and then the second network element directly sends the third message to the access network device through the control plane port information of the access network device. In another example, the first network element can send a third message to the second network element, and then the second network element sends the third message to the access network device through the third network element.

[0225] In some embodiments, the third message includes one or more of the following:

[0226] The identification information of the first session (Session ID);

[0227] The identification information of the first task (Task ID);

[0228] Correlation ID.

[0229] S730, the first network element receives a fourth message sent by the access network device through the second connection. The fourth message is used to transmit service data and / or service-related signaling.

[0230] The first network element receives a fourth message through the second connection, the fourth message being used to confirm the first session and / or the first task associated with the second connection.

[0231] It should be understood that after configuring the first task and / or the first session, the access network device can transmit the service data and / or service-related signaling corresponding to the first task and / or the first session to the first network element through the second connection.

[0232] In some embodiments, the fourth message is also used to confirm the first session and / or the first task.

[0233] In some embodiments, the fourth message may include one or more of the following:

[0234] The identification information of the first session (Session ID);

[0235] The identification information of the first task (Task ID);

[0236] Correlation ID.

[0237] It should be understood that in Method 1A, a node-level user plane connection can be established by the first network element sending the user plane address and the corresponding binding information to the access network device, and the access network device sending the RAN ID and / or binding information to the first network element. Subsequent session-level message interactions are transmitted on this node-level user plane connection.

[0238] In Mode 1A, a node-level user plane connection is established by the second network element sending second address information and / or binding information to the access network device, and the access network device sending RAN ID and / or binding information to the first network element. Subsequent session / task-level data interaction (including first data and / or second data) between the first network element and the access network device can be achieved through the second connection. This enables user plane transmission between the access network device and a specific network element, improving the communication performance between them.

[0239] For method 1B described above (the first connection is different from the second connection, and / or the first connection can be established based on the second connection), after the second connection at the node level is established, the first connection at the Task / Session level also needs to be established.

[0240] In some embodiments, referring to FIG8, for method 1B, after the second connection is established, the following steps may also be included:

[0241] S810, the second network element sends a third request message to the first network element, or in other words, the first network element receives the third request message sent by the second network element. The third request message is used to request the first network element to configure the first connection based on the second connection.

[0242] It should be noted that the third request information can also be understood as a task configuration request, which is used to request the first network element to configure the first connection corresponding to the Task / Session.

[0243] In some embodiments, the third request information may include one or more of the following:

[0244] RAN ID (Identification Information of Access Network Equipment);

[0245] The identification information of the first session (Session ID);

[0246] The identification information of the first task (Task ID);

[0247] Correlation ID.

[0248] In some embodiments, the second network element can obtain the Session ID and / or Task ID based on the service / data request information in step S602, or other service / data request information received before step S810. In this way, the second network element can send a third request to the first network element.

[0249] S820: The first network element sends the fifth message to the access network device through the second connection.

[0250] In some embodiments, the fifth message includes information related to the first connection. This information can be used to establish the first connection.

[0251] It should be noted that the information related to the first connection can also be understood as the configuration information of the first connection, or the first user plane information (UP information), or the first data plane information.

[0252] It should be understood that after the second node-level connection is established based on steps S610 to S640, the first network element can establish the first Task / Session-level connection through the second connection.

[0253] Specifically, in step S820, the first network element can send a fifth message to the access network device through the second connection.

[0254] In some embodiments, the relevant information for the first connection may include one or more of the following:

[0255] First address information of the first connection;

[0256] The identification information (Session ID) of the first session corresponding to the first connection;

[0257] The identifier information (Task ID) of the first task corresponding to the first connection;

[0258] Correlation ID corresponding to the first connection.

[0259] In some embodiments, the first address information may include one or more of the following: IP address information, port information, and fully qualified domain name (FQDN) information. This application embodiment does not limit the type of address information.

[0260] It should be noted that the first address information of the first connection is different from the second address information of the second connection.

[0261] S830, the first network element receives the seventh message sent by the access network device through the first connection. The seventh message is used to transmit service data and / or service-related signaling.

[0262] It should be understood that after the first connection corresponding to the first task and / or the first session is established, the access network device can transmit the service data and / or service-related signaling corresponding to the first task and / or the first session to the first network element through the first connection, or in other words, through the first address information.

[0263] In some embodiments, the seventh message is also used to confirm the first session and / or the first task.

[0264] In some embodiments, the seventh message may include:

[0265] The identification information of the first session (Session ID);

[0266] The identification information of the first task (Task ID);

[0267] Correlation ID;

[0268] RAN ID (Identification Information) of Access Network Equipment.

[0269] It should be noted that the seventh message can also be called a confirmation message or a feedback message, and this application embodiment does not limit it in this way.

[0270] It should be noted that the RAN ID in the seventh message is optional; that is, the RAN ID may not be included in the seventh message. It should be understood that in some scenarios, the Session ID / Task ID / Correlation ID / correlation ID can be globally unique. This means that different sessions / tasks use different Session IDs / Task IDs / Correlation IDs / correlation IDs. Therefore, even without the RAN ID, the first network element can still determine which RAN node sent the data and which Session / Task it corresponds to based solely on the Session ID / Task ID / Correlation ID / correlation ID.

[0271] It should also be noted that after receiving the seventh message, the first network element can maintain the mapping relationship between the RAN ID, Session ID / Task ID / Correlation ID, and the current first connection based on the seventh message. In other words, the first network element can bind the first connection to the first task and / or the first session, or bind the first connection to the access network device corresponding to the RAN ID.

[0272] In some embodiments, after step S820, the method provided in this application embodiment may further include step S830.

[0273] S840. The access network device sends an eighth message to the first network element through the first connection. The eighth message is used to transmit service data and / or service-related signaling.

[0274] In other words, after establishing the first connection corresponding to the first task and / or the first session, the first network element can transmit the service data and / or service-related signaling corresponding to the first task and / or the first session to the access network device associated with or bound to the first connection through the first connection.

[0275] It should be noted that the eighth message may include one or more of the following:

[0276] The identification information of the first session (Session ID);

[0277] The identification information of the first task (Task ID);

[0278] Correlation ID.

[0279] It should also be noted that steps S830 and S840 are optional steps, meaning that steps S830 and S840 can be performed or not. In Figure 8, these optional steps are indicated by dashed arrows.

[0280] It should also be noted that, based on the established node-level second connection, multiple session / task-level first connections can be established. Different first connections can be associated with different sessions / tasks.

[0281] Using method 1B above, after establishing the second connection, a Session / Task-level first connection can be configured based on the second connection. This allows for Session / Task-level data exchange (including first data and / or second data) between the first network element and the access network device via the first connection. This enables user plane transmission between the access network device and a specific network element, improving communication performance between them. Simultaneously, the node-level second connection can be isolated from the Session / Task-level first connection.

[0282] For method 2, the second network element can be directly configured with the first connection.

[0283] It should be noted that in Method 2, the first connection can be a Task / Session-level user plane connection. The first connection can correspond to the first session and / or the first task. That is to say, the second network element can be directly configured with a Task / Session-level user plane connection to directly realize Task / Session-level user plane data interaction.

[0284] In some embodiments, referring to FIG9, for method 2, the following steps may be included before performing step S510:

[0285] S910. The second network element sends a fourth request message to the first network element, or in other words, the first network element receives the fourth request message sent by the second network element. The fourth request message is used to request the first network element to configure the first connection.

[0286] It should be noted that the fourth request information can also be understood as a task configuration request, which is used to request the first network element to directly configure the first connection at the Task / Session level.

[0287] In some embodiments, the fourth request information can be understood as User Plane (UP) configuration information.

[0288] In some embodiments, the fourth request information may include one or more of the following:

[0289] RAN ID (Identification Information of Access Network Equipment);

[0290] The identification information of the first session (Session ID);

[0291] The identification information of the first task (Task ID);

[0292] Correlation ID.

[0293] In some embodiments, the second network element can obtain the Session ID and / or Task ID based on other service / data request information received before step S910. In this way, the second network element can send a fourth request message to the first network element.

[0294] S920, the first network element sends a second response message to the second network element, or in other words, the second network element receives the second response message sent by the first network element.

[0295] It should be understood that the second response information can be a response to the fourth request information. The second response information can be understood as the UP configuration response information.

[0296] In some embodiments, the second response information includes the first address information of the first connection.

[0297] It should be noted that the first address information may include one or more of the following: IP address information, port information, and fully qualified domain name (FQDN) information. This application embodiment does not limit the type of address information.

[0298] S930. The second network element sends a sixth message to the access network device, or the second network element sends a sixth message to the access network device through the third network element.

[0299] In some embodiments, the sixth message may include information related to the first connection. This information can be used to establish the first connection.

[0300] It should be noted that the information related to the first connection can also be understood as the configuration information of the first connection, or the first user plane information (UP information), or the first data plane information.

[0301] In some embodiments, the information related to the first connection may include one or more of the following:

[0302] First address information of the first connection;

[0303] The identification information (Session ID) of the first session corresponding to the first connection;

[0304] The identifier information (Task ID) of the first task corresponding to the first connection;

[0305] Correlation ID corresponding to the first connection.

[0306] In one possible implementation, the second network element can directly send the sixth message to the access network device. That is, the sixth message received by the access network device can come from the second network element.

[0307] It should be understood that if the second network element stores the ID of the access network device or the control plane interface information of the access network device, the second network element can send a sixth message to the access network device based on the ID of the access network device or the control plane interface information to establish a first connection.

[0308] In one possible implementation, the second network element can send a sixth message to the access network device through the third network element. That is, the sixth message received by the access network device can come from the third network element.

[0309] It should be noted that the third network element can be a management network element associated with the access network device. Specifically, the third network element can be a registration management network element and / or a mobility management network element. For example, the third network element can be an AMF network element in a 5G network or an MM network element in a 6G network.

[0310] Specifically, in this implementation, step S930 may include:

[0311] S930a, the second network element sends a sixth request message to the third network element. The sixth request message is used to request the third network element to send a sixth message to the access network device.

[0312] S930b, the third network element sends the sixth message to the access network equipment.

[0313] In some embodiments, the sixth request information may include one or more of the following:

[0314] First address information of the first connection;

[0315] RAN ID (Identification Information of Access Network Equipment);

[0316] The identification information of the first session (Session ID);

[0317] The identification information of the first task (Task ID);

[0318] Correlation ID.

[0319] In some embodiments, the third network element may determine the access network device to which the second connection is to be established based on the RAN ID. It should be understood that the third network element may manage or maintain multiple access network devices, and the third network element may determine the access network device to which the second connection is to be established based on the RAN ID in the sixth request information.

[0320] S940. The first network element receives the seventh message sent by the access network device through the first connection. The seventh message is used to transmit service data and / or service-related signaling.

[0321] It should be understood that after the first connection corresponding to the first task and / or the first session is established, the access network device can transmit the service data and / or service-related signaling corresponding to the first task and / or the first session to the first network element through the first connection, or in other words, through the first address information.

[0322] In some embodiments, the seventh message is also used to confirm the first session and / or the first task.

[0323] In some embodiments, the seventh message may include:

[0324] The identification information of the first session (Session ID);

[0325] The identification information of the first task (Task ID);

[0326] Correlation ID;

[0327] RAN ID (Identification Information) of Access Network Equipment.

[0328] It should be noted that the seventh message can also be called a confirmation message or a feedback message, and this application embodiment does not impose any limitations on this.

[0329] It should be noted that the RAN ID in the seventh message is optional; that is, the RAN ID may not be included in the seventh message. It should be understood that in some scenarios, the Session ID / Task ID / Correlation ID / correlation ID can be globally unique. This means that different sessions / tasks use different Session IDs / Task IDs / Correlation IDs / correlation IDs. Therefore, even without the RAN ID, the first network element can still determine which RAN node sent the data and which Session / Task it corresponds to based solely on the Session ID / Task ID / Correlation ID / correlation ID.

[0330] It should also be noted that after receiving the seventh message, the first network element can maintain the mapping relationship between the RAN ID, Session ID / Task ID / Correlation ID, and the current first connection based on the seventh message. In other words, the first network element can bind the first connection to the first task and / or the first session, or bind the first connection to the access network device corresponding to the RAN ID.

[0331] In some embodiments, after step S940, the method provided in this application embodiment may further include step S950.

[0332] S950: The access network device sends an eighth message to the first network element through the first connection. The eighth message is used to transmit service data and / or service-related signaling.

[0333] In other words, after establishing the first connection corresponding to the first task and / or the first session, the first network element can transmit the service data and / or service-related signaling corresponding to the first task and / or the first session to the access network device associated with or bound to the first connection through the first connection.

[0334] It should be noted that the eighth message may include one or more of the following:

[0335] The identification information of the first session (Session ID);

[0336] The identification information of the first task (Task ID);

[0337] Correlation ID.

[0338] It should also be noted that steps S940 and S950 are optional steps, meaning that steps S940 and S950 can be performed or not. In Figure 9, these optional steps are indicated by dashed arrows.

[0339] It should also be noted that in step S910 above, the second network element sending the fourth request information to the first network element can be triggered by the second network element itself or by an external application network element.

[0340] In some embodiments, referring to FIG9, before step S910, the following steps are further included:

[0341] S902, the second network element receives service / data request information sent by external application network elements.

[0342] It should be noted that an external application network element can be an entity that requests services or data from other network elements in the core network. For example, an external application network element can be a Consumer Network Function (Consumer NF).

[0343] It should also be noted that the service / data request information may include target information and the corresponding service requirement.

[0344] In one example, target information may include one or more of the following: a specific geographic area, a specific UE, a specific object, a specific RAN, etc.

[0345] In one example, service requirements may include one or more of the following: sensing method, sensing accuracy, latency, etc.

[0346] S904. The second network element selects the third network element and access network equipment based on the service / data request information.

[0347] It should be noted that the second network element can obtain the ID information, control plane port information, or address information of the access network device by querying NRF / AMF, etc.

[0348] It should be understood that Method 2 can directly configure the Session ID / Task ID / Correlation ID and the corresponding user plane address information to the RAN device, and the RAN device can directly send Session / Task level messages to the user plane address, thus directly realizing session-level user plane information interaction.

[0349] The methods provided in the embodiments of this application will be described in detail below in conjunction with perception application scenarios.

[0350] In sensing application scenarios, the first network element can be SF-U, the second network element can be SF-C, and the third network element can be AMF (or MM).

[0351] Example 1: Establish a node-level connection between SF-U and RAN.

[0352] Refer to Figure 10 for a schematic diagram of signaling interaction between network elements.

[0353] SF-C can request the address information (corresponding to the second address information above) of the node-level user plane connection (corresponding to the second connection in the above embodiment) from SF-U. SF-U can send the address information of the node-level user plane connection back to SF-C.

[0354] The SF-C can send the node-level user plane address information to the RAN. Specifically, the SF-C can send the node-level user plane address information directly to the RAN, or it can send the node-level user plane address information to the RAN through the AMF.

[0355] The RAN establishes a node-level user plane connection (corresponding to the second connection in the above embodiment) by having the user report confirmation information (including RAN ID and / or binding information) to the SF-U.

[0356] SF-U can bind the node-level user plane connection to the corresponding RAN ID based on the RAN ID or binding information reported by the RAN. In subsequent processes, it can directly send session / task-level awareness messages to the RAN and perform subsequent interactions.

[0357] Referring to the flowchart shown in Figure 11, Embodiment 1 may include the following steps:

[0358] 1. SF-C receives sensing request information sent by external application network elements.

[0359] It should be noted that an external application network element can be an entity that requests services or data from other network elements in the core network. For example, an external application network element can be a Consumer Network Function (Consumer NF).

[0360] It should also be noted that the perception request information may include target information and the corresponding service requirement.

[0361] In one example, target information may include one or more of the following: a specific geographic area, a specific UE, or a specific object.

[0362] In one example, service requirements may include one or more of the following: sensing method, sensing accuracy, and latency.

[0363] 2. SF-C selects between AMF and RAN based on the perception request information.

[0364] It should be noted that SF-C can obtain RAN ID or address information by querying NRF / AMF, etc.

[0365] 3a. SF-C sends UP configuration request information to SF-U (corresponding to the second request information in the above embodiment).

[0366] In some embodiments, the UP configuration request information may include the RAN ID.

[0367] In some embodiments, as an option, the UP configuration request information may also include binding information, which is used to associate with the RAN node / Connection ID.

[0368] In one example, binding information can be a RAN ID.

[0369] In one example, binding information can be a temporary identifier assigned by SF, which is referred to as binding ID in this embodiment of the application.

[0370] In one example, the binding information can be the connection ID of the user plane connection.

[0371] 3b. SF-U sends UP configuration response information back to SF-C (corresponding to the second response information in the above embodiment).

[0372] In some embodiments, the UP configuration response information may include the address information of the SF-U node-level user plane connection (corresponding to the second address information in the above embodiments).

[0373] In some embodiments, the address information may include IP address, port information, and FQDN information.

[0374] 4a. SF-C sends a request message to AMF (corresponding to the third request message in the above embodiment).

[0375] In some embodiments, the request information may include RAN ID information and address information for the node-level user plane connection (corresponding to the second address information in the above embodiments).

[0376] In some embodiments, as an option, the request information may also include binding information, which is used to associate the node-level user plane connection (corresponding to the second connection in the above embodiments) with the RAN node.

[0377] 4b. AMF sends the first message to the RAN node based on the RAN ID information.

[0378] In some embodiments, the first message may include the address information of the SF-U node-level user plane connection (i.e., the second address information of the second connection in the above embodiments).

[0379] In some embodiments, as an option, the first message may also include the corresponding binding information.

[0380] 5. SF-C can send the first message directly to the RAN based on the RAN's address information or control plane interface information.

[0381] In some embodiments, the first message may include SF-U node-level user plane address information (corresponding to the second address information in the above embodiments).

[0382] In some embodiments, as an option, the first message may also include the corresponding binding information.

[0383] It should be noted that steps 4 and 5 are two parallel methods, and only one of them needs to be performed.

[0384] 6. The RAN sends the second message to the SF-U through the node-connected user plane connection (corresponding to the second connection mentioned above).

[0385] In some embodiments, the second message may include RAN ID information and / or binding information.

[0386] In some embodiments, after receiving the second message, the SF-U maintains the mapping relationship between the RAN ID and the node-level user plane connection (the second connection in the above embodiments).

[0387] 7. SF-C sends a task configuration request message to SF-U (corresponding to the second request message in the above embodiment).

[0388] In some embodiments, the task configuration request information may include RAN ID information and Session / Task ID.

[0389] 8. SF-U sends downlink-aware messages (corresponding to the third message in the above embodiments) to the RAN through the node-level user plane connection (corresponding to the second connection in the above embodiments).

[0390] In some embodiments, the downlink-aware message may include Session ID / Task ID / Correlation ID.

[0391] 9. The RAN transmits uplink awareness messages (corresponding to the fourth message in the above embodiment) to the SF through the node-level user plane connection (corresponding to the second connection in the above embodiment).

[0392] In some embodiments, the uplink awareness message may include Session ID / Task ID / Correlation ID / Correlation ID.

[0393] 10. Subsequent perception process.

[0394] It should be noted that in subsequent processes, the SF and RAN can use the aforementioned user plane connection to interact with each other at the session / task level to obtain sensing data. For example, the SF can send downlink sensing data (corresponding to the first data in the above embodiment) to the RAN via the aforementioned user plane connection, and / or the RAN can send uplink sensing data (corresponding to the second data in the above embodiment) to the SF via the aforementioned user plane connection.

[0395] Example 2: Establish a session / task-level connection between SF-U and RAN.

[0396] Referring to the second schematic diagram of signaling interaction between network elements shown in Figure 12, SF-C can request the address information (corresponding to the first address information in the above embodiment) of the Session / Task-level user plane connection from SF-U. SF-U can send the address information of the Session / Task-level user plane connection back to SF-C.

[0397] The SF-C can send the Session / Task-level user plane address information to the RAN. Specifically, the SF-C can send this information directly to the RAN, or it can send it through the AMF. The RAN establishes a Session / Task-level user plane connection (corresponding to the first connection in the previous embodiment) using user plane confirmation information (including Session ID / Task ID / Correlation ID / Correlation ID, RAN ID). The RAN then directly reports the Session / Task data to the SF-U based on the aforementioned information.

[0398] Referring to the flowchart shown in Figure 13, Embodiment 2 may include the following steps:

[0399] 1. SF-C receives sensing request information sent by external application network elements.

[0400] It should be noted that an external application network element can be an entity that requests services or data from other network elements in the core network. For example, an external application network element can be a Consumer Network Function (Consumer NF).

[0401] It should also be noted that the perception request information may include target information and the corresponding service requirement.

[0402] In one example, target information may include one or more of the following: a specific geographic area, a specific UE, or a specific object.

[0403] In one example, service requirements may include one or more of the following: sensing method, sensing accuracy, and latency.

[0404] 2. SF-C selects between AMF and RAN based on the perception request information.

[0405] It should be noted that SF-C can obtain RAN ID or address information by querying NRF / AMF, etc.

[0406] 3a. SF-C sends UP configuration request information to SF-U (corresponding to the fourth request information in the above embodiment).

[0407] In some embodiments, the UP configuration request information may include RAN ID, Session ID / Task ID / Correlation ID / Correlation ID.

[0408] 3b. SF-U sends UP configuration response information back to SF-C (corresponding to the second response information in the above embodiment).

[0409] In some embodiments, the UP configuration response information may include the address information of the SF-U Session / Task level user plane connection (corresponding to the first address information in the above embodiments).

[0410] In some embodiments, the address information may include IP address, port information, and FQDN information.

[0411] 4a. SF-C sends a request message to AMF (corresponding to the sixth request message in the above embodiment).

[0412] In some embodiments, the request information may include:

[0413] 1) RAN ID information;

[0414] 2) Address information of Session / Task level user plane connections (corresponding to the first address information in the above embodiments);

[0415] 3)Session ID / Task ID / Correlation ID / Correlation ID.

[0416] 4b. AMF sends the sixth message to the RAN node based on the RAN ID information.

[0417] In some embodiments, the sixth message may include: the address information of the SF-U Session / Task level user plane connection (i.e., the first address information in the above embodiments), and the Session ID / Task ID / Correlation ID / Correlation ID.

[0418] 5. SF-C can send the sixth message directly to the RAN based on the RAN's address information or control plane interface information.

[0419] In some embodiments, the sixth message may include: the address information of the SF-U Session / Task level user plane connection (i.e., the first address information in the above embodiments), and the Session ID / Task ID / Correlation ID / Correlation ID.

[0420] It should be noted that steps 4 and 5 are two parallel methods, and only one of them needs to be performed.

[0421] The 6RAN transmits uplink awareness messages (corresponding to the seventh message in the above embodiment) to the SF-U through the Session / Task user plane connection (corresponding to the first connection in the above embodiment).

[0422] In some embodiments, the uplink awareness message may include the RAN ID, as well as the Session ID / Task ID / Correlation ID / Correlation ID.

[0423] In some embodiments, after receiving the information, the SF maintains the mapping relationship between the RAN ID, Session / Task ID, and the current sensing message.

[0424] 7. SF-U sends downlink-aware messages (corresponding to the eighth message in the above embodiments) to the RAN through a Session / Task-level user plane connection (corresponding to the first connection in the above embodiments).

[0425] In some embodiments, the downlink-aware message may include Session ID / Task ID / Correlation ID / Correlation ID.

[0426] In some embodiments, the downlink-aware message may also include the RAN ID as an optional component.

[0427] 8. Subsequent sensing process.

[0428] It should be noted that in subsequent processes, the SF and RAN can exchange session / task-level sensing data through the aforementioned user plane connection. For example, the SF can send downlink sensing data (corresponding to the first data in the above embodiment) to the RAN through the aforementioned user plane connection, and / or the RAN can send uplink sensing data (corresponding to the second data in the above embodiment) to the SF through the aforementioned user plane connection.

[0429] In Example 3, the SF establishes a node-level user plane connection with the RAN (corresponding to the second connection in the above example), and then determines the user plane connection for Session / Task message transmission (corresponding to the first connection in the above example) through the message interaction of the user plane.

[0430] Refer to Figure 14 for the schematic diagram of signaling interaction between network elements.

[0431] SF-C can request the address information (corresponding to the second address information above) of the node-level user plane connection (corresponding to the second connection in the above embodiment) from SF-U. SF-U can send the address information of the node-level user plane connection back to SF-C.

[0432] Furthermore, the SF-C can send the node-level user plane address information to the RAN. Specifically, the SF-C can send the node-level user plane address information directly to the RAN, or it can send the node-level user plane address information to the RAN through the AMF.

[0433] The RAN establishes a node-level user plane connection (corresponding to the second connection in the above embodiment) by having the user plane report confirmation information (including RAN ID and / or binding information) to the SF-U. The SF-U can bind the node-level user plane connection to the corresponding RAN ID based on the RAN ID or binding information reported by the RAN node.

[0434] In subsequent data interaction, SF-U and RAN can establish a user plane connection at the Session / Task granularity (corresponding to the first connection in the above embodiment), or a per Session / Task user plane connection, and realize data interaction through this Session / Task granular user plane connection.

[0435] Referring to the flowchart shown in Figure 15, Embodiment 3 may include the following steps:

[0436] Steps 1-6 are the same as in Example 1, and will not be repeated here for the sake of simplicity.

[0437] 7. SF-C sends a task configuration request message to SF-U (corresponding to the third request message in the above embodiment).

[0438] In some embodiments, the task configuration request information may include RAN ID information and Session / Task ID.

[0439] 8. SF-U sends the fifth message to the RAN through the node-level user plane connection (corresponding to the second connection in the above embodiment).

[0440] In some embodiments, the fifth message may include user plane address information at the Session / Task granularity (corresponding to the first address information in the above embodiments). This address information is different from the address information of the previous node-level user plane connection.

[0441] In some embodiments, the fifth message may also include the Session ID / Task ID / Correlation ID / Correlation ID of the current perception task.

[0442] 9. The RAN transmits uplink awareness messages (corresponding to the seventh message in the above embodiments) to the SF-U through a user plane connection at the Session / Task granularity (corresponding to the first connection in the above embodiments). That is, the uplink awareness messages are transmitted through address information at the Session / Task granularity (corresponding to the first address information in the above embodiments).

[0443] In some embodiments, the uplink awareness message may include Session ID / Task ID / Correlation ID / Correlation ID.

[0444] In some embodiments, after receiving the information, the SF maintains the mapping relationship between the RAN ID and the Session ID / Task ID / Correlation ID / Correlation ID and the current sensing message.

[0445] 10. SF-U sends downlink-aware messages (corresponding to the eighth message in the above embodiments) to the RAN through a user plane connection at the Session / Task granularity (corresponding to the first connection in the above embodiments). That is, downlink-aware messages are transmitted through address information at the Session / Task granularity (corresponding to the first address information in the above embodiments).

[0446] In some embodiments, the downlink-aware message may include Session ID / Task ID / Correlation ID / Correlation ID.

[0447] 11. Subsequent perception process.

[0448] It should be noted that in subsequent processes, the SF and RAN can interact and sense data through the user plane connection at the Session / Task granularity described above. For example, the SF can send downlink sense data (corresponding to the first data in the above embodiment) to the RAN through the user plane connection described above, and / or the RAN can send uplink sense data (corresponding to the second data in the above embodiment) to the SF through the user plane connection described above.

[0449] In the above embodiments, Embodiment 1 establishes a device-level user plane connection by sending the user plane address and corresponding binding information to the RAN node via SF-C, and the RAN node then sends the RAN ID and / or binding information to SF-U. Subsequent session-level message interactions are transmitted on this node-level connection. Embodiment 2 directly configures the Session ID / Task ID / Correlation ID and corresponding user plane address information to the RAN node, allowing the RAN node to directly send Session / Task-level messages to this user plane address, thus directly achieving session-level user plane information interaction. Embodiment 3, based on the established device-level user plane connection, configures a Session / Task-level user plane address on this connection, thereby enabling the transmission of Session / Task-level messages on other user plane connections and achieving user plane connection isolation.

[0450] In summary, this invention achieves the effect of establishing a user plane connection and transmitting user plane data between the SF-C configured RAN node and the SF-U through three different embodiments.

[0451] One embodiment of this application provides a data transmission apparatus, which can be applied to the first network element provided in the above embodiment. As shown in FIG16, the data transmission apparatus 1600 provided in this embodiment may include:

[0452] The first communication unit 1610 is configured to send first data to the access network device based on the first connection; and / or to receive second data sent by the access network device based on the first connection.

[0453] In some embodiments, the first connection is associated with the second connection, where the second connection corresponds to the access network device and / or the first network element.

[0454] In some embodiments, the first communication unit 1610 is further configured to receive a first request message sent by a second network element, the first request message being used to request the first network element to configure the second connection.

[0455] In some embodiments, the first request information includes one or more of the following:

[0456] The identification information of the access network device;

[0457] The first identification information is used to identify the association between the second connection and the access network device.

[0458] In some embodiments, the first communication unit 1610 is further configured to send first response information corresponding to the first request information to the second network element, wherein the first response information includes second address information of the second connection.

[0459] In some embodiments, the first communication unit 1610 is further configured to receive a second message sent by the access network device through the second connection; the second message is used by the first network element to determine the binding relationship of the second connection.

[0460] In some embodiments, the second message includes one or more of the following:

[0461] Identification information of access network equipment;

[0462] The first identification information is used to identify the association between the second connection and the access network device.

[0463] In some embodiments, the first connection and the second connection are the same user plane connection.

[0464] In some embodiments, the first communication unit 1610 is further configured to receive a second request message sent by a second network element, the second request message being used to request the first network element to configure a first task and / or a first session.

[0465] In some embodiments, the second request information includes one or more of the following:

[0466] The identification information of the access network device;

[0467] The identification information of the first session;

[0468] The identification information of the first task;

[0469] Associated identification information.

[0470] In some embodiments, the first communication unit 1610 is further configured to send a third message to the access network device via the second connection, the third message being used to configure the first task and / or the first session.

[0471] In some embodiments, the first communication unit 1610 is further configured to receive a fourth message via the second connection, the fourth message being used for transmitting service data and / or service-related signaling.

[0472] In some embodiments, the fourth message is also used to confirm the first session and / or the first task.

[0473] In some embodiments, the third message, and / or the fourth message, includes one or more of the following:

[0474] The identification information of the first session;

[0475] The identification information of the first task;

[0476] Associated identification information.

[0477] In some embodiments, the first connection is established based on the second connection; and / or, the first address information of the first connection is different from the second address information of the second connection.

[0478] In some embodiments, the first communication unit 1610 is further configured to receive third request information sent by the second network element, the third request information being used to request the first network element to configure the first connection based on the second connection.

[0479] In some embodiments, the third request information includes one or more of the following:

[0480] The identification information of the access network device;

[0481] The identifier information of the first session corresponding to the first connection;

[0482] The identification information of the first task corresponding to the first connection;

[0483] The associated identification information corresponding to the first connection.

[0484] In some embodiments, the first communication unit 1610 is further configured to send a fifth message to the access network device via the second connection, the fifth message including relevant information of the first connection.

[0485] In some embodiments, the information related to the first connection includes one or more of the following:

[0486] The first address information of the first connection;

[0487] The identification information of the first task corresponding to the first connection;

[0488] The identifier information of the first session corresponding to the first connection;

[0489] The associated identification information corresponding to the first connection.

[0490] In some embodiments, the first communication unit 1610 is further configured to receive a fourth request message sent by the second network element, the fourth request message being used to request the first network element to configure the first connection.

[0491] In some embodiments, the fourth request information includes one or more of the following:

[0492] The identification information of the access network device;

[0493] The identifier information of the first session corresponding to the first connection;

[0494] The identification information of the first task corresponding to the first connection;

[0495] The associated identification information corresponding to the first connection.

[0496] In some embodiments, the first communication unit 1610 is further configured to send second response information to the second network element, the second response information including the first address information of the first connection.

[0497] In some embodiments, the first communication unit 1610 is further configured to receive a seventh message sent by the access network device through the first connection, and / or send an eighth message to the access network device through the first connection;

[0498] The seventh message and / or the eighth message includes one or more of the following:

[0499] The identification information of the access network device;

[0500] The identifier information of the first session corresponding to the first connection;

[0501] The identification information of the first task corresponding to the first connection;

[0502] The associated identification information corresponding to the first connection.

[0503] In some embodiments, the first connection corresponds to a first session or a first task;

[0504] Wherein, the first session is any one of multiple sessions between the access network device and the first network element, and / or, the first task is any one of multiple tasks between the access network device and the first network element.

[0505] In some embodiments, the first network element is one or more of the following: the user plane portion of a sensing network element, the user plane portion of a positioning management network element, and a data collection network element;

[0506] The second network element is one or more of the following: the control plane portion of a sensing network element, the control plane portion of a positioning-related network element, and a data management network element.

[0507] One embodiment of this application provides a data transmission apparatus, which can be applied to the second network element provided in the above embodiment. As shown in FIG17, the data transmission apparatus 1700 provided in this embodiment may include:

[0508] The second communication unit 1710 is configured to send a first request message to the first network element, the first request message being used to request the first network element to configure a second connection; the first connection between the first network element and the access network device is related to the second connection.

[0509] or,

[0510] The second communication unit 1710 is configured to send a fourth request message to the first network element, the fourth request message being used to request the first network element to configure a first connection;

[0511] The first connection is used to transmit first data and / or second data, wherein the first data is data sent by the first network element to the access network device, and the second data is data sent by the access network device to the first network element.

[0512] In some embodiments, the second connection corresponds to the access network device and / or the first network element.

[0513] In some embodiments, the first request information includes one or more of the following:

[0514] The identification information of the access network device;

[0515] The first identification information is used to identify the association between the second connection and the access network device.

[0516] In some embodiments, the second communication unit 1710 is further configured to receive first response information corresponding to the first request information sent by the first network element, wherein the first response information includes second address information of the second connection.

[0517] In some embodiments, the second communication unit 1710 is further configured to send a first message to the access network device, the first message including information related to the second connection.

[0518] In some embodiments, the second communication unit 1710 is further configured to send a fifth request message to the third network element;

[0519] The third network element is the management network element associated with the access network device;

[0520] The fifth request information is used to request the third network element to send a first message to the access network device, the first message including relevant information about the second connection.

[0521] In some embodiments, the fifth request information includes one or more of the following:

[0522] The identification information of the access network device;

[0523] The second address information of the second connection;

[0524] First identification information, which is used to identify the association between the second connection and the access network device;

[0525] The identification information of the access network device is used by the third network element to identify the access network device.

[0526] In some embodiments, the relevant information of the second connection includes one or more of the following:

[0527] The second address information of the second connection;

[0528] The first identification information is used to identify the association between the second connection and the access network device.

[0529] In some embodiments, the first connection being related to the second connection includes: the first connection and the second connection being the same user plane connection.

[0530] In some embodiments, the first connection being related to the second connection includes: the first connection being established based on the second connection; and / or, the first address information of the first connection being different from the second address information of the second connection.

[0531] In some embodiments, the fourth request information includes one or more of the following:

[0532] The identification information of the access network device;

[0533] The identifier information of the first session corresponding to the first connection;

[0534] The identification information of the first task corresponding to the first connection;

[0535] The associated identification information corresponding to the first connection.

[0536] In some embodiments, the second communication unit 1710 is further configured to receive second response information sent by the first network element, the second response information including first address information of the first connection.

[0537] In some embodiments, the second communication unit 1710 is further configured to send a sixth message to the access network device, the sixth message including information related to the first connection.

[0538] In some embodiments, the second communication unit 1710 is further configured to send a sixth request message to the third network element;

[0539] The third network element is the management network element associated with the access network device;

[0540] The sixth request information is used to request the third network element to send a sixth message to the access network device; the sixth message includes relevant information about the first connection.

[0541] In some embodiments, the sixth request information includes one or more of the following:

[0542] The identification information of the access network device;

[0543] The first address information of the first connection;

[0544] The identification information of the first task corresponding to the first connection;

[0545] The identifier information of the first session corresponding to the first connection;

[0546] The associated identification information corresponding to the first connection.

[0547] In some embodiments, the information related to the first connection includes one or more of the following:

[0548] The identification information of the access network device;

[0549] The identification information of the first task corresponding to the first connection;

[0550] The identifier information of the first session corresponding to the first connection;

[0551] The associated identification information corresponding to the first connection.

[0552] In some embodiments, the first connection corresponds to a first session or a first task;

[0553] Wherein, the first session is any one of multiple sessions between the access network device and the first network element, and / or, the first task is any one of multiple tasks between the access network device and the first network element.

[0554] In some embodiments, the first network element is one or more of the following: the user plane portion of a sensing network element, the user plane portion of a positioning management network element, and a data collection network element;

[0555] The second network element is one or more of the following: the control plane portion of a sensing network element, the control plane portion of a positioning-related network element, and a data management network element;

[0556] The third network element registration management network element, and / or the mobility management network element.

[0557] One embodiment of this application provides a data transmission apparatus, which can be applied to the access network equipment provided in the above embodiments. As shown in FIG18, the data transmission apparatus 1800 provided in this application embodiment may include:

[0558] The third communication unit 1810 is configured to receive first data sent by the first network element based on the first connection; and / or send second data to the first network element based on the first connection.

[0559] In some embodiments, the first connection is associated with the second connection; wherein the second connection corresponds to the access network device and / or the first network element.

[0560] In some embodiments, the third communication unit 1810 is further configured to receive a first message, the first message including information related to the second connection.

[0561] In some embodiments, the relevant information of the second connection includes one or more of the following:

[0562] The second address information of the second connection;

[0563] The first identification information is used to identify the association between the second connection and the access network device.

[0564] In some embodiments, the first message originates from the second network element;

[0565] or,

[0566] The first message comes from a third network element, which is the management network element associated with the access network device;

[0567] The third network element is used to receive the fifth request information sent by the second network element, and the fifth request information is used to request the third network element to send the first message to the access network device.

[0568] In some embodiments, the third communication unit 1810 is further configured to send a second message to the first network element through the second connection; the second message is used by the first network element to determine the binding relationship of the second connection.

[0569] In some embodiments, the second message includes one or more of the following:

[0570] The identification information of the access network device;

[0571] The first identification information is used to identify the association between the second connection and the access network device.

[0572] In some embodiments, the first connection and the second connection are the same user plane connection.

[0573] In some embodiments, the third communication unit 1810 is further configured to receive a third message through the second connection, the third message being used to configure a first task and / or a first session corresponding to the second connection.

[0574] In some embodiments, the third communication unit 1810 is further configured to send a fourth message through the second connection, the fourth message being used to confirm the first session and / or the first task associated with the second connection.

[0575] In some embodiments, the third message, and / or the fourth message, includes one or more of the following:

[0576] The identification information of the first session;

[0577] The identification information of the first task;

[0578] Associated identification information.

[0579] In some embodiments, the first connection is established based on the second connection, and / or the first address information of the first connection is different from the second address information of the second connection.

[0580] In some embodiments, the third communication unit 1810 is further configured to receive a fifth message via the second connection, the fifth message including relevant information about the first connection.

[0581] In some embodiments, the third communication unit 1810 is further configured to receive a sixth message, the sixth message including information related to the first connection.

[0582] In some embodiments, the sixth message originates from the second network element;

[0583] or,

[0584] The sixth message comes from a third network element, which is the management network element associated with the access network device;

[0585] The third network element is used to receive the sixth request information sent by the second network element, and the sixth request information is used to request the third network element to send the sixth message to the access network device.

[0586] In some embodiments, the relevant information for the first connection includes one or more of the following:

[0587] The first address information of the first connection;

[0588] Identification information for the first session;

[0589] The identification information for the first task;

[0590] Associated identification information.

[0591] In some embodiments, the third communication unit 1810 is further configured to send a seventh message to the first network element through the first connection, and / or receive an eighth message sent by the first network element through the first connection.

[0592] The seventh message and / or the eighth message includes one or more of the following:

[0593] The identification information of the access network device;

[0594] The identifier information of the first session corresponding to the first connection;

[0595] The identification information of the first task corresponding to the first connection;

[0596] The associated identification information corresponding to the first connection.

[0597] In some embodiments, the first connection corresponds to a first session or a first task;

[0598] Wherein, the first session is any one of multiple sessions between the access network device and the first network element, and / or, the first task is any one of multiple tasks between the access network device and the first network element.

[0599] In some embodiments, the first network element is one or more of the following: the user plane portion of a sensing network element, the user plane portion of a positioning management network element, and a data collection network element;

[0600] The second network element is one or more of the following: the control plane portion of a sensing network element, the control plane portion of a positioning-related network element, and a data management network element;

[0601] The third network element registration management network element, and / or the mobility management network element.

[0602] One embodiment of this application provides a data transmission apparatus that can be applied to the third network element provided in the above embodiments. As shown in FIG19, the data transmission apparatus 1900 provided in this application embodiment may include:

[0603] The fourth communication unit 1910 is configured to receive a fifth request message or a sixth request message;

[0604] The fifth request information is used to request the second network element to send a first message to the access network device, the first message including relevant information about the second connection;

[0605] The sixth request information is used to request the second network element to send a sixth message to the access network device. The sixth message includes information related to the first connection between the first network element and the access network element.

[0606] In some embodiments, the second connection corresponds to the access network device and / or the first network element, and the first connection is related to the second connection.

[0607] In some embodiments, the first connection corresponds to a first session or a first task;

[0608] Wherein, the first session is any one of multiple sessions between the access network device and the first network element, and / or, the first task is any one of multiple tasks between the access network device and the first network element.

[0609] In some embodiments, the fifth request information includes one or more of the following:

[0610] The identification information of the access network device;

[0611] The second address information of the second connection;

[0612] First identification information, which is used to identify the association between the second connection and the access network device;

[0613] The identification information of the access network device is used by the third network element to identify the access network device.

[0614] In some embodiments, the sixth request information includes one or more of the following:

[0615] The identification information of the access network device;

[0616] The first address information of the first connection;

[0617] The identifier information of the first session corresponding to the first connection;

[0618] The identification information of the first task corresponding to the first connection;

[0619] The associated identification information corresponding to the first connection;

[0620] The identification information of the access network device is used by the third network element to identify the access network device.

[0621] In some embodiments, the relevant information of the second connection includes one or more of the following:

[0622] The second address information of the second connection;

[0623] The first identification information is used to identify the association between the second connection and the access network device.

[0624] In some embodiments, the relevant information for the first connection includes one or more of the following:

[0625] The first address information of the first connection;

[0626] The identifier information of the first session corresponding to the first connection;

[0627] The identification information of the first task corresponding to the first connection;

[0628] The associated identification information corresponding to the first connection.

[0629] Those skilled in the art should understand that the description of the data transmission device in the embodiments of this application can be understood with reference to the description of the data transmission method in the embodiments of this application.

[0630] Figure 20 is a schematic structural diagram of a communication device provided in an embodiment of this application. This communication device can be a first network element, an access network device, a second network element, or a third network element. The communication device 2000 shown in Figure 20 includes a processor 2000, which can call and run computer programs from memory to implement the methods in the embodiments of this application.

[0631] Optionally, as shown in FIG20, the communication device 2000 may further include a memory 2020. The processor 2010 may retrieve and run computer programs from the memory 2020 to implement the methods in the embodiments of this application.

[0632] The memory 2020 can be a separate device independent of the processor 2010, or it can be integrated into the processor 2010.

[0633] Optionally, as shown in FIG20, the communication device 2000 may further include a transceiver 2030, and the processor 2010 may control the transceiver 2030 to communicate with other devices. Specifically, it may send information or data to other devices or receive information or data sent by other devices.

[0634] The transceiver 2030 may include a transmitter and a receiver. The transceiver 2030 may further include an antenna, and the number of antennas may be one or more.

[0635] Optionally, the communication device 2000 may specifically be the first network element in the embodiments of this application, and the communication device 2000 may implement the corresponding processes implemented by the first network element in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0636] Optionally, the communication device 2000 may specifically be the second network element in the embodiments of this application, and the communication device 2000 may implement the corresponding processes implemented by the second network element in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0637] Optionally, the communication device 2000 may specifically be an access network device in the embodiments of this application, and the communication device 2000 may implement the corresponding processes implemented by the access network device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0638] Optionally, the communication device 2000 may specifically be a third network element in the embodiments of this application, and the communication device 2000 may implement the corresponding processes implemented by the third network element in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0639] Figure 21 is a schematic structural diagram of a chip according to an embodiment of this application. The chip 2100 shown in Figure 21 includes a processor 2110, which can call and run computer programs from memory to implement the methods in the embodiments of this application.

[0640] Optionally, as shown in FIG21, chip 2100 may further include memory 2020. Processor 2110 can call and run computer programs from memory 2120 to implement the methods in the embodiments of this application.

[0641] The memory 2120 can be a separate device independent of the processor 2110, or it can be integrated into the processor 2110.

[0642] Optionally, the chip 2100 may also include an input interface 2130. The processor 2110 can control the input interface 2130 to communicate with other devices or chips; specifically, it can acquire information or data sent by other devices or chips.

[0643] Optionally, the chip 2100 may also include an output interface 2140. The processor 2110 can control the output interface 2140 to communicate with other devices or chips, specifically, to output information or data to other devices or chips.

[0644] Optionally, the chip can be applied to the first network element in the embodiments of this application, and the chip can implement the corresponding processes implemented by the first network element in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0645] Optionally, the chip can be applied to the second network element in the embodiments of this application, and the chip can implement the corresponding processes implemented by the second network element in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0646] Optionally, the chip can be applied to the access network device in the embodiments of this application, and the chip can implement the corresponding processes implemented by the access network device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0647] Optionally, the chip can be applied to the third network element in the embodiments of this application, and the chip can implement the corresponding processes implemented by the third network element in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0648] It should be understood that the chip mentioned in the embodiments of this application may also be referred to as a system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.

[0649] This application also provides a computer storage medium that stores one or more programs, which can be executed by one or more processors to implement the methods in this application.

[0650] Figure 22 is a schematic block diagram of a communication system provided in an embodiment of this application. As shown in Figure 22, the communication system 2200 includes a first network element 2210, a second network element 2220, an access network device 2230, and a third network element 2240.

[0651] The first network element 2210 can be used to implement the corresponding functions implemented by the first network element in the above method, and the first network element 2210 can be used to implement the corresponding functions implemented by the first network element in the above method. For the sake of brevity, it will not be described in detail here.

[0652] The second network element 2220 can be used to implement the corresponding functions implemented by the second network element in the above method, and the second network element 2220 can be used to implement the corresponding functions implemented by the second network element in the above method. For the sake of brevity, it will not be described in detail here.

[0653] The access network device 2230 can be used to implement the corresponding functions implemented by the access network device in the above method, and the access network device 2230 can be used to implement the corresponding functions implemented by the access network device in the above method. For the sake of brevity, it will not be described in detail here.

[0654] The third network element 2240 can be used to implement the corresponding functions implemented by the second network element in the above method, and the third network element 2240 can be used to implement the corresponding functions implemented by the second network element in the above method. For the sake of brevity, it will not be described in detail here.

[0655] It should be noted that the functional units in the above embodiments can be integrated into one processing module, or each unit can exist physically separately, or two or more units can be integrated into one module. The integrated module can be implemented in hardware or as a software functional module.

[0656] It should be noted that the functional units in the above embodiments can be integrated into one processing module, or each unit can exist physically separately, or two or more units can be integrated into one module. The integrated module can be implemented in hardware or as a software functional module.

[0657] If an integrated module is implemented as a software functional module and is not sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this embodiment, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) or processor to execute all or part of the steps of the method of this embodiment. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0658] In the embodiments provided in this application, the processor can be at least one of the following: Application Specific Integrated Circuit (ASIC), Digital Signal Processor (DSP), Digital Signal Processing Device (DSPD), Programmable Logic Device (PLD), Field Programmable Gate Array (FPGA), Central Processing Unit (CPU), and controller. It is understood that for different devices, the electronic device used to implement the above processor function can also be other types, and the embodiments in this application do not specifically limit it.

[0659] In practical applications, the memory can be volatile memory, such as RAM; or non-volatile memory, such as ROM, flash memory, hard disk drive (HDD) or solid-state drive (SSD); or a combination of the above types of memory, and provide instructions and data to the processor 1101.

[0660] This application also provides a computer storage medium, specifically a computer-readable storage medium. It stores computer instructions, which, when executed by a processor, implement any step of the data transmission method described in this application when the computer storage medium is located in a RAN or network element.

[0661] This application also provides a computer program product, including computer program instructions.

[0662] When the computer program instructions are run on the computer, the computer executes the corresponding processes implemented by the RAN and network elements in the various methods of the embodiments of this application. For the sake of brevity, these will not be described in detail here.

[0663] The aforementioned computer storage media / memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic random access memory (FRAM), flash memory, magnetic surface memory, optical disc, or compact disc read-only memory (CD-ROM), etc.; or it can be various terminals that include one or any combination of the above-mentioned memories, such as mobile phones, computers, tablet devices, personal digital assistants, etc.

[0664] It should be understood that the terms "an embodiment," "an embodiment," "an embodiment of this application," "the foregoing embodiments," or "some embodiments" mentioned throughout the specification mean that the target features, structures, or characteristics related to the embodiment are included in at least one embodiment of this application. Therefore, the phrases "an embodiment," "an embodiment," "an embodiment of this application," "the foregoing embodiments," or "some embodiments" appearing throughout the specification do not necessarily refer to the same embodiment. Furthermore, these target features, structures, or characteristics can be combined in any suitable manner in one or more embodiments. It should be understood that in the various embodiments of this application, the sequence numbers of the above-described processes do not imply a sequential order of execution; the execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application. The sequence numbers of the above-described embodiments of this application are merely descriptive and do not represent the superiority or inferiority of the embodiments.

[0665] Unless otherwise specified, any step in the embodiments of this application performed by the detection device may be executed by the processor of the detection device. Unless otherwise specified, the embodiments of this application do not limit the order in which the detection device performs the following steps. Furthermore, the methods used to process data in different embodiments may be the same or different methods. It should also be noted that any step in the embodiments of this application can be executed independently by the detection device; that is, when the detection device performs any step in the above embodiments, it may not depend on the execution of other steps.

[0666] In the several embodiments provided in this application, it should be understood that the disclosed devices and methods can be implemented in other ways. The device embodiments described above are merely illustrative. For example, the division of units is only a logical functional division, and in actual implementation, there may be other division methods, such as: multiple units or components can be combined, or integrated into another system, or some features can be ignored or not executed. In addition, the coupling, direct coupling, or communication connection between the various components shown or discussed can be through some interfaces, and the indirect coupling or communication connection between devices or units can be electrical, mechanical, or other forms.

[0667] The units described above as separate components may or may not be physically separate. The components shown as units may or may not be physical units. They may be located in one place or distributed across multiple network units. Some or all of the units may be selected to achieve the purpose of this embodiment according to actual needs.

[0668] In addition, each functional unit in the various embodiments of this application can be integrated into one processing unit, or each unit can be a separate unit, or two or more units can be integrated into one unit; the integrated unit can be implemented in hardware or in the form of hardware plus software functional units.

[0669] The methods disclosed in the several method embodiments provided in this application can be arbitrarily combined without conflict to obtain new method embodiments.

[0670] The features disclosed in the several product embodiments provided in this application can be arbitrarily combined without conflict to obtain new product embodiments.

[0671] The features disclosed in the several method or device embodiments provided in this application can be arbitrarily combined without conflict to obtain new method or device embodiments.

[0672] Those skilled in the art will understand that all or part of the steps of the above method embodiments can be implemented by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When the program is executed, it performs the steps of the above method embodiments. The aforementioned storage medium includes various media that can store program code, such as mobile storage devices, read-only memory (ROM), magnetic disks, or optical disks.

[0673] Alternatively, if the integrated units described above are implemented as software functional modules and sold or used as independent products, they can also be stored in a computer-readable storage medium. Based on this understanding, the technical solutions of the embodiments of this application, or the parts that contribute to related technologies, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, testing equipment, or network device, etc.) to execute all or part of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as mobile storage devices, ROMs, magnetic disks, or optical disks.

[0674] In the embodiments of this application, descriptions of the same steps and content in different embodiments can be referred to each other. In the embodiments of this application, the term "and" does not affect the order of steps.

[0675] The above description is merely an embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A data transmission method, the method comprising: The first network element sends the first data to the access network device based on the first connection; And / or, the first network element receives second data sent by the access network device based on the first connection.

2. The method according to claim 1, wherein, The first connection is related to the second connection, and the second connection corresponds to the access network device and / or the first network element.

3. The method of claim 2, wherein, The method further includes: The first network element receives a first request message sent by the second network element, the first request message being used to request the first network element to configure the second connection.

4. The method of claim 5, wherein, The first request information includes one or more of the following: The identification information of the access network device; The first identification information is used to identify the association between the second connection and the access network device.

5. The method of claim 3 or 4, wherein, The method further includes: The first network element sends a first response message corresponding to the first request message to the second network element. The first response message includes the second address information of the second connection.

6. The method of claim 5, wherein, The method further includes: The first network element receives a second message sent by the access network device through the second connection; the second message is used by the first network element to determine the binding relationship of the second connection.

7. The method of claim 6, wherein, The second message includes one or more of the following: Identification information of access network equipment; The first identification information is used to identify the association between the second connection and the access network device.

8. The method according to any one of claims 2-7, wherein, The first connection and the second connection are the same user plane connection.

9. The method of claim 8, wherein, The method further includes: The first network element receives a second request message sent by the second network element. The second request message is used to request the first network element to configure a first task and / or a first session.

10. The method of claim 9, wherein, The second request information includes one or more of the following: The identification information of the access network device; the identification information of the first session; the identification information of the first task; and the associated identification information.

11. The method of claim 9 or 10, wherein, The method further includes: The first network element sends a third message to the access network device through the second connection. The third message is used to configure the first task and / or the first session.

12. The method of claim 11, wherein, The method further includes: The first network element receives a fourth message through the second connection. The fourth message is used for transmitting service data and / or service-related signaling.

13. The method according to claim 12, wherein, The fourth message is also used to confirm the first session and / or the first task.

14. The method of any one of claims 11-13, wherein, The third message, and / or the fourth message, includes one or more of the following: identification information of the first session; identification information of the first task; and association identification information.

15. The method according to any one of claims 2-7, wherein, The first connection is established based on the second connection; and / or, the first address information of the first connection is different from the second address information of the second connection.

16. The method of claim 15, wherein, The method further includes: The first network element receives a third request message sent by the second network element, the third request message being used to request the first network element to configure the first connection based on the second connection.

17. The method of claim 16, wherein, The third request information includes one or more of the following: The identification information of the access network device; The identifier information of the first session corresponding to the first connection; The identification information of the first task corresponding to the first connection; The associated identification information corresponding to the first connection.

18. The method of claim 16 or 17, wherein, The method further includes: The first network element sends a fifth message to the access network device through the second connection, and the fifth message includes relevant information of the first connection.

19. The method of claim 18, wherein, The relevant information for the first connection includes one or more of the following: The first address information of the first connection; The identification information of the first task corresponding to the first connection; The identifier information of the first session corresponding to the first connection; The association identifier information of the first session corresponding to the first connection.

20. The method of claim 1, wherein, The method further includes: The first network element receives a fourth request message sent by the second network element, the fourth request message being used to request the first network element to configure the first connection.

21. The method of claim 20, wherein, The fourth request information includes one or more of the following: The identification information of the access network device; The identifier information of the first session corresponding to the first connection; The identification information of the first task corresponding to the first connection; The associated identification information corresponding to the first connection.

22. The method of claim 20 or 21, wherein, The method further includes: The first network element sends a second response message to the second network element, the second response message including the first address information of the first connection.

23. The method of any one of claims 18, 19, 22, wherein, The method further includes: The first network element receives the seventh message sent by the access network device through the first connection. And / or, The first network element sends an eighth message to the access network device through the first connection; The seventh message and / or the eighth message includes one or more of the following: The identification information of the access network device; The identifier information of the first session corresponding to the first connection; The identification information of the first task corresponding to the first connection; The associated identification information corresponding to the first connection.

24. The method according to any one of claims 15-23, wherein, The first connection corresponds to the first session or the first task; Wherein, the first session is any one of multiple sessions between the access network device and the first network element, and / or, the first task is any one of multiple tasks between the access network device and the first network element.

25. The method according to any one of claims 1-24, wherein, The first network element is one or more of the following: the user plane portion of a sensing network element, the user plane portion of a positioning and management network element, and a data collection network element; The second network element is one or more of the following: the control plane portion of a sensing network element, the control plane portion of a positioning-related network element, and a data management network element.

26. A data transmission method, the method comprising: The second network element sends a first request message to the first network element, the first request message being used to request the first network element to configure a second connection; The first connection between the first network element and the access network device is related to the second connection; or, The second network element sends a fourth request message to the first network element, the fourth request message being used to request the first network element to configure a first connection; The first connection is used to transmit first data and / or second data, wherein the first data is data sent by the first network element to the access network device, and the second data is data sent by the access network device to the first network element.

27. The method according to claim 26, wherein, The second connection corresponds to the access network device and / or the first network element.

28. The method of claim 26 or 27, wherein, The first request information includes one or more of the following: The identification information of the access network device; The first identification information is used to identify the association between the second connection and the access network device.

29. The method according to any one of claims 26-28, wherein, The method further includes: The second network element receives the first response information corresponding to the first request information sent by the first network element, and the first response information includes the second address information of the second connection.

30. The method according to claim 29, wherein, The second network element sends a first message to the access network device, the first message including relevant information about the second connection.

31. The method according to claim 29, wherein, The second network element sends a fifth request message to the third network element; The third network element is the management network element associated with the access network device; The fifth request information is used to request the third network element to send a first message to the access network device, the first message including relevant information about the second connection.

32. The method of claim 30 or 31, wherein, The fifth request information includes one or more of the following: The identification information of the access network device; The second address information of the second connection; First identification information, which is used to identify the association between the second connection and the access network device; The identification information of the access network device is used by the third network element to identify the access network device.

33. The method of any one of claims 30-32, wherein, The relevant information for the second connection includes one or more of the following: The second address information of the second connection; The first identification information is used to identify the association between the second connection and the access network device.

34. The method according to any one of claims 26-33, wherein, The first connection is related to the second connection in that the first connection and the second connection are the same user plane connection.

35. The method according to any one of claims 26-33, wherein, The first connection being related to the second connection includes: the first connection being established based on the second connection; and / or, the first address information of the first connection being different from the second address information of the second connection.

36. The method of claim 26, wherein, The fourth request information includes one or more of the following: The identification information of the access network device; The identifier information of the first session corresponding to the first connection; The identification information of the first task corresponding to the first connection; The associated identification information corresponding to the first connection.

37. The method of claim 36, wherein, The method further includes: The second network element receives a second response information sent by the first network element, the second response information including the first address information of the first connection.

38. The method of claim 37, wherein, The method further includes: The second network element sends a sixth message to the access network device, the sixth message including information related to the first connection.

39. The method of claim 38, wherein, The method further includes: The second network element sends a sixth request message to the third network element; The third network element is the management network element associated with the access network device; The sixth request information is used to request the third network element to send a sixth message to the access network device; the sixth message includes relevant information about the first connection.

40. The method of claim 39, wherein, The sixth request information includes one or more of the following: The identification information of the access network device; The first address information of the first connection; The identification information of the first task corresponding to the first connection; The identifier information of the first session corresponding to the first connection; The associated identification information corresponding to the first connection.

41. The method of any one of claims 38-40, wherein, The relevant information for the first connection includes one or more of the following: The identification information of the access network device; The identification information of the first task corresponding to the first connection; The identifier information of the first session corresponding to the first connection; The associated identification information corresponding to the first connection.

42. The method according to any one of claims 35-41, wherein, The first connection corresponds to the first session or the first task; Wherein, the first session is any one of multiple sessions between the access network device and the first network element, and / or, the first task is any one of multiple tasks between the access network device and the first network element.

43. The method according to any one of claims 26-42, wherein, The first network element is one or more of the following: the user plane portion of a sensing network element, the user plane portion of a positioning and management network element, and a data collection network element; The second network element is one or more of the following: the control plane portion of a sensing network element, the control plane portion of a positioning-related network element, and a data management network element; The third network element registration management network element, and / or the mobility management network element.

44. A data transmission method, the method comprising: The access network device receives first data sent by the first network element based on the first connection; And / or, the access network device sends second data to the first network element based on the first connection.

45. The method according to claim 44, wherein, The first connection is related to the second connection; wherein the second connection corresponds to the access network device and / or the first network element.

46. The method of claim 45, wherein, The method further includes: The access network device receives a first message, which includes information related to the second connection.

47. The method of claim 46, wherein, The relevant information for the second connection includes one or more of the following: The second address information of the second connection; The first identification information is used to identify the association between the second connection and the access network device.

48. The method according to claim 46 or 47, wherein, The first message originates from the second network element; or, The first message comes from a third network element, which is the management network element associated with the access network device; The third network element is used to receive the fifth request information sent by the second network element, and the fifth request information is used to request the third network element to send the first message to the access network device.

49. The method of any one of claims 46-48, wherein, The method further includes: The access network device sends a second message to the first network element through the second connection; the second message is used by the first network element to determine the binding relationship of the second connection.

50. The method of claim 49, wherein, The second message includes one or more of the following: The identification information of the access network device; The first identification information is used to identify the association between the second connection and the access network device.

51. The method of any one of claims 45-50, wherein, The first connection and the second connection are the same user plane connection.

52. The method of claim 51, wherein, The method further includes: The access network device receives a third message through the second connection, the third message being used to configure a first task and / or a first session corresponding to the second connection.

53. The method according to claim 52, wherein, The access network device sends a fourth message through the second connection, the fourth message being used to confirm the first session and / or the first task associated with the second connection.

54. The method of claim 52 or 53, wherein, The third message, and / or the fourth message, includes one or more of the following: The identification information of the first session; The identification information of the first task; Associated identification information.

55. The method of any one of claims 45-50, wherein, The first connection is established based on the second connection, and / or the first address information of the first connection is different from the second address information of the second connection.

56. The method of claim 55, wherein, The method further includes: The access network device receives a fifth message through the second connection, and the fifth message includes relevant information of the first connection.

57. The method of claim 44, wherein, The method further includes: The access network device receives a sixth message, which includes information related to the first connection.

58. The method according to claim 57, wherein, The sixth message originates from the second network element; or, The sixth message comes from a third network element, which is the management network element associated with the access network device; The third network element is used to receive the sixth request information sent by the second network element, and the sixth request information is used to request the third network element to send the sixth message to the access network device.

59. The method of any one of claims 56-58, wherein, The relevant information for the first connection includes one or more of the following: The first address information of the first connection; Identification information for the first session; The identification information for the first task; Associated identification information.

60. The method of any one of claims 56-59, wherein, The method further includes: The access network device sends a seventh message to the first network element through the first connection, and / or the access network device receives an eighth message sent by the first network element through the first connection; The seventh message and / or the eighth message includes one or more of the following: The identification information of the access network device; The identifier information of the first session corresponding to the first connection; The identification information of the first task corresponding to the first connection; The associated identification information corresponding to the first connection.

61. The method of any one of claims 55-60, wherein, The first connection corresponds to the first session or the first task; Wherein, the first session is any one of multiple sessions between the access network device and the first network element, and / or, the first task is any one of multiple tasks between the access network device and the first network element.

62. The method of any one of claims 44-61, wherein, The first network element is one or more of the following: the user plane portion of a sensing network element, the user plane portion of a positioning management network element, and a data collection network element; the second network element is one or more of the following: the control plane portion of a sensing network element, the control plane portion of a positioning association network element, and a data management network element; the third network element is a registration management network element, and / or a mobility management network element.

63. A data transmission method, the method comprising: The third network element receives the fifth or sixth request information; The fifth request information is used to request the second network element to send a first message to the access network device, the first message including relevant information about the second connection; The sixth request information is used to request the second network element to send a sixth message to the access network device. The sixth message includes information related to the first connection between the first network element and the access network element.

64. The method according to claim 63, wherein, The second connection corresponds to the access network device and / or the first network element, and the first connection is related to the second connection.

65. The method according to claim 63 or 64, wherein, The first connection corresponds to the first session or the first task; Wherein, the first session is any one of multiple sessions between the access network device and the first network element, and / or, the first task is any one of multiple tasks between the access network device and the first network element.

66. The method of any one of claims 63-65, wherein, The fifth request information includes one or more of the following: The identification information of the access network device; The second address information of the second connection; First identification information, which is used to identify the association between the second connection and the access network device; The identification information of the access network device is used by the third network element to identify the access network device.

67. The method of any one of claims 63-63, wherein, The sixth request information includes one or more of the following: The identification information of the access network device; The first address information of the first connection; The identifier information of the first session corresponding to the first connection; The identification information of the first task corresponding to the first connection; The associated identification information corresponding to the first connection; The identification information of the access network device is used by the third network element to identify the access network device.

68. The method of any one of claims 63-67, wherein, The relevant information of the second connection includes one or more of the following: the second address information of the second connection; and the first identification information, which is used to identify the association between the second connection and the access network device.

69. The method of any one of claims 63-68, wherein, The relevant information for the first connection includes one or more of the following: The first address information of the first connection; The identifier information of the first session corresponding to the first connection; The identification information of the first task corresponding to the first connection; The associated identification information corresponding to the first connection.

70. A data transmission apparatus applied to a first network element, the apparatus comprising: The first communication unit is configured to send first data to the access network device based on the first connection; And / or, receive second data sent by the access network device based on the first connection.

71. A data transmission apparatus applied to a second network element, the apparatus comprising: The second communication unit is configured to send a first request message to the first network element, wherein the first request message is used to request the first network element to configure a second connection. The first connection between the first network element and the access network device is related to the second connection; or, the second communication unit is configured to send a fourth request message to the first network element, the fourth request message being used to request the first network element to configure the first connection. The first connection is used to transmit first data and / or second data, wherein the first data is data sent by the first network element to the access network device, and the second data is data sent by the access network device to the first network element.

72. A data transmission apparatus, applied to an access network device, the apparatus comprising: The third communication unit is configured to receive first data sent by the first network element based on the first connection; And / or, send second data to the first network element based on the first connection.

73. A data transmission apparatus applied to a third network element, the apparatus comprising: The fourth communication unit is configured to receive either the fifth or sixth request information. The fifth request information is used to request the second network element to send a first message to the access network device, the first message including relevant information about the second connection; The sixth request information is used to request the second network element to send a sixth message to the access network device. The sixth message includes information related to the first connection between the first network element and the access network element.

74. A communication device, the communication device comprising: Memory, used to store computer programs; A processor, connected to the memory, is configured to retrieve and run the computer program from the memory to implement the method of any one of claims 1 to 25, or the method of any one of claims 26 to 43; or the method of any one of claims 44 to 62; or the method of any one of claims 63 to 69. A transceiver is used to receive and send information when exchanging information with other external devices.

75. A chip, the chip comprising: Memory, used to store computer programs; A processor, connected to the memory, is configured to retrieve and run a computer program from the memory, causing a device having the chip mounted to perform the method as described in any one of claims 1 to 25, or to perform the method as described in any one of claims 26 to 43; or to implement the method as described in any one of claims 44 to 62; or to implement the method as described in any one of claims 63 to 69. A transceiver is used to receive and send information during the exchange of information with a device or chip.

76. A computer-readable storage medium storing a computer program that, when executed by at least one processor, implements the method as claimed in any one of claims 1 to 25, or implements the method as claimed in any one of claims 26 to 43; or implements the method as claimed in any one of claims 44 to 62; or implements the method as claimed in any one of claims 63 to 69.

77. A computer program product comprising a computer program or instructions which, when executed by a processor, implement the steps of the method as claimed in any one of claims 1 to 25; or implement the steps of the method as claimed in any one of claims 26 to 43; or implement the steps of the method as claimed in any one of claims 44 to 62; or implement the steps of the method as claimed in any one of claims 63 to 69.

78. A computer program that, when executed, causes a computer to perform the method as claimed in any one of claims 1 to 25, or to implement the method as claimed in any one of claims 26 to 43; or to implement the method as claimed in any one of claims 44 to 62; or to implement the method as claimed in any one of claims 63 to 69.