Data interaction method, and device

Abstract

The present application belongs to the technical field of communications. Disclosed are a data interaction method, and a device. The data interaction method in the embodiments of the present application comprises: a first device sending a first request message to a second device, wherein the first request message is configured to request the establishment of a data plane connection with a target device, or is configured to acquire data from the target device on the basis of the data plane connection; and the first device receiving a response message of the first request message from the second device.

Description

Data interaction method and device

[0001] This application claims priority to the Chinese patent application filed with the China Patent Office on December 22, 2023, with application number 202311793579.7 and invention name “Data Interaction Method and Device”, the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The present application belongs to the field of communication technology, and specifically relates to a data interaction method and device. Background Art

[0003] The concept of the data plane has been proposed in current discussions of 6G network architecture. The data plane comprises core network data plane functions, radio access network data plane functions, and terminal data plane functions, providing end-to-end connectivity. The data plane is responsible for data control, including data collection coordination, data collection configuration, and data transmission configuration. It also handles data acquisition, data transmission, data preprocessing, data privacy and security, data analysis, data storage, and data services.

[0004] When the terminal obtains corresponding data from the core network device, that is, the core network device serves as the data source, how the terminal, access network device and core network device interact to establish a data plane connection and collect data is a technical problem that needs to be solved urgently. Summary of the Invention

[0005] The embodiments of the present application provide a data interaction method and device, in which a first device obtains data from a target device based on a data plane connection, with low implementation complexity.

[0006] In a first aspect, a data interaction method is provided, comprising:

[0007] The first device sends a first request message to the second device, where the first request message is used to request to establish a data plane connection with the target device, or to obtain data from the target device based on the data plane connection;

[0008] The first device receives a response message to the first request message from the second device.

[0009] In a second aspect, a data interaction method is provided, comprising:

[0010] The second device receives a first request message sent by the first device, where the first request message is used to request establishment of a data plane connection with the target device, or to obtain data from the target device based on the data plane connection;

[0011] The second device sends a response message to the first request message to the first device.

[0012] In a third aspect, a data interaction device is provided, comprising:

[0013] a sending module, configured to send a first request message to the second device, where the first request message is used to request establishment of a data plane connection with the target device, or to obtain data from the target device based on the data plane connection;

[0014] A receiving module is configured to receive a response message to the first request message from the second device.

[0015] In a fourth aspect, a data interaction device is provided, comprising:

[0016] a receiving module, configured to receive a first request message sent by a first device, where the first request message is used to request establishment of a data plane connection with a target device, or to obtain data from the target device based on the data plane connection;

[0017] A sending module is used to send a response message of the first request message to the first device.

[0018] In a fifth aspect, a first device is provided, which includes a processor and a memory, wherein the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the steps of the method described in the first aspect are implemented.

[0019] In the sixth aspect, a first device is provided, comprising a processor and a communication interface, wherein the communication interface is used to send a first request message to a second device, wherein the first request message is used to request to establish a data plane connection with the target device, or to obtain data from the target device based on the data plane connection; and receive a response message to the first request message from the second device.

[0020] In the seventh aspect, a second device is provided, which includes a processor and a memory, wherein the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the steps of the method described in the second aspect are implemented.

[0021] In the eighth aspect, a second device is provided, including a processor and a communication interface, wherein the communication interface is used to receive a first request message sent by a first device, the first request message being used to request to establish a data plane connection with a target device, or to obtain data from a target device based on the data plane connection; and to send a response message to the first request message to the first device.

[0022] In the ninth aspect, a readable storage medium is provided, on which a program or instruction is stored. When the program or instruction is executed by a processor, the steps of the method described in the first aspect are implemented, or the steps of the method described in the second aspect are implemented.

[0023] In the tenth aspect, a wireless communication system is provided, comprising: a first device and a second device, wherein the first device can be used to execute the steps of the method described in the first aspect, and the second device can be used to execute the steps of the method described in the second aspect.

[0024] In the eleventh aspect, a chip is provided, comprising a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the method described in the first aspect, or to implement the method described in the second aspect.

[0025] In the twelfth aspect, a computer program / program product is provided, which is stored in a storage medium and is executed by at least one processor to implement the steps of the data interaction method as described in the first aspect or the second aspect.

[0026] In an embodiment of the present application, a first device sends a first request message to a second device, where the first request message is used to request establishment of a data plane connection with a target device, or to obtain data from a target device based on the data plane connection; the first device receives a response message to the first request message from the second device, thereby establishing a data plane connection between the first device and the target device, or the first device obtains data from the target device based on the data plane connection, with low implementation complexity. BRIEF DESCRIPTION OF THE DRAWINGS

[0027] FIG1 is a schematic diagram of the architecture of a wireless communication system provided in an embodiment of the present application;

[0028] FIG2 is a schematic diagram of a data plane architecture provided in an embodiment of the present application;

[0029] FIG3 is a flow chart of a data interaction method according to an embodiment of the present invention;

[0030] FIG4 is a schematic diagram of one of the interaction flow diagrams of the data interaction method provided in an embodiment of the present application;

[0031] FIG5 is a second interactive flow diagram of the data interaction method provided in an embodiment of the present application;

[0032] FIG6 is a third interactive flow diagram of the data interaction method provided in an embodiment of the present application;

[0033] FIG7 is a second flow chart of the data interaction method provided in an embodiment of the present application;

[0034] FIG8 is a schematic diagram of a structure of a data interaction device according to an embodiment of the present application;

[0035] FIG9 is a second structural diagram of the data interaction device provided in an embodiment of the present application;

[0036] FIG10 is a schematic structural diagram of a communication device provided in an embodiment of the present application;

[0037] FIG11 is a schematic structural diagram of a terminal according to an embodiment of the present application;

[0038] FIG12 is a schematic diagram of a structure of a network side device according to an embodiment of the present application;

[0039] FIG13 is a second schematic diagram of the structure of the network side device according to an embodiment of the present application. DETAILED DESCRIPTION

[0040] The following will be combined with the accompanying drawings in the embodiments of this application to clearly describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field are within the scope of protection of this application.

[0041] The terms "first", "second", etc. in this application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the terms used in this way are interchangeable where appropriate, so that the embodiments of the present application can be implemented in an order other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same type, and do not limit the number of objects, for example, the first object can be one or more. In addition, "or" in this application represents at least one of the connected objects. For example, "A or B" covers three options, namely, Option 1: including A but not including B; Option 2: including B but not including A; Option 3: including both A and B. The character " / " generally indicates that the objects associated before and after are in an "or" relationship.

[0042] The term "indication" in this application can be either a direct indication (or explicit indication) or an indirect indication (or implicit indication). A direct indication can be understood as the sender explicitly informing the receiver of specific information, the operation to be performed, or the requested result, etc. in the instruction sent; an indirect indication can be understood as the receiver determining the corresponding information based on the instruction sent by the sender, or making a judgment and determining the operation to be performed or the requested result, etc. based on the judgment result.

[0043] It is worth noting that the technology described in the embodiments of the present application is not limited to the Long Term Evolution (LTE) / LTE-Advanced (LTE-A) system, but can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA) or other systems. The terms "system" and "network" in the embodiments of the present application are often used interchangeably, and the technology described can be used for the systems and radio technologies mentioned above, as well as for other systems and radio technologies. The following description describes a New Radio (NR) system for illustrative purposes, and NR terminology is used in most of the following description, but these technologies can also be applied to systems other than NR systems, such as 6th generation (6G) systems. th Generation, 6G) communication system.

[0044] FIG1 is a block diagram of a wireless communication system applicable to an embodiment of the present application. The wireless communication system includes a terminal 11 and a network-side device 12. The terminal 11 may be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer), a notebook computer, a personal digital assistant (PDA), a handheld computer, a netbook, an ultra-mobile personal computer (UMPC), a mobile internet device (MID), an augmented reality (AR), a virtual reality (VR) device, a robot, a wearable device (Wearable Device), an aircraft (Flight Vehicle), a vehicle-mounted device (VUE), a ship-mounted device, a pedestrian user equipment (PUE), a smart home (home appliances with wireless communication capabilities, such as refrigerators, televisions, washing machines, or furniture), a game console, a personal computer (PC), an ATM, or a self-service machine, or other terminal-side devices. Wearable devices include: smart watches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart bracelets, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, etc. Among them, the vehicle-mounted device can also be called a vehicle-mounted terminal, a vehicle-mounted controller, a vehicle-mounted module, a vehicle-mounted component, a vehicle-mounted chip or a vehicle-mounted unit, etc. It should be noted that the specific type of the terminal 11 is not limited in the embodiment of the present application. The network side device 12 may include an access network device or a core network device, wherein the access network device may also be called a radio access network (Radio Access Network, RAN) device, a radio access network function or a radio access network unit. The access network device may include a base station, a wireless local area network (WLAN) access point (AP) or a wireless fidelity (WiFi) node, etc.Among them, the base station can be referred to as Node B (NB), Evolved Node B (eNB), the next generation Node B (gNB), New Radio Node B (NR Node B), access point, Relay Base Station (RBS), Serving Base Station (SBS), Base Transceiver Station (BTS), radio base station, radio transceiver, Basic Service Set (BSS), Extended Service Set (ESS), Home Node B (HNB), Home Evolved Node B (home evolved Node B), Transmission Reception Point (TRP) or other appropriate terms in the field. As long as the same technical effect is achieved, the base station is not limited to specific technical vocabulary. It should be noted that in the embodiment of the present application, only the base station in the NR system is used as an example for introduction, and the specific type of the base station is not limited.

[0045] The core network equipment may include but is not limited to at least one of the following: core network node, core network function, mobility management entity (MME), access mobility management function (AMF), session management function (SMF), user plane function (UPF), policy control function (PCF), policy and charging rules function unit (PCRF), edge application service discovery function (EASDF), unified data management (UDM), unified data repository (UDR), home user server (HSS), centralized network configuration (CNC), network storage function (NRF), network exposure function (NEF), local NEF (L-NEF), binding support function (BSF), application function ( Function, AF), etc. It should be noted that in the embodiments of the present application, only the core network device in the NR system is introduced as an example, and the specific type of the core network device is not limited.

