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, achieving more efficient data transmission and improving communication performance.
Patent Information
- Application Number
- PCT/CN2025/094113
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2025-05-09
- Publication Date
- 2026-11-12
AI Technical Summary
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 the control plane connection is difficult to effectively meet the data volume and latency requirements.
By establishing a user plane connection between the access network equipment and the first network element, data interaction is achieved, and data transmission is carried out using the user plane connection to meet the requirements of large data volume and high latency.
It improves the communication performance between access network equipment and the first network element, enabling the effective transmission of large amounts of data while meeting high latency requirements.
Smart Images

Figure CN2025094113_12112026_PF_FP_ABST
Abstract
Description
Data transmission method and device, access network equipment, network element and storage medium TECHNICAL FIELD
[0001] The present application relates to the technical field of communication, in particular to a data transmission method and device, access network equipment, network element and storage medium. BACKGROUND
[0002] In the current system architecture, the transmission between the access network equipment and the specific core network element needs to be transmitted through the control plane connection, which is difficult to meet the data transmission requirements of large data volume and high delay. SUMMARY
[0003] The embodiments of the present application provide a data transmission method and device, access network equipment, network element and storage medium.
[0004] In a first aspect, a data transmission method is provided, and the method comprises:
[0005] The first network element sends first data to the access network equipment based on a first connection; and / or, the first network element receives second data sent by the access network equipment based on the first connection; the first connection is a user plane connection between the access network equipment and the first network element.
[0006] In a second aspect, a data transmission method is provided, and the method comprises:
[0007] The access network equipment receives first data sent by the first network element based on a first connection; and / or, the access network equipment sends second data to the first network element based on the first connection; the first connection is a user plane connection between the access network equipment and the first network element.
[0008] In a third aspect, a data transmission method is provided, and the method comprises:
[0009] The second network element receives first request information or second request information;
[0010] The first request information is used to request the second network element to send a first message to the access network equipment, and the first message comprises related information of a second connection between the first network element and the access network element;
[0011] The second request information is used to request the second network element to send a sixth message to the access network equipment, and the sixth message comprises related information of a first connection between the first network element and the access network element.
[0012] In a fourth aspect, a data transmission device is provided, which is applied to a first network element, and the device comprises:
[0013] 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;
[0014] The first connection is a user plane connection between the access network device and the first network element.
[0015] In a fifth aspect, a data transmission apparatus is provided, which is applied to an access network device, and the apparatus comprises:
[0016] The second 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.
[0017] The first connection is a user plane connection between the access network device and the first network element.
[0018] In a sixth aspect, a data transmission apparatus is provided, which is applied to a second network element, and the apparatus comprises:
[0019] The third communication unit is configured to receive first request information or second request information.
[0020] The first request information is used to request the second network element to send a first message to the access network device, and the first message comprises related information of a second connection between the first network element and the access network element.
[0021] The second request information is used to request the second network element to send a sixth message to the access network device, and the sixth message comprises related information of the first connection between the first network element and the access network element.
[0022] In a seventh aspect, a communication device is provided, which comprises a memory, a transceiver, a processor and a bus system.
[0023] The memory is used to store programs and instructions.
[0024] The transceiver is used to receive or send information under the control of the processor.
[0025] The processor is used to execute the programs in the memory.
[0026] The bus system is used to connect the memory, the transceiver and the processor, so that the memory, the transceiver and the processor communicate with each other.
[0027] The processor is used to call the program instructions in the memory, and execute the above-mentioned data transmission method.
[0028] The chip provided by the embodiments of the present application is used to implement the above-mentioned data transmission method.
[0029] 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.
[0030] 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.
[0031] The computer program product provided in this application includes computer program instructions that cause a computer to execute the above-described data transmission method.
[0032] The computer program provided in this application embodiment, when run on a computer, causes the computer to execute the above-described data transmission method.
[0033] In the data transmission method provided in this application 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 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
[0034] Figure 1 is a schematic diagram of a system architecture provided in an embodiment of this application;
[0035] Figure 2 is a schematic diagram of a system architecture for a perception service provided in an embodiment of this application;
[0036] Figure 3 is a schematic diagram of a system architecture for a location service provided in an embodiment of this application;
[0037] Figure 4 is a schematic diagram of a location service process provided in an embodiment of this application;
[0038] Figure 5 is a flowchart illustrating a data transmission method according to an embodiment of this application;
[0039] Figure 6 is a schematic flowchart of a data transmission method provided in an embodiment of this application;
[0040] Figure 7 is a schematic flowchart of a data transmission method provided in an embodiment of this application;
[0041] Figure 8 is a schematic flowchart of a data transmission method provided in an embodiment of this application;
[0042] Figure 9 is a flowchart illustrating a data transmission method according to an embodiment of this application.
[0043] Figure 10 is a schematic diagram of a signaling interaction provided in an embodiment of this application;
[0044] Figure 11 is a schematic flowchart of a data transmission method provided in an embodiment of this application;
[0045] Figure 12 is a second schematic diagram of signaling interaction provided in an embodiment of this application;
[0046] Figure 13 is a schematic flowchart of a data transmission method provided in an embodiment of this application;
[0047] Figure 14 is a schematic diagram of a signaling interaction provided in an embodiment of this application;
[0048] Figure 15 is a flowchart illustrating a data transmission method according to an embodiment of this application.
[0049] Figure 16 is a schematic diagram of the structure of a data transmission device 1600 provided in an embodiment of this application;
[0050] Figure 17 is a structural schematic diagram of a data transmission device 1700 provided in an embodiment of this application;
[0051] Figure 18 is a structural schematic diagram of a data transmission device 1800 provided in an embodiment of this application;
[0052] Figure 19 is a schematic structural diagram of a communication device provided in an embodiment of this application;
[0053] Figure 20 is a schematic structural diagram of a chip according to an embodiment of this application;
[0054] Figure 21 is a schematic block diagram of a communication system provided in an embodiment of this application. Detailed Implementation
[0055] 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.
[0056] 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.
[0057] 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.
[0058] 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.
[0059] 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).
[0060] 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.
[0061] 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.
[0062] 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.
[0063] 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.
[0064] (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.
[0065] 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.
[0066] DN network elements are mainly used to provide services to users, such as operator services, Internet access services, and third-party services.
[0067] 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.
[0068] 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.
[0069] The following section introduces sensing technology.
[0070] 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.
[0071] 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.
[0072] 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".
[0073] 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.
[0074] 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).
[0075] 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.
[0076] 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.
[0077] The main wireless sensing scenarios for integrated sensing are as follows:
[0078] 1) Base station echo sensing link (single gNB sensing): The base station sends sensing signals and receives echo signals;
[0079] 2) Inter-base station sensing link (gNB-gNB sensing): Base station B receives sensing signals sent by base station A;
[0080] 3) Air interface uplink sensing link (UE-gNB uplink sensing): The base station receives sensing signals sent by the terminal;
[0081] 4) Air interface downlink sensing link (UE-gNB downlink sensing): The terminal receives sensing signals sent by the base station;
[0082] 5) Terminal echo sensing link (single UE sensing): The terminal sends sensing signals and receives echo signals;
[0083] 6) Inter-terminal sensing link (UE-UE sensing): Terminal B receives sensing signals sent by Terminal A.
[0084] 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.
[0085] 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.
[0086] 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.
[0087] The following section introduces deferred positioning technology.
[0088] 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:
[0089] S1. Delay 5GC-MT-LR steps 1-14 and execute according to the existing process. AF, LCS client or NF triggers periodic location events.
[0090] 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).
[0091] S3. Delay 5GC-MT-LR steps 18-21 and execute them according to the existing process, with the following modifications:
[0092] 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.
[0093] 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.
[0094] S5.AMF forwards the message to NG-RAN.
[0095] S6-7a.NG-RAN returns E-CID measurement initialization response (TS 38.455 Clause 8.2.1.2).
[0096] S6-7b.NG-RAN returned measurement response (TS 38.455 Clause 8.5.1.2).
[0097] 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.
[0098] S8-9b.LMF periodically receives measurement reports from NG-RAN (TS 38.455 Clause 8.5.2.2) and calculates the location results accordingly.
[0099] S10.LMF calls the Nlmf_Location_EventNotify service operation (following step 28) to transmit location information to VGMLC or (H)GMLC.
[0100] S11. Delay 5GC-MT-LR step 29 and execute it according to the existing process.
[0101] S12a. Delay 5GC-MT-LR step 30a and execute it according to the existing process.
[0102] S12b-1. Delay 5GC-MT-LR step 30b-1 as per existing procedure.
[0103] S12b-2. Delay 5GC-MT-LR step 30b-2 as per existing procedure.
[0104] S12c. Delay 5GC-MT-LR step 30c and execute according to the existing process.
[0105] S8 to S12c are executed periodically.
[0106] It should be noted that in S1-S12 shown in Figure 4, S4-S6 are the LMF's reporting requests to the RAN device to configure the control plane through the AMF, while S8-S9 are the RAN nodes reporting measurement data to the control plane through the AMF after obtaining the measurement data. The configuration of the control plane can call the AMF's fixed service interface.
[0107] 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.
[0108] 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.
[0109] 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.
[0110] 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.
[0111] 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.
[0112] 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.
[0113] 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.
[0114] 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.
[0115] 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.
[0116] 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.
[0117] In some embodiments, the first connection is a user plane connection between the access network device and the first network element.
[0118] In some embodiments, the first connection is a data plane connection between the access network device and the first network element.
[0119] It should be noted that the first network element can be one or more of the following: SF network element, LMF network element, data collection network element, and data management network element.
[0120] It should also be noted that the first network element may include a control plane portion and a data plane portion. The control plane portion and data plane portion of the first network element are not separated; that is, the first network element can implement both control plane functions and user plane functions.
[0121] 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 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.
[0122] It should be noted that in Figure 2, the SF-C and SF-U of the SF network element are set on the same physical device, that is, the SF network element is a non-CU-separated device.
[0123] In one example, the data transmission method provided in this application embodiment can be applied to the architecture shown in Figure 3. The first network element can be an LMF network element. The first data and the second data can be location-related data.
[0124] 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.
[0125] 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.
[0126] 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).
[0127] 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.
[0128] In the embodiments of this application, the configuration methods of the first connection include multiple methods.
[0129] In one possible implementation (referred to as implementation 1 in this application embodiment), the first network element can be configured with a second connection. The first connection is associated with the second connection.
[0130] It should be noted that the second connection can also be a connection between the access network device and the first network element.
[0131] In some embodiments, the second connection is a user plane connection between the access network device and the first network element.
[0132] In some embodiments, the second connection is a data plane connection between the access network device and the first network element.
[0133] In another possible implementation (referred to as mode 2 in this application embodiment), the first network element can be directly configured with the first connection.
[0134] In method 1, the first network element can be configured with a second connection, wherein the first connection is related to the second connection.
[0135] 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.
[0136] 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. That is, for implementation 1A, the first connection is a node-level user plane connection, and the first connection may correspond to an access network device and / or a first network element.
[0137] 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.
[0138] 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.
[0139] It should also be noted that in Method 1B, the first connection is a Task / Session level user plane connection. This first connection corresponds to the first task and / or the first session.
[0140] 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.
[0141] The following describes the specific steps for configuring the second connection using the first network element.
[0142] Referring to the flowchart shown in Figure 6, the configuration process for the second connection includes the following steps:
[0143] S610. The first network element sends a first message to the access network device, or the first network element sends a first message to the access network device through the second network element.
[0144] In some embodiments, the first message may include information related to the second connection. This information can be used to establish the second connection.
[0145] 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 plane information.
[0146] In some embodiments, the relevant information for the second connection may include one or more of the following:
[0147] Second address information for the second connection;
[0148] First identification information.
[0149] In some embodiments, 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.
[0150] In some embodiments, the first identification information can be used to identify the association of the second connection with the access network device, or in other words, the first identification can be used to associate the established second connection with the RAN.
[0151] It should be noted that the first identification information can also be called binding information.
[0152] In one example, the first identification information or binding information can be the RAN ID.
[0153] 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.
[0154] In one example, the first identification information or binding information can be the connection ID of the second connection.
[0155] 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.
[0156] In one possible implementation, the first 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 first network element.
[0157] It should be understood that if the first network element stores the ID of the access network device or the control plane interface information of the access network device, the first 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.
[0158] In another possible implementation, the first network element can send the first message to the access network device through the second network element. That is, the first message received by the access network device can come from the second network element.
[0159] It should be noted that the second network element can be a management network element associated with the access network device. Specifically, the second network element can be a registration management network element and / or a mobility management network element. For example, the second network element can be an AMF network element in a 5G network or an MM network element in a 6G network.
[0160] Specifically, in this implementation, step S610 may include:
[0161] S610a, the first network element sends a first request message to the second network element, the first request message being used to request the second network element to send a first message to the access network device.
[0162] S610b, the second network element sends the first message to the access network equipment.
[0163] In some embodiments, the first request information may include one or more of the following:
[0164] 1) Second address information of the second connection;
[0165] 2) First identification information;
[0166] 3) Identification information (RAN ID) of access network equipment.
[0167] In some embodiments, the second address information in information 1) 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.
[0168] In some embodiments, the first identification information in information 2) can identify the association of the second connection with the access network device, or in other words, the first identification can be used to associate the established second connection with the RAN.
[0169] It should be noted that the first identification information can also be called binding information.
[0170] In one example, the first identification information or binding information can be the RAN ID.
[0171] 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.
[0172] In one example, the first identification information or binding information can be the connection ID of the second connection.
[0173] In some embodiments, the RAN ID in information 3) can be used by the second network element to determine the corresponding access network device RAN. It should be understood that the second network element can manage or maintain multiple access network devices, and the second network element can determine the access network device to which the second connection is to be established based on the RAN ID in the first request information.
[0174] S620. 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.
[0175] In some embodiments, the second message includes one or more of the following:
[0176] RAN ID (Identification Information of Access Network Equipment);
[0177] First binding information.
[0178] It should be understood that after receiving the second address information, the access network device establishes a second connection with the first network element through the second address information. The access network device can send a second message to the first network element through the second connection, or in other words, it can use the second address information.
[0179] 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.
[0180] 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.
[0181] 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.
[0182] It should also be noted that step S620 is an optional step, meaning that step S620 can be performed or not. In Figure 6, this optional step is indicated by a dashed arrow.
[0183] In this embodiment of the application, the establishment of the second connection can be triggered by the first network element itself or by an external application network element.
[0184] In some embodiments, referring to FIG6, before step S610, the following steps are further included:
[0185] S602, The first network element receives service / data request information sent by an external application network element.
[0186] 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).
[0187] It should also be noted that the service / data request information may include target information and the corresponding service requirement.
[0188] 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.
[0189] In one example, service requirements may include one or more of the following: sensing method, sensing accuracy, latency, etc.
[0190] S604. The first network element selects the second network element and access network equipment based on the service / data request information.
[0191] It should be noted that the first network element can obtain the ID information, control plane port information, or address information of the access network device by querying NRF / AMF, etc.
[0192] 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).
[0193] It should be noted that before the first network element and the access network device can interact with each other based on the second connection at the node level, it is also necessary to configure the associated Task / Session / Correlation.
[0194] 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:
[0195] S710. The first network element sends a third message to the access network device, or in other words, the access network device receives a third message sent by the first network element. The third message is used to configure the first session and / or the first task.
[0196] It should be noted that the first data and / or the second data in step S510 are both Task / Session / Correlation level data. Before the first network element and the access network device perform data interaction in step S510, it is also necessary to configure the associated session and / or task.
[0197] In some embodiments, the first network element may send a third message to the access network device based on the service / data request information in step S602 or other service / data request information received before step S710, to configure a first session and / or a first task for the access network device.
[0198] In one possible implementation, the first network element can send a third message to the access network element through an established second connection.
[0199] In another possible implementation, the first network element sends the third message via a control plane connection. In one example, the first network element can directly send the third message to the access network device using the control plane port information of the access network device. In another example, the first network element can send the third message to a second network element, which then forwards the third message to the access network device.
[0200] In another possible implementation, the first network element can send part of the third message through the established second connection, and send another part of the third message through the control plane connection.
[0201] In some embodiments, the third message may include one or more of the following:
[0202] The identification information of the first session (Session ID);
[0203] The identification information of the first task (Task ID);
[0204] Correlation ID.
[0205] S720, 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.
[0206] 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.
[0207] In some embodiments, the fourth message is also used to confirm the first session and / or the first task.
[0208] In some embodiments, the fourth message may include one or more of the following:
[0209] The identification information of the first session (Session ID);
[0210] The identification information of the first task (Task ID);
[0211] Correlation ID
[0212] 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 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.
[0213] Through method 1A above, after establishing the second connection and configuring the relevant Session ID / Task ID / Correlation ID, the first network element and the access network device can perform Session / Task-level data interaction (including first data and / or second data) through the second connection. This enables user plane transmission between the access network device and a specific network element, improving the communication performance between the access network device and the specific network element.
[0214] 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.
[0215] In some embodiments, referring to FIG8, for method 1B, after the second connection is established, the following steps may also be included:
[0216] S810, the first network element sends the fifth message to the access network device through the second connection.
[0217] In some embodiments, the fifth message includes information related to the first connection. This information can be used to establish the first connection.
[0218] 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.
[0219] It should be understood that after the second node-level connection is established based on steps S610 and S620, the first network element can establish the first Task / Session-level connection through the second connection.
[0220] Specifically, in step S810, the first network element can send a fifth message to the access network device through the second connection.
[0221] In some embodiments, the information related to the first connection may include one or more of the following:
[0222] First address information of the first connection;
[0223] The identification information of the first session (Session ID);
[0224] The identification information of the first task (Task ID);
[0225] Correlation ID.
[0226] 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.
[0227] It should be noted that the first address information of the first connection is different from the second address information of the second connection.
[0228] S820, 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.
[0229] 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.
[0230] In some embodiments, the seventh message is also used to confirm the first session and / or the first task.
[0231] In some embodiments, the seventh message may include:
[0232] The identification information of the first session (Session ID);
[0233] The identification information of the first task (Task ID);
[0234] Correlation ID;
[0235] RAN ID (Identification Information) of Access Network Equipment.
[0236] 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.
[0237] It should be noted that the RAN ID in the seventh message is optional information; 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 can be globally unique. This means that different sessions / tasks use different Session IDs / Task IDs / correlation IDs. Therefore, even without the RAN ID, the first network element can determine which RAN node sent the data and which Session / Task it corresponds to based solely on the Session ID / Task ID / correlation ID.
[0238] 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.
[0239] In some embodiments, after step S820, the method provided in this application embodiment may further include step S830.
[0240] S830: 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.
[0241] 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.
[0242] It should be noted that the eighth message may include one or more of the following:
[0243] The identification information of the first session (Session ID);
[0244] The identification information of the first task (Task ID);
[0245] Correlation ID.
[0246] 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.
[0247] 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.
[0248] For method 2, the first network element can be directly configured with the first connection.
[0249] 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 first network element can be directly configured with a Task / Session level user plane connection to directly realize Task / Session level user plane data interaction.
[0250] In some embodiments, referring to FIG9, for method 2, the following steps may be included before performing step S510:
[0251] S910. The first network element sends a sixth message to the access network device, or the first network element sends a sixth message to the access network device through the second network element.
[0252] In some embodiments, the sixth message may include information related to the first connection. This information can be used to establish the first connection.
[0253] 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.
[0254] In some embodiments, the information related to 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 one possible implementation, the first network element can directly send the sixth message to the access network device, meaning that the sixth message received by the access network device comes from the first network element.
[0260] It should be understood that if the first network element stores the ID of the access network device or the control plane interface information of the access network device, the first 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.
[0261] In another possible implementation, the first network element sends the sixth message to the access network device through the second network element. That is, the sixth message received by the access network device can come from the second network element.
[0262] It should be noted that the second network element can be a management network element associated with the access network device. Specifically, the second network element can be a registration management network element and / or a mobility management network element. For example, the second network element can be an AMF network element in a 5G network or an MM network element in a 6G network.
[0263] Specifically, in this implementation, step S910 may include:
[0264] S910a, the first network element sends a second request message to the second network element, the second request message being used to request the second network element to send a sixth message to the access network device.
[0265] S910b, the second network element sends the sixth message to the access network equipment.
[0266] In some embodiments, the second request information may include one or more of the following:
[0267] 1) First address information of the first connection;
[0268] 2) The identification information (Session ID) of the first session corresponding to the first connection;
[0269] 3) The identifier information (Task ID) of the first task corresponding to the first connection;
[0270] 4) Correlation ID information corresponding to the first connection;
[0271] 5) Identification information (RAN ID) of access network equipment.
[0272] In some embodiments, the first address information in information 1) 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.
[0273] In some embodiments, information 2) and information 3) may be determined by the first network element based on service / data request information sent by an external application network element.
[0274] In some embodiments, the RAN ID in information 3) can be used by the second network element to determine the corresponding access network device RAN. It should be understood that the second network element can manage or maintain multiple access network devices, and the second network element can determine the access network device to which the first connection is to be established based on the RAN ID in the second request information.
[0275] S920, 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.
[0276] 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.
[0277] In some embodiments, the seventh message is also used to confirm the first session and / or the first task.
[0278] In some embodiments, the seventh message may include:
[0279] The identification information of the first session (Session ID);
[0280] The identification information of the first task (Task ID);
[0281] Correlation ID;
[0282] RAN ID (Identification Information) of Access Network Equipment.
[0283] 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.
[0284] It should be noted that the RAN ID in the seventh message is optional information; 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 can be globally unique. This means that different sessions / tasks use different Session IDs / Task IDs / correlation IDs. Therefore, even without the RAN ID, the first network element can determine which RAN node sent the data and which Session / Task it corresponds to based solely on the Session ID / Task ID / correlation ID.
[0285] 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.
[0286] In some embodiments, after step S920, the method provided in this application embodiment may further include step S930.
[0287] S930. 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.
[0288] 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.
[0289] It should be noted that the eighth message may include one or more of the following:
[0290] The identification information of the first session (Session ID);
[0291] The identification information of the first task (Task ID);
[0292] Correlation ID.
[0293] It should be noted that in step S910 above, the first network element sending the sixth message to the access network device can be triggered by the first network element itself or by an external application network element.
[0294] In some embodiments, referring to FIG9, before step S910, the following steps are further included:
[0295] S902, the first network element receives service / data request information sent by an external application network element.
[0296] 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).
[0297] It should also be noted that the service / data request information may include target information and the corresponding service requirement.
[0298] 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.
[0299] In one example, service requirements may include one or more of the following: sensing method, sensing accuracy, latency, etc.
[0300] S904. The first network element selects the second network element and access network equipment based on the service / data request information.
[0301] It should be noted that the first network element can obtain the ID information, control plane port information, or address information of the access network device by querying NRF / AMF, etc.
[0302] Using method 2 above, the first network element 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.
[0303] The methods provided in the embodiments of this application will be described in detail below in conjunction with perception application scenarios.
[0304] In sensing application scenarios, the first network element can be SF, and the second network element can be AMF (or MM).
[0305] Example 1: Establish a node-level connection between SF and RAN.
[0306] Refer to Figure 10 for a schematic diagram of signaling interaction between network elements.
[0307] The SF can send node-level user plane address information to the RAN (corresponding to the second address information of the second connection in the above embodiment). The SF can send the node-level user plane address information directly to the RAN, or the SF can send the node-level user plane address information to the RAN through the AMF.
[0308] The RAN reports acknowledgment information (including RAN ID and / or binding information) to the SF via the user plane connection to establish a node-level user plane connection (corresponding to the second connection in the above embodiment).
[0309] SF can bind the user plane connection to the corresponding RAN ID based on the RAN ID or binding information reported by the RAN node. In subsequent processes, SF can directly send session / task-level awareness messages to the RAN and perform subsequent interactions.
[0310] Referring to the flowchart shown in Figure 11, Embodiment 1 may include the following steps:
[0311] 1. SF receives the perception request information sent by Consumer NF.
[0312] It should be noted that the perception request information may include target information and the corresponding service requirement.
[0313] In one example, target information may include one or more of the following: a specific geographic area, a specific UE, or a specific object.
[0314] In one example, service requirements may include one or more of the following: sensing method, sensing accuracy, and latency.
[0315] 2. SF selects AMF and RAN based on the perception request information.
[0316] It should be noted that SF can obtain RAN ID or address information by querying NRF / AMF, etc.
[0317] 3a.SF sends a request message to AMF (corresponding to the first request message in the above embodiment).
[0318] In some embodiments, the request information may include RAN ID information and SF address information (corresponding to the second address information in the above embodiments) for establishing a user plane connection (corresponding to the second connection in the above embodiments).
[0319] In some embodiments, the address information may include IP address, port information, and FQDN information.
[0320] In some embodiments, as an option, the request information may also include binding information, which is used to associate the user plane connection (corresponding to the second connection in the above embodiments) with the RAN node / Connection ID.
[0321] In one example, binding information can be a RAN ID.
[0322] 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.
[0323] In one example, the binding information can be the connection ID of the user plane connection.
[0324] 3b. The AMF sends the first message to the RAN node based on the RAN ID information (the same as the first message in the above embodiment).
[0325] In some embodiments, the first message may include the user plane address information of the SF (i.e., the second address information of the second connection in the above embodiments).
[0326] In some embodiments, as an option, the first message may also include the corresponding binding information.
[0327] 4. SF can send the first message directly to RAN based on RAN address information or control plane interface information.
[0328] In some embodiments, the first message may include SF's user plane address information (corresponding to the second address information in the above embodiments).
[0329] In some embodiments, as an option, the first message may also include the corresponding binding information.
[0330] It should be noted that step 4 and step 3 are two parallel methods, and only one of them needs to be performed.
[0331] 5. The RAN sends a second message to the SF via the user plane connection (the same as the second message in the above embodiment).
[0332] In some embodiments, the second message may include RAN ID information and / or binding information.
[0333] In some embodiments, after receiving the second message, the SF maintains the mapping relationship between the RAN ID and the current user plane connection (the second connection in the above embodiments).
[0334] 6. SF sends downlink-aware messages (corresponding to the third message in the above embodiments) to RAN through the user plane connection (corresponding to the second connection in the above embodiments).
[0335] In some embodiments, the downlink-aware message may include Session ID / Task ID / Correlation ID.
[0336] It should be noted that SF can also send downlink awareness messages through the control plane connection.
[0337] 7. The RAN transmits uplink awareness messages (corresponding to the fourth message in the above embodiment) to the SF through the user plane connection (corresponding to the second connection in the above embodiment).
[0338] In some embodiments, the uplink awareness message may include Session ID / Task ID / Correlation ID.
[0339] 8. Subsequent sensing process.
[0340] 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.
[0341] Example 2: Establish a session / task-level connection between SF and RAN.
[0342] Referring to the second schematic diagram of signaling interaction between network elements shown in Figure 12, the SF can send user plane address information (corresponding to the first address information in the above embodiment) and the corresponding Session ID / Task ID / Correlation ID to the RAN. Specifically, the SF can directly send user plane address information and the corresponding Session ID / Task ID / Correlation ID to the RAN, or the SF can send user plane address information and the corresponding Session ID / Task ID / Correlation ID to the RAN through the AMF. Accordingly, the RAN directly reports Session / Task data based on the above information.
[0343] Referring to the flowchart shown in Figure 13, Embodiment 2 may include the following steps:
[0344] 1. SF receives perception request information sent by external application network elements.
[0345] 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).
[0346] It should also be noted that the perception request information may include target information and the corresponding service requirement.
[0347] In one example, target information may include one or more of the following: a specific geographic area, a specific UE, or a specific object.
[0348] In one example, service requirements may include one or more of the following: sensing method, sensing accuracy, and latency.
[0349] 2. SF selects AMF and RAN based on the perception request information.
[0350] It should be noted that SF can obtain RAN ID or address information by querying NRF / AMF, etc.
[0351] 3a.SF sends a request message to AMF (corresponding to the second request message in the above embodiment).
[0352] In some embodiments, the request information may include the following:
[0353] 1) RAN ID information;
[0354] 2) SF is used to establish the address information (corresponding to the first address information in the above embodiment) for establishing the user plane connection (corresponding to the first connection in the above embodiment);
[0355] 3)Session ID / Task ID / Correlation ID.
[0356] In some embodiments, the address information may include IP address, port information, and FQDN information.
[0357] 3b. The AMF sends a sixth message to the RAN node based on the RAN ID information (the same as the sixth message in the above embodiment).
[0358] In some embodiments, the sixth message may include the user plane address information of the SF (i.e., the first address information of the first connection in the above embodiments), as well as the Session ID / Task ID / Correlation ID.
[0359] 4. SF can send the sixth message directly to RAN based on RAN address information or control plane interface information.
[0360] In some embodiments, the sixth message may include the user plane address information of the SF (i.e., the first address information of the first connection in the above embodiments), as well as the Session ID / Task ID / Correlation ID.
[0361] It should be noted that step 4 and step 3 are two parallel methods, and only one of them needs to be performed.
[0362] 5. The RAN transmits uplink sensing messages (corresponding to the seventh message in the above embodiment) to the SF through the user plane connection (corresponding to the first connection in the above embodiment).
[0363] In some embodiments, the uplink awareness message may include the RAN ID, as well as the Session ID / Task ID / Correlation ID.
[0364] 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.
[0365] 6. SF sends a downlink-aware message (corresponding to the eighth message in the above embodiment) to RAN through the user plane connection (corresponding to the first connection in the above embodiment).
[0366] In some embodiments, the downlink-aware message may include Session ID / Task ID / Correlation ID.
[0367] In some embodiments, the downlink-aware message may also include the RAN ID as an optional component.
[0368] 7. Subsequent sensing process.
[0369] 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.
[0370] 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.
[0371] Refer to Figure 14 for the schematic diagram of signaling interaction between network elements.
[0372] The SF can send node-level user plane address information to the RAN (corresponding to the second address information of the second connection in the above embodiment). The SF can send the node-level user plane address information directly to the RAN, or the SF can send the node-level user plane address information to the RAN through the AMF.
[0373] Furthermore, the RAN reports acknowledgment information (including RAN ID and / or binding information) to the SF via the node-level user plane connection to establish the user plane connection. The SF can then bind the node-level user plane connection to the corresponding RAN ID / Connection ID based on the RAN ID or binding information reported by the RAN node.
[0374] In subsequent data interaction, SF 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, to achieve data interaction.
[0375] Referring to the flowchart shown in Figure 15, Embodiment 3 may include the following steps:
[0376] Steps 1-5 are the same as in Example 1, and will not be repeated here for the sake of simplicity.
[0377] 6. SF sends a fifth message (the same as the fifth message in the above embodiment) to RAN through a node-level user plane connection (corresponding to the second connection in the above embodiment).
[0378] 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.
[0379] In some embodiments, the fifth message may also include the Session ID / Task ID / Correlation ID of the current perception task.
[0380] 7. The RAN transmits uplink awareness messages (corresponding to the seventh message in the above embodiments) to the SF 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).
[0381] In some embodiments, the uplink awareness message may include Session ID / Task ID / Correlation ID.
[0382] In some embodiments, after receiving the information, the SF maintains the mapping relationship between the RAN ID, Session ID / Task ID / Correlation ID, and the current sensing message.
[0383] 8. The SF sends a downlink-aware message (corresponding to the eighth message in the above embodiment) to the RAN through a user plane connection at the Session / Task granularity (corresponding to the first connection in the above embodiment). That is, the downlink-aware message is transmitted through address information at the Session / Task granularity (corresponding to the first address information in the above embodiment).
[0384] In some embodiments, the downlink-aware message may include a Session ID / Task ID / Correlation ID.
[0385] 9. Subsequent sensing process.
[0386] 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.
[0387] In the above embodiments, Embodiment 1 establishes a node-level user plane connection by having the SF send the user plane address and corresponding binding ID to the RAN node, and the RAN node then sends the RAN ID and / or binding ID to the SF. Subsequent session-level message interactions are transmitted over 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 over other user plane connections and achieving user plane connection isolation.
[0388] In summary, this invention achieves the effect of establishing a user plane connection and transmitting user plane data between the RAN node and the SF through three different embodiments.
[0389] 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:
[0390] The first communication unit 1610 is configured to send first data to the access network device based on a first connection; and / or receive second data sent by the access network device based on the first connection; the first connection is a user plane connection between the access network device and the first network element.
[0391] In some embodiments, the first connection is associated with a second connection, and the second connection corresponds to the access network device and / or the first network element.
[0392] In some embodiments, the first communication unit 1610 is further configured to send a first message to the access network device, the first message including information related to the second connection.
[0393] In some embodiments, the first communication unit 1610 is further configured to send a first request message to the second network element;
[0394] The second network element is the management network element associated with the access network device;
[0395] The first 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.
[0396] In some embodiments, the first request information includes one or more of the following:
[0397] The identification information of the access network device;
[0398] The second address information of the second connection;
[0399] First identification information, which is used to identify the association between the second connection and the access network device;
[0400] The identification information of the access network device is used by the second network element to identify the access network device.
[0401] In some embodiments, the relevant information of the second connection includes one or more of the following:
[0402] The second address information of the second connection;
[0403] The first identification information is used to identify the association between the second connection and the access network device.
[0404] In some embodiments, a second message is received through the second connection; the second message is used by the first network element to determine the binding relationship of the second connection.
[0405] In some embodiments, the second message includes one or more of the following:
[0406] The identification information of the access network device;
[0407] The first identification information is used to identify the association between the second connection and the access network device.
[0408] In some embodiments, the first connection and the second connection are the same user plane connection.
[0409] In some embodiments, the first communication unit 1610 is further configured to send a third message, the third message being used to configure a first session and / or a first task.
[0410] In some embodiments, the first communication unit 1610 is further configured to send the third message via the second connection; and / or, to send the third message via a control plane connection.
[0411] 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 to transmit service data and / or service-related signaling.
[0412] In some embodiments, the fourth message is also used to confirm the first session and / or the first task.
[0413] In some embodiments, the third message, and / or the fourth message, includes one or more of the following:
[0414] The identification information of the first session;
[0415] The identification information of the first task;
[0416] Correlation ID.
[0417] 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.
[0418] 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.
[0419] In some embodiments, the first communication unit 1610 is further configured to send a sixth message to the access network device, the sixth message including information related to the first connection.
[0420] In some embodiments, the first communication unit 1610 is further configured to send a second request message to the second network element;
[0421] The second network element is the management network element associated with the access network device;
[0422] The second request information is used to request the second network element to send a sixth message to the access network device, and the sixth message includes information related to the first connection.
[0423] In some embodiments, the second request information includes one or more of the following:
[0424] The identification information of the access network device;
[0425] The first address information of the first connection;
[0426] The identifier information of the first session corresponding to the first connection;
[0427] The identification information of the first task corresponding to the first connection;
[0428] The Correlation ID corresponding to the first connection;
[0429] The identification information of the access network device is used by the second network element to identify the access network device.
[0430] In some embodiments, the information related to the first connection includes one or more of the following:
[0431] The first address information of the first connection;
[0432] The identifier information of the first session corresponding to the first connection;
[0433] The identification information of the first task corresponding to the first connection;
[0434] The first connection corresponds to the Correlation ID.
[0435] 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, the seventh message being used to transmit service data and / or service-related signaling.
[0436] In some embodiments, the seventh message is also used to confirm that the first connection has been established.
[0437] In some embodiments, the seventh message includes one or more of the following:
[0438] The identification information of the first session;
[0439] The identification information of the first task;
[0440] Correlation ID;
[0441] The identification information of the access network device.
[0442] In some embodiments, the first connection corresponds to a first session or a first task;
[0443] 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.
[0444] In some embodiments, the first network element is one or more of a sensing network element, a positioning management function network element, a data collection network element, and a data management network element; the second network element is a registration management network element, and / or a mobility management network element.
[0445] 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 FIG17, the data transmission apparatus 1700 provided in this application embodiment may include:
[0446] The second communication unit 1710 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; the first connection is a user plane connection between the access network device and the first network element.
[0447] In some embodiments, the first connection is associated with a second connection, and the second connection corresponds to the access network device and / or the first network element.
[0448] In some embodiments, the second communication unit 1710 is further configured to receive a first message, the first message including information related to the second connection.
[0449] In some embodiments, the first message includes one or more of the following:
[0450] The second address information of the second connection;
[0451] The first identification information is used to identify the association between the second connection and the access network device.
[0452] In some embodiments, the second communication unit 1710 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.
[0453] In some embodiments, the second message includes one or more of the following:
[0454] The identification information of the access network device;
[0455] The first identification information is used to identify the association between the second connection and the access network device.
[0456] In some embodiments, the first message originates from the first network element;
[0457] or,
[0458] The first message comes from the second network element, which is the management network element associated with the access network device;
[0459] The second network element is used to receive a first request information sent by the first network element, and the first request information is used to request the second network element to send the first message to the access network device.
[0460] In some embodiments, the first connection and the second connection are the same user plane connection.
[0461] In some embodiments, the second communication unit 1710 is further configured to receive a third message, the third message being used to configure a first session and / or a first task.
[0462] In some embodiments, the third message is received via the second connection; and / or, the third message is received via a control plane connection.
[0463] In some embodiments, the second communication unit 1710 is further configured to send a fourth message through the second connection, the fourth message being used to transmit service data and / or service-related signaling.
[0464] In some embodiments, the fourth message is also used to confirm the first session and / or the first task.
[0465] In some embodiments, the third message, and / or the fourth message, includes one or more of the following:
[0466] The identification information of the first session;
[0467] The identification information of the first task;
[0468] Correlation ID.
[0469] In some embodiments, the first connection is established based on the second connection, and / or the address information of the first connection is different from the address information of the second connection.
[0470] In some embodiments, the second communication unit 1710 is further configured to receive a fifth message via the second connection, the fifth message including information related to the first connection.
[0471] In some embodiments, the second communication unit 1710 is further configured to receive a sixth message, the sixth message including information related to the first connection.
[0472] In some embodiments, the sixth message originates from the first network element;
[0473] or,
[0474] The sixth message comes from the second network element, which is the management network element associated with the access network device;
[0475] The second network element is used to receive the second request information sent by the first network element, and the second request information is used to request the second network element to send the sixth message to the access network device.
[0476] In some embodiments, the information related to the first connection includes one or more of the following:
[0477] The first address information of the first connection;
[0478] The identifier information of the first session corresponding to the first connection;
[0479] The identification information of the first task corresponding to the first connection;
[0480] The first connection corresponds to the Correlation ID.
[0481] In some embodiments, the second communication unit 1710 is further configured to send a seventh message to the first network element through the first connection, the seventh message being used to transmit service data and / or service-related signaling.
[0482] In some embodiments, the seventh message is also used to confirm that the first connection has been established.
[0483] In some embodiments, the seventh message includes one or more of the following:
[0484] The identification information of the first session;
[0485] The identification information of the first task;
[0486] Correlation ID;
[0487] The identification information of the access network device.
[0488] In some embodiments, the first connection corresponds to a first session or a first task;
[0489] 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.
[0490] In some embodiments, the first network element is one or more of a sensing management network element, a data collection network element, and a data management network element;
[0491] The second network element is a mobility management network element, and / or an access and mobility management network element.
[0492] 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 FIG18, the data transmission apparatus 1800 provided in this embodiment may include:
[0493] The third communication unit 1810 is configured to receive a first request information or a second request information;
[0494] Wherein, the first request information is used to request the second network element to send a first message to the access network device, the first message being used to establish a second connection between the first network element and the access network element; the second request information is used to request the second network element to send a sixth message to the access network device, the sixth message being used to establish a first connection between the first network element and the access network element.
[0495] 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.
[0496] In some embodiments, the first connection corresponds to a first session or a first task;
[0497] 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.
[0498] In some embodiments, the first request information includes one or more of the following:
[0499] The identification information of the access network device;
[0500] The second address information of the second connection;
[0501] First identification information, which is used to identify the association between the second connection and the access network device;
[0502] The identification information of the access network device is used by the second network element to identify the access network device.
[0503] In some embodiments, the second request information includes one or more of the following:
[0504] The identification information of the access network device;
[0505] The first address information of the first connection;
[0506] The identifier information of the first session corresponding to the first connection;
[0507] The identification information of the first task corresponding to the first connection;
[0508] The Correlation ID corresponding to the first connection.
[0509] The identification information of the access network device is used by the second network element to identify the access network device.
[0510] In some embodiments, the first message includes one or more of the following:
[0511] The second address information of the second connection;
[0512] The first identification information is used to identify the association between the second connection and the access network device.
[0513] In some embodiments, the sixth message includes one or more of the following:
[0514] The first address information of the first connection;
[0515] The identifier information of the first session corresponding to the first connection;
[0516] The identification information of the first task corresponding to the first connection;
[0517] The first connection corresponds to the Correlation ID.
[0518] 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.
[0519] Figure 19 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, or a second network element. The communication device 1900 shown in Figure 19 includes a processor 1900, which can call and run computer programs from memory to implement the methods in the embodiments of this application.
[0520] Optionally, as shown in FIG19, the communication device 1900 may further include a memory 1920. The processor 1910 may retrieve and run computer programs from the memory 1920 to implement the methods described in the embodiments of this application.
[0521] The memory 1920 can be a separate device independent of the processor 1910, or it can be integrated into the processor 1910.
[0522] Optionally, as shown in FIG19, the communication device 1900 may further include a transceiver 1930, and the processor 1910 may control the transceiver 1030 to communicate with other devices. Specifically, it may send information or data to other devices or receive information or data sent by other devices.
[0523] The transceiver 1930 may include a transmitter and a receiver. The transceiver 1930 may further include an antenna, and the number of antennas may be one or more.
[0524] Optionally, the communication device 1900 may specifically be the first network element in the embodiments of this application, and the communication device 1900 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.
[0525] Optionally, the communication device 1900 may specifically be an access network device in the embodiments of this application, and the communication device 1900 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.
[0526] Optionally, the communication device 1900 may specifically be a second network element in the embodiments of this application, and the communication device 1900 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.
[0527] Figure 20 is a schematic structural diagram of a chip according to an embodiment of this application. The chip 2000 shown in Figure 20 includes a processor 2010, which can call and run computer programs from memory to implement the methods in the embodiments of this application.
[0528] Optionally, as shown in FIG20, chip 2000 may further include memory 2020. Processor 2010 can call and run computer programs from memory 2020 to implement the methods in the embodiments of this application.
[0529] The memory 2020 can be a separate device independent of the processor 2010, or it can be integrated into the processor 2010.
[0530] Optionally, the chip 2000 may also include an input interface 2030. The processor 2010 can control the input interface 2030 to communicate with other devices or chips; specifically, it can acquire information or data sent by other devices or chips.
[0531] Optionally, the chip 2000 may also include an output interface 2040. The processor 2010 can control the output interface 2040 to communicate with other devices or chips, specifically, to output information or data to other devices or chips.
[0532] 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.
[0533] 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.
[0534] 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.
[0535] 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.
[0536] This application also provides a computer storage medium storing one or more programs, which can be executed by one or more processors to implement the methods in this application.
[0537] Figure 21 is a schematic block diagram of a communication system provided in an embodiment of this application. As shown in Figure 21, the communication system 2100 includes a first network element 2110, an access network device 2120, and a second network element 2130.
[0538] The first network element 2110 can be used to implement the corresponding functions implemented by the first network element in the above method, and the first network element 2110 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.
[0539] The access network device 2120 can be used to implement the corresponding functions implemented by the access network device in the above method, and the access network device 2120 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.
[0540] The second network element 2130 can be used to implement the corresponding functions implemented by the second network element in the above method, and the second network element 1220 can be used to implement the corresponding functions implemented by the second network element in the above method. For the sake of brevity, these will not be elaborated here.
[0541] 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.
[0542] 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.
[0543] 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.
[0544] 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.
[0545] 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 network element or access network device.
[0546] This application also provides a computer program product, including computer program instructions.
[0547] When the computer program instructions are run on the computer, the computer executes the corresponding processes implemented by the network element or access network device in the various methods of the embodiments of this application. For the sake of brevity, they will not be described in detail here.
[0548] 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.
[0549] 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.
[0550] 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.
[0551] 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.
[0552] 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.
[0553] 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.
[0554] The methods disclosed in the several method embodiments provided in this application can be arbitrarily combined without conflict to obtain new method embodiments.
[0555] The features disclosed in the several product embodiments provided in this application can be arbitrarily combined without conflict to obtain new product embodiments.
[0556] 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.
[0557] 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.
[0558] 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.
[0559] 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.
[0560] 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 according to claim 2, wherein, The method further includes: The first network element sends a first message to the access network device, the first message including information related to the second connection.
4. The method according to claim 2, wherein, The method further includes: The first network element sends a first request message to the second network element; The second network element is the management network element associated with the access network device; The first 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.
5. The method according to claim 4, wherein, The first 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 second network element to identify the access network device.
6. The method according to any one of claims 3-5, 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.
7. The method according to any one of claims 3-6, wherein, Also includes: The first network element receives the second message through the second connection; The second message is used by the first network element to determine the binding relationship of the second connection.
8. The method according to claim 7, 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.
9. The method according to any one of claims 2-8, wherein, The first connection and the second connection are the same user plane connection.
10. The method according to any one of claims 2-9, wherein, The method further includes: The first network element sends a third message, which is used to configure the first session and / or the first task.
11. The method according to claim 10, wherein, The first network element sends the third message through the second connection; And / or, The first network element sends the third message through the control plane connection.
12. The method according to claim 10 or 11, wherein, The method further includes: The first network element receives a fourth message through the second connection. The fourth message is used to transmit 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 according to any one of claims 10-13, 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.
15. The method according to any one of claims 2-8, 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 according to claim 15, 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.
17. The method according to claim 1 or 2, wherein, The method further includes: The first network element sends a sixth message to the access network device, the sixth message being used to include relevant information about the first connection.
18. The method according to claim 1 or 2, wherein, The method further includes: The first network element sends a second request message to the second network element; The second network element is the management network element associated with the access network device; The second request information is used to request the second network element to send a sixth message to the access network device, and the sixth message includes information related to the first connection.
19. The method according to claim 18, wherein, The second 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 second network element to identify the access network device.
20. The method according to any one of claims 16-19, 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.
21. The method according to any one of claims 16-20, wherein, The method further includes: The first network element receives a 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.
22. The method according to claim 21, wherein, The seventh message is also used to confirm that the first connection has been established.
23. The method according to claim 21 or 22, wherein, The seventh message includes one or more of the following: The identification information of the first session; The identification information of the first task; The associated identification information The identification information of the access network device.
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: a sensing network element, a positioning and management function network element, a data collection network element, and a data management network element; The second network element is the registration management network element, and / or the mobility management network element.
26. 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.
27. The method according to claim 26, 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.
28. The method according to claim 27, wherein, The method further includes: The access network device receives a first message, which includes information related to the second connection.
29. The method according to claim 28, 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.
30. The method according to claim 28 or 29, 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.
31. The method according to claim 30, 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.
32. The method according to any one of claims 28-31, wherein, The first message comes from the first network element; or, the first message comes from the second network element, which is the management network element associated with the access network device. The second network element is used to receive a first request information sent by the first network element, and the first request information is used to request the second network element to send the first message to the access network device.
33. The method according to any one of claims 27-32, wherein, The first connection and the second connection are the same user plane connection.
34. The method according to claim 33, wherein, The method further includes: The access network device receives a third message, which is used to configure the first session and / or the first task.
35. The method according to claim 34, wherein, The third message is received via the second connection; and / or, the third message is received via the control plane connection.
36. The method according to claim 34 or 35, wherein, The access network device sends a fourth message through the second connection. The fourth message is used to transmit service data and / or service-related signaling.
37. The method of claim 36, wherein, The fourth message is also used to confirm the first session and / or the first task.
38. The method according to any one of claims 34-37, wherein, The third message, and / or the fourth message, includes one or more of the following: Identification information for the first session; The identification information for the first task; Associated identification information.
39. The method according to any one of claims 27-32, wherein, The first connection is established based on the second connection, and / or the address information of the first connection is different from the address information of the second connection.
40. The method according to claim 39, 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.
41. The method according to claim 26, wherein, The method further includes: The access network device receives a sixth message, which includes information related to the first connection.
42. The method according to claim 41, wherein, The sixth message originates from the first network element; or, The sixth message comes from the second network element, which is the management network element associated with the access network device; The second network element is used to receive the second request information sent by the first network element, and the second request information is used to request the second network element to send the sixth message to the access network device.
43. The method according to any one of claims 40-42, 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.
44. The method according to any one of claims 40-43, wherein, The method further includes: The access network device sends a seventh message to the first network element through the first connection. The seventh message is used to transmit service data and / or service-related signaling.
45. The method according to claim 44, wherein, The seventh message is also used to confirm that the first connection has been established.
46. The method according to claim 44 or 45, wherein, The seventh 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; The identification information of the access network device.
47. The method according to any one of claims 39-46, 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.
48. The method according to any one of claims 26-47, wherein, The first network element is one or more of the following: a sensing and management network element, a data collection network element, and a data management network element; The second network element is a mobility management network element, and / or an access and mobility management network element.
49. A data transmission method, the method comprising: The second network element receives the first request information or the second request information; The first request information is used to request the second network element to send a first message to the access network device. The first message includes information related to the second connection between the first network element and the access network element. The second 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.
50. The method according to claim 49, 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.
51. The method according to claim 49 or 50, 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.
52. The method according to any one of claims 49-51, wherein, The first 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 second network element to identify the access network device.
53. The method according to any one of claims 49-52, wherein, The second 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; Identification information for the first session; The identification information for the first task; Associated identification information; The identification information of the access network device is used by the second network element to identify the access network device.
54. The method according to any one of claims 49-53, 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.
55. The method according to any one of claims 49-54, 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.
56. 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.
57. The apparatus according to claim 56, 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.
58. The apparatus according to claim 57, wherein, The first communication unit is further configured to send a first message to the access network device, the first message including information related to the second connection.
59. The apparatus according to claim 57, wherein, The first communication unit is further configured to send a first request message to the second network element; The second network element is the management network element associated with the access network device; The first 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.
60. The apparatus according to claim 59, wherein, The first 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 second network element to identify the access network device.
61. The apparatus according to any one of claims 58-60, 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.
62. The apparatus according to any one of claims 58-61, wherein, The first communication unit is further configured to receive a second message through the second connection; the second message is used by the first network element to determine the binding relationship of the second connection.
63. The apparatus according to claim 62, 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.
64. The method according to any one of claims 57-63, wherein, The first connection and the second connection are the same user plane connection.
65. The apparatus according to any one of claims 57-64, wherein, The method further includes: The first communication unit is further configured to send a third message, the third message being used to configure the first session and / or the first task.
66. The apparatus according to claim 65, wherein, The first communication unit is further configured to send the third message via the second connection; and / or, via a control plane connection.
67. The apparatus according to claim 65 or 66, wherein, The first communication unit is further configured to receive a fourth message via the second connection, the fourth message being used to transmit service data and / or service-related signaling.
68. The apparatus according to claim 67, wherein, The fourth message is also used to confirm the first session and / or the first task.
69. The apparatus according to any one of claims 65-68, 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.
70. The apparatus according to any one of claims 57-63, 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.
71. The apparatus according to claim 70, wherein, The first communication unit 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.
72. The apparatus according to claim 56 or 57, wherein, The first communication unit is further configured to send a sixth message to the access network device, the sixth message being used to include relevant information about the first connection.
73. The apparatus according to claim 56 or 57, wherein, The first communication unit is further configured to send a second request message to the second network element; The second network element is the management network element associated with the access network device; The second request information is used to request the second network element to send a sixth message to the access network device, and the sixth message includes information related to the first connection.
74. The apparatus according to claim 73, wherein, The second 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 second network element to identify the access network device.
75. The apparatus according to any one of claims 71-74, 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.
76. The apparatus according to any one of claims 71-75, wherein, The first communication unit is further configured to receive a seventh message sent by the access network device through the first connection, the seventh message being used to transmit service data and / or service-related signaling.
77. [Correction 22.05.2025 according to Rule 91] The apparatus according to claim 76, wherein, The seventh message is also used to confirm that the first connection has been established.
78. [Amended according to Rule 91, 22.05.2025] The apparatus according to claim 76 or 77, wherein, The seventh message includes one or more of the following: The identification information of the first session; The identification information of the first task; The associated identification information The identification information of the access network device.
79. [Correction 22.05.2025 according to Rule 91] The apparatus according to any one of claims 70-78, 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.
80. [Correction 22.05.2025 according to Rule 91] The apparatus according to any one of claims 56-79, wherein, The first network element is one or more of the following: a sensing network element, a positioning and management function network element, a data collection network element, and a data management network element; The second network element is the registration management network element, and / or the mobility management network element.
81. [Corrected according to Rule 91, 22.05.2025] A data transmission apparatus, applied to an access network device, the apparatus comprising: The second 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.
82. [Correction 22.05.2025 according to Rule 91] The apparatus according to claim 81, 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.
83. [Correction 22.05.2025 according to Rule 91] The apparatus according to claim 82, wherein, The method further includes: The access network device receives a first message, which includes information related to the second connection.
84. [Correction 22.05.2025 according to Rule 91] The apparatus according to claim 83, 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.
85. [Correction 22.05.2025 according to Rule 91] The apparatus according to claim 83 or 84, wherein, The second communication unit 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.
86. [Correction 22.05.2025 according to Rule 91] The apparatus according to claim 85, 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.
87. [Correction 22.05.2025 according to Rule 91] The apparatus according to any one of claims 83-86, wherein, The first message originates from the first network element; or, The first message comes from the second network element, which is the management network element associated with the access network device; The second network element is used to receive a first request information sent by the first network element, and the first request information is used to request the second network element to send the first message to the access network device.
88. [Correction 22.05.2025 according to Rule 91] The apparatus according to any one of claims 82-87, wherein, The first connection and the second connection are the same user plane connection.
89. [Correction 22.05.2025 according to Rule 91] The apparatus according to claim 88, wherein, The second communication unit is further configured to receive a third message, the third message being used to configure a first session and / or a first task.
90. [Correction 22.05.2025 according to Rule 91] The apparatus according to claim 89, wherein, The third message is received via the second connection; And / or, The third message is received via a control plane connection.
91. [Correction 22.05.2025 according to Rule 91] The apparatus according to claim 89 or 90, wherein, The second communication unit is further configured to send a fourth message through the second connection, the fourth message being used to transmit service data and / or service-related signaling.
92. [Correction 22.05.2025 according to Rule 91] The apparatus according to claim 91, wherein, The fourth message is also used to confirm the first session and / or the first task.
93. [Correction 22.05.2025 according to Rule 91] The apparatus according to any one of claims 89-92, wherein, The third message, and / or the fourth message, includes one or more of the following: Identification information for the first session; The identification information for the first task; Associated identification information.
94. [Correction 22.05.2025 according to Rule 91] The apparatus according to any one of claims 82-87, wherein, The first connection is established based on the second connection, and / or the address information of the first connection is different from the address information of the second connection.
95. [Correction 22.05.2025 according to Rule 91] The apparatus according to claim 94, wherein, The second communication unit is further configured to receive a fifth message via the second connection, the fifth message including relevant information of the first connection.
96. [Correction 22.05.2025 according to Rule 91] The apparatus according to claim 81, wherein, The second communication unit is further configured to receive a sixth message, the sixth message including information related to the first connection.
97. [Correction 22.05.2025 according to Rule 91] The apparatus according to claim 96, wherein, The sixth message originates from the first network element; or, The sixth message comes from the second network element, which is the management network element associated with the access network device; The second network element is used to receive the second request information sent by the first network element, and the second request information is used to request the second network element to send the sixth message to the access network device.
98. [Correction 22.05.2025 according to Rule 91] The apparatus according to any one of claims 95-97, 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.
99. [Correction 22.05.2025 according to Rule 91] The apparatus according to any one of claims 95-98, wherein, The second communication unit is further configured to send a seventh message to the first network element through the first connection, the seventh message being used to transmit service data and / or service-related signaling.
100. [Correction 22.05.2025 according to Rule 91] The apparatus according to claim 99, wherein, The seventh message is also used to confirm that the first connection has been established.
101. [Correction 22.05.2025 according to Rule 91] The apparatus according to claim 99 or 100, wherein, The seventh 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; The identification information of the access network device.
102. [Correction 22.05.2025 according to Rule 91] The apparatus according to any one of claims 94-101, 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.
103. [Correction 22.05.2025 according to Rule 91] The apparatus according to any one of claims 81-102, wherein, The first network element is one or more of the following: a sensing and management network element, a data collection network element, and a data management network element; The second network element is a mobility management network element, and / or an access and mobility management network element.
104. [Corrected according to Rule 91, 22.05.2025] A data transmission apparatus, applied to a second network element, the apparatus comprising: The third communication unit is configured to receive a first request message or a second request message; The first request information is used to request the second network element to send a first message to the access network device, and the first message is used to establish a second connection between the first network element and the access network element; The second request information is used to request the second network element to send a sixth message to the access network device, the sixth message being used to establish a first connection between the first network element and the access network element.
105. [Correction 22.05.2025 according to Rule 91] The apparatus according to claim 104, 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.
106. [Correction 22.05.2025 according to Rule 91] The apparatus according to claim 104 or 105, 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.
107. [Correction 22.05.2025 according to Rule 91] The apparatus according to any one of claims 104-106, wherein, The first 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 second network element to identify the access network device.
108. [Correction 22.05.2025 according to Rule 91] The apparatus according to any one of claims 104-107, wherein, The second 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; Identification information for the first session; The identification information for the first task; Associated identification information; The identification information of the access network device is used by the second network element to identify the access network device.
109. [Correction 22.05.2025 according to Rule 91] The apparatus according to any one of claims 104-108, 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.
110. [Correction 22.05.2025 according to Rule 91] The apparatus according to any one of claims 104-109, 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.
111. [Corrected according to Rule 91, 22.05.2025] 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 48; or the method of any one of claims 49 to 55. A transceiver is used to receive and send information when exchanging information with other external devices.
112. [Correction 22.05.2025 based on Rule 91] 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 on which the chip is 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 48; or to implement the method as described in any one of claims 49 to 55. A transceiver is used to receive and send information during the exchange of information with a device or chip.
113. [Revised according to Rule 91, 22.05.2025] 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 48; or implements the method as claimed in any one of claims 49 to 55.
114. [Revised according to Rule 91, 22.05.2025] 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 48; or, implement the steps of the method as claimed in any one of claims 49 to 55.
115. [Revised according to Rule 91, 22.05.2025] 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 48; or to implement the method as claimed in any one of claims 49 to 55.
