Wireless communication system, data processing method and wireless communication device

By introducing a Data Management Function (DMF), data acquisition and transmission tasks are managed in a unified manner, solving the problems of inconsistent data acquisition processes and repetitive acquisition in existing technologies, thereby improving system efficiency and flexibility.

WO2026232649A1PCT designated stage Publication Date: 2026-11-12SHENZHEN TCL NEW-TECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

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

AI Technical Summary

Technical Problem

In existing technologies, data acquisition processes vary and lack unified management, leading to increased system complexity, redundant data collection, and inflexible upgrades, making it difficult to meet changing market demands.

Method used

The system introduces a Data Management Function (DMF) to uniformly manage data acquisition and transmission tasks. It establishes a dedicated bearer through the SBI and N2 interfaces to support data acquisition and transmission across distributed subnets and provides data processing, storage, and open services.

Benefits of technology

It enables unified management of the data acquisition process, reduces redundant data collection, improves system efficiency and flexibility, and allows for rapid response to changes in market demand.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN2025097426_12112026_PF_FP_ABST
    Figure CN2025097426_12112026_PF_FP_ABST
Patent Text Reader

Abstract

Provided in the present disclosure is a method executed on a first device. The method comprises: receiving real-time or variable capability information reported by at least one second device, wherein the capability information comprises, but is not limited to, at least one of the following: a data type, a node type, a node identifier, a data-collection spatial range, a data-collection temporal range, and a condition of a data-consuming device under which data acquisition is allowable.
Need to check novelty before this filing date? Find Prior Art

Description

Wireless communication systems, data processing methods and wireless communication devices

[0001] This application claims priority to patent application No. PCT / CN2025 / 094086, filed on May 9, 2025, the entire contents of which are incorporated herein by reference. Technical Field

[0002] This disclosure relates to the field of wireless communication, and in particular to wireless communication systems, data processing methods, and wireless communication devices. Background Technology

[0003] In current network systems, data is managed separately by various network elements. Connection service management nodes such as AMF and SMF manage service data such as UE Context and PDU Session Context; UDM and UDR manage UE subscription data. Meanwhile, new services introduced in future communication systems will lead to new demands for data management and large-scale data transmission, such as AI data and sensor data. Several unresolved issues exist regarding the processing of this data. Therefore, it is necessary to propose wireless communication systems, data processing methods, and wireless communication equipment to improve existing technologies. Summary of the Invention

[0004] The technical problem to be solved by the present invention is to provide a wireless communication system, a data processing method and a wireless communication device to address the above-mentioned deficiencies in the prior art, thereby solving the problems existing in the prior art.

[0005] According to one aspect of this disclosure, a wireless communication system is provided, the wireless communication system comprising: a data management function, wherein the data management function is used to uniformly manage data acquisition and transmission tasks.

[0006] According to one aspect of this disclosure, a method is provided for execution on a first device, wherein the method includes: receiving real-time or variable capability information reported by at least one node; wherein the capability information includes, but is not limited to, at least one of the following: data type, node type, node identifier, data acquisition spatial range, data acquisition time range, and device conditions for consuming data that allow data acquisition.

[0007] According to one aspect of this disclosure, a data processing method is provided, executed on a first device, wherein the method includes: receiving a data transmission establishment request message, the data transmission establishment request message including at least one of the following: a device identifier for consuming data, device filtering conditions for consuming data, and / or an association between a created data transmission task and a data acquisition task.

[0008] According to one aspect of this disclosure, a data processing method is provided, executed on a second device, wherein the method includes: sending at least one node to report real-time or variable capability information; wherein the capability information includes, but is not limited to, at least one of the following: data type, node type, node identifier, data acquisition spatial range, data acquisition time range, and device conditions for consuming data that allows data acquisition.

[0009] According to one aspect of this disclosure, a data processing method is provided, executed on a third device, wherein the method includes: sending creation information and / or notification information, wherein the creation information indicates the creation of a first data acquisition task, the creation information including but not limited to at least one of the following: data type, data source, data frequency, data acquisition task list, data reporting cycle, data storage information, data processing information and / or data transmission target, and the notification information indicating the control plane address of the device consuming the data.

[0010] According to one aspect of this disclosure, a data processing method is provided, executed on a second device, wherein the method includes: sending a data transmission establishment request message, the data transmission establishment request message including at least one of the following: a device identifier for consuming data, device filtering conditions for consuming data, and / or an association between a created data transmission task and a data acquisition task.

[0011] According to one aspect of this disclosure, a data processing method is provided, executed in a second device and in a third device, wherein the method includes: receiving a data plane transmission establishment request.

[0012] According to one aspect of this disclosure, a wireless communication device is provided, including a processor and a memory for storing a computer program, the processor for calling and running the computer program stored in the memory to perform steps in the data processing method as described in any of the preceding claims.

[0013] According to one aspect of this disclosure, a readable storage medium is provided for storing a computer program that is invoked and executed by a processor to perform any of the methods described above. Attached Figure Description

[0014] To more clearly illustrate the embodiments of this disclosure or related technologies, the following figures will be briefly described in the embodiments. Obviously, the figures are merely some embodiments of this disclosure, and those skilled in the art can obtain other figures based on these figures without creative effort.

[0015] Figure 1 illustrates a schematic diagram of the wireless communication system architecture provided in this disclosure.

[0016] Figures 2a-2b illustrate schematic diagrams of the data plane functional network element architecture in the distributed subnet provided in this disclosure.

[0017] Figure 2c illustrates a schematic diagram of the cross-distributed subnet network architecture provided in this disclosure.

[0018] Figure 3-30 illustrates a flowchart of the data extraction method provided in this disclosure.

[0019] Figure 31 illustrates an exemplary block diagram of a wireless communication system provided in this disclosure. Detailed Implementation

[0020] The embodiments of this disclosure have been described in detail with reference to the accompanying drawings, outlining technical aspects, structural features, objectives, and effects, as described below. Specifically, the terminology used in the embodiments of this disclosure is for the purpose of describing particular embodiments only and is not intended to limit the disclosure.

[0021] In this disclosure, “A or B” may mean “A only”, “B only”, or “both A and B”.

[0022] In other words, in this disclosure, “A or B” can be interpreted as “A and / or B”. For example, in this disclosure, “A, B or C” can mean “A only”, “B only”, “C only” or “any combination of A, B, and C”.

[0023] The forward slash ( / ) or comma used in this disclosure can mean "and / or". For example, "A / B" can mean "A and / or B". Therefore, "A / B" can mean "A only", "B only", or "both A and B". For example, "A, B, C" can mean "A, B, or C".

[0024] In this disclosure, "at least one of A and B" may mean "only A", "only B" or "both A and B". Furthermore, in this disclosure, the expression "at least one of A or B" or "at least one of A and / or B" may be interpreted as "at least one of A and B".

[0025] Additionally, in this disclosure, "at least one of A, B, and C" may mean "A only", "B only", "C only" or "any combination of A, B, and C". Furthermore, "at least one of A, B, or C" or "at least one of A, B, and / or C" may mean "at least one of A, B, and C".

[0026] Furthermore, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of the stated features. In the description of this application, "multiple" means two or more, unless otherwise explicitly specified.

[0027] Those skilled in the art will recognize and understand that the details of the described examples are merely illustrative of some embodiments, and that the teachings set forth herein are applicable to various alternative settings.

[0028] The technical solutions disclosed herein can be applied to various wireless communication systems, such as: Long Term Evolution (LTE) systems, LTE Frequency Division Duplex (FDD) systems, LTE Time Division Duplex (TDD) systems, 5G communication systems, or future wireless communication systems, etc.

[0029] For example, the wireless communication system 100 of this disclosure is shown in FIG1. ​​The wireless communication system 100 may include a base station 110, which may be a device communicating with user equipment (UE) 120. The base station 110 can provide communication coverage for a specific geographical area and can communicate with user equipment located within that coverage area. Optionally, the base station 110 may be an evolved Node B (eNB or eNodeB) in an LTE system, or it may be a mobile switching center, relay station, access point, vehicle-mounted equipment, wearable device, hub, switch, bridge, router, network-side equipment in a 5G network, or a base station in a future communication system, etc.

[0030] The wireless communication system 100 also includes at least one user equipment 120 located within the coverage area of ​​the base station 110. "User equipment" as used herein includes, but is not limited to, devices configured to receive / transmit communication signals via wired connections, such as via Public Switched Telephone Networks (PSTN), Digital Subscriber Line (DSL), digital cable, direct cable connection; and / or another data connection / network; and / or via a wireless interface, such as for cellular networks, Wireless Local Area Networks (WLAN), digital television networks such as DVB-H networks, satellite networks, AM-FM broadcast transmitters; and / or other user equipment. User equipment configured to communicate via a wireless interface may be referred to as a "wireless communication terminal," "wireless terminal," or "mobile terminal." Examples of mobile terminals include, but are not limited to, satellite or cellular phones; personal communications system (PCS) terminals that can combine cellular radiotelephone with data processing, fax, and data communication capabilities; PDAs that may include radiotelephones, pagers, Internet / intranet access, web browsers, notebooks, calendars, and / or Global Positioning System (GPS) receivers; and conventional laptop and / or handheld receivers or other electronic devices that include radiotelephone transceivers. User equipment can refer to access terminals, user units, user stations, mobile stations, mobile stations, remote stations, remote user equipment, mobile devices, wireless communication equipment, or user agents. Access terminals can be cellular phones, cordless phones, Session Initiation Protocol (SIP) phones, Wireless Local Loop (WLL) stations, personal digital assistants (PDAs), handheld devices with wireless communication capabilities, computing devices or other processing devices connected to a wireless modem, in-vehicle equipment, wearable devices, user equipment in 5G networks, or user equipment in future PLMN evolutions, etc.

[0031] Optionally, user equipment 120 can perform device-to-device (D2D) communication with each other.

[0032] Alternatively, 5G communication systems or 5G networks may also be referred to as New Radio (NR) systems or NR networks.