[0046] First, the technical terms and application scenarios involved in the embodiments of this application are introduced:

[0047] When a network device needs to establish a data plane connection with a terminal to obtain data from the terminal, multiple potential paths may exist. For example, the data plane connection can be based on a user plane path (user plane protocol stack), a control plane path (control plane protocol stack), or optionally, a newly defined data plane path (data plane protocol stack). However, it is currently unclear how the terminal and network device determine and negotiate the selection of a path to carry the data plane connection.

[0048] Data transmission on the data plane connection between the terminal and the network-side device may use a variety of data encoding methods, including JavaScript Object Notation (JSON), Abstract Syntax Notation One (ASN.1), Protocol Buffer (Protobuf), Extensible Markup Language (XML), Yet Another Markup Language (YAML), MessagePack, and Binary JSON (BSON). Each method has its own characteristics, as follows:

[0049] JSON: A lightweight data exchange format that's easy to read and write, supports multiple programming languages, and is commonly used in web applications. However, JSON is text-based, resulting in low data encoding and transmission efficiency.

[0050] ASN.1: It has the advantages of compact coding, type safety, and good interoperability, but it requires the use of specialized encoding and decoding tools and rules, making it difficult to implement.

[0051] Protocol Buffer: An efficient binary serialization format that supports multiple programming languages ​​and is commonly used in large-scale distributed systems.

[0052] XML: A markup language used to describe data that supports multiple programming languages ​​and is commonly used in web applications and data exchange.

[0053] YAML: A human-readable data serialization format for configuration files and data exchange, supporting multiple programming languages.

[0054] MessagePack: An efficient binary serialization format that supports multiple programming languages ​​and is faster and smaller than JSON.

[0055] BSON: A binary JSON format that supports more data types and better performance, commonly used in MongoDB databases.

[0056] However, it is not clear how the terminal and network-side devices select and negotiate data encoding methods based on different requirements.

[0057] Figure 2 shows the data plane architecture, the data plane (DP) connection between the terminal and the network side equipment, for example, the terminal is the data source;

[0058] DP-C and DP-U are two modules related to the data plane inside the terminal:

[0059] 1. DP-C is the data plane control module, which is used to control the establishment, modification and deletion of data plane related signaling.

[0060] 2. DP-U is the data plane forwarding module, which is used to collect, process and forward relevant data in the terminal.

[0061] Correspondingly, the core network side has corresponding network elements (such as the Data Plane Function (DPF)) corresponding to the above two modules in the terminal:

[0062] 1. DPF-C is the data plane control network element, which is used to control the establishment, modification and deletion of related signaling of the data plane.

[0063] 2. DPF-U is a data plane forwarding network element used to collect, process and forward relevant data from terminals, RAN or other data sources.

[0064] It should be noted that the network elements on the above-mentioned core network side can be other network element names, or be replaced by network elements with other similar functions, such as the Data Collection Coordination Function (DCCF) network element, or the Messaging Framework Adaptor Function (MFAF) network element.

[0065] Among them, the terminal's data plane related signaling (i.e., signaling controlled by the DP-C module) can interact with the core network side DPF-C based on different protocol stacks. For example, as shown in line 2 in Figure 2:

[0066] 1. Based on the existing CP plane protocol stack (such as the non-access stratum (NAS) and the underlying access layer AS protocol layer);

[0067] 2. Based on the newly added DP protocol stack (such as Data Stratum Protocol 1 (DsP1) and Packet Data Convergence Protocol (PDCP), where DsP1 is the data interface peer-to-peer protocol layer between the terminal and the RAN);

[0068] It should be noted that the DP plane protocol stack between the terminal and the network side may pass through (over) or not pass through the DsP1 protocol layer.

[0069] When passing through the DsP1 layer, the RAN can parse the DsP1 protocol layer, and can obtain and parse part or all of the information in the data transmitted by the terminal to the core network side, which is conducive to the data plane module in the RAN to obtain relevant information.

[0070] If the data does not pass through DsP1, RAN transparently transmits the data transmitted by the terminal to the core network side.

[0071] Similarly, the data forwarding of the terminal's data plane (i.e., data processed by the DP-U module) can interact with the core network DPF-U based on different protocol stacks. For example, as shown in line 1 in Figure 2:

[0072] 1. Based on the CP-side protocol stack (such as NAS and the underlying AS protocol layer);

[0073] 2. Based on the UP plane protocol stack (such as IP, Service Data Adaptation Protocol (SDAP), PDCP, etc.)

[0074] 3. Based on the DP plane protocol stack (such as DsP1, PDCP, etc., where DsP1 is the data plane peer protocol layer between the terminal and RAN)

[0075] Among them, the DP plane protocol stack is a newly defined protocol stack exclusively for the data plane, which conforms to the new characteristics of data transmission on the data plane, such as massive data transmission, large bandwidth, large data segmentation, simple encapsulation format, and streamlined encryption.

[0076] Optionally, DsP1-C and DsP1-U in FIG2 may be absent;

[0077] Optionally, DsP1-C and DsP1-U can be combined into one;

[0078] Optionally, the DP-U and DP-C paths may be combined into one.

[0079] Alternatively, FIG2 takes the separation of DP-C and DP-U, and the separation of DPF-C and DPF-U as an example, but in fact DP-C and DP-U can be combined, and DPF-C and DPF-U can also be combined.

[0080] Optionally, in the embodiment of the present application, the data source (Data source) includes at least one of the following: terminal, RAN, core network function (Core Network Network Function, CN NF), operation and maintenance management (OAM), data storage network element (such as analytical data storage function (ADRF)), application layer function (AF), etc. The modules that generate data in the terminal include but are not limited to business data modules and basic public data modules such as sensing, artificial intelligence (AI), and positioning. The data source in RAN can include access network data plane equipment. The data source in CN includes but is not limited to sensing function, data storage function (data storage, such as ADRF), AI-related equipment (such as network data analysis function (NWDAF)), etc. The data source of AF includes but is not limited to trusted AF, untrusted AF, etc. Among them, the data source includes data sources connected to the service-oriented architecture (such as CN NF, OAM, etc.) and sources that are not connected to the service-oriented architecture (such as terminals, RAN, etc.).

[0081] Data consumers include at least one of the following: terminal, RAN, CN NF, OAM, ADRF, AF, etc. Data consumers include consumers connected to the service-based architecture (such as CN NF, OAM, etc.) and consumers not connected to the service-based architecture (such as terminal, RAN, etc.).

[0082] Optionally, the architecture of the embodiment of the present application may not fully realize network service, that is, some devices or network elements (such as terminals, RAN, certain AFs, etc.) are not service-oriented, and they still communicate with other devices in the network (including service-based architecture (SBA) network element devices) through point-to-point interfaces.

[0083] For example, when a terminal acts as a data consumer, how to agree on the path and processing method for signaling and data transmission between the terminal, access network equipment and core network CN in the process of establishing a data plane connection, so that the terminal can obtain the corresponding data from the CN data plane network elements in an appropriate and efficient manner, is a technical problem that needs to be solved.

[0084] The data interaction method provided in the embodiments of the present application is described in detail below through some embodiments and their application scenarios in conjunction with the accompanying drawings.

[0085] Referring to FIG3 , an embodiment of the present application provides a data interaction method. The execution subject of this embodiment is a first device. The method includes:

[0086] Step 101: A first device sends a first request message to a second device, where the first request message is used to request establishment of a data plane connection with a target device, or to obtain data from the target device based on the data plane connection.

[0087] Step 102: The first device receives a response message to the first request message from the second device.

[0088] Optionally, the first device includes at least one of a terminal and an access network device.

[0089] Optionally, the second device includes at least one of an access network device and a core network device.

[0090] Optionally, the target device includes at least one of an access network device and a core network device.

[0091] Specifically, the first device may send a first request message to the second device based on the data request of the data consumer device, where the second request message is used to request establishment of a data plane connection with the first device, or to obtain data from the target device based on the data plane connection.

[0092] Optionally, establishing the data plane connection may involve selecting a path on an existing path between the first device and the target device and establishing the data plane connection, or directly creating a path between the first device and the target device and establishing the data plane connection. Based on the first request message, the second device establishes a data plane connection between the first device and the target device; or, based on the first request message, the second device sends a data collection request message to the target device, whereupon the target device obtains the data and sends it to the first device via the data plane connection. Optionally, the target device may be the second device, or another device in the network domain to which the second device belongs, such as another network element in the core network.

[0093] The second device sends a response message to the first request message to the first device, and the first device receives the response message.

[0094] For example, the first device is a terminal, the second device can be a core network device (such as DPF-C), and the target device can be a core network device (such as DPF-U); the first device is an access network device, the second device is a core network device (such as DPF-C), and the target device is a core network device (such as DPF-U).

[0095] For example, the first device is a terminal, the second device may be an access network device, and the target device may be an access network device or a core network device.

[0096] In the method of this embodiment, a first device sends a first request message to a second device, where the first request message is used to request establishment of a data plane connection with a target device, or to obtain data from the target device based on the data plane connection; the first device receives a response message to the first request message from the second device, thereby establishing a data plane connection between the first device and the target device, or the first device obtains data from the target device based on the data plane connection, with low implementation complexity.

[0097] Optionally, the first request message includes at least one of the following: first path information of data plane control signaling; second path information of data plane data forwarding; a first data encoding method; and a first data encryption method.

[0098] Specifically, the first path information, the second path information, the first data encoding method, and the first data encryption method included in the first request message may be selected or determined by the second device.

[0099] The following description is made by taking the first device as a terminal and the second device as a core network device as an example, for example, the second device is a DPF:

[0100] 1. First path information of data plane control signaling recommended by the terminal: indicates the preferred first path information to the DPF-C. The first path is used to transmit data plane related control signaling.

[0101] Optionally, the first path may be expressed as: a CP plane path, a data plane control DP-C plane path. The first path may also be expressed as the protocol layers that the data plane signaling needs to pass through (such as NAS-PDCP-layer 2 protocol-layer 1 protocol, or DsP1-C-PDCP-layer 2 protocol-layer 1 protocol).

[0102] 2. Information about the second path recommended by the terminal for forwarding data plane data: indicates to the DPF-C information about the second path preferred by the terminal. The second path is used to forward data plane data.

[0103] Optionally, the second path may be expressed as: CP plane path, UP plane path, data plane forwarding DP-U plane path. The second path may also be expressed as the protocol layer that needs to be passed through for forwarding data plane related data (such as NAS-PDCP-layer 2 protocol-layer 1 protocol; or, SDAP-PDCP-layer 2 protocol-layer 1 protocol; or, DsP1-U-PDCP-layer 2 protocol-layer 1 protocol).

[0104] 3. The first data encoding method recommended by the terminal: including but not limited to the data serialization method used to instruct the DPF-C to use when reporting data, such as ASN.1, Protobuf, JSON, and others.

[0105] 4. The first data encryption method recommended by the terminal, including but not limited to indicating whether the data reported by the DPF-C needs to be encrypted.

[0106] In the above implementation, by including at least one of the following items in the first request message: first path information of data plane control signaling; second path information of data plane data forwarding; first data encoding method; first data encryption method, it is possible to establish a data plane connection or obtain data between the first device and the second device with low implementation complexity.

[0107] Optionally, a data consumer device (such as another terminal, service function (SF) or AF) requests data from the first device (such as a terminal), an internal module of the terminal generates an interaction process, and the data consumption module (such as a high-level business module, a sensing module) initiates a data request to the DP-C module to obtain certain business data or basic public data from the network.

[0108] Optionally, the method further includes:

[0109] The first device receives data sent from the target device through the data plane connection.

[0110] Optionally, before the first device receives the data sent from the target device through the data plane connection, the method may further include:

[0111] The first device sends a second request message to the second device, where the second request message is used to request the data.

[0112] Specifically, the first request message may be a request to establish a data plane connection, and the first device may request the second device to obtain data from the target device through the second request message, and then the first device receives the data sent from the target device through the data plane connection.

[0113] Optionally, the method further includes:

[0114] The first device determines the first request message.

[0115] Specifically, the terminal determines the first request message, for example, the DP-C module of the terminal needs to determine the content included in the first request message.

[0116] Optionally, the first device determines the first request message, including:

[0117] The first device determines the first path information of the data plane control signaling based on a first factor, wherein the first factor includes at least one of the following:

[0118] The forwarding delay requirement of the data plane control signaling;

[0119] Whether the data plane control signaling needs to be parsed by the access network device.

[0120] Specifically, the first device determines the first path information of the data plane control signaling according to a first factor. The first factor includes at least one of the following:

[0121] (1) Forwarding delay requirements for data plane control signaling. For example, when the delay requirement is high, the data plane control signaling path needs to streamline protocol layers, skip encryption and decryption, etc. In this case, the protocol stack corresponding to the newly defined streamlined DP plane path or the CP plane protocol stack can be used; conversely, the data plane control signaling path can utilize the UP plane protocol stack.

[0122] (2) Whether the data plane control signaling needs to be parsed by the access network equipment RAN. For example, when it needs to be parsed by the RAN, the signaling needs to be processed by the RAN data plane peer protocol layer (such as DsP, DsP1, PDCP, layer 2 protocol, layer 1 protocol; or DsP, DsP1, RRC, PDCP, layer 2 protocol, layer 1 protocol, which can be considered to belong to the DP plane path and has DsP1 layer processing); otherwise, the signaling does not need to be processed by the RAN data plane peer protocol layer (such as DsP, PDCP, layer 2 protocol, layer 1 protocol (i.e., through the DP plane path); or DsP, NAS, RRC, PDCP, layer 2 protocol, layer 1 protocol (i.e., through the CP plane path)).

[0123] Optionally, the first device determining the first request message includes:

[0124] The first device determines the second path information for forwarding the data plane data based on a second factor, wherein the second factor includes at least one of the following:

[0125] Obtaining the latency requirement of the data plane data;

[0126] The amount of data to be transferred;

[0127] Whether the data plane data needs to be parsed by the access network device.

[0128] Specifically, the first device determines the second path information for forwarding the data plane data based on a second factor. The second factor includes at least one of the following:

[0129] (1) Delay requirement for obtaining data plane data: For example, when the required delay for obtaining data plane data is lower than a preset threshold, the first device selects the CP plane path as the data forwarding path.

[0130] (2) Amount of data to be transmitted: For example, when the amount of data is higher than a preset threshold, the first device selects the UP plane path as the data forwarding path.

[0131] (3) Whether the data plane data needs to be parsed by the RAN. For example, when the data plane data needs to be acquired and parsed by the RAN-side data plane function, the first device selects the DP plane path. Optionally, the DP plane path also needs to undergo encapsulation and parsing processing at the DsP1 protocol layer.

[0132] Optionally, the first device determining the first request message includes:

[0133] The first device determines the first data encoding mode based on a third factor; wherein the third factor includes at least one of the following:

[0134] Coding delay requirement of the data plane data;

[0135] Coding efficiency requirements for the data plane data;

[0136] Readability requirements of the data plane data;

[0137] Security requirements for the data plane data;

[0138] The reliability requirements of the data plane data.

[0139] Specifically, the first device determines the first data encoding method based on a third factor. The third factor includes at least one of the following:

[0140] (1) Data plane data encoding delay requirements: For example, when the encoding delay requirements are high, the first device may select a serialization method corresponding to binary encoding (such as Protocol Buffer, etc.).

[0141] (2) Coding efficiency requirements for data plane data: For example, when the coding efficiency requirement is high, the first device may select a serialization method corresponding to binary coding (such as Protocol Buffer, etc.).

[0142] (3) Data readability requirements for data plane data. For example, when the data is required to be highly human-readable, the first device may select a basic text data serialization method (such as JSON, XML, etc.)

[0143] (4) Data security requirements on the data plane: For example, when data transmission requires a certain level of security, the first device may select a serialization method based on ASN.1.

[0144] (5) Data reliability requirements on the data plane: For example, when data transmission requires a certain degree of reliability, the first device may select a serialization method based on ASN.1.

[0145] Optionally, the DP-C module determines the first data encryption mode, for example, determining whether to encrypt or not encrypt or the encryption mode based on delay requirements, security requirements, etc.

[0146] In the above implementation, the first device determines the first request message based on its own needs, such as at least one of the first factor, the second factor, and the third factor, and then establishes a data plane connection with the target device based on the first request message, or obtains data from the target device through the data plane connection, thereby achieving low complexity and high reliability.

[0147] Optionally, the first path information includes at least one of the following: control plane path indication information, user plane path indication information, data plane control path indication information, and information about protocol layers that data plane signaling needs to pass through.

[0148] Optionally, the second path information includes at least one of the following: control plane path indication information, user plane path indication information, data plane forwarding path indication information, and information about protocol layers that the data plane needs to pass through when forwarding data.

[0149] In the embodiment of the present application, the control plane path indication information may be, for example, information related to the CP path, the user plane path indication information may be, for example, information related to the UP path, the data plane control path indication information may be information related to the DP-C path, and the data plane forwarding path indication information may be information related to the DP-U path. It is understood that the control plane path indication information may be information indicating the CP path, the user plane path indication information may be information indicating the UP path, the data plane control path indication information may be information indicating the DP-C path, and the data plane forwarding path indication information may be information indicating the DP-U path.

[0150] Optionally, the first request message further includes at least one of the following information of the data plane data:

[0151] The type of data collected;

[0152] Data filtering information, used to filter required data during data collection;

[0153] Data reporting condition information;

[0154] How your data is processed;

[0155] Data storage format;

[0156] The data filtering information includes at least one of the following:

[0157] Location-limited information of the data collection object;

[0158] Time limit information for data collection;

[0159] Business or application qualification information, used to qualify the business or application that generates the data;

[0160] The data reporting condition information includes at least one of the following:

[0161] Time period information for data reporting;

[0162] Event information that triggers data reporting.

[0163] Specifically, the first request message may also include other information, such as:

[0164] (1) Data type, for example, represented by a data type list, indicating the type of data to be collected. Specifically, the data type is used to indicate what type of data to be collected, and may be in the form of a list of data. For example, the collected data includes but is not limited to business data and basic public data such as sensing, AI, and location in the terminal.

[0165] (2) Data filter information (location, time, business or application, etc.), which is used to indicate the scope and conditions for data collection and can further filter out the required data based on the set filter parameters. Data filter information includes at least one of the following:

[0166] (2-1) Location information (location) limits the location where the data was generated. This information can be expressed in granularity, such as a cell, a tracking area (TA), or latitude and longitude. For example, if the location information value is a cell area, the target device will only collect data generated within this area.

[0167] (2-2) Time limit information (time) is used to limit the time when data is generated. It can include the start and end time of collection. For example, the time limit information value is 08:00 for the start time and 18:00 for the end time. Then, when the target device collects data, it will only collect data generated during this time period.

[0168] (2-3) Business or application qualification information (application) is used to limit the business or application that generates the data. This business or application qualification information includes, for example, the name of the business or application and its identification information. For example, if the application qualification information value is "xx music," the target device will only collect data generated by this application during data collection.

[0169] (3) Data reporting information, which is used to indicate the conditions for data reporting. The data reporting information includes at least one of the following:

[0170] (3-1) Data reporting period information: This period information is used to indicate that the data collected within a preset time period will be reported according to a certain period and set the period. For example, if the period information value is daily, the terminal will report the data for that day every day.

[0171] (3-2) Event information that triggers data reporting, which indicates that the terminal should report data when a target time is reached or when a target event condition is met. For example, event information could be: the data volume reaches a threshold at a certain time point, or the terminal moves to a certain target location.

[0172] (4) Data processing method, which indicates how the final data must be processed before being stored on the network. For example, if the network expects the data to be the maximum value within a certain period of time, then the maximum value will be found and uploaded for the collected data. Other data processing methods can include: average, variance, minimum, averaging, normalization, etc.