[0033] The wireless communication system 100 also includes a core network 130. The core network 130 may be an IP mobile communication network operated by a mobile communication operator. For example, the core network 130 may be the core network used by the mobile communication operator that operates and manages the wireless communication system 100, or it may be the core network used by a virtual mobile communication operator such as an MVNO (Mobile Virtual Network Operator).

[0034] The core network 130 can connect to the base station 110, serving as a relay device for transmitting user data. User equipment 120 transmits and receives user data via the core network 130. It should be noted that user data communication is not limited to IP communication; it can also be non-IP communication.

[0035] Figure 1 illustrates an exemplary base station 110, two user equipment 120, and a core network 130. Optionally, the wireless communication system 100 may include multiple base stations, and each base station may include other numbers of user equipment within its coverage area. This disclosure does not limit this.

[0036] Optionally, the wireless communication system 100 may also include other network entities such as a network controller, a mobility management entity, and network elements, and this disclosure does not limit this. For example, the core network 130 may include other network entities such as a network controller, a mobility management entity, and network elements, and this disclosure does not limit this.

[0037] It should be understood that devices with wireless communication capabilities in the network / system described in this disclosure may be referred to as wireless communication devices. Taking the wireless communication system 100 shown in Figure 1 as an example, the wireless communication devices may include a base station 110, a user equipment 120, and a core network 130 with communication capabilities. The base station 110 and the user equipment 120 may be the specific devices described above, which will not be repeated here. The wireless communication devices may also include other devices in the wireless communication system 100 (core network 130). For example, the core network 130 may include other network entities such as network controllers and mobility management entities, which are not limited in this disclosure.

[0038] This disclosure addresses at least one of the following problems:

[0039] Question 1: Different data types have different acquisition processes and methods, and are implemented at different protocol layers. Currently, there is no unified way to manage the data acquisition process, increasing system complexity. The data acquisition processes of current network methods such as MDT, LPP, and NWDAF differ significantly, and the functions they provide also vary. Therefore, it is impossible to directly reuse existing processes to centrally and uniformly manage all data acquisition and transmission needs.

[0040] Question 2: Data collected by each business process is managed separately by each functional node, without the knowledge of each other, potentially leading to duplicate data collection. Furthermore, the lack of a unified platform to manage the collected data hinders network operators from further developing the commercial value and applications of network data.

[0041] Question 3: Currently, different data rely on varying message formats or fixed, open subscription interfaces within different protocol processes during collection and reporting, hindering flexible upgrades and evolutions to update data collection capabilities according to market demands. Opening new data collection capabilities or updating existing data reporting capabilities requires modifying protocols to open specific interfaces to meet these needs, resulting in excessively long upgrade and update cycles that fail to keep pace with changing market demands.

[0042] The information sending method provided in this application will be described in detail below with reference to the accompanying drawings and through some embodiments and application scenarios.

[0043] Figure 2a or 2b illustrates one of the flowcharts of a wireless communication system provided in this disclosure. The wireless communication system includes a data management function, wherein the data management function is used to uniformly manage data acquisition and transmission tasks.

[0044] Specifically, the data management function can be a functional network element within the core network or an external functional network element; there are no restrictions on this. The data management function primarily provides data acquisition capability management, data acquisition task management, and data transmission management services. The service interfaces related to the data management function include at least one of the following: the SBI interface and / or the N2 interface. Specifically, the control plane manages the devices that provide data (Data Collector / Data Provider) and consume data, distributed across UEs, access network nodes, and core network elements. For UEs with a NAS control plane, a new NAS-DM can be established and processed in parallel with existing NAS-SMs, etc.; for core network NFs, the control plane is the SBI interface; for RAN nodes, the control plane can be the SBI or the N2 interface forwarded via AMF.

[0045] Data transfer between devices providing data and devices consuming data can be conducted via a dedicated bearer to provide the required transmission services. This dedicated bearer can be a channel-based transmission based on GTP or a bus-based transmission based on IP ports, as shown in Figure 2a or 2b.

[0046] In some embodiments, the wireless communication system further includes at least one of the following: a data processing function for processing and / or preprocessing data and sending the processed data to a device that actually consumes the data; a data storage function for storing data and storing data for asynchronous reading by a device that consumes the data, according to the needs of the data acquisition task; and / or a data opening function.

[0047] Specifically, the following network elements can be set up in a wireless communication system to provide data processing, preprocessing, storage, and external exposure services:

[0048] Data Processing Function (DPF): Processes and / or preprocesses data, and sends the processed data to the device that actually consumes the data.

[0049] Data Storage Function (DSF): A data storage service that stores data according to the needs of data acquisition tasks for asynchronous reading by devices consuming the data.

[0050] Data Exposure Function (DEF): This is a data exposure service that exposes the data plane's data acquisition capabilities to AFs outside the 3GPP network, allowing AFs to act as data consumers and participate in the data plane process.

[0051] For a distributed network architecture, as shown in Figure 2c, the DMF, acting as a data plane management function, needs to support data acquisition and transmission task management across distributed subnets. In cross-subnet scenarios, the DMF needs to act as a proxy for other data-providing and data-consuming devices within the subnet, becoming virtual data-providing and data-consuming devices for other subnets, accessing DMF functional nodes in other subnets through SEPP and / or SCP. The distributed network architecture can also be implemented through network slicing or regional management within the same PLMN.

[0052] In this scenario, one of the devices providing or consuming data in the subsequent process might be a DMF (Data Provider Function) node in another subnet. The DMF, acting as a proxy for providing data, coordinates the data acquisition capabilities available within its subnet to provide services to other certified subnets; within its own subnet, it acts as a data consumer, receiving data transmissions from the actual data-providing devices before transmitting them to other subnets. The DMF, acting as a proxy for consuming data, creates acquisition tasks for the DMFs of other subnets based on the data acquisition needs of its own subnet; and it also proxies the receiving of data transmissions, transmitting data within its own subnet as a data-providing device to the actual data-consuming devices. See Example 15 for the specific process. The DMF can simultaneously proxy multiple actual data-providing devices, breaking down a single acquisition task. See Example 9. The DMF can act as a data plane proxy across subnets, or it can act as a pure control plane node, designating other data plane function nodes as data plane proxies.

[0053] It is worth noting that the subsequent data processing methods may or may not rely on the wireless communication system described above, and this disclosure does not impose any restrictions on this.

[0054] Figure 3 illustrates one of the flowcharts of a data processing method provided in this disclosure, as shown in Figure 3. The method includes:

[0055] Step S100: The second device reports real-time or variable capability information to the first device; wherein, the capability information includes, but is not limited to, at least one of the following: data type, node type, node identifier, data acquisition spatial range, data acquisition time range, and device conditions for consuming data that are allowed to acquire data.

[0056] Step S200: The second device receives a first response message, wherein the first response message includes a reply forwarded by the intermediate node confirming that its capability information has been successfully recorded, and / or the first device replies to the second device confirming that its capability information has been successfully recorded;

[0057] Specifically, the first device is a device or network element that provides data management functions (such as the DMF in the wireless communication system mentioned above); the second device is a device that provides data. Capability information can be used to indicate that the second device has data acquisition capabilities. When a core network node or access network node with data acquisition capabilities goes online, or a terminal with data acquisition capabilities enters the jurisdiction of the first device, or a relevant node starts its relevant data acquisition function, the data-providing device registers its data acquisition capabilities with the first device. Capability information includes, but is not limited to, data type, its own node type, its own node ID, data acquisition spatial range (TAI, RNA, and / or cell), data acquisition time range, and / or the device conditions that allow the acquisition of data from consumer data.

[0058] In some embodiments, a data acquisition task is assigned to one of the at least one second device; wherein the data acquisition task is matched with the capability information of the node.

[0059] In some embodiments, the at least one second device includes a terminal device, an access network node, or a core network node, and when the terminal device, access network node, or core network node is a data providing device, the capability information is forwarded through an intermediate node.

[0060] When the second device receives the response message, it means that the capability information reported by the second device has been successfully recorded.

[0061] Referring to Figure 4, this communication method, by executing steps S100 and S200, enables the first device (such as DMF) to manage the data acquisition capabilities within its jurisdiction.

[0062] Steps S100 and S200 will be described in detail below through Examples 1 and 2.

[0063] Example 1

[0064] In some embodiments, the second device is a terminal device, and when the terminal device is a data-providing device, the capability information is forwarded through an intermediate node.

[0065] In some embodiments, the capability information is carried in registration information, which includes, but is not limited to, at least one of the following: terminal device identifier, capability information, and / or terminal device location information.

[0066] In some embodiments, the first response information indicates that the data acquisition capability has been successfully registered.

[0067] Specifically, as shown in Figure 5, the UE (Terminal Equipment or User Equipment) can report this data acquisition capability through Non-Standalone Access (NAS) messages and register with the DMF during the registration process. The UE can first report its data acquisition capability to the intermediate node (core network equipment) during the registration process. The data acquisition capability reported by the UE mainly includes the types of data that can be collected. During the registration process, the AMF can add the cell identifier of the cell where the UE is currently located and the tracking area (TA) information to the data acquisition capability description to improve the UE's data acquisition capability description. Reporting through the registration process can accommodate both initial UE registration and mobility registration scenarios, facilitating the DMF's real-time awareness of whether the UE, as the data provider, is still within its jurisdiction. For example, the UE completes the data acquisition capability reporting process through a procedure containing one or more of the following signaling messages.

[0068] Step 1: The UE initiates a registration request via a NAS message. The existing NAS layer registration request message is extended by adding a data acquisition capability information element. This element may further include at least one of the following information: the data type that can be acquired, the time range for data acquisition, and / or the consumer conditions that allow data acquisition. The data type DMF can be used to match the UE with subsequent data acquisition tasks.

[0069] Step 2: The AMF processes the UE's registration request and recognizes that the UE has reported data collection capabilities. For the mobility registration process, the AMF obtains the old DMF information (the DMF of the previous service or the DMF that provided the service last time) through the UE Context, and determines whether the DMF needs to be updated based on the service scope of the DMF. If so, the UE's data collection capabilities are deregistered on the old DMF.