[0173] (5) Data storage format, which indicates the format in which the final data is stored in the network. For example, if the network expects data to be stored in integer format, then the collected decimal / floating point data must be converted to integers before being stored. Other data storage formats can include integers, decimals, floating point numbers, 16-bit floating point numbers, 8-bit floating point numbers, and string types.

[0174] Optionally, the above-mentioned specific information related to the requested data can be included in the first request message and sent, or can be included in other subsequent request messages and sent (such as the second request message), which is not limited in this embodiment of the present application.

[0175] Optionally, the second device (such as DPF-C) verifies the data acquisition-related authorization information of the terminal.

[0176] Specifically, the DPF-C may send a contract data acquisition request or an authorization verification request message to the UDM or the authentication server function (AUSF), etc., which carries the terminal ID for verifying whether the terminal has the right to obtain the requested specific data.

[0177] Optionally, the second device (eg, DPF-C) and the third device (eg, policy control network element (eg, PCF)) establish / modify a data collection policy association (data collection policy association) corresponding to the data plane of the first device.

[0178] Specifically, the second device decides to establish a data collection policy corresponding to the data plane of the first device;

[0179] The second device sends a policy association establishment request to the third device;

[0180] The third device feeds back the requested data collection policy information corresponding to the data plane of the first device to the second device.

[0181] Optionally, the second device obtains data collection policy information from the third device;

[0182] The data collection policy information includes at least one of the following:

[0183] Data status;

[0184] Anonymity indication information, used to indicate whether the collected data is anonymous;

[0185] A path type, used to indicate a path type accepted or supported by the first device when acquiring data;

[0186] Encoding method;

[0187] Encryption method.

[0188] The data collection policy information corresponding to the data plane of the first device may be used to instruct the second device (such as DPF-C and DPF-U) on how to collect data. The data collection policy information corresponding to the data plane of the first device includes at least one of the following information:

[0189] Data status indicates the state of the collected data, i.e., whether the data is raw data or processed data. Raw data refers to unprocessed data, maintaining the format in which it was collected. Processed data refers to data that has undergone data preprocessing. Data preprocessing operations can include data cleaning, data integration, data reduction, and data transformation.

[0190] Anonymity indication information is used to indicate whether the collected data is anonymous. If the data is anonymous, the second device may only collect the data without knowing which first device / user the data belongs to. The identification information corresponding to the data may be the processed first device identification or identification information mapped based on the network element. This anonymization step may be performed by the first device at the time of reporting, or by the second device or a network element during reporting.

[0191] The path type is used to indicate a path mode that the first device can accept / support when acquiring data, which can be acquired through a user plane (UP), a control plane (CP), a data plane (DP), etc.

[0192] The encoding method is used to indicate, including but not limited to, the data serialization method used by the target device when sending data to the first device, and may include, for example, ASN.1, Protocol Buffer, JSON, and others.

[0193] The encryption method includes, but is not limited to, indicating whether data sent by the target device to the first device needs to be encrypted.

[0194] Optionally, the first device sending a first request message to the second device includes:

[0195] The first device sends the first request message to the second device based on the first information;

[0196] The first information includes at least one of the following: the address, identification, and port information of the target device.

[0197] Optionally, the first information is obtained by the first device from the second device; or,

[0198] The first information is obtained by the first device through a domain name system DNS query.

[0199] Specifically, before the first device (such as the DP-U module of the terminal) obtains data from the target device (such as the DPF-U) using the UP path, it needs to know at least one of the address, identification and port information of the target device.

[0200] Optionally, a way to obtain the first information includes but is not limited to any of the following:

[0201] a) the first information is obtained by the first device from the second device, for example, in a message sent by the DPF-C to the terminal, carrying at least one of the address, identifier, and port information of the target device (such as the DPF-U);

[0202] b) The first device queries at least one of the address, identifier, and port information of the target device (such as DPF-U) through DNS.

[0203] Optionally, the DPF-C determines whether to accept the first request message according to the authorization information for data acquisition of the first device and the availability (availability, etc.) of the requested data, thereby sending a response message to the first device.

[0204] Optionally, the response message to the first request message includes at least one of the following:

[0205] Third path information for data plane control signaling;

[0206] Fourth path information for data plane data forwarding;

[0207] a second data encoding method;

[0208] Second data encryption method.

[0209] Specifically, the second device sends a response message to the first request message to the first device, where the response message indicates whether the second device accepts the first request message. Optionally, the response message is sent to the first device via a third device (such as an AMF), and optionally, the response message also includes identification information of the first device.

[0210] If the second device accepts the first request message, the response message may include at least one of the following information:

[0211] Third path information of the data plane control signaling selected by the second device;

[0212] Fourth path information for forwarding data on the data plane selected by the second device;

[0213] a second data encoding mode selected by the second device;

[0214] The second data encryption method selected by the second device.

[0215] For example, the third path information and the fourth path information include indication information of the CP path or the protocol stack corresponding to the CP path, that is, the data plane connection is based on the control plane path; the third path information and the fourth path information include indication information of the UP path or the protocol stack corresponding to the UP path, that is, the data plane connection is based on the user plane path; the third path information and the fourth path information include indication information of the DP forwarding path or the protocol stack corresponding to the DP forwarding path, that is, the data plane connection is based on the data plane forwarding path.

[0216] Optionally, the first path information and the third path information may be the same or different, and the second path information and the fourth path information may be the same or different.

[0217] Optionally, the first device determines the first request message, including:

[0218] The data plane control module of the first device determines the first request message;

[0219] The method further comprises:

[0220] The data plane control module of the first device forwards the first request message to the data plane forwarding module of the first device;

[0221] The first device sending a first request message to the second device includes:

[0222] The data plane forwarding module of the first device sends the first request message to the second device.

[0223] Specifically, the data plane-related modules within the first device interact with each other, including at least one of the following:

[0224] The data plane control module DP-C determines the content of the first request message;

[0225] DP-C forwards the first request message to the data plane forwarding module DP-U;

[0226] The DP-U establishes a data plane connection with the target device based on the first request message.

[0227] Optionally, the first request message may be used to request establishment of a data plane connection, but does not carry path information selected by the terminal, etc. The DP-C module receives the content of a response message to the first request message from the NAS module (optionally, it may include path information selected by the DPF-C, etc.);

[0228] The DP-C module determines, based on the content of the response message to the first request message and at least one of the first factor, the second factor, and the third factor, at least one of the following information selected by the terminal: first path information of data plane control signaling, second path information of data plane data forwarding, a first data encoding mode, and a first data encryption mode;

[0229] The DP-C sends at least one of the following information selected by the terminal to the DP-U: first path information of data plane control signaling, second path information of data plane data forwarding, a first data encoding method, and a first data encryption method.

[0230] Optionally, in the case that the DPF-C accepts the first request message, the DPF-C requests the data requested by the terminal from a data source, and the data source may send the data to the DPF-U.

[0231] Alternatively, if the DPF-C determines that the data has already been acquired and stored, the step of acquiring the data from the data source may be omitted. For example, if the DPF-U or ADRF has stored the data, the DPF-C may extract the data from the DPF-U.

[0232] Optionally, when DPF-C selects the CP plane path as the data plane data forwarding path, DPF-C sends the data obtained from the data source or DPF-U / ADRF to AMF so that AMF forwards the data to the terminal.

[0233] Optionally, the above data is processed in the selected data encoding method and data encryption method and then sent.

[0234] Optionally, before feeding back the requested data to the terminal, if the terminal is in an idle state, the AMF may trigger a service request process (such as a Network Triggered Service Request process) to activate the terminal, for example, changing the terminal from an idle state to an active state.

[0235] Optionally, the AMF sends a downlink NAS message to the terminal, and the downlink NAS message carries the data requested by the terminal.

[0236] Exemplarily, as shown in FIG4 , where the MM function is a Mobility Management (MM) function and the PC function is a Policy Control (PC) function, the method includes:

[0237] Step 1: Interaction between modules within the terminal;

[0238] Step 2: The terminal sends a data request / subscription to the DPF (or DPF-C), for example, carrying the terminal ID, requested data, recommended data plane control signaling path, data forwarding path (such as CP), data encoding method, etc.

[0239] Step 3: Terminal data collection authorization;

[0240] Step 4: The DPF (or DPF-C) determines a data collection response, including, for example, the selected data plane control signaling path, the data forwarding path (e.g., CP), the data encoding method, etc.

[0241] Step 5: The DPF (or DPF-C) sends a data request / subscription response to the terminal, including, for example, the selected data plane control signaling path, the data forwarding path (e.g., CP), the data encoding method, etc.

[0242] Step 5a: Interaction with the data plane DP module inside the terminal;

[0243] Step 6: DPF-U collects data, for example, by interacting with DPF-C and data sources;

[0244] Step 6a: DPF-U or ADRF stores data;

[0245] Step 7: The DPF (or DPF-C) performs data notification (e.g., transmits data after data encoding) via the CP path.

[0246] Step 8: Network-triggered service request.

[0247] Step 9: AMF sends data notification to the terminal through the CP path.

[0248] Optionally, the method further includes:

[0249] The first device triggers establishment of the data plane connection with the target device according to the second path information or the fourth path information.

[0250] Specifically, the first request message may be used to request data acquisition, and the first device may initiate a process of establishing a data plane connection after the first request message, which may be achieved by the first device initiating other request messages to the second device.

[0251] Optionally, when the data plane connection is based on a user plane path, the first request message further includes at least one of the following:

[0252] Identification information corresponding to the user plane path;

[0253] address information or identification information of the first device corresponding to the user plane path;

[0254] The port information of the first device corresponding to the user plane path.

[0255] Specifically, the data plane data forwarding path recommended by the first device to the second device, or selected by the second device itself, is a UP plane path, or a protocol layer corresponding to the UP plane path.

[0256] The second path information of the data plane data forwarding selected by the first device and carried in the first request message by the first device is set to the UP plane path, or the protocol layer corresponding to the UP plane path.

[0257] Optionally, as shown in FIG5 , the first request message may further carry at least one of the following information:

[0258] a) Identification information corresponding to the user plane UP path (such as PDU session ID, QoS flow ID);

[0259] b) the address information or identification information of the first device corresponding to the data plane path, i.e., the address information or identification information (such as the IP address or Ethernet address of the terminal) assigned to the first device corresponding to the UP path;

[0260] c) Port information of the first device corresponding to the data plane path, that is, the port information of the first device allocated corresponding to the UP path (such as the terminal port number (port num)).

[0261] The information carried in the above response message is used to inform the second device that the first device will use the UP path to obtain data.

[0262] Furthermore, the first device (eg, DP-U module) obtains data from the target device (eg, DPF-U) based on the selected UP path.

[0263] Optionally, the DPF-C sends a notification message to the DPF-U, which includes a) carried in the first request message.

[0264] , b) and c) of the content.

[0265] Optionally, step 1a in FIG. 5 may occur after step 5, and the terminal needs to send another ACK to the DPF-C to inform the terminal of its assigned IP address and port number, etc.

[0266] Optionally, when the data plane connection is based on a data plane forwarding path, the first request message further includes at least one of the following:

[0267] Identification information corresponding to the data plane path;

[0268] address information or identification information of the first device corresponding to the data plane path;

[0269] The port information of the first device corresponding to the data plane path.

[0270] Specifically, the data plane data forwarding path recommended by the first device to the second device, or selected by the second device itself, is the DP plane path, or the protocol layer corresponding to the DP plane path.

[0271] The data plane data forwarding path selected by the first device and carried in the first request message is set to the DP plane path, or the protocol layer corresponding to the DP plane path.

[0272] Exemplarily, as shown in FIG5 , the method includes:

[0273] Step 1: Interaction between modules within the terminal;

[0274] Step 1a: Terminal PDU session establishment;

[0275] Step 2: The terminal sends a data request / subscription to the DPF (or DPF-C), for example, carrying the terminal ID, requested data, recommended data plane control signaling path, data forwarding path (for example, UP, the path information may include PDU session ID, terminal IP, etc.), data encoding method, etc.

[0276] Step 3: Terminal data collection authorization;

[0277] Step 4: The DPF (or DPF-C) determines the data collection response, including, for example: the selected data plane control signaling path, the data forwarding path (e.g., UP, where the path information may include PDU session ID, terminal IP, etc.), the data encoding method, etc.

[0278] Step 4a: DPF-C sends a data request / subscription to DPF-U, which may include the terminal ID, requested data, recommended data plane control signaling path, data forwarding path (e.g., UP, the path information may include PDU session ID, terminal IP, etc.), data encoding method, etc.

[0279] Step 5. The DPF (or DPF-C) sends a data request / subscription response to the terminal, including, for example, the selected data plane control signaling path, the data forwarding path (e.g., UP, the path information may include PDU session ID, terminal IP, etc.), data encoding mode, etc.

[0280] Step 5a: Interaction with the data plane DP module inside the terminal;

[0281] Step 6: DPF-U collects data, for example, by interacting with DPF-C and data sources;

[0282] Step 6a: DPF-U or ADRF stores data;

[0283] Step 7: The DPF (or DPF-C) performs data notification (eg, transmits data after data encoding) via the UP path.

[0284] Furthermore, optionally, as shown in FIG6 , the first request message may also carry at least one of the following information:

[0285] a) Identification information corresponding to the DP path (such as DP session ID or QoS flow ID);

[0286] b) address information or identification information of the first device corresponding to the data plane path, for example, address information (such as the IP address or Ethernet address corresponding to the terminal DP session) or identification information assigned to the first device corresponding to the DP path;

[0287] c) Port information of the first device corresponding to the data plane path, for example, port information (for example, terminal port number) allocated to the first device corresponding to the DP path.

[0288] The information carried in the above first request message is used to inform the second device that the first device will use the DP path to obtain data.

[0289] Furthermore, the second device (such as DPU-U) sends the acquired data to the first device based on the selected DP path.

[0290] Exemplarily, as shown in FIG6 , the method includes:

[0291] Step 1: Interaction between modules within the terminal;

[0292] Step 2: The terminal sends a data request / subscription to the DPF (or DPF-C), for example, carrying the terminal ID, requested data, recommended data plane control signaling path, data forwarding path (for example, UP, the path information may include PDU session ID, terminal IP, etc.), data encoding method, etc.

[0293] Step 3: Terminal data collection authorization;

[0294] Step 4: The DPF (or DPF-C) determines the data collection response, including, for example: the selected data plane control signaling path, the data forwarding path (e.g., UP, where the path information may include PDU session ID, terminal IP, etc.), the data encoding method, etc.

[0295] Step 4a. DPF-C sends a data request / subscription to DPF-U, for example, carrying the terminal ID, requested data, recommended data plane control signaling path, data forwarding path (for example, DP, DsP1 or through RAN, the path information may include the terminal DP IP or RAN DP IP, etc.), data encoding method, etc.

[0296] Step 5. The DPF (or DPF-C) sends a data request / subscription response to the terminal, including, for example, the selected data plane control signaling path, the data forwarding path (for example, DP, DsP1 or through RAN, the path information may include the terminal DP IP or RAN DP IP, etc.), the data encoding method, etc.

[0297] Step 5a: Interaction with the data plane DP module inside the terminal;

[0298] Step 6: DPF-U collects data, for example, by interacting with DPF-C and data sources;

[0299] Step 6a: DPF-U or ADRF stores data;

[0300] Step 7: The DPF (or DPF-C) performs data notification (eg, transmits data after data encoding) via the DP path.

[0301] In the examples of Figures 4 to 6 above, Figure 4 uses the CP path, Figure 5 uses the UP path, and Figure 6 uses the DP path.

[0302] Referring to FIG. 7 , an embodiment of the present application provides a data interaction method. The execution subject of this embodiment is a second device. The method includes:

[0303] Step 201: A second device receives a first request message sent by a first device, where the first request message is used to request establishment of a data plane connection with a target device, or to obtain data from the target device based on the data plane connection.

[0304] Step 202: The second device sends a response message to the first request message to the first device.

[0305] Optionally, the first request message includes at least one of the following: first path information of data plane control signaling; second path information of data plane data forwarding; a first data encoding method; and a first data encryption method.

[0306] Optionally, the method further includes:

[0307] When the second device is the target device, the second device sends data to the first device through the data plane connection.

[0308] Optionally, the method further includes:

[0309] The second device obtains the data from a data source or a third device (DPF-U), for example, the second device is a target device in this case.

[0310] Optionally, the method further includes:

[0311] The second device receives a second request message sent by the first device, where the second request message is used to request the data.

[0312] Optionally, the first path information includes at least one of the following: control plane path indication information, user plane path indication information, data plane control path indication information, and information about protocol layers that data plane signaling needs to pass through.

[0313] Optionally, the second path information includes at least one of the following: control plane path indication information, user plane path indication information, data plane forwarding path indication information, and information about protocol layers that the data plane needs to pass through when forwarding data.

[0314] Optionally, the first request message further includes at least one of the following information of the data plane data:

[0315] The type of data collected;

[0316] Data filtering information, used to filter required data during data collection;

[0317] Data reporting condition information;

[0318] How your data is processed;

[0319] Data storage format;

[0320] The data filtering information includes at least one of the following:

[0321] Location-limited information of the data collection object;

[0322] Time limit information for data collection;

[0323] Business or application qualification information, used to qualify the business or application that generates the data;

[0324] Data source information;

[0325] The data reporting condition information includes at least one of the following:

[0326] Time period information for data reporting; event information that triggers data reporting.

[0327] Optionally, the response message to the first request message includes at least one of the following:

[0328] Third path information for data plane control signaling;

[0329] Fourth path information for data plane data forwarding;

[0330] a second data encoding method;

[0331] Second data encryption method.

[0332] Optionally, when the data plane connection is based on a user plane path, the first request message further includes at least one of the following:

[0333] Identification information corresponding to the user plane path;

[0334] address information or identification information of the first device corresponding to the user plane path;

[0335] The port information of the first device corresponding to the user plane path.

[0336] Optionally, when the data plane connection is based on a data plane forwarding path, the first request message further includes at least one of the following:

[0337] Identification information corresponding to the data plane path;

[0338] address information or identification information of the first device corresponding to the data plane path;

[0339] The port information of the first device corresponding to the data plane path.

[0340] Optionally, the method further includes:

[0341] The second device sends a third request message to the target device, where the third request message is used to request the target device to establish a data plane connection with the first device, or to notify the target device that the first device needs to obtain data from the target device based on the data plane connection;

[0342] Optionally, the third request message includes at least one of the following information:

[0343] The type of data collected;

[0344] Data filtering information, used to filter required data during data collection;

[0345] Data reporting condition information;

[0346] How your data is processed;

[0347] Data storage format.

[0348] Optionally, the content of the third request message may be the same as that of the first request message, or may be set according to the first request message.

[0349] Optionally, the method further includes:

[0350] The second device sends at least one of the following information to the target device:

[0351] the first path information or the third path information;

[0352] the second path information or the fourth path information;

[0353] the first data encoding mode or the second data encoding mode;

[0354] the second data encryption method or the second data encryption method;

[0355] address information or identification information of the first device;

[0356] Port information of the first device.

[0357] Optionally, the at least one item of information sent by the second device to the target device may be carried by the third request message.

[0358] Optionally, the method further includes:

[0359] The second device (DPF-C) obtains second information of the target device (DPF-U);

[0360] The second information includes at least one of the following: the address, identification, and port information of the target device.

[0361] Optionally, the second device sends the second information to the first device, for example, the second information may be carried in a response message to the first request message, such as carrying at least one of the address, identifier and port information of the target device (such as DPF-U).

[0362] The specific implementation process and technical effects of the method of this embodiment are similar to those in the first device-side method embodiment. For details, please refer to the detailed introduction in the first device-side method embodiment, and no further details will be given here.

[0363] The data interaction method provided in the embodiment of the present application can be executed by a data interaction device. In the embodiment of the present application, the data interaction device provided in the embodiment of the present application is described by taking the data interaction method executed by the data interaction device as an example.