[0070] Step 3: Based on the data acquisition capabilities reported by the UE, the AMF further adds the relevant UE ID and / or the UE's location (cell, and / or TAI) to mark the geographical range of data that can be collected. The AMF ID registered by the UE is used to facilitate the target DMF (or the DMF currently providing the service) to find the UE later. The AMF initiates data acquisition capability registration with the DMF for the UE.

[0071] Step 4: The DMF responds with a confirmation that the data acquisition capability registration is successful, indicating that the UE's data acquisition capability has been recorded. This capability will be matched with a data acquisition task. If the data acquisition capability matches an existing data acquisition task, the DMF can initiate a signaling process to issue the data acquisition task to the data-providing device. This function also applies to scenarios where access network nodes and core network nodes register their data acquisition capabilities as data-providing devices.

[0072] Step 5: The AMF stores the DMF information (recording the target DMF currently providing services) in the UE Context and continues to execute the remaining registration process.

[0073] It is worth noting that with the evolution of 6G networks and future communications, UEs are also allowed to directly send a NAS message to the DMF after completing the registration process to register their data acquisition capabilities. In this case, the NAS message contains at least one of the following: UE ID, the types of data the UE can collect, the spatial and temporal range of the data that can be collected, and / or the currently registered AMF, etc.

[0074] It is worth noting that steps 1 to 5 above can be implemented independently to complete the interaction of UE capability information. The interaction includes the reporting of UE capability information and the response received by UE.

[0075] In some embodiments, after receiving registration information containing capability information, the first device sends reference information, which is used to instruct the device that provides data to modify the specified data acquisition capability, as detailed in Embodiment 2.

[0076] Example 2

[0077] As shown in Figure 6, the device providing data calls the Application Programming Interface (API) `... / Ndmf_DataCollectCapability` via a POST request. The message body contains capability information and / or task receiving information, which is used to receive subsequent data collection tasks. A single data-providing device can register data collection capabilities for different services separately.

[0078] The capability information used for data acquisition includes, but is not limited to, the device identity information (node ​​ID, node IP port address, and / or UE ID, etc.) that provides the data, the data type that can be acquired, the geographic range of the data source (cell ID List, RNA List, and / or TAI List), the time range of the data that can be acquired, and / or the consumer conditions that allow data acquisition.

[0079] For Task Receiving Info, access network nodes and / or core network nodes can provide a callback URI on the SBI to receive subsequent data acquisition tasks. When the device providing the data is a UE, the registered AMF can be provided to initiate paging of the UE when subsequent acquisition tasks are issued.

[0080] When the capability information is successfully registered, the DMF replies with a 201 message, including a reference (DataCollectCapabilityReference) to identify the registered data collection capability profile. This reference information allows the data-providing device to modify the specified data collection capability.

[0081] When capability information registration fails, the DMF returns 4xx (e.g., 400, 401, 404) or 5xx (e.g., 500, 503) results, specifying the exact cause of the error in the Problem Details. Possible errors include cell errors or the device providing the data not being within the current DMF management scope.

[0082] It is worth noting that Example 1 can be implemented independently, and Example 2 can also be implemented independently.

[0083] In some embodiments, after the second device sends registration information containing capability information, it sends updated capability information and / or deregistered capability information through the function interface of the data management function, as detailed in Embodiments 3 and 4.

[0084] Example 3

[0085] As shown in Figure 7, when the data-providing device's data type is updated or it moves to a new geographical location, the data-providing device can initiate a data collection capability update to the DMF. The DMF can provide the update as a service operation in the updated capability information (Ndmf_DataCollectCapability) service.

[0086] The device providing the data calls the API `... / Ndmf_DataCollectCapability / DataCollectCapabilityReference / update` via HTTP Method POST. The `DataCollectCapabilityReference` returned by the registration service identifies the data collection capability information that needs updating. The message body contains the specific data collection capability information, sharing the same data structure as the message body used during registration, but may only carry the information elements that need to be changed.

[0087] If successful, the DMF will respond with a 200 OK error. If it fails, the DMF will return a 4xx or 5xx error and specify the exact reason for the error in the ProblemDetails section.

[0088] Example 4

[0089] As shown in Figure 8, when a data-providing device (either the data-providing device or the data acquisition device) terminates its data acquisition function or leaves the current DMF management scope, the data-providing device or mobility management node cancels its data acquisition capability with the DMF. The DMF can provide a deregister as a service operation within the Ndmf_DataCollectCapability service.

[0090] The device providing the data calls the API ... / Ndmf_DataCollectCapability / DataCollectCapabilityReference, deregister / via HTTP Method POST. The DataCollectCapabilityReference returned by the registration service identifies the data collection capabilities that need to be deregistered.

[0091] DMF deletes the specified capability information used for data acquisition and replies with a 204 No Content error.

[0092] It is worth noting that Embodiment 3 can be based on Embodiment 1 or Embodiment 2; Embodiment 4 can be based on Embodiment 1 or Embodiment 2; Embodiments 3 and 4 can be based on Embodiment 1 or Embodiment 2.

[0093] Step S300: The first device receives at least one creation information and / or notification information sent by the third device, wherein the creation information indicates the creation of a first data acquisition task, and the creation information includes, but is not limited to, at least one of the following: data type, data source, data frequency, data acquisition task list, data reporting cycle, data storage information, data processing information and / or data transmission target, and the notification information indicates the control plane address of the device consuming the data.

[0094] Step S400: When it is determined that the first data acquisition task can be completed, the method further includes: sending a second response information corresponding to the creation information, wherein the second response information indicates that the first data acquisition task has been successfully established, and / or assigning an acquisition task identifier ID.

[0095] It is worth noting that steps S300 and S400 can be implemented based on steps S100 and S200, enabling automatic matching between the data-providing device and the data collection requirement. Alternatively, steps S300 and S400 can be implemented independently of steps S100 and S200, allowing the data-consuming device to request data collection from the designated data-providing device. Steps S300 and S400 can then complete the management services for the first data collection task.

[0096] Specifically, the third device can be a data-consuming device. In step S300, the third device can specify the required data through the first data acquisition task in the creation information, but does not need to describe the data acquisition configuration in detail (such as the specific acquisition configuration of the air interface). The specific data acquisition configuration is determined or negotiated by the data-providing device based on the first data acquisition task. If the data-consuming device is a UE, the creation information is transmitted through NAS; if the data-consuming device is an access network or core network node, the creation information is transmitted through the control plane (SBI); if it is an AF node outside the 3GPP network, the data acquisition capability of the 3GPP network is exposed through the Data Exposure Function (DEF), that is, the AF is allowed to call the data acquisition task to create through NEF, which is equivalent to exposing the data acquisition capability of the 3GPP network to the outside of the network.

[0097] DMF provides a primary data acquisition task management service to devices consuming data. This service allows devices to declare the data types they need to acquire, as well as information about the data source nodes, geographic locations, and time. DMF matches the data types and sources with registered data acquisition capabilities, checks if any data-providing devices can provide the specified type of data within the specified time and space range, and then distributes the acquisition task to the corresponding data-providing device. DMF can provide one or more of the following service interfaces to devices consuming data.

[0098] Steps S300 and S400 are further discussed below through examples, see Example 5 for details.

[0099] Example 5

[0100] As shown in Figure 9, the device consuming data calls the ... / Ndmf_DataCollectTaskManagement service via POST. The message body contains creation information (collection task information) and / or task notification information.

[0101] The creation information (data acquisition task information) may include one or more of the following information elements to describe the data to be acquired and subsequent transmission requirements:

[0102] Data Type: Corresponding to the data type in the capability information, it describes the type of data required. The device providing the data can further determine the specific measurement configuration scheme through the data type.

[0103] Data Source ID in the data source: The target of the data source, which gives the specific ID of the device that provides the data. Specific data can be obtained by specifying one or more devices that provide the data.

[0104] Data Source Location: Specifies the geographic location range of data collection that the data collection task is interested in. This can be specified using cell, Radio Access Network (RNA), and / or Tracking Area Identifier (TAI).

[0105] The target time range (data source period) in the data source field specifies the time when the data of interest to the data collection task was generated. This can be a past time period, a future time period, or the current moment. If it is a future time period, the collection task will automatically expire and be deleted across the entire network after the termination time.

[0106] Data collection period or not: This refers to whether the device providing the data is required to collect data repeatedly at a specific period or to transmit data only once.

[0107] Data Collection Task List: Devices consuming data specify one or more registered data collection tasks, requiring data-providing devices to immediately report the data required for that task. This method can bypass the reporting cycle and target conditions configured in the original data collection task, triggering a temporary, on-demand data transmission.

[0108] Data Report Period: This parameter requires the data-providing device to periodically report the collected data. It does not need to be the same as the data collection period. If this parameter is not included or its value is 0, it means that the data-consuming device requires the data-providing device to report the data immediately after collection.

[0109] Data Transfer Target List (or Data Transfer Target): The device consuming the data specifies the target for subsequent data transfers, which can be a node ID, IP address, etc. A device consuming data can specify multiple data transfer targets, including specific data service functions (DSFs) used to store data.

[0110] Data Storage Info: Indicates whether the data needs to be stored over the network. If no DSF is specified in the Data Transfer Target Listor, the DMF should proxy the selection of an appropriate DSF.

[0111] Data Processing Info: Indicates whether the data needs processing before being transmitted to the device consuming the data. It allows you to specify the required processing and the processing node. If no processing node is specified, the DMF can select the appropriate Data Processing Function (DPF) based on the required processing agent.

[0112] The task notification information indicates the control plane address of the device consuming the data, which is used to notify the device consuming the data when the feasibility of the data acquisition task changes.

[0113] If a matching acquisition capability exists, the DMF creates the current data acquisition task and assigns a Data Acquisition Task ID in the 201 Created response. If no match is found, the system replies that the data acquisition task creation failed.

[0114] Devices consuming data can indicate in the data acquisition task whether the task needs to be executed immediately. If deferred execution is allowed, the task will be created even if no data-providing device has the acquisition capabilities to match the current data acquisition task, waiting for a suitable data-providing device to become available.