[0364] FIG8 is a structural diagram of a data interaction device provided in an embodiment of the present application. As shown in FIG8 , the data interaction device provided in this embodiment can be applied to a first device, and the data interaction device includes:

[0365] A sending module 110 is configured to send a first request message to the second device, where the first request message is used to request establishment of a data plane connection with the target device, or to obtain data from the target device based on the data plane connection;

[0366] The receiving module 120 is configured to receive a response message to the first request message from the second device.

[0367] Optionally, the first request message includes at least one of the following: first path information of data plane control signaling; second path information of data plane data forwarding; a first data encoding method; and a first data encryption method.

[0368] Optionally, the receiving module 120 is further configured to:

[0369] Receive data sent from the target device through the data plane connection.

[0370] Optionally, the sending module 110 is further configured to:

[0371] A second request message is sent to the second device, where the second request message is used to request the data.

[0372] Optionally, the first path information includes at least one of the following: control plane path indication information, user plane path indication information, data plane control path indication information, and information about protocol layers that data plane signaling needs to pass through.

[0373] Optionally, the second path information includes at least one of the following: control plane path indication information, user plane path indication information, data plane forwarding path indication information, and information about protocol layers that the data plane needs to pass through when forwarding data.

[0374] Optionally, the device further comprises:

[0375] A processing module is used to determine the first request message.

[0376] Optionally, the processing module is specifically configured to:

[0377] Determine the first path information of the data plane control signaling based on a first factor, wherein the first factor includes at least one of the following:

[0378] The forwarding delay requirement of the data plane control signaling;

[0379] Whether the data plane control signaling needs to be parsed by the access network device.

[0380] Optionally, the processing module is specifically configured to:

[0381] Determine the second path information for forwarding the data plane data based on a second factor, wherein the second factor includes at least one of the following:

[0382] Obtaining the latency requirement of the data plane data;

[0383] The amount of data to be transferred;

[0384] Whether the data plane data needs to be parsed by the access network device.

[0385] Optionally, the processing module is specifically configured to:

[0386] The first data encoding mode is determined based on a third factor; wherein the third factor includes at least one of the following:

[0387] Coding delay requirement of the data plane data;

[0388] Coding efficiency requirements for the data plane data;

[0389] Readability requirements of the data plane data;

[0390] Security requirements for the data plane data;

[0391] The reliability requirements of the data plane data.

[0392] Optionally, the first request message further includes at least one of the following information of the data plane data:

[0393] The type of data collected;

[0394] Data filtering information, used to filter required data during data collection;

[0395] Data reporting condition information;

[0396] How your data is processed;

[0397] Data storage format;

[0398] The data filtering information includes at least one of the following:

[0399] Location-limited information of the data collection object;

[0400] Time limit information for data collection;

[0401] Business or application qualification information, used to qualify the business or application that generates the data;

[0402] Data source information;

[0403] The data reporting condition information includes at least one of the following:

[0404] Time period information for data reporting; event information that triggers data reporting.

[0405] Optionally, the response message to the first request message includes at least one of the following:

[0406] Third path information for data plane control signaling;

[0407] Fourth path information for data plane data forwarding;

[0408] a second data encoding method;

[0409] Second data encryption method.

[0410] Optionally, the processing module is further configured to:

[0411] Establishing the data plane connection with the target device is triggered according to the second path information or the fourth path information.

[0412] Optionally, when the data plane connection is based on a user plane path, the first request message further includes at least one of the following:

[0413] Identification information corresponding to the user plane path;

[0414] address information or identification information of the first device corresponding to the user plane path;

[0415] The port information of the first device corresponding to the user plane path.

[0416] Optionally, when the data plane connection is based on a data plane forwarding path, the first request message further includes at least one of the following:

[0417] Identification information corresponding to the data plane path;

[0418] address information or identification information of the first device corresponding to the data plane path;

[0419] The port information of the first device corresponding to the data plane path.

[0420] Optionally, the sending module 110 is specifically configured to:

[0421] Sending the first request message to the second device based on the first information;

[0422] The first information includes at least one of the following: the address, identification, and port information of the target device.

[0423] Optionally, the first information is obtained by the first device from the second device; or,

[0424] The first information is obtained by the first device through a domain name system DNS query.

[0425] Optionally, the processing module is specifically configured to:

[0426] Determining, by a data plane control module of the first device, the first request message;

[0427] Forwarding the first request message to the data plane forwarding module of the first device through the data plane control module of the first device;

[0428] Optionally, the sending module 110 is specifically configured to:

[0429] The first request message is sent to the second device through the data plane forwarding module of the first device.

[0430] Optionally, the first device includes at least one of a terminal and an access network device.

[0431] Optionally, the second device includes at least one of an access network device and a core network device.

[0432] The device of this embodiment can be used to execute each process in the aforementioned first device-side method embodiment. Its specific implementation process and technical effects are similar to those in the first device-side method embodiment. For details, please refer to the detailed introduction in the first device-side method embodiment, which will not be repeated here.

[0433] FIG9 is a second structural diagram of the data interaction device provided in an embodiment of the present application. As shown in FIG9 , the data interaction device provided in this embodiment can be applied to a second device, and the data interaction device includes:

[0434] The receiving module 210 is configured to receive a first request message sent by a first device, where the first request message is used to request establishment of a data plane connection with a target device, or to obtain data from the target device based on the data plane connection;

[0435] The sending module 220 is configured to send a response message to the first request message to the first device.

[0436] Optionally, the first request message includes at least one of the following: first path information of data plane control signaling; second path information of data plane data forwarding; a first data encoding method; and a first data encryption method.

[0437] Optionally, when the second device is the target device, the sending module 220 is configured to:

[0438] Data is sent to the first device through the data plane connection.

[0439] Optionally, the receiving module 210 is further configured to:

[0440] The data is obtained from a data source or a third device (such as DPF-U), for example, the second device is the target device.

[0441] Optionally, the receiving module 210 is further configured to:

[0442] A second request message sent by the first device is received, where the second request message is used to request the data.

[0443] Optionally, the first path information includes at least one of the following: control plane path indication information, user plane path indication information, data plane control path indication information, and information about protocol layers that data plane signaling needs to pass through.

[0444] Optionally, the second path information includes at least one of the following: control plane path indication information, user plane path indication information, data plane forwarding path indication information, and information about protocol layers that the data plane needs to pass through when forwarding data.

[0445] Optionally, the first request message further includes at least one of the following information of the data plane data:

[0446] The type of data collected;

[0447] Data filtering information, used to filter required data during data collection;

[0448] Data reporting condition information;

[0449] How your data is processed;

[0450] Data storage format;

[0451] The data filtering information includes at least one of the following:

[0452] Location-limited information of the data collection object;

[0453] Time limit information for data collection;

[0454] Business or application qualification information, used to qualify the business or application that generates the data;

[0455] Data source information;

[0456] The data reporting condition information includes at least one of the following:

[0457] Time period information for data reporting; event information that triggers data reporting.

[0458] Optionally, the response message to the first request message includes at least one of the following:

[0459] Third path information for data plane control signaling;

[0460] Fourth path information for data plane data forwarding;

[0461] a second data encoding method;

[0462] Second data encryption method.

[0463] Optionally, when the data plane connection is based on a user plane path, the first request message further includes at least one of the following:

[0464] Identification information corresponding to the user plane path;

[0465] address information or identification information of the first device corresponding to the user plane path;

[0466] The port information of the first device corresponding to the user plane path.

[0467] Optionally, when the data plane connection is based on a data plane forwarding path, the first request message further includes at least one of the following:

[0468] Identification information corresponding to the data plane path;

[0469] address information or identification information of the first device corresponding to the data plane path;

[0470] The port information of the first device corresponding to the data plane path.

[0471] Optionally, the sending module 220 is further configured to:

[0472] Sending a third request message to the target device, where the third request message is used to request the target device to establish a data plane connection with the first device, or to notify the first device to obtain data from the target device based on the data plane connection;

[0473] Optionally, the third request message includes at least one of the following information:

[0474] The type of data collected;

[0475] Data filtering information, used to filter required data during data collection;

[0476] Data reporting condition information;

[0477] How your data is processed;

[0478] Data storage format.

[0479] Optionally, the sending module 220 is further configured to:

[0480] Send at least one of the following information to the target device:

[0481] the first path information or the third path information;

[0482] the second path information or the fourth path information;

[0483] the first data encoding mode or the second data encoding mode;

[0484] the second data encryption method or the second data encryption method;

[0485] address information or identification information of the first device;

[0486] Port information of the first device.

[0487] Optionally, the at least one item of information sent to the target device may be carried by the third request message.

[0488] Optionally, the receiving module 210 is further configured to:

[0489] Obtaining second information of the target device (DPF-U);

[0490] The second information includes at least one of the following: the address, identification, and port information of the target device.

[0491] The device of this embodiment can be used to execute the method of any embodiment of the aforementioned second device side method embodiment. Its specific implementation process and technical effects are similar to those in the second device side method embodiment. For details, please refer to the detailed introduction in the second device side method embodiment, which will not be repeated here.

[0492] The data interaction device in the embodiments of the present application can be an electronic device, such as an electronic device with an operating system, or a component in an electronic device, such as an integrated circuit or chip. The electronic device can be a terminal, or it can be other devices other than a terminal. For example, the terminal can include but is not limited to the types of terminal 11 listed above, and other devices can be servers, network attached storage (NAS), etc., which are not specifically limited in the embodiments of the present application.

[0493] The data interaction device provided in the embodiment of the present application can implement the various processes implemented in the method embodiments of Figures 2 to 7 and achieve the same technical effects. To avoid repetition, they will not be described here.

[0494] As shown in Figure 10, an embodiment of the present application further provides a communication device 1000, including a processor 1001 and a memory 1002, wherein the memory 1002 stores a program or instruction that can be run on the processor 1001. For example, when the communication device 1000 is a terminal, the program or instruction is executed by the processor 1001 to implement the various steps of the above-mentioned method embodiment for establishing a data plane connection, and can achieve the same technical effect. When the communication device 1000 is a network-side device, the program or instruction is executed by the processor 1001 to implement the various steps of the above-mentioned method embodiment for establishing a data plane connection, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0495] The present application also provides a terminal including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is configured to execute a program or instruction to implement the steps of the method embodiment shown in FIG3 . This terminal embodiment corresponds to the aforementioned terminal-side method embodiment, and each implementation process and implementation method of the aforementioned method embodiment is applicable to this terminal embodiment and can achieve the same technical effects. Specifically, FIG11 is a schematic diagram of the hardware structure of a terminal implementing an embodiment of the present application.

[0496] The terminal 1100 includes but is not limited to: a radio frequency unit 1101, a network module 1102, an audio output unit 1103, an input unit 1104, a sensor 1105, a display unit 1106, a user input unit 1107, an interface unit 1108, a memory 1109 and at least some of the components of the processor 1110.

[0497] Those skilled in the art will appreciate that the terminal 1100 may also include a power supply (such as a battery) to power various components. The power supply may be logically connected to the processor 1110 via a power management system, thereby enabling the power management system to manage charging, discharging, and power consumption. The terminal structure shown in FIG11 does not limit the terminal. The terminal may include more or fewer components than shown, or combine certain components, or arrange the components differently, which will not be described in detail here.

[0498] It should be understood that in an embodiment of the present application, the input unit 1104 may include a graphics processing unit (GPU) 11041 and a microphone 11042, and the graphics processor 11041 processes the image data of a static picture or video obtained by an image capture device (such as a camera) in a video capture mode or an image capture mode. The display unit 1106 may include a display panel 11061, and the display panel 11061 may be configured in the form of a liquid crystal display, an organic light emitting diode, etc. The user input unit 1107 includes a touch panel 11071 and at least one of other input devices 11072. The touch panel 11071 is also called a touch screen. The touch panel 11071 may include two parts: a touch detection device and a touch controller. Other input devices 11072 may include, but are not limited to, a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a trackball, a mouse, and a joystick, which will not be repeated here.

[0499] In the embodiment of the present application, after receiving downlink data from a network-side device, the RF unit 1101 may transmit the data to the processor 1110 for processing. Furthermore, the RF unit 1101 may send uplink data to the network-side device. Typically, the RF unit 1101 includes, but is not limited to, an antenna, an amplifier, a transceiver, a coupler, a low-noise amplifier, a duplexer, and the like.

[0500] The memory 1109 can be used to store software programs or instructions and various data. The memory 1109 may mainly include a first storage area for storing programs or instructions and a second storage area for storing data, wherein the first storage area may store an operating system, applications or instructions required for at least one function (such as a sound playback function, an image playback function, etc.). In addition, the memory 1109 may include a volatile memory or a non-volatile memory. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be random access memory (RAM), static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM bus random access memory (DRRAM). The memory 1109 in the embodiment of the present application includes but is not limited to these and any other suitable types of memory.

[0501] Processor 1110 may include one or more processing units. Optionally, processor 1110 integrates an application processor and a modem processor. The application processor primarily handles operations related to the operating system, user interface, and application programs, while the modem processor primarily processes wireless communication signals, such as a baseband processor. It is understood that the modem processor may not be integrated into processor 1110.

[0502] The radio frequency unit 1101 is configured to send a first request message to the second device, where the first request message is used to request establishment of a data plane connection with the target device, or to obtain data from the target device based on the data plane connection;

[0503] The radio frequency unit 1101 is further configured to receive a response message to the first request message from the second device.

[0504] Optionally, the first request message includes at least one of the following: first path information of data plane control signaling; second path information of data plane data forwarding; a first data encoding method; and a first data encryption method.

[0505] Optionally, the radio frequency unit 1101 is further configured to:

[0506] Receive data sent from the target device through the data plane connection.

[0507] Optionally, the radio frequency unit 1101 is further configured to:

[0508] A second request message is sent to the second device, where the second request message is used to request the data.

[0509] Optionally, the first path information includes at least one of the following: control plane path indication information, user plane path indication information, data plane control path indication information, and information about protocol layers that data plane signaling needs to pass through.

[0510] Optionally, the second path information includes at least one of the following: control plane path indication information, user plane path indication information, data plane forwarding path indication information, and information about protocol layers that the data plane needs to pass through when forwarding data.

[0511] Optionally, the processor 1010 is further configured to determine the first request message.

[0512] Optionally, the processor 1010 is specifically configured to:

[0513] Determine the first path information of the data plane control signaling based on a first factor, wherein the first factor includes at least one of the following:

[0514] The forwarding delay requirement of the data plane control signaling;

[0515] Whether the data plane control signaling needs to be parsed by the access network device.

[0516] Optionally, the processor 1010 is specifically configured to:

[0517] Determine the second path information for forwarding the data plane data based on a second factor, wherein the second factor includes at least one of the following:

[0518] Obtaining the latency requirement of the data plane data;

[0519] The amount of data to be transferred;

[0520] Whether the data plane data needs to be parsed by the access network device.

[0521] Optionally, the processor 1010 is specifically configured to:

[0522] The first data encoding mode is determined based on a third factor; wherein the third factor includes at least one of the following:

[0523] Coding delay requirement of the data plane data;

[0524] Coding efficiency requirements for the data plane data;

[0525] Readability requirements of the data plane data;

[0526] Security requirements for the data plane data;

[0527] The reliability requirements of the data plane data.

[0528] Optionally, the first request message further includes at least one of the following information of the data plane data:

[0529] The type of data collected;

[0530] Data filtering information, used to filter required data during data collection;

[0531] Data reporting condition information;

[0532] How your data is processed;

[0533] Data storage format;

[0534] The data filtering information includes at least one of the following:

[0535] Location-limited information of the data collection object;

[0536] Time limit information for data collection;

[0537] Business or application qualification information, used to qualify the business or application that generates the data;

[0538] Data source information;

[0539] The data reporting condition information includes at least one of the following:

[0540] Time period information for data reporting; event information that triggers data reporting.

[0541] Optionally, the response message to the first request message includes at least one of the following:

[0542] Third path information for data plane control signaling;

[0543] Fourth path information for data plane data forwarding;

[0544] a second data encoding method;

[0545] Second data encryption method.

[0546] Optionally, the processor 1010 is further configured to:

[0547] Establishing the data plane connection with the target device is triggered according to the second path information or the fourth path information.

[0548] Optionally, when the data plane connection is based on a user plane path, the first request message further includes at least one of the following:

[0549] Identification information corresponding to the user plane path;

[0550] address information or identification information of the first device corresponding to the user plane path;

[0551] The port information of the first device corresponding to the user plane path.

[0552] Optionally, when the data plane connection is based on a data plane forwarding path, the first request message further includes at least one of the following:

[0553] Identification information corresponding to the data plane path;

[0554] address information or identification information of the first device corresponding to the data plane path;

[0555] The port information of the first device corresponding to the data plane path.

[0556] Optionally, the radio frequency unit 1001 is specifically configured to:

[0557] Sending the first request message to the second device based on the first information;

[0558] The first information includes at least one of the following: the address, identification, and port information of the target device.

[0559] Optionally, the first information is obtained by the first device from the second device; or,

[0560] The first information is obtained by the first device through a domain name system DNS query.

[0561] Optionally, the processor 1010 is specifically configured to:

[0562] Determining, by a data plane control module of the first device, the first request message;

[0563] Forwarding the first request message to the data plane forwarding module of the first device through the data plane control module of the first device;

[0564] Optionally, the radio frequency unit 1001 is specifically configured to:

[0565] The first request message is sent to the second device through the data plane forwarding module of the first device.

[0566] Optionally, the first device includes at least one of a terminal and an access network device.

[0567] Optionally, the second device includes at least one of an access network device and a core network device.

[0568] It can be understood that the implementation process of each implementation method mentioned in this embodiment can refer to the relevant description of the method embodiment shown in Figure 3, and achieve the same or corresponding technical effects. To avoid repetition, it will not be repeated here.

[0569] The present application also provides a network-side device, including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is configured to execute a program or instruction to implement the steps of the method embodiment shown in FIG3 or FIG7 . This network-side device embodiment corresponds to the aforementioned network-side device method embodiment, and each implementation process and implementation method of the aforementioned method embodiment is applicable to this network-side device embodiment and can achieve the same technical effects.

[0570] Specifically, embodiments of the present application also provide a network-side device. As shown in Figure 12, the network-side device 1200 includes an antenna 121, a radio frequency device 122, a baseband device 123, a processor 124, and a memory 125. Antenna 121 is connected to radio frequency device 122. In the uplink direction, radio frequency device 122 receives information via antenna 121 and sends the received information to baseband device 123 for processing. In the downlink direction, baseband device 123 processes the information to be transmitted and sends it to radio frequency device 122. Radio frequency device 122 processes the received information and then sends it through antenna 121.

[0571] The method executed by the network-side device in the above embodiment may be implemented in the baseband device 123 , which includes a baseband processor.

[0572] The baseband device 123 may include, for example, at least one baseband board, on which multiple chips are arranged, as shown in Figure 12, one of the chips is, for example, a baseband processor, which is connected to the memory 125 through a bus interface to call the program in the memory 125 and execute the network device operations shown in the above method embodiment.

[0573] The network side device may further include a network interface 126 , which is, for example, a Common Public Radio Interface (CPRI).

[0574] Specifically, the network side device 1200 of the embodiment of the present application also includes: instructions or programs stored in the memory 125 and executable on the processor 124. The processor 124 calls the instructions or programs in the memory 125 to execute the methods executed by the modules shown in FIG8 or FIG9 and achieve the same technical effect. To avoid repetition, they will not be elaborated here.

[0575] Specifically, the embodiment of the present application further provides a network-side device. As shown in FIG13 , the network-side device 1300 includes a processor 1301, a network interface 1302, and a memory 1303. The network interface 1302 is, for example, a common public radio interface (CPRI).