[0115] In some embodiments, after receiving creation information, the first device receives an update and / or cancellation message for the first data acquisition task. In some embodiments, the method further includes the first device matching a data providing device according to the updated first data acquisition task. See Embodiments 6 and 7 for details.

[0116] Example 6

[0117] As shown in Figure 10, the device consuming data calls the ... / Ndmf_DataCollectTaskManagement / TaskID / update service via POST. The message body (creation information) contains the updated collection task information. Alternatively, the device consuming data can provide only the modified portion of the collection task information.

[0118] DMF matches the data-providing device with the new data acquisition task information. If a data-providing device can be matched, or if no data-providing device can be matched, the new data acquisition task can be postponed, and a 200 OK response is sent. If the data-providing device remains unchanged, DMF updates the data acquisition task to the data-providing device via notification. If there are changes, DMF cancels the outdated data acquisition task via notification and issues a new data acquisition task to the new data-providing device. If no data-providing device can be matched and the task requires immediate execution, a 4xx or 5xx response is sent, stating the specific reason for failure in the Problem Details. In this case, DMF can delete the failed update of the acquisition task and notify the previously matched data-providing device.

[0119] Example 7

[0120] As shown in Figure 11, the device consuming data calls the … / Ndmf_DataCollectTaskManagement / TaskID / delete service via POST.

[0121] DMF deletes the data acquisition task corresponding to Task ID and sends a 204 No Content response. DMF then sends a notification to the data-providing devices that previously matched and accepted the data acquisition task, canceling the corresponding data acquisition task.

[0122] It is worth noting that Embodiment 6 may include steps S300 and S400; Embodiment 7 may include steps S300 and S400; Embodiments 6 and 7 may include steps S300 and S400.

[0123] Furthermore, as shown in Figure 12, in some other separate embodiments, when a data acquisition task experiences a change in execution status due to a change in data acquisition capability, the DMF can notify the data consuming device through this notification. The execution status of the data acquisition task may change from executing to inexecutable; from executable to inexecutable (waiting for a capable device to provide data); or from inexecutable to executable.

[0124] Furthermore, as shown in Figure 13, in some other separate implementations, the DMF matches the data acquisition task with the data acquisition capability of the data-providing device, and then issues the acquisition task through the task receiving address registered by the data-providing device. If the data-providing device is a UE, then it initiates a paging and downlink NAS transmission process by receiving information from the designated AMF.

[0125] This notification can be activated when a data collection task is created, updated, or deleted. Based on the specific content of the Task Info, DMF can create, update, or cancel a specified data collection task at the device providing the data.

[0126] Furthermore, in some other separately implemented embodiments, based on the self-contained nature of the SBA architecture, a service ideally only needs to rely on the resources it manages to complete its task. The data acquisition service depends on the data acquisition capability information managed by the service provider. The two services can be merged; that is, the data acquisition service and the data acquisition capability information can be combined, and the above functions can be implemented through different service operations. In other words, each of the above embodiments provides one service, and each URL represents a service operation. After merging the two services, the URLs can be further subdivided to distinguish the service operations corresponding to each URL.

[0127] In some embodiments, multiple creation information is received, and the multiple creation information is compared and analyzed to determine several differences.

[0128] Specifically, as shown in Figure 14, to avoid data-providing devices repeatedly measuring and transmitting the same data, the DMF can compare data acquisition tasks. For multiple tasks, if the data requirements are the same, only one data acquisition task (such as the one requiring the highest reporting frequency) is issued to the data-providing device. The remaining acquisition tasks are associated internally within the DMF, and transmission bearers are established simultaneously for all data-consuming devices during subsequent data transmission.

[0129] For example, if the DMF comparison finds that the tasks overlap, the DMF can be associated with each other, and the difference can be sent to the device that provides the data for subsequent tasks only, thus reducing the burden on the device that provides the data.

[0130] By comparing the Data Type, Data Source ID, Data Source Location, and Data Source Period of the creation information for each data acquisition task, if they are the same, it indicates that the same type of data was collected from the same data provider in the same area at the same time, and the tasks can be directly merged. In this case, if the reporting periods are different, the DMF needs to update the reporting periods to meet the requirements of each task.

[0131] If the Data Source ID contains an existing task and other parameters are the same, DMF will only issue a new acquisition task to the newly added data providing device. For duplicate devices, no new task will be issued, but the old task will be associated with the new task.

[0132] If the Data Source Location and Data Source Period contain existing tasks and other parameters are the same, the DMF will only issue data collection tasks for new areas or time periods.

[0133] In one implementation, the device consuming the data can specify, through the data transmission target, whether the collected data needs to be transmitted directly to a consumer or transmitted to a DSF for storage.

[0134] In some embodiments, after the first device executes step S300, when the first data acquisition task is single, small in quantity and / or immediate, the first device instructs the data providing device to complete the data transmission through the control plane. For details, see Embodiment 8, which can be implemented independently.

[0135] Example 8

[0136] Specifically, for single, small-volume, and immediate data transmissions, the DMF or the data-providing device can choose not to establish an additional data plane transmission bearer and directly complete the data transmission through the control plane. As shown in Figure 15, the DMF or the data-providing device completes the data transmission through a process consisting of one or more signaling commands.

[0137] 1. Devices that collect consumer data create data acquisition tasks.

[0138] 2. The DMF issues a data acquisition task to the matched data-providing device. If the DMF determines that the task can be transmitted via the control plane, it sends an indication to the data-providing device to directly report the data in its response.

[0139] 3. If the data-providing device receives a control plane data transmission indication or independently determines that the data transmission can be completed through the control plane, it will include the data to be transmitted in the notification response. In scenarios where the data-providing device makes its own determination, it will include an indication in the DMF's response that data transmission is possible.

[0140] 4. The DMF notifies the device consuming data that the data acquisition task has been completed via a data acquisition task change notification. The notification includes the data acquisition task identifier (Task ID) and the data to be transmitted, and the task status is set to completed. The device consuming data then reads the data from the notification.

[0141] In some embodiments, the method further includes a first device matching a first data acquisition task with data acquisition capabilities to determine whether the first data acquisition task can be completed.

[0142] Specifically, if the first device matches the data acquisition task with the data acquisition capabilities within the DMF management area, it will reply that the first data acquisition task has been successfully established and assign an acquisition task ID; if the first device does not match the data acquisition task with the data acquisition capabilities within the DMF management area, it will reply that the first acquisition task has failed to be established and provide information on the elements that cannot be satisfied in the acquisition task. The first device can decide whether to establish an additional data plane carrier based on the data acquisition task.

[0143] Step S500: The first device sends a second data acquisition task to the second device based on the matching result of the first data acquisition task and the data acquisition capability. The second data acquisition task includes, but is not limited to, at least one of the following: acquisition task ID, data type, data source, and data frequency.

[0144] Specifically, based on the matching result between the first data acquisition task and the data acquisition capability, the first device sends a second data acquisition task to the data-providing device whose data acquisition task and data acquisition capability match. If the first data acquisition task matches the capability information used for data acquisition, the issued second data acquisition task includes, but is not limited to, acquisition task ID, acquisition data type, acquisition data source (target geographical location, and / or target time range), and / or acquisition data frequency (one-time, and / or periodic).

[0145] In some embodiments, when it is determined, based on preset rules, that the second data acquisition task is to be completed jointly by multiple data providing devices, multiple second data acquisition tasks are sent in parallel.

[0146] Specifically, the preset rule can be the number of devices providing data indicated by NW or the number of devices providing data in a specified area that meet the capability information for data acquisition. If DMF matching determines that the acquisition task requires multiple devices providing data to complete together, then DMF will send a second data acquisition task to multiple devices providing data in parallel.

[0147] In some embodiments, the device providing the data determines the specific measurement configuration required for execution based on the data acquisition task. If the device providing the data cannot determine the measurement configuration itself, it actively negotiates the required measurement configuration with other nodes, such as the UE and RAN collaborating to complete the air interface measurement configuration. In addition to nodes that provide data measurement capabilities, the device providing the data can also be a Data Storage Function (DSF), which directly queries the database based on the acquisition task.

[0148] In some embodiments, the device providing the data can further break down the second data acquisition task and distribute it to other devices providing data, as detailed in Embodiment 9; it is worth noting that Embodiment 9 can be implemented independently.

[0149] Example 9

[0150] As a data provider, the received data acquisition task can be further decomposed into sub-tasks that can be executed by other data-providing devices. For example, if an access network node receives a task requiring data collection within a specific cell, it can further distribute this task to UE nodes within that cell for actual measurement and collection. In this case, the access network node essentially provides DMF functionality within the access network and acts as a data-consuming device for the sub-task, receiving the data transmission from the sub-task. After aggregating and processing the data acquisition results from the sub-tasks, the access network node provides the data to the actual data-consuming device.

[0151] This functionality can also be applied to data acquisition tasks across distributed subnets. Within a subnet, the DMF represents the entire subnet as a unified data provider and consumer, uniformly handling data transmission needs within the subnet and determining which data acquisition capabilities can be provided to other subnets or the central network node.

[0152] As shown in Figure 16, a data-providing device with the ability to break down data acquisition tasks instructs other data-providing devices to acquire data through a process consisting of one or more of the following signaling messages:

[0153] 1. Data-providing devices 2 and 3 can register their data acquisition capabilities with data-providing device 1. Data-providing device 1 registers its data acquisition capabilities with the DMF, which includes the data acquisition capabilities of data-providing devices 2 and 3. Data-providing device 1 may register its relevant data acquisition capabilities with the DMF through network planning and other configuration information without requiring active registration from devices 2 and 3. Data-providing device 1 can also perform DMF functions within a certain scope.

[0154] 2. Devices consuming data create a data acquisition task in the DMF. The DMF assigns Task ID 1.

[0155] 3. The DMF sends a data acquisition task to the matching data-providing device 1, which includes Task ID 1.

[0156] 4. Device 1, providing data, determines that this task requires the collaborative completion of devices 2 and 3, which also provide data. Based on the capabilities of devices 2 and 3, it breaks down the current task and issues data acquisition tasks to them, each containing subtask ID 1 and subtask ID 2. Device 1 maintains the mapping relationship between Task ID 1 and subtask IDs 1 and 2.

[0157] 5. Devices 2 and 3, which provide data, complete their data acquisition tasks and report the data to device 1, which also provides data. The reporting message specifies that the corresponding data acquisition tasks are subtask ID 1 and subtask ID 2.

[0158] 6. Device 1, which provides the data, recognizes that all subtasks of Task ID 1 have been completed and summarizes and transmits the corresponding data.

[0159] Step S600: The first device receives a third response message sent by the second device, wherein the third response message indicates that a data acquisition task has been created and the first device can execute the second data acquisition task.

[0160] It is worth noting that step S500 can be implemented together with step S600 to dispatch a data acquisition task to the data-providing device and start its data acquisition function; step S500 and step S600 can be implemented together with steps S300 and S400 to call the data acquisition capability of the specified data-providing device according to the needs of the data-consuming device; step S500 and step S600 can be implemented together with steps S100 and S200, and steps S300 and S400 to automatically match the data-providing device that meets the needs of the data-consuming device and call its corresponding data acquisition capability.

[0161] Step S700: Receive the data plane transmission establishment request message.

[0162] Specifically, after completing data acquisition, the data-providing device invokes the data transmission management service provided by the DMF to initiate a data plane transmission establishment request. The service interfaces provided by the DMF are detailed above. The data-providing device reports a task ID to the DMF, indicating the data acquisition task to be served by the subsequent data plane transmission. If a bidirectional data plane transmission bearer needs to be established, the data-providing device provides its own connection or routing information.

[0163] In some embodiments, if the device consuming data is a UE, the data plane transmission establishment request message is received and transmitted through NAS. The subsequent transmission establishment process involves additional access network node signaling, as detailed in Embodiment 10. It is worth noting that Embodiment 10 can be implemented independently.

[0164] Example 10

[0165] As shown in Figure 17, the UE, as a common data provider, needs to establish data plane transmission at the reporting time specified in the task after completing the data acquisition task. Data plane transmission can be unidirectional (since data reporting does not require interaction of service data between the two parties) or bidirectional, depending on service requirements. The UE establishes data plane transmission through a process consisting of one or more of the following signaling rules.

[0166] 1. The UE initiates a data plane transmission establishment request to the DMF via a NAS message. The request includes the UE ID and the data acquisition task ID to which the data to be reported belongs.

[0167] 2. The DMF identifies the device that needs to transmit the corresponding consumer data based on the data acquisition task ID. The DMF sends a data plane transmission establishment request to all addresses based on the device address of the consumer data recorded in the data acquisition task. The request includes the corresponding task ID and transmission quality requirements. If tasks are managed in a merged manner as described above (e.g., for multiple tasks, if the data acquisition requirements are the same, only one data acquisition task (e.g., the one requiring the highest reporting frequency) is issued to the data-providing device; the remaining acquisition tasks are associated internally within the DMF, and transmission bearers are established simultaneously for all data-consuming devices during subsequent data transmission), the request sent by the DMF to each data-consuming device includes the task ID returned when the task was created.

[0168] 3. The device consuming data allocates the corresponding data plane resources and provides data plane connection information based on the transmission establishment request. This information may be an IP port address, tunnel information (GTP protocol), or other information, depending on the data plane bearer method. If the device consuming data has data transmission requirements to the UE, it can also include an indicator in this response.

[0169] 4. The DMF sends a data plane transmission configuration request to the base station where the UE is located, including the UE identifier (UE ID) and data plane connection information of the device consuming data. Based on the information provided by the device consuming data, the DMF indicates to the base station whether it is necessary to transmit the base station-side data plane connection information to establish a downlink connection. Depending on the RAN architecture, this message can be forwarded by the AMF or sent directly via the SBI.

[0170] 5. The base station configures the air interface resources required for data plane transmission for the UE. At this point, the data plane uplink transmission channel has been established, and the UE can begin sending data to the devices consuming the data.

[0171] 6. The base station sends a data plane transmission configuration response to the DMF. If the base station is instructed to establish bidirectional data plane transmission, the base station carries the data plane connection information allocated to the UE in the response.

[0172] 7. When bidirectional data plane transmission needs to be established, the DMF updates the base station's data plane connection information to the data consuming device. At this time, the data consuming device obtains the data plane transmission connection address on the base station side and can send downlink data.

[0173] In some embodiments, the UE receives the transmission as a device for consuming data, as detailed in Embodiment 11. It is worth noting that Embodiment 11 can be implemented independently.

[0174] Example 11

[0175] As shown in Figure 18, when the UE acts as a data-consuming device, after the DMF receives a data transmission establishment request initiated by the data-providing device, it establishes direct data plane transmission between the UE and the data-providing device through a process containing one or more of the following signaling:

[0176] 1. The device providing the data sends a data transmission establishment request to the DMF. The request contains the task ID of the acquisition task served by the subsequent data transmission.

[0177] 2. The DMF matches the device consuming data based on the task ID. When the device consuming data is a UE, a data transmission trigger command is issued via a NAS message, containing the task ID that triggered the command. This NAS signaling can be paging and forwarded via the AMF and / or base station.

[0178] 3. The UE initiates a data plane transmission establishment request to the DMF based on the triggering command, including its own UEID and the Task ID of the associated task. If the UE needs to provide data to the data-providing device in this Task, it can also indicate this in the establishment request.

[0179] 4. The DMF sends a Data Session Setup Request to the base station based on the transmission requirements registered by the data acquisition task, which includes the UE ID and transmission quality control parameters.

[0180] 5. The base station configures air interface resources according to the data plane transmission configuration.

[0181] 6. The base station sends a data plane transmission configuration response to the DMF, which includes the data plane connection information allocated by the base station for the UE.

[0182] 7. The DMF sends a data plane transmission establishment reply to the data-providing device, which contains the data plane connection information allocated by the base station to the UE. At this point, the data-providing device can send data to the UE.

[0183] 8. If an instruction to establish bidirectional data transmission is received in step 3, the DMF executes signaling steps 2, 3, and 4 in 4.7.1 to update the data plane connection information of the data-providing device to the base station, which is not shown again in this figure.

[0184] In one implementation, replacing messages 2 and 3 in the process given in Example 10 with messages 2, 3, 4, 5, and 6 of Example 11 can establish a direct data plane dedicated transmission between a data providing UE and another data consuming UE.

[0185] In some embodiments, if the device consuming the data is a core network or access network node, this message is transmitted via the control plane (SBI, forwarded via AMF through NGAP).

[0186] Step S800: The first device matches the third device according to the acquisition task ID, and / or sends a data plane transmission establishment request to the third device.

[0187] Specifically, the first device matches the third device that needs to receive data based on the task ID, and / or sends a data plane transmission establishment request to the third device, whose address can be determined according to the data transmission target specified by the device consuming data in step S300.

[0188] Optionally, if a bidirectional data plane transport bearer needs to be established, the request may include connection or routing information of the device providing the data.

[0189] Optionally, if the device consuming the data is a UE terminal, additional access network-related signaling is involved, as detailed in Example 10, and will not be repeated here.

[0190] In some embodiments, the first device transmits data to at least one intermediate node for data processing or preprocessing according to the second data acquisition task, as detailed in Embodiment 12. It is worth noting that Embodiment 12 can be implemented independently.

[0191] Example 12

[0192] As shown in Figure 19, intermediate nodes can be such as Data Processing Functions (DPFs) or other nodes, without restriction. Depending on the business requirements of the data acquisition task, data may need to be transmitted to a designated intermediate node for processing before being transmitted to the data consumption device. A DMF establishes a data plane transmission including intermediate processing nodes through a process containing one or more of the following signaling:

[0193] 1. The device providing the data initiates a data plane transmission establishment request. The device providing the data may include in this message whether data processing is required and / or specify a data processing node.

[0194] 2. The DMF matches the device consuming the data with the data acquisition task and sends a data plane transmission establishment request to the device consuming the data.

[0195] 3. The device consuming the data sends a data plane transmission establishment reply, which includes the data plane connection information of the device consuming the data. The device consuming the data may also include in this message whether data processing is required and / or specify a data processing node.

[0196] 4. Based on the instructions from both ends of the data transmission in steps 1 and 3 and / or the information recorded in the data acquisition task, the DMF determines whether an intermediate processing node (e.g., DPF) needs to be added, and selects an intermediate processing node. The DMF sends a data plane transmission configuration request to the intermediate processing node, including the data acquisition task ID, the required data processing services, and the data plane connection information of the devices consuming the data.

[0197] 5. The intermediate processing node replies with a DMF containing its data plane connection information. At this point, the data plane transmission from the intermediate processing node to the device consuming the data is established. After receiving the data from the device providing the data, the intermediate node can process and forward it to the device consuming the data.

[0198] 6. The DMF responds to the data-providing device's data plane transmission establishment request, which includes data plane connection information for intermediate nodes. At this point, the data-providing device can transmit data to the intermediate processing node via the data plane bearer. The data transmission carries a Task ID so that the DMF can match the corresponding data processing service and subsequent forwarding path.

[0199] In some cases, a single data transmission by a data-providing device may need to be transmitted to multiple nodes. For example, a data acquisition task may require additional storage of data on a storage node; or multiple data acquisition tasks may be found to require the same data to be collected. Therefore, the following communication method is disclosed in this disclosure.

[0200] In some embodiments, when the second data acquisition task matches multiple devices consuming data, a data plane transmission establishment request is sent to the multiple devices consuming data.

[0201] In one implementation, for a single data transmission request initiated by the data-providing device, the DMF can simultaneously establish multiple data plane transport bearers. See Embodiment 13 for details; it is worth noting that Embodiment 13 can be implemented independently.

[0202] Example 13

[0203] As shown in Figure 20, a transport bearer is established through a process that includes one or more of the following signaling:

[0204] 1. The device providing the data sends a data transmission establishment request to the DMF. The request contains the task ID of the acquisition task served by the subsequent data transmission.