[0576] Specifically, the network side device 1300 of the embodiment of the present application also includes: instructions or programs stored in the memory 1303 and executable on the processor 1301. The processor 1301 calls the instructions or programs in the memory 1303 to execute the method of execution of each module shown in Figure 9 and achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0577] An embodiment of the present application also provides a readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, the various processes of the above-mentioned data interaction method embodiment are implemented and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

[0578] The processor is the processor in the terminal described in the above embodiment. The readable storage medium includes a computer-readable storage medium, such as a computer read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk. In some examples, the readable storage medium may be a non-transitory readable storage medium.

[0579] An embodiment of the present application further provides a chip, which includes a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the various processes of the above-mentioned data interaction method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0580] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0581] An embodiment of the present application further provides a computer program / program product, which is stored in a storage medium. The computer program / program product is executed by at least one processor to implement the various processes of the above-mentioned data interaction method embodiment and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0582] An embodiment of the present application also provides a communication system, including: a first device and a second device, wherein the terminal can be used to execute the steps of the data interaction method described above, and the network side device can be used to execute the steps of the data interaction method described above.

[0583] It should be noted that, in this article, the terms "comprise", "include" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprises a ..." does not exclude the presence of other identical elements in the process, method, article or device comprising the element. In addition, it should be pointed out that the scope of the methods and devices in the embodiments of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in the opposite order according to the functions involved. For example, the described method may be performed in an order different from that described, and various steps may also be added, omitted or combined. In addition, the features described with reference to certain examples may be combined in other examples.

[0584] Through the description of the above embodiments, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of a computer software product plus a necessary general-purpose hardware platform, or of course, by hardware. The computer software product is stored in a storage medium (such as ROM, RAM, magnetic disk, optical disk, etc.) and includes a number of instructions for enabling a terminal or network-side device to execute the methods described in each embodiment of the present application.

[0585] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of this application, ordinary technicians in this field can also make many forms of implementation methods without departing from the purpose of this application and the scope of protection of the claims. These implementation methods are all within the protection of this application.

Claims

1. A data interaction method, wherein: include: The first device sends a first request message to the second device, where the first request message is used to request to establish a data plane connection with the target device, or to obtain data from the target device based on the data plane connection; The first device receives a response message to the first request message from the second device.

2. The method according to claim 1, wherein: The first request message includes at least one of the following: first path information of data plane control signaling; second path information of data plane data forwarding; a first data encoding method; and a first data encryption method.

3. The method according to claim 1 or 2, wherein: The method further comprises: The first device receives data sent from the target device through the data plane connection.

4. The method according to claim 3, wherein: The method further comprises: The first device sends a second request message to the second device, where the second request message is used to request the data.

5. The method according to claim 2, wherein: The first path information includes at least one of the following: control plane path indication information, user plane path indication information, data plane control path indication information, and information of a protocol layer that data plane signaling needs to pass through.

6. The method according to claim 2, wherein: The second path information includes at least one of the following: control plane path indication information, user plane path indication information, data plane forwarding path indication information, and information about the protocol layers that the data plane needs to pass through when forwarding data.

7. The method according to any one of claims 2, 5 or 6, wherein: The method further comprises: The first device determines the first request message.

8. The method according to claim 7, wherein: The first device determines the first request message, including: The first device determines the first path information of the data plane control signaling based on a first factor; wherein the first factor includes at least one of the following: The forwarding delay requirement of the data plane control signaling; Whether the data plane control signaling needs to be parsed by the access network device.

9. The method according to claim 7, wherein: The first device determines the first request message, including: The first device determines the second path information of the data plane data forwarding based on the second factor; wherein the second factor includes at least one of the following: Obtaining the latency requirement of the data plane data; The amount of data to be transferred; Whether the data plane data needs to be parsed by the access network device.

10. The method according to claim 7, wherein: The first device determines the first request message, including: The first device determines the first data encoding method based on a third factor; wherein the third factor includes at least one of the following: The encoding delay requirement of the data plane data; Coding efficiency requirement for the data plane data; Readability requirements of the data plane data; The security requirements of the data plane data; The data plane data reliability requirements.

11. The method according to any one of claims 1 to 10, wherein: The first request message further includes at least one of the following information of the data plane data: The type of data collected; Data filtering information, used to filter required data during data collection; Data reporting condition information; How your data is processed; Data storage format; The data filtering information includes at least one of the following: Location-limited information of the data collection object; Information on the time limit for data collection; Business or application qualification information, used to qualify the business or application that generates the data; Data source information; The data reporting condition information includes at least one of the following: Time period information for data reporting; event information that triggers data reporting.

12. The method according to any one of claims 2, 5 or 6, wherein: The response message to the first request message includes at least one of the following: Third path information of data plane control signaling; Fourth path information of data plane data forwarding; A second data encoding method; Second data encryption method.

13. The method according to claim 12, wherein: The method further comprises: The first device triggers establishment of the data plane connection with the target device according to the second path information or the fourth path information.

14. The method according to claim 2, wherein: In a case where the data plane connection is based on a user plane path, the first request message further includes at least one of the following: Identification information corresponding to the user plane path; address information or identification information of the first device corresponding to the user plane path; The port information of the first device corresponding to the user plane path.

15. The method according to claim 2, wherein: In a case where the data plane connection is based on a data plane forwarding path, the first request message further includes at least one of the following: Identification information corresponding to the data plane path; address information or identification information of the first device corresponding to the data plane path; The port information of the first device corresponding to the data plane path.

16. The method according to any one of claims 1 to 15, wherein: The first device sending a first request message to the second device includes: The first device sends the first request message to the second device based on the first information; The first information includes at least one of the following: the address, identification and port information of the target device.

17. The method according to claim 16, wherein: The first information is obtained by the first device from the second device; or, The first information is obtained by the first device through a domain name system DNS.

18. The method according to claim 7, wherein: The first device determines the first request message, including: The data plane control module of the first device determines the first request message; The method further comprises: The data plane control module of the first device forwards the first request message to the data plane forwarding module of the first device; The first device sending a first request message to the second device includes: The data plane forwarding module of the first device sends the first request message to the second device.

19. The method according to any one of claims 1 to 18, wherein: The first device includes at least one of a terminal and an access network device.

20. The method according to any one of claims 1 to 18, wherein: The second device includes at least one of an access network device and a core network device.

21. A data interaction method, wherein: include: The second device receives a first request message sent by the first device, where the first request message is used to request to establish a data plane connection with the target device, or to obtain data from the target device based on the data plane connection; The second device sends a response message to the first request message to the first device.

22. The method according to claim 21, wherein: The first request message includes at least one of the following: first path information of data plane control signaling; second path information of data plane data forwarding; a first data encoding method; and a first data encryption method.

23. The method according to claim 21 or 22, wherein: The method further comprises: The second device sends the data from the target device to the first device through the data plane connection.

24. The method according to claim 23, wherein: The method further comprises: The second device receives a second request message sent by the first device, where the second request message is used to request the data.

25. The method according to claim 22, wherein: The first path information includes at least one of the following: control plane path indication information, user plane path indication information, data plane control path indication information, and information of a protocol layer that data plane signaling needs to pass through.

26. The method of claim 22, wherein: The second path information includes at least one of the following: control plane path indication information, user plane path indication information, data plane forwarding path indication information, and information about the protocol layers that the data plane needs to pass through when forwarding data.

27. The method according to any one of claims 21 to 26, wherein: The first request message further includes at least one of the following information of the data plane data: The type of data collected; Data filtering information, used to filter required data during data collection; Data reporting condition information; How your data is processed; Data storage format; The data filtering information includes at least one of the following: Location-limited information of the data collection object; Information on the time limit for data collection; Business or application qualification information, used to qualify the business or application that generates the data; Data source information; The data reporting condition information includes at least one of the following: Time period information for data reporting; event information that triggers data reporting.

28. The method according to any one of claims 21 to 27, wherein: The response message to the first request message includes at least one of the following: Third path information of data plane control signaling; Fourth path information of data plane data forwarding; A second data encoding method; Second data encryption method.

29. The method according to any one of claims 22 to 27, wherein: In a case where the data plane connection is based on a user plane path, the first request message further includes at least one of the following: Identification information corresponding to the user plane path; address information or identification information of the first device corresponding to the user plane path; The port information of the first device corresponding to the user plane path.

30. The method according to any one of claims 22 to 27, wherein: In a case where the data plane connection is based on a data plane forwarding path, the first request message further includes at least one of the following: Identification information corresponding to the data plane path; address information or identification information of the first device corresponding to the data plane path; The port information of the first device corresponding to the data plane path.

31. The method of claim 28, wherein: The method further comprises: The second device sends at least one of the following information to the target device: the first path information or the third path information; the second path information or the fourth path information; the first data encoding method or the second data encoding method; the second data encryption method or the second data encryption method; address information or identification information of the first device; The port information of the first device.

32. A data interaction device, wherein: include: A sending module, configured to send a first request message to the second device, wherein the first request message is used to request to establish a data plane connection with the target device, or to obtain data from the target device based on the data plane connection; The receiving module is used to receive a response message to the first request message from the second device.

33. A data interaction device, wherein: include: A receiving module, configured to receive a first request message sent by a first device, wherein the first request message is used to request to establish a data plane connection with a target device, or to obtain data from the target device based on the data plane connection; A sending module is used to send a response message of the first request message to the first device.

34. A first device, wherein: It includes a processor and a memory, the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the steps of the data interaction method as described in any one of claims 1 to 20 are implemented.

35. A second device, wherein: It includes a processor and a memory, the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the steps of the data interaction method as described in any one of claims 21 to 31 are implemented.

36. A readable storage medium, wherein: The readable storage medium stores a program or instruction, and when the program or instruction is executed by the processor, it implements the data interaction method as described in any one of claims 1 to 20, or implements the steps of the data interaction method as described in any one of claims 21 to 31.

37. A chip, wherein: The chip includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is used to run a program or instruction to implement the method according to any one of claims 1 to 20, or to implement the method according to any one of claims 21 to 31.

38. A computer program product, wherein: The program product is stored in a non-transitory storage medium, and the program product is executed by at least one processor to implement the method according to any one of claims 1 to 20, or to implement the method according to any one of claims 21 to 31.

Images