[0205] 2. The DMF matches multiple data transmission targets. The DMF sends data transmission establishment requests to each of the devices or data storage functions (DSFs) that are the targets for consuming data.

[0206] 3. Each device consuming data sends a data plane transmission establishment reply, which includes the data plane connection information of the device consuming data and the corresponding data acquisition task ID.

[0207] 4. The DMF aggregates the data plane connection information of the devices receiving consumer data, forming a data plane connection information list, and replies it to the data-providing device. If task merging as described above exists (e.g., for multiple tasks, if the data collection requirements are the same, only one data collection task (e.g., the one requiring the highest reporting frequency) is issued to the data-providing device, and the remaining collection tasks are associated internally within the DMF, establishing transmission bearers to all consumer data devices simultaneously during subsequent data transmission), the DMF specifies the corresponding Task ID for each data plane connection information in the list. The data-providing device directly transmits data to each data plane endpoint via the data plane bearer. The data transmission carries the corresponding Task ID to inform the consumer data device of the corresponding collection task.

[0208] In another implementation, the DMF can choose to insert intermediate proxy nodes to complete data distribution. In this case, the device providing the data only needs to send the data out once, and the intermediate data forwarding proxy node will complete the distribution and transmission to each device consuming the data. See Embodiment 14 for details. It is worth noting that Embodiment 14 can be implemented independently.

[0209] Example 14

[0210] As shown in Figure 21, a transport bearer is established through a process that includes one or more of the following signaling:

[0211] 1. The device providing the data sends a data transmission establishment request to the DMF. The request contains the task ID of the acquisition task served by the subsequent data transmission.

[0212] 2. The DMF matches multiple data transmission targets. The DMF sends data transmission establishment requests to each of the devices or data storage functions (DSFs) that are the targets for consuming data.

[0213] 3. Each device or DSF that consumes data as the data transmission target replies with data plane connection information, and the message also includes the corresponding data acquisition task ID.

[0214] 4. The DMF aggregates the data plane connection information of the devices consuming data or the DSF, forming a list of target data plane connection information for the current transmission, and sends it to the data proxy node. The DPF can also function as a data proxy. At this point, the transmission channels from the data proxy to each data-consuming device or DSF have been successfully established, and data distribution can begin as it awaits data transmission from the data-providing device.

[0215] 5. The node acting as the data proxy sends its own data plane connection information to the DMF via a reply.

[0216] 6. The DMF sends the Data Proxy's data plane connection information to the data-providing device via a reply. At this point, the data-providing device can transmit data to the data proxy node. The data transmission carries a Task ID for the proxy node to match subsequent forwarding paths.

[0217] Step S900: The device providing the data returns the connection or routing information required for its own data plane transmission. Depending on the bearer method, this information can be a Tunnel ID, an IP address, or a port.

[0218] Step S1000: The DMF sends the connection or routing information of the device consuming the data to the device providing the data.

[0219] In some embodiments, if there are intermediate nodes, see the processing method in Embodiment 12.

[0220] In some embodiments, if there are multiple devices with consumption data, see the processing method in Embodiment 13 or Embodiment 14.

[0221] Step S1100: The device providing data transmits data to the device consuming data via a data plane. The data transmission carries a Task ID to inform the device consuming data of the corresponding data collection task.

[0222] Furthermore, based on this service, service consumers can request the DMF to help establish a dedicated data plane transport bearer for a specified data transmission task. This bearer can handle the demand for high-speed, high-volume data plane transmission, and its protocol stack can include GTP, HTTP, FTP, etc., without limitation in this embodiment.

[0223] In some embodiments, after the data-providing device completes a data acquisition task or meets the reporting conditions specified in the data acquisition task, the data-providing device may actively request the DMF to establish a data plane transmission for the specified data acquisition task. As shown in Figure 22, the DMF provides this service through the following interface:

[0224] 1. The device providing the data calls the / Ndmf_DataSession API to obtain services. This message contains the task ID of the data collection task being served and the type of the current session establishment request. For the device providing the data, this value can be data_provider_trigger.

[0225] 2. The DMF matches the device consuming the data corresponding to the task. Based on the Data Transfer Target List (or Data Transfer Target List) received during the creation of the data acquisition task, there may be multiple targets. The DMF issues instructions to the control plane addresses provided by these targets, requesting the allocation of data plane connection resources and returning the results to the DMF. If successful, the DMF replies with a 201 Created response. The message body contains the Task ID and the data plane connection information of the device consuming the data. Different information may be included depending on the data plane transport bearer type. For example, when the data plane bearer uses the GTP protocol, it carries the tunnel ID; when the data plane bearer uses the HTTP protocol, it carries the IP address, port, and / or fully qualified domain name (FQDN).

[0226] 3. In case of failure, DMF will reply with a 4xx or 5xx error code and include specific information in the Problem Details, such as the data collection task not existing.

[0227] Upon receiving this service request, in order to complete the service, DMF may issue a data plane transport establishment instruction via an HTTP message on the SBI to the control plane address provided by the device consuming the data, in any of the following ways.

[0228] In some embodiments, the DMF can consider the device consuming data to directly provide a data plane transmission establishment service, accessing this service via the POST method. The Data Consumer directly replies with the established data plane transmission connection information in the 201Created form, as shown in Figure 23.

[0229] In some embodiments, the DMF can also notify the device consuming the data that a data plane transfer needs to be established. The device consuming the data transmits the data plane transfer connection information in its notification response. In this case, the Data Transfer Target List when creating the data acquisition task must provide the specific URI of the data receiver's control plane as the callback URI. The process is shown in Figure 24.

[0230] In some embodiments, the DMF can also notify the data-providing device of a data plane transmission establishment requirement, requesting the data-providing device to allocate data plane resources and then actively invoke the DMF's data plane transmission establishment service. In this case, the session establishment request type can be set to data_consumer_response. The process is shown in Figure 25.

[0231] Furthermore, devices consuming data can proactively request an immediate data reporting from a currently executing data acquisition task. To achieve this, besides creating a new single data acquisition task, a service can be established by accessing DMF data transfer, as shown in Figure 26.

[0232] Devices consuming data specify the data collection task to be reported immediately via Task ID, declared as data_consumer_trigger in Session Type. They can directly allocate data plane resources and provide data plane transport connection information in the request, or wait for the subsequent transport establishment process.

[0233] Upon receiving this service request, DMF transforms the transmission request into a single, immediate data acquisition task and sends it to the corresponding data-providing device via the signaling shown in Figure 12. Upon receiving the immediate data acquisition task, the data-providing device should immediately initiate the process shown in Figure 21 to establish a data plane transmission.

[0234] In some embodiments, steps S100-S1100 can be as shown in Figure 3.

[0235] It is worth noting that steps S700, S800, S900, S1000, and S1100 are implemented together to establish a dedicated data plane transmission channel and transmit data; steps S700, S800, S900, S1000, and S1100 can depend on steps S500 and S600 to invoke the data acquisition capability of a designated data-providing device based on an operation command and transmit the data to a designated data-consuming device via the data plane; steps S700, S800, S900, S1000, and S1100 can depend on... Steps S300, S400, S500, and S600 are implemented together to enable devices based on consumption data to invoke the data acquisition capabilities of designated data-providing devices and transmit and report data as needed through the data plane. Steps S700, S800, S900, S1000, and S1100 can depend on steps S100 and S200. Steps S300 and S400, and S500 and S600 are implemented together to enable devices based on consumption data to automatically match and invoke the data acquisition capabilities of data-providing devices and transmit and report data as needed through the data plane.

[0236] In some application scenarios, data transmission requests are not initiated by the data-consuming device itself, but rather by the data-providing device proactively based on the business context. For example, after providing a pre-trained model to the AI ​​model user, the AI ​​model training node collects the user's model performance data. Based on actual usage data, it fine-tunes the model and then proactively transmits model data back to the AI ​​model user to update the model. As shown in Figure 27, the data transmission process can be initiated through a flow containing one or more of the following signaling signals.

[0237] Step H100: The first device receives a data transmission establishment request message sent by the second device. The data transmission establishment request message includes at least one of the following: the device identifier for consuming data, the device filtering conditions for consuming data, and / or the association between the created data transmission task and the data acquisition task. The device identifier for consuming data may be, for example, the NF ID, gNodeB ID, and / or UE ID of the device consuming the data, and the device filtering conditions for consuming data may be, for example, geographical location and / or node type.

[0238] Specifically, the data-providing device can directly specify the consumer ID (NF ID, gNodeB ID, UE ID) or control plane address (IP port, FQDN) of the receiving data in the Data Session Establishment Request message, allowing the DMF to directly initiate the data transmission establishment process. In some implementations, the data-providing device can also register a Data Transmission Task with the DMF, providing the target consumer node information in the task information. In some implementations (e.g., AI model data update applications), the target of the proactive data transmission is related to a previously registered data acquisition task (e.g., collecting AI model performance for fine-tuning). Therefore, when creating a data transmission task, the data-providing device can associate it with several existing data acquisition tasks, specifying the data-providing device and / or data-consuming device as the target data-consuming device for this data transmission. This approach allows for flexible configuration of the data transmission target.

[0239] Step H200, see the relevant description in step S800, and will not be repeated here.

[0240] Step H300, see the relevant description in step S900, and will not be repeated here.

[0241] Step H400, see the relevant description in step S1000, and will not be repeated here.

[0242] Step H500, see the relevant description in step S1100, and will not be repeated here.

[0243] By executing steps H100-H500, data plane transmission initiated by the device providing the data is achieved.

[0244] In some embodiments, certain data acquisition tasks may not be completed within the current jurisdiction of the first device. In this case, the first device should be able to acquire relevant data from external sources. The first device needs the ability to access data acquisition from other areas, other network slices, or other subnets; in this embodiment, this is collectively referred to as accessing other distributed subnets.

[0245] In one implementation, cross-distributed network data acquisition and transmission includes cross-subnet data acquisition capability registration, as detailed in Embodiment 15. It is worth noting that Embodiment 15 can be implemented independently.

[0246] Example 15

[0247] As shown in Figure 28, the DMF provides data acquisition capability information to external devices within the proxy subnet that actually provide data through a process containing one or more of the following signaling:

[0248] 1. Devices providing data within the subnet register their data acquisition capabilities with the DMF and provide their addresses to receive subsequent data acquisition tasks.

[0249] 2. The DMF integrates the data acquisition capabilities within the subnet. Based on local and carrier configurations, it selects appropriate data acquisition capabilities to be opened to other subnets and aggregates them, adding a distributed subnet ID to indicate data ownership. In the data acquisition capability registration message, the DMF replaces the address in the task receiving information with its own. The DMF can initiate data acquisition capability registration with the DMF node in the central node network.

[0250] 3. DMFs can also directly register data collection capabilities with DMFs in a specified subnet based on local configuration and operator policies.

[0251] In one implementation, cross-distributed network data acquisition and transmission includes the creation of cross-subnet data acquisition tasks, as detailed in Example 16. It is worth noting that Example 16 can be implemented independently.

[0252] Example 16

[0253] As shown in Figure 29, the DMF creates a data acquisition task for devices that generate real consumption data within the subnet through a process agent that includes one or more of the following signaling:

[0254] 1. Devices consuming data invoke the DMF (Data Acquisition Function) within their subnet to create a data acquisition task. The acquisition task specifies the data source or a specific data type to indicate that it needs to acquire data from other subnets.

[0255] 2. The DMF determines whether data needs to be collected from other subnets based on the data acquisition task requirements. The DMF replies to the device consuming the data, including task ID 1 from within one subnet.

[0256] 3. Once the DMF has matched the data provision capability of another suitable subnet (registered via message 3 in Example 15), the DMF directly initiates a data collection task notification to the DMF of that subnet. The notification can carry a mask identifier (Mask ID) associated with the network (Internal) Task ID 1 for cross-subnet use, or it can directly use the Internal Task ID 1 assigned in message 2. The DMF of the device providing the data records the DMF address from which the task originated.

[0257] 4. If the DMF does not find a suitable data provider in another subnet locally, the DMF initiates a data acquisition task creation request to the DMF in the central node network, and transmits the data acquisition requirements of the devices consuming data.

[0258] 5. The central DMF assigns an External Task ID across subnets to identify the task. The central DMF then replies that the subnet DMF data acquisition task has been established.

[0259] 6. The central DMF sends a data collection task to the matched subnet DMF, which includes an External Task ID that identifies the task across subnets.

[0260] 7. The DMF of the data-providing subnet further distributes the data acquisition task to the data-providing devices, including the Task ID 2 assigned by the subnet DMF. The data-providing devices treat this as a normal data acquisition task.

[0261] In one implementation, cross-distributed network data acquisition and transmission includes cross-subnet data transmission establishment, as detailed in Embodiment 17. It is worth noting that Embodiment 17 can be implemented independently.

[0262] Example 17

[0263] As shown in Figure 30, the device providing data establishes cross-subnet data plane transmission through a process that includes one or more of the following signaling rules. The DMF and Data Proxy within each subnet can be the same node or different nodes.

[0264] 1. The device providing the data initiates the establishment of a data plane transmission, identifying that the transmission belongs to Internal Task ID 2 (assigned by message 7 in Example 16).

[0265] 2. The DMF matches the corresponding external Task ID and the external DMF based on Internal Task ID 2, and initiates the data plane transmission establishment. If the previous task was directly issued by the DMF of another subnet, this request is sent directly to the DMF of the corresponding subnet and carries Internal Task ID 1 or Mask ID (assigned in message 3 in Example 16).

[0266] 3. If the task issuance is controlled by the central DMF, the transmission establishment is also sent to the central DMF, carrying the External Task ID (assigned in message 4 in Example 16).

[0267] 4. The central DMF forwards the data plane transmission establishment request to the DMF of the data consumer side subnet.

[0268] 5. The DMF on the data consumption side matches the received collection task ID. If it is an external identifier (External ID) or an external version of an internal identifier (Internal Task ID 1) (assigned in message 3 in embodiment 16), then it matches the Internal ID 1 used within the subnet and initiates data transmission establishment to the device that actually consumes the data.

[0269] 6. Devices consuming data return their own data plane connection information.

[0270] 7. If the DMF in the subnet and the Data Proxy connecting the internal and external data planes of the subnet are not the same node, the DMF sends a Data Session Setup to the Data Proxy. This includes the device data plane connection information for consuming data and Internal Task ID 1. If an external ID exists, it should also be included. At this time, the Data Proxy waits for data transmissions from other subnets with External ID, Mask ID, or Internal Task ID 1, and converts them into data transmissions identified by Internal Task ID 1 before sending them to the device consuming the data.

[0271] 8. Data Proxy returns its own data plane connection information.

[0272] 9. If the data plane transmission establishment request comes directly from the DMF (message 2) of another subnet, the DMF will directly return a data transmission establishment reply, which includes the data plane connection information of the Data Proxy of this subnet.

[0273] 10. If the data plane transmission establishment request comes directly from the central DMF (messages 3 and 4), the DMF will send a reply to the central DMF.

[0274] 11. The central DMF will forward the response to the DMF of the data-providing subnet.

[0275] 12. If the DMF in the subnet and the Data Proxy connecting the internal and external data planes of the subnet are not the same node, the DMF sends a Data Session Setup message to the Data Proxy. The message contains the data plane connection information of the consumer-side Data Proxy, the Internal Task ID 2 of the device providing the data within the subnet, and the External ID or the external version (i.e., mask task ID, a mask used to generate a task ID) assigned to Internal Task ID 1 by the consumer, or the Internal Task ID 1 of the device consuming the data. At this time, the data-providing device Data Proxy waits for data transmission identified as Internal Task ID 2, and then sends the data transmission to the data-consuming device Data Proxy with the External ID, Mask ID, or Internal Task ID 1.

[0276] 13. Data Proxy returns its own data plane connection information.

[0277] 14. The DMF replies to the data-providing device, including the Data Proxy data plane connection information for the providing subnet. The data-providing device sends a data transmission identified by Internal Task ID 2 to the Data Proxy.

[0278] Furthermore, this disclosure achieves at least one of the following technical effects through the various communication methods described above: 1. It provides a unified data acquisition process, enabling data acquisition and transmission services to be obtained through a single process for all data-providing devices and consumers within the network, regardless of whether they are UEs, RAN nodes, or core network nodes, thereby reducing the complexity of network process implementation; 2. It provides a unified data management node, which can clearly and easily identify the data available for acquisition in the current network; facilitating network operators to identify and provide network data, conveniently offering data as a service to customers, and developing the commercial potential of the large amount of data collected in the network. Devices consuming data can also easily and intuitively understand the available data through a platform, thus matching their actual needs; 3. The provided data plane management method allows users to dynamically configure their own data acquisition capabilities, no longer relying on pre-configuration or protocol message formats, facilitating network users to update their data acquisition and transmission functions as their actual needs evolve; 4. For the devices being collected, the devices consuming data (users) can specify the data they can provide and the devices that can acquire the corresponding data, giving users complete control over their data exposure and allowing data to be collected only when permitted by the user.

[0279] This document describes data processing methods applicable to communication such as between a UE and a base station, and between a core network and a base station. However, these inventive concepts, methods, apparatuses, devices, computer-readable storage media, chips, and computer program products are not limited to wireless communication and can be extended to other communication scenarios to achieve the same technical benefits and effects.

[0280] In these scalable communication scenarios, the first and / or second and / or third devices can be entities such as User Equipment (UE), base stations (e.g., gNB, eNodeB, Transmitter Receiving Point (TRP), NodeB for next-generation communication, or Wi-Fi access points), or network elements. User Equipment (UE) refers to a device used for communication at the user end, such as a mobile phone, and can also be called a terminal, mobile station, or mobile terminal. UE can be various devices, including but not limited to mobile phones, tablets, virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals for industrial control, wireless terminals for autonomous driving, wireless terminals for remote medical surgery, wireless terminals for smart grids, wireless terminals for environmental monitoring, wireless terminals for smart cities, and wireless terminals for smart homes, etc.

[0281] Furthermore, UEs and base stations can be deployed in various environments, including but not limited to indoor, outdoor, handheld devices, vehicle-mounted devices, or even on water, in the air, on airplanes, drones, or on satellites.

[0282] Therefore, although this document describes methods and devices for wireless communication, the inventive concepts and techniques contained herein can be extended to other communication scenarios and are expected to achieve the same technical benefits and effects. It is readily apparent that these inventive concepts have broad applicability and scalability, whether for communication between different types of base stations and user equipment, or for communication in different deployment environments.

[0283] It should be noted that the above steps are merely examples and do not limit the scope of the invention. Various modifications and variations can be made to the steps without departing from the spirit and scope of the invention.

[0284] The order of the described steps (signaling / boxes) is not intended to be construed as a limitation, and any number of the described steps (signaling / boxes) can be skipped or combined in any order to implement the method or an alternative method.

[0285] This disclosure describes examples of communication between terminals and network element components in the network architecture described in the above embodiments, which are primarily for illustrative purposes and not for limitation.

[0286] The order of the described steps (signaling / blocks) is not intended to be construed as limiting, and any number of the described steps (signaling / blocks) can be skipped or combined in any order to implement the method or alternative methods. Generally, any of the components, modules, methods, and operations described herein can be implemented using software, firmware, hardware (e.g., fixed logic circuitry), manual processing, or any combination thereof. Some operations of the example methods can be described in the general context of executable instructions stored on computer-readable storage located locally and / or remotely on a computer processing system, and implementations can include software applications, programs, functions, etc. Alternatively or additionally, any functionality described herein can be performed at least in part by one or more hardware logic components, such as, but not limited to, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), system-on-a-chip (SoCs), complex programmable logic devices (CPLDs), etc.

[0287] Furthermore, the signaling transmission described in the embodiments of this disclosure can be implemented in any manner known in the art. For example, signaling transmission can be explicit and / or implicit. Moreover, the illustrated steps (signaling / blocks) are for illustrative purposes only and are not intended to limit this application.

[0288] Figure 31 is a schematic structural diagram of a wireless communication device 900 provided in this disclosure. The wireless communication device includes a processor and a memory, the memory for storing computer programs, and the processor for calling and running the computer programs stored in the memory, executing instructions for at least one of the operations described above.

[0289] The wireless communication device can be a user equipment, a base station, or a network element. The wireless communication device 900 shown in Figure 31 includes a processor 910, which can call and run computer programs from memory to implement the methods in the embodiments of this application.

[0290] Optionally, as shown in FIG31, the wireless communication device 900 may further include a memory 920. The processor 910 can retrieve and run computer programs from the memory 920 to implement the methods in the embodiments of this application. The memory 920 may be a separate device independent of the processor 910, or it may be integrated into the processor 910.

[0291] Optionally, as shown in Figure 31, the wireless communication device 900 may further include a transceiver 930. The processor 910 can control the transceiver 930 to communicate with other devices. Specifically, it can send information or data to other devices or receive information or data sent by other devices. The transceiver 930 may include a transmitter and a receiver. The transceiver 930 may further include an antenna, and the number of antennas may be one or more.

[0292] Optionally, the wireless communication device 900 may specifically be a base station in the embodiments of this application, and the wireless communication device 900 may implement the corresponding processes implemented by the base station in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0293] Optionally, the wireless communication device 900 may specifically be a mobile user equipment / user equipment in the embodiments of this application, and the wireless communication device 900 may implement the corresponding processes implemented by the mobile user equipment / user equipment in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

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

[0295] According to an example embodiment, a chip is provided, the chip including: a processor for calling and running a computer program from a memory, causing a device on which the chip is installed to perform the method according to any one of the above embodiments, examples, or example embodiments.

[0296] According to an example embodiment, a computer-readable storage medium is provided for storing a computer program that causes a computer to perform a method according to any one of the above embodiments, examples, or example embodiments.

[0297] According to an example embodiment, a computer program product is provided, including a computer program / instructions that, when executed by a processor (e.g., by the processor or an apparatus, device, computer, or machine including the processor), implement the method according to any one of the above embodiments, examples, or example embodiments.

[0298] Embodiments of this disclosure are combinations of technologies / processes that can be employed in 3GPP specifications to create a final product.

[0299] While this disclosure has been described in conjunction with what are considered to be the most practical and preferred embodiments, it should be understood that this disclosure is not limited to the disclosed embodiments, but is intended to cover various arrangements made without departing from the broadest interpretation of the appended claims.

Claims

1. A wireless communication system, the wireless communication system comprising: The data management function is used to uniformly manage data acquisition and transmission tasks.

2. The system according to claim 1, wherein, The wireless communication system further includes at least one of the following: Data processing functions are used to process and / or preprocess data, and send the processed data to the device that actually consumes the data; The data storage function is used for data storage services. Based on the needs of data acquisition tasks, the data is stored for asynchronous reading by devices that consume data. and / or Data openness function.

3. A data processing method, executed in a first device, wherein, The method includes: Receive real-time or variable capability information reported by at least one second device; wherein the capability information includes, but is not limited to, at least one of the following: data type, node type, node identifier, data acquisition spatial range, data acquisition time range, and device conditions for consuming data that are allowed to acquire data.

4. The method according to claim 3, wherein, For one of the at least one second device, a data acquisition task is assigned to the second device; wherein the data acquisition task is matched with the capability information of the second device.

5. The method according to claim 3, wherein, When the at least one second device includes a terminal device, an access network node, or a core network node, and the terminal device, access network node, or core network node is a data providing device, the capability information is forwarded through an intermediate node.

6. The method according to claim 5, wherein, The capability information is carried in the registration information, which includes, but is not limited to, at least one of the following: terminal device identifier, capability information, and / or terminal device location information.

7. The method according to claim 3, wherein, The method further includes sending a first response message.

8. The method according to claim 7, wherein, When a data acquisition task matches a stored data acquisition task, a signaling process is initiated to issue the data acquisition task.

9. The method according to claim 3, wherein, The method further includes sending reference information, which is used to instruct devices that are allowed to provide data to modify specified data acquisition capabilities.

10. The method according to claim 3, wherein, The method also includes receiving updated capability information and / or deregistered capability information through the functional interface of the data management function.

11. The method according to claim 3, wherein, The method further includes: receiving at least one creation information and / or notification information, wherein the creation information indicates the creation of a first data acquisition task, and the creation information includes, but is not limited to, at least one of the following: data type, data source, data frequency, data acquisition task list, data reporting cycle, data storage information, data processing information and / or data transmission target, and the notification information indicates the control plane address of the device consuming the data.

12. The method according to claim 11, wherein, Receive multiple creation information entries, compare and analyze them, and identify several differences.

13. The method according to claim 11, wherein, The method also includes receiving messages for updating and / or canceling the first data acquisition task.

14. The method according to claim 13, wherein, The method also includes matching a data providing device based on an updated first data acquisition task.

15. The method according to claim 3 or 11, wherein, The method further includes matching the first data acquisition task with the data acquisition capability to determine whether the first data acquisition task can be completed.

16. The method according to claim 15, wherein, When it is determined that the first data acquisition task can be completed, the method further includes: sending a second response message corresponding to the creation information, wherein the second response message indicates that the first data acquisition task has been successfully established, and / or assigning an acquisition task identifier ID.

17. The method according to claim 16, wherein, When the first data acquisition task is single, small in quantity, and / or immediate, the data providing device is instructed to complete the data transmission through the control plane.

18. The method according to claim 15, wherein, Based on the matching result between the first data acquisition task and the data acquisition capability, a second data acquisition task is sent. The second data acquisition task includes, but is not limited to, at least one of the following: acquisition task ID, data type, data source, and data frequency.

19. The method according to claim 18, wherein, When it is determined, based on preset rules, that the second data acquisition task is to be completed jointly by multiple data providing devices, multiple second data acquisition tasks are sent in parallel.

20. The method according to claim 18, wherein, The method further includes receiving a third response message, wherein the third response message indicates that a data acquisition task has been created.

21. The method according to claim 3, wherein, The method further includes: receiving a data plane transmission establishment request message.

22. The method according to claim 18, wherein, The method further includes: matching a third device based on the acquisition task ID, and / or sending a data plane transmission establishment request to the third device.

23. The method according to claim 22, wherein, The method further includes: transmitting data to at least one intermediate node for data processing according to the second data acquisition task.

24. The method according to claim 22, wherein, The method further includes: when the second data acquisition task matches multiple devices consuming data, sending a data plane transmission establishment request to the multiple devices consuming data.

25. A data processing method, executed in a first device, wherein, The method includes: Receive a data transmission establishment request message, which includes at least one of the following: device identifier for consuming data, device filtering conditions for consuming data, and / or the association between the created data transmission task and the data acquisition task.

26. The method according to claim 25, wherein, The method further includes: matching the device consuming the data according to the acquisition task ID contained in the data acquisition task, and / or sending a data plane transmission establishment request to the device consuming the data.

27. The method according to claim 26, wherein, The method further includes: transmitting data to at least one intermediate node for data processing according to the second data acquisition task.

28. The method according to claim 26, wherein, The method further includes: when the second data acquisition task matches multiple devices consuming data, sending a data plane transmission establishment request to the multiple devices consuming data.

29. A data processing method, executed in a second device, wherein, The method includes: Send at least one second device to report real-time or variable capability information; wherein the capability information includes, but is not limited to, at least one of the following: data type, node type, node identifier, data acquisition spatial range, data acquisition time range, and device conditions for consuming data that are allowed to acquire data.

30. The method according to claim 29, wherein, The method further includes: receiving first response information.

31. The method according to claim 29, wherein, The method further includes receiving reference information, which is used to instruct a device that is allowed to provide data to modify a specified data acquisition capability.

32. The method according to claim 29, wherein, The method also includes sending updated capability information and / or deregistered capability information through the functional interface of the data management function.

33. The method according to claim 29, wherein, The method also includes receiving indication information from the indication data providing device to complete data transmission through the control plane.

34. The method according to claim 29, wherein, The method further includes receiving a second data acquisition task, which includes, but is not limited to, at least one of the following: acquisition task ID, data type, data source, and data frequency.

35. The method according to claim 29, wherein, The method further includes sending a third response message, wherein the third response message indicates that a data acquisition task has been created.

36. The method according to claim 29, wherein, The method further includes sending a data plane transmission establishment request message.

37. A data processing method, executed on a third device, wherein, The method includes sending creation information and / or notification information, wherein the creation information indicates the creation of a first data acquisition task, and the creation information includes, but is not limited to, at least one of the following: data type, data source, data frequency, data acquisition task list, data reporting cycle, data storage information, data processing information and / or data transmission target, and the notification information indicates the control plane address of the device consuming the data.

38. The method according to claim 37, wherein, The method also includes sending messages to update and / or cancel the first data acquisition task.

39. The method according to claim 37, wherein, The method also includes matching a data providing device based on an updated first data acquisition task.

40. The method of claim 37, wherein, When it is determined that the first data acquisition task can be completed, the method further includes: sending a second response message corresponding to the creation information, wherein the second response message indicates that the first data acquisition task has been successfully established, and / or assigning an acquisition task identifier ID.

41. The method according to claim 37, wherein, The method further includes: receiving a data plane transmission establishment request.

42. A data processing method, executed in a second device, wherein, The method includes: Send a data transmission establishment request message, which includes at least one of the following: device identifier for consuming data, device filtering conditions for consuming data, and / or the association between the created data transmission task and the data acquisition task.

43. A data processing method, executed on a third device, wherein, The method includes: receiving a data plane transmission establishment request.

44. A wireless communication device, wherein, The wireless communication device includes a processor and a memory for storing computer programs, the processor for calling and running the computer programs stored in the memory to perform the method as described in any one of claims 3 to 43.

45. A readable storage medium for storing a computer program that is invoked and executed by a processor to perform the method as described in any one of 3-43.