Data acquisition method and apparatus, and terminal device and network-side device

Abstract

The present application belongs to the technical field of communications. Disclosed are a data acquisition method and apparatus, and a terminal device and a network-side device. The data acquisition method in the embodiments of the present application comprises: a first device receiving a first data acquisition request from a second device, wherein the first data acquisition request is used for requesting the acquisition of data; and the first device sending a first response message to the second device or a fourth device, wherein the first response message carries at least one of the following: first data identification information, which is used for indicating a label corresponding to data requested by the second device or the fourth device, first storage identification information, which is used for indicating a data set corresponding to the data requested by the second device or the fourth device, and device identification information, which is used for indicating a corresponding data storage device that stores the data requested by the second device or the fourth device.

Description

Data acquisition method and device, terminal device and network side device

[0001] Cross-reference to Related Applications

[0002] The present application claims priority to a Chinese patent application No. 202411059111.X, filed on August 2, 2024, entitled "Data acquisition method and device, terminal device and network side device", and a Chinese patent application No. 202411387197.9, filed on September 30, 2024, entitled "Data acquisition method and device, terminal device and network side device", the contents of which are incorporated herein by reference in their entirety. TECHNICAL FIELD

[0003] The present application belongs to the field of communication technology, and particularly relates to a data acquisition method and device, terminal device and network side device. BACKGROUND

[0004] At present, artificial intelligence (AI) technology has been widely applied in various fields and has played a good role. Therefore, it is an important task for future wireless communication networks to integrate AI technology into wireless communication networks to significantly improve technical indicators such as throughput, latency and user capacity.

[0005] Among them, AI technology is a data-driven technology, which can train an artificial intelligence model using labeled training data, and then apply the trained artificial intelligence model to an actual scenario to process corresponding services.

[0006] Model training and use process need to acquire AI model, model training data, to-be-processed data, etc. In related technologies, a data provider can store data into a data storage device, such as an analytics data repository function (ADRF), and the data provider can also acquire the data previously stored by the data provider by interacting with the data storage device. However, after the data is stored into the data storage device, the data provider lacks an updating process and triggering condition, and the stored data cannot be used by other devices. SUMMARY

[0007] Embodiments of the present application provide a data acquisition method and device, terminal device and network side device, which can solve the problem that the existing data acquisition method cannot provide the stored data to other devices for use.

[0008] In a first aspect, a data acquisition method is provided, comprising:

[0009] The first device receives a first data acquisition request from a second device; the first data acquisition request is used to request to acquire data;

[0010] The first device sends a first response message to the second device or a fourth device;

[0011] The first response message carries at least one of the following:

[0012] First data identification information, the first data identification information is used to indicate the label corresponding to the data requested by the second device or the fourth device;

[0013] First storage identification information, the first storage identification information is used to indicate the data set corresponding to the data requested by the second device or the fourth device;

[0014] Device identification information, the device identification information is used to indicate the data storage device storing the data requested by the second device or the fourth device.

[0015] In a second aspect, another data acquisition method is provided, comprising:

[0016] The second device sends a first data acquisition request to the first device; the first data acquisition request is used to request to acquire data.

[0017] Optionally, the method further comprises:

[0018] The second device receives a first response message from the first device;

[0019] The first response message carries at least one of the following:

[0020] First data identification information, the data identification information is used to indicate the topic corresponding to the data requested by the second device;

[0021] First storage identification information, the storage identification is used to indicate the data set corresponding to the data requested by the second device;

[0022] Device identification information, the device identification information is used to indicate the data storage device storing the data requested by the second device.

[0023] In a third aspect, an information transmission method is provided, comprising:

[0024] The third device receives a token acquisition request from a second device, the token acquisition request is used to request to acquire access token information;

[0025] The third device verifies the token acquisition request;

[0026] The third device sends the first access token or the second access token to the second device.

[0027] In a fourth aspect, another information transmission method is provided, comprising:

[0028] The third device receives a search request message from the second device; the search request message is used to request searching for the first device;

[0029] The third device determines at least one first device according to the search request message;

[0030] The third device sends feedback information to the second device; the feedback information comprises information of at least one first device;

[0031] The search request message comprises at least one of the following:

[0032] First indication information, the first indication information is used to indicate searching for a first device with data collection capability;

[0033] Second indication information, the second indication information is used to indicate searching for a first device with passive data collection capability;

[0034] Third indication information, the third indication information is used to indicate searching for a first device with data opening capability;

[0035] Fourth indication information, the fourth indication information is used to indicate searching for a first device supporting data opening service.

[0036] In a fifth aspect, another information transmission method is provided, comprising:

[0037] The first device sends a registration request message to the third device;

[0038] The registration request message comprises at least one of the following:

[0039] Fifth indication information, the fifth indication information is used to indicate that the first device has data collection capability;

[0040] Sixth indication information, the sixth indication information is used to indicate that the first device has passive data collection capability;

[0041] Seventh indication information, the seventh indication information is used to indicate that the first device has data opening capability;

[0042] Eighth indication information, the eighth indication information is used to indicate that the first device supports data opening service.

[0043] In a sixth aspect, another information transmission method is provided, comprising:

[0044] The second device sends a search request message to the third device; the search request message is used to request the search of the first device.

[0045] The second device receives feedback information from the third device; the feedback information includes information from at least one first device.

[0046] The search request message includes at least one of the following:

[0047] First indication information, the first indication information being used to indicate the location of a first device with data collection capabilities;

[0048] The second instruction information is used to instruct the search for a first device with passive data collection capabilities;

[0049] The third instruction information is used to indicate the search for a first device with data openness capabilities;

[0050] The fourth instruction information is used to instruct the search for a first device that supports the data open service.

[0051] In a seventh aspect, a data acquisition device is provided, applied to a first device, comprising:

[0052] The first data acquisition request receiving module is used to receive a first data acquisition request from the second device; the first data acquisition request is used to request data acquisition.

[0053] The first response message sending module is used to send a first response message to the second device or the fourth device;

[0054] The first response message carries at least one of the following:

[0055] First data identification information, which is used to indicate the tag corresponding to the data requested by the second device or the fourth device;

[0056] First storage identification information, which is used to indicate the dataset corresponding to the data requested by the second device or the fourth device;

[0057] Device identification information, which is used to indicate the data storage device corresponding to the data requested by the second device or the fourth device.

[0058] Eighthly, another data acquisition device is provided for use in the second device, including:

[0059] The first data acquisition request sending module is configured to send a first data acquisition request to the first device, wherein the first data acquisition request is configured to request acquisition of data.

[0060] Optionally, the apparatus further comprises:

[0061] The first response message receiving module is configured to receive a first response message from the first device.

[0062] The first response message comprises at least one of the following:

[0063] The first data identification information is configured to indicate a topic corresponding to the data requested by the second device.

[0064] The first storage identification information is configured to indicate a data set corresponding to the data requested by the second device.

[0065] The device identification information is configured to indicate a data storage device storing the data requested by the second device.

[0066] In a ninth aspect, an information transmission apparatus is provided, which is applied to a third device and comprises:

[0067] The token acquisition request receiving module is configured to receive a token acquisition request from a second device, wherein the token acquisition request is configured to request acquisition of access token information.

[0068] The token acquisition request verifying module is configured to verify the token acquisition request.

[0069] The access token sending module is configured to send a first access token or a second access token to the second device.

[0070] In a tenth aspect, an information transmission apparatus is provided, which is applied to a third device and comprises:

[0071] The search request message receiving module is configured to receive a search request message from a second device, wherein the search request message is configured to request search for a first device.

[0072] The determining module is configured to determine at least one first device according to the search request message.

[0073] The feedback information sending module is configured to send feedback information to the second device, wherein the feedback information comprises information of at least one first device.

[0074] The search request message comprises at least one of the following:

[0075] The first indication information is configured to indicate search for a first device having a data collection capability.

[0076] second indication information, used for indicating to find the first device with passive data collection capability;

[0077] third indication information, used for indicating to find the first device with data opening capability;

[0078] fourth indication information, used for indicating to find the first device supporting data opening service.

[0079] In a eleventh aspect, another information transmission apparatus is provided, applied to a first device, comprising:

[0080] a registration request message sending module, configured to send a registration request message to a third device;

[0081] wherein the registration request message comprises at least one of the following:

[0082] fifth indication information, used for indicating that the first device has data collection capability;

[0083] sixth indication information, used for indicating that the first device has passive data collection capability;

[0084] seventh indication information, used for indicating that the first device has data opening capability;

[0085] eighth indication information, used for indicating that the first device supports data opening service.

[0086] In a twelfth aspect, another information transmission apparatus is provided, applied to a second device, comprising:

[0087] a search request message sending module, configured to send a search request message to a third device; the search request message is used for requesting to search for a first device;

[0088] a feedback information receiving module, configured to receive feedback information from the third device; the feedback information comprises information of at least one first device;

[0089] wherein the search request message comprises at least one of the following:

[0090] first indication information, used for indicating to find the first device with data collection capability;

[0091] second indication information, used for indicating to find the first device with passive data collection capability;

[0092] The third indication information is used for indicating to find the first device with the data opening capability.

[0093] The fourth indication information is used for indicating to find the first device supporting the data opening service.

[0094] In a thirteenth aspect, a terminal device is provided, which includes a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions being executed by the processor to implement the steps of the data acquisition method according to any one of the first aspect or the second aspect, or implement the steps of the information transmission method according to any one of the fifth aspect or the sixth aspect.

[0095] In a fourteenth aspect, a network side device is provided, which includes a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions being executed by the processor to implement the steps of the data acquisition method according to any one of the first aspect or the second aspect, or implement the steps of the information transmission method according to any one of the third aspect or the fourth aspect, the fifth aspect or the sixth aspect.

[0096] In a fifteenth aspect, an information transmission system is provided, which includes a network side device and a terminal device, the network side device being configured to implement the steps of the information transmission method according to the third aspect or the fourth aspect, and the terminal device being configured to implement the steps of the data acquisition method according to the fifth aspect or the sixth aspect.

[0097] In a sixteenth aspect, a data acquisition system is provided, which includes a terminal device and a network side device, the terminal device being configured to implement the steps of the data acquisition method according to the first aspect or the second aspect, and the network side device being configured to implement the steps of the data acquisition method according to the second aspect or the first aspect.

[0098] In a seventeenth aspect, a readable storage medium is provided, which stores a program or instructions, the program or instructions being executed by a processor to implement the steps of the data acquisition method or the information transmission method.

[0099] In an eighteenth aspect, a chip is provided, which includes a processor and a communication interface, the communication interface being coupled to the processor, the processor being configured to run a program or instructions to implement the steps of the data acquisition method or the information transmission method.

[0100] In a nineteenth aspect, a computer program / program product is provided, which is stored in a storage medium, and is executed by at least one processor to implement the steps of the foregoing data acquisition method, or to implement the steps of the foregoing information transmission method.

[0101] The embodiment of the present application provides a data acquisition method, a first device as a data provider can receive a first data acquisition request of a second device, and after receiving the first data acquisition request, sends a first response message to the second device or a fourth device, wherein the first response message carries at least one of data identification information, storage identification information and device identification information, and the second device or the fourth device can acquire data from a data storage device according to the first response message. In the embodiment of the present application, after the data provider stores data into the data storage device, the data can be used by other devices, thereby expanding the data usage range and improving the data utilization rate. BRIEF DESCRIPTION OF DRAWINGS

[0102] FIG. 1 is a block diagram of a wireless communication system to which the embodiment of the present application can be applied;

[0103] FIG. 2 is a schematic diagram of a data storage and acquisition process in the embodiment of the present application;

[0104] FIG. 3 is a flowchart of a data acquisition method in the embodiment of the present application;

[0105] FIG. 4 is a flowchart of another data acquisition method in the embodiment of the present application;

[0106] FIG. 5 is a flowchart of an information transmission method in the embodiment of the present application;

[0107] FIG. 6 is a flowchart of another information transmission method in the embodiment of the present application;

[0108] FIG. 7 is a flowchart of another information transmission method in the embodiment of the present application;

[0109] FIG. 8 is a flowchart of another information transmission method in the embodiment of the present application;

[0110] FIG. 9 is a schematic diagram of a device interaction process in the embodiment of the present application;

[0111] FIG. 10 is a schematic diagram of another device interaction process in the embodiment of the present application;

[0112] FIG. 11 is a structural block diagram of a data acquisition apparatus in the embodiment of the present application;

[0113] FIG. 12 is a structural block diagram of another data acquisition apparatus in the embodiment of the present application;

[0114] FIG. 13 is a structural block diagram of an information transmission apparatus according to an embodiment of the present application;

[0115] FIG. 14 is a structural block diagram of an information transmission apparatus according to an embodiment of the present application;

[0116] FIG. 15 is a structural block diagram of an information transmission apparatus according to an embodiment of the present application;

[0117] FIG. 16 is a structural block diagram of another information transmission apparatus according to an embodiment of the present application;

[0118] FIG. 17 is a structural block diagram of a communication device according to an embodiment of the present application;

[0119] FIG. 18 is a structural block diagram of a terminal device according to an embodiment of the present application;

[0120] FIG. 19 is a structural block diagram of a network-side device according to an embodiment of the present application;

[0121] FIG. 20 is a structural block diagram of another network-side device according to an embodiment of the present application. DETAILED DESCRIPTION

[0122] The technical solutions in the embodiments of the present application will be clearly described below with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are only some of the embodiments of the present application, but not all of them. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art belong to the scope of protection of the present application.

[0123] The terms "first", "second", and the like in the present application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the terms used in this way can be interchanged under appropriate circumstances, so that the embodiments of the present application can be implemented in an order other than that illustrated or described herein, and the objects distinguished by "first", "second" are usually a category, and are not limited to the number of objects, for example, the first object can be one or more. In addition, "or" in the present application means at least one of the connected objects. For example, the protection scope of "A or B" at least covers three schemes, namely, scheme one: including A and not including B; scheme two: including B and not including A; scheme three: including A and B. In addition, the terms "A and / or B", "at least one of A and B", "at least one of A or B" also at least cover the above three schemes, respectively. The character " / " generally represents that the objects before and after are in an "or" relationship.

[0124] The term "indication" in this application can be a direct indication (or explicit indication) or an indirect indication (or implicit indication). The direct indication can be understood as the sender explicitly informing the receiver of specific information, operations to be performed or requested results, etc. in the indication sent by the sender. The indirect indication can be understood as the receiver determining the corresponding information according to the indication sent by the sender, or making a judgment and determining the operations to be performed or the requested results according to the judgment result.

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

[0126] ​Figure 1 shows a block diagram of a wireless communication system applicable to an embodiment of this application. The wireless communication system includes a terminal 11 and a network-side device 12. The terminal 11 can also be referred to as User Equipment (UE), and can be a mobile phone, tablet computer, laptop computer, notebook computer, personal digital assistant (PDA), handheld computer, netbook, ultra-mobile personal computer (UMPC), mobile internet device (MID), augmented reality (AR), virtual reality (VR) device, robot, wearable device, flight vehicle, vehicle user equipment (VUE), shipboard equipment, pedestrian user equipment (PUE), smart home (home devices with wireless communication capabilities, such as refrigerators, televisions, washing machines, or furniture), game console, personal computer (PC), ATM, or self-service machine, etc. Wearable devices include: smartwatches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart chains, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, etc. Among these, in-vehicle devices can also be referred to as in-vehicle terminals, in-vehicle controllers, in-vehicle modules, in-vehicle components, in-vehicle chips, or in-vehicle units, etc. It should be noted that the specific type of terminal 11 is not limited in this application embodiment. Network-side equipment 12 may include access network equipment or core network equipment, wherein access network equipment may also be referred to as Radio Access Network (RAN) equipment, radio access network function, or radio access network unit. Access network equipment may include base stations, Wireless Local Area Network (WLAN) access points (APs), or Wireless Fidelity (WiFi) nodes, etc.Among them, base stations can be referred to as Node B (NB), Evolved Node B (eNB), Next Generation Node B (gNB), New Radio Node B (NR Node B), Access Point, Relay Base Station (RBS), Serving Base Station (SBS), Base Transceiver Station (BTS), Radio Base Station, Radio Transceiver, Basic Service Set (BSS), Extended Service Set (ESS), Home Node B (HNB), Home Evolved Node B, Transmit / Receive Point (TRP), Non-Terrestrial Network (NTN) equipment (such as satellite or high altitude platform stations). The term "base station" can be any suitable term in the field, such as "station" or any other appropriate term in the relevant field, as long as the same technical effect is achieved. The term "base station" is not limited to specific technical terms. It should be noted that the embodiments of this application only use the base station in the NR system as an example for introduction, and do not limit the specific type of base station.

[0127] Core network equipment, also known as core network nodes, core network functions, or core network elements, includes, but is not limited to, at least one of the following: Mobility Management Entity (MME), Access and Mobility Management Function (AMF), Session Management Function (SMF), User Plane Function (UPF), Policy Control Function (PCF), Policy and Charging Rules Function (PCRF), Edge Application Server Discovery Function (EASDF), Unified Data Management (UDM), Unified Data Repository (UDR), Home Subscriber Server (HSS), Centralized network configuration (CNC), Network Repository Function (NRF), Network Exposure Function (NEF), Local NEF (L-NEF), and Binding Support. Functions include BSF, Application Function (AF), Location Management Function (LMF), Gateway Mobile Location Centre (GMLC), Network Data Analytics Function (NWDAF), and Non-Terrestrial Network (NTN) equipment (such as satellite or high altitude platform station).It should be noted that the embodiments of this application only use the core network equipment in the NR system as an example for introduction, and do not limit the specific type of core network equipment. If the name of the core network equipment mentioned in the embodiments of this application changes in subsequent protocol versions (e.g., 6G), it is also within the scope of protection of this application.

[0128] Optionally, the core network equipment can be implemented by one or more functional modules in a single device, or by multiple devices working together; this application does not specifically limit this. It is understood that the aforementioned functional modules can be network elements in hardware devices, software functional modules running on dedicated hardware, or virtualized functional modules instantiated on a platform (e.g., a cloud platform).

[0129] Currently, artificial intelligence (AI) technology has been widely applied in various fields and has played a positive role. Therefore, integrating AI technology into wireless communication networks to significantly improve technical indicators such as throughput, latency, and user capacity is an important task for future wireless communication networks.

[0130] AI technology is a data-driven technology that can use labeled training data to train artificial intelligence models, and then apply the trained artificial intelligence models to real-world scenarios to process corresponding business operations.

[0131] Model training and usage require acquiring AI models, model training data, and data to be processed. In related technologies, data providers can store data in data storage devices, such as analytics data repository functions (ADRF). Data providers can also interact with these data storage devices to retrieve previously stored data.

[0132] It should be noted that the Network Data Analytics Function (NWDAF), as a big data analytics network element introduced in 5G networks, can provide data analytics services to the network.

[0133] 3GPP has introduced the 5G Core Network AI Unit (NWDAF) to form a closed-loop control system for data collection, training, and inference, as well as a network big data analysis architecture that supports diverse solutions. As the AI ​​and big data engine of the 5G network, NWDAF is responsible for collecting data from network management, services, network, and terminals, performing data model training, and outputting prediction, inference, and decision-making results to assist network operation and maintenance and promote the rational allocation of 5G network resources.

[0134] Different types of NWDAFs have different logical functions: NWDAFs with an Analysis Logical Function (AnLF) are logical analysis function units, responsible for using the model trained by the Model Training Logical Function (MTLF) to perform analysis and output analysis results; NWDAFs with MTLF functions are model training function units, responsible for training and producing the model used by the AnLF, and multiple MTLFs can be used to jointly train the model in a federated learning manner.

[0135] Referring to Figure 2, a schematic diagram of a data storage and retrieval process is shown. As shown in Figure 2, the NWDAF can act as a data provider to request data storage from the ADRF, such as by requesting data storage from the ADRF through service-oriented signaling such as Nadrf_DataManagement_StorageRequest.

[0136] ADRF stores the received data, and the stored data may carry a storage transaction ID to identify the data.

[0137] ADRF feedback provides the corresponding Response information.

[0138] NWDAF can retrieve its previously stored data, such as by interacting with ADRF through service-oriented signaling such as Nadrf_DataManagement_RetrievalRequest. Service-oriented signaling such as Nadrf_DataManagement_RetrievalRequest can carry identification information such as Storage Transaction ID.

[0139] ADRF feedback stores the data.

[0140] In addition, data providers can include the DataSetTag attribute in their storage requests. When ADRF stores the data, the data record will be associated with this attribute. The DataSetTag attribute is defined in Table 1 below. A data record can be associated with multiple DataSetTag attributes.

[0141] Table 1

[0142] As shown in Table 1, the DataSetTag attribute can include: DataSetTag, which identifies the dataset; and DataSetDescription, which provides human-readable information about the characteristics of the dataset.

[0143] The data acquisition method provided in this application will be described in detail below with reference to the accompanying drawings, through some embodiments and application scenarios.

[0144] Referring to Figure 3, a flowchart of a data acquisition method provided in an embodiment of this application is shown. The method is applied to a first device. As shown in Figure 3, the method may specifically include:

[0145] Step 201: The first device receives a first data acquisition request from the second device; the first data acquisition request is used to request data acquisition.

[0146] Step 202: The first device sends a first response message to the second or fourth device.

[0147] The first response message carries at least one of the following:

[0148] First data identification information, which is used to indicate the tag corresponding to the data requested by the second device or the fourth device;

[0149] First storage identification information, which is used to indicate the dataset corresponding to the data requested by the second device or the fourth device;

[0150] Device identification information, which is used to indicate the data storage device corresponding to the data requested by the second device or the fourth device.

[0151] It should be noted that the first device in this application embodiment can be a data provider. The first device can collect and provide data. For example, in a model training scenario, the first device can provide training data, a trained AI / ML model, data to be analyzed, and analysis results output after analysis using the AI / ML model, etc. Alternatively, in a location analysis scenario, the first device can be a device assisting in location management, which can collect location information and positioning measurement information of the terminal device. Alternatively, the first device can also be a data storage network element, such as ADRF. In this scenario, ADRF, as the first device, can receive data acquisition requests from a second device, such as an LMF, and send a response message to a fourth device, such as an NWDAF or MTLF. It should be noted that the above response message may also include the data corresponding to the data acquisition request.

[0152] For example, the first device can be a network-side device or a terminal device. The terminal device includes a conventional terminal device and / or a positioning reference unit (PRU). The conventional terminal device can be terminal device 11 in Figure 1. The positioning reference unit (PRU) can perform positioning measurements, such as RSTD, RSRP, UE Rx-Tx time difference measurement, etc., and store these measurement results in a data storage device, such as ADRF. Furthermore, the PRU can send a positioning reference signal (PRS) to the TRP, enabling the TRP to measure and report UL positioning measurements from the PRU at a known location, such as RTOA, UL-AoA, gNB Rx-Tx time difference, etc.

[0153] The network-side device can be the access network device shown in Figure 1, such as a base station or a newly defined artificial intelligence processing node on the access network side, or the core network device shown in Figure 1, such as a Network Data Analytics Function (NWDAF), a Location Management Function (LMF), or a newly defined processing node on the core network side, or a combination of the above-mentioned nodes. In this embodiment, the first device can collect various data generated in the network, such as network management, service, network, and terminal data.

[0154] In this application, the second or fourth device refers to a data acquirer. The second or fourth device can be a device with model training capabilities, a device with specific data analysis capabilities, or other devices that need to acquire data. The second or fourth device can perform intelligent data analysis on the acquired data, ultimately generating corresponding data analysis results to detect or predict various events occurring in the network. For example, in the embodiments of this application, the second or fourth device can be an NWDAF (MTLF), responsible for training an AI / ML model using the acquired training data, performing data analysis using the trained model, and outputting the analysis results. Of course, the second or fourth device can also be other devices or network elements capable of collecting and analyzing data, such as OAM, or external security functions (e.g., firewalls, intrusion detection systems, intrusion prevention systems, etc.), and this application does not impose any limitations on this. For example, the second device in this application can be a communication device configured with an AI model, which is trained to implement network data analysis functions. The fourth device can be the same as or different from the second device.

[0155] Alternatively, the second device in this application can also refer to a communication device that acquires data on behalf of the data acquirer, such as a GMLC, AMF, LMF, etc. It should be noted that when the second device is a communication device that acquires data on behalf of the data acquirer, before sending a data acquisition request to the first device, the second device will receive a data acquisition request from a fourth device (which can be a third data acquisition request). The third data acquisition request may carry at least one of the following:

[0156] Instructions for requesting data;

[0157] Instructions requesting data for model training;

[0158] Requesting instructions to obtain location-related data;

[0159] Data type information, which indicates the type of data requested;

[0160] Time information, which is used to indicate the time range corresponding to the requested data;

[0161] Regional information, which is used to indicate the regional range corresponding to the requested data;

[0162] Data granularity information, which is used to indicate the granularity of the requested data;

[0163] The equipment information of the fourth device, such as the device identification information and address information of the fourth device;

[0164] The fourth item includes the device's certification information, etc.

[0165] The device information of the fourth device can be represented through the notification address / endpoint. Authentication information refers to the token information signed by the fourth device, which allows other devices to send messages to the fourth device. For example, this authentication information could be a CCA (Client Credentials Assertion). This authentication information can be generated by the data acquirer and carries the data acquirer's identification information, validity period, and / or the data they require. The required data can refer to a description of the data, such as its type, time, region, and granularity.

[0166] In this embodiment of the application, the second device or the fourth device sends a first data acquisition request to the first device, the first data acquisition request being used to request data acquisition.

[0167] After receiving a first data acquisition request from a second or fourth device, the first device sends a first response message to the second or fourth device to provide feedback on the result of the data acquisition request. The second or fourth device can acquire data from the data storage device based on at least one of the first data identification information, first storage identification information, and device identification information carried in the first response message.

[0168] The first data identification information is used to indicate the tag corresponding to the data requested by the second or fourth device. For example, the first data identification information may be a DataSetTag or a dataset tag. In one embodiment, the first data identification information is used to indicate a type of data, such as indicating that the data is location service related data.

[0169] The first storage identification information is used to indicate the dataset corresponding to the data requested by the second or fourth device. For example, the first storage identification information may be a Storage Transaction ID. The device identification information is used to indicate the data storage device storing the data requested by the second or fourth device. The device identification information may be the identity identifier of the data storage device, such as ADRFID.

[0170] For example, each of the first devices stores data in the same data storage device. When the first response message carries first data identification information, the second or fourth device can request the target data corresponding to the tag indicated by the first data identification information from the data storage device (e.g., a pre-configured data storage device, or the data storage device carried in the first response message). For example, if the first data identification information indicates a location service, then the second or fourth device can obtain data related to the location service from the data storage device based on the first data identification information. When the first response message carries first storage identification information, the second or fourth device can request the target data contained in the dataset indicated by the first storage identification information from the data storage device.

[0171] It should be noted that the first data identification information can also indicate one or more topics, subjects, data types, etc.; that is, it represents a type of data by describing the topic.

[0172] Alternatively, different first devices can store data in different data storage devices, each managed by a unified management device. When the first response message carries first data identification information, the second or fourth device can request target data under the tag or topic indicated by the first data identification information from the management device. For example, if the first data identification information indicates the topic as location service, then the second or fourth device can send a location service data acquisition request to the management device based on the first data identification information. After receiving the location service data acquisition request, the management device forwards the request to each managed data storage device, and the data storage device containing location service-related data feeds back the target data related to the location service to the second or fourth device. When the first response message carries first storage identification information, the second or fourth device can send a dataset acquisition request to the management device, requesting target data contained in the dataset indicated by the first storage identification information. After receiving the dataset acquisition request, the management device forwards the request to each managed data storage device, and the data storage device of the dataset indicated by the first storage identification information feeds back the target data to the second or fourth device. If the first response message contains device identification information, the second or fourth device sends a data acquisition request to the management device, and includes the device identification information in the data acquisition request. The management device then directly notifies the data storage device corresponding to the device identification information to send the target data back to the second or fourth device.

[0173] Alternatively, different first devices can store data in different data storage devices. When the first response message carries first data identification information and / or first storage identification information, the second or fourth device sends a data retrieval request to each of the other second or fourth devices via broadcast. The data storage device storing the target data indicated by the first data identification information and / or the target data indicated by the first storage identification information then feeds back the target data to the second or fourth device. If the first response message carries device identification information, the second or fourth device can directly send a data retrieval request to the data storage device indicated by the device identification information to request data retrieval.

[0174] It should be noted that the target data can be data requested by a second or fourth device, or data stored by the first device. Specifically, the target data can be data used for model training, or positioning-related data, such as measurement data, positioning result numbers, or auxiliary data. In addition to positioning-related data, the target data can also include corresponding terminal identifiers, RAN device identifiers, or positioning reference unit (PRU) identifiers.

[0175] In one possible application scenario of this application, the first device can be a terminal device with positioning capabilities. During movement, the terminal device continuously acquires location data and, upon receiving first information from a network-side device, labels the location data according to the instructions in the first information to obtain data tags, which are then stored in a data storage device, such as an ADRF (Advanced Data Retrieval System). The second or fourth device can be a network-side device that requests model training data via a first data acquisition request. The terminal device sends a first response message to the network-side device, enabling the network-side device to retrieve data tags from the data storage device based on the first response message, iteratively train the machine learning model, and then use the trained machine learning model to execute target services, such as location services, information push services, etc.

[0176] Furthermore, after the network-side device completes the training of the machine learning model, it can act as a data provider (the first device in this application) to store the trained machine learning model in a data storage device so that the terminal device or other network-side device can use the trained machine learning model to perform target services.

[0177] In another possible application scenario of this application, the first device can be a terminal device with model training capabilities. After the terminal device labels the collected location data to obtain data tags, it uses the data tags to iteratively train a machine learning model locally, and then uses the trained machine learning model to execute the target service. In this embodiment of the application, the target data is the execution result corresponding to the target service. After receiving a first data acquisition request sent by a second device or a fourth device (e.g., a network-side device or other terminal device), the terminal device sends a first response message to the second device or the fourth device. The second device or the fourth device obtains the execution result of the target service based on at least one of the first data identification information, first storage identification information, and device identification information carried in the first response message.

[0178] Alternatively, in this embodiment, the target data can be a trained machine learning model. Upon receiving a first data acquisition request, the terminal device sends a first response message to a second or fourth device (e.g., a network-side device or other terminal device). The second or fourth device acquires the trained machine learning model based on the first response message, and then uses the trained machine learning model to execute the target service.

[0179] It should be noted that the first data acquisition request in this application embodiment may be a service-oriented signaling related to event exposure, data management, location measurement, or a dedicated data acquisition service.

[0180] Optionally, the first data acquisition request carries at least one of the following:

[0181] The first access token of the second device;

[0182] A first instruction, the first instruction being used to indicate a request to obtain data;

[0183] Data type information, which indicates the type of data requested;

[0184] Time information, which is used to indicate the time range corresponding to the requested data;

[0185] Regional information, which is used to indicate the regional range corresponding to the requested data;

[0186] Data granularity information, which is used to indicate the granularity of the requested data;

[0187] The fourth device's certification information;

[0188] The device information of the fourth device, such as the device identification information and address information of the fourth device.

[0189] The first access token refers to the token information used by the second device when it initiates a first data acquisition request to the first device. This first access token can be an access token obtained by the second device through interaction with a third device. The first device can use the first access token in the first data acquisition request to verify the identity and authorization of the second and / or fourth devices. If the second and / or fourth devices do not have the permission to acquire the requested data, the first device may choose not to send a first response message to the second and / or fourth devices, or the first device may send a response message indicating that the request has been rejected, thereby protecting the data from being acquired by unauthorized devices.

[0190] Specifically, the first access token may carry device information of the second device and / or the fourth device, and the first device may determine whether it can send a first response message to the fourth device based on the device information of the second device and / or the fourth device in the first access token.

[0191] For example, the second device sends a token acquisition request to the third device. This request may include the second device's desired service information, its own device information, the target device information, and the desired data type information. The target device information refers to the device information corresponding to the data provider, such as device type information and device identification information. The second device's own device information may include its identification information and manufacturer information. After receiving the token acquisition request from the second device, the third device can determine whether the second device has permission to acquire the target data based on at least one of the following: the second device's own device information, desired service information, target device information, and desired data type information in the token acquisition request. If the second device has permission to acquire the target data, the third device sends a first access token to the second device. The second device then initiates a first data acquisition request to the first device based on the acquired first access token.

[0192] It should be noted that the first access token can be based on data type granularity. That is, the first access token can be used to instruct the second device to obtain the target data corresponding to the data type from the first device, but not to obtain data corresponding to other data types.

[0193] It should be noted that, in this application embodiment, the third device refers to a device used for managing and storing NF registration information, or a device with authorization functions, or a device with token issuance functions, etc. For example, the third device can be a Network Storage Function (NRF). The NRF is used for NF registration, management, and status detection to achieve automated management of all NFs. Each NF must register with the NRF before it can provide services. Registration information includes NF type, address, service list, etc. Of course, the third device in this application embodiment can also be other network elements or devices with storage functions.

[0194] The first instruction is used to indicate a request to obtain data. For example, the first instruction could be an instruction to request location-related data. The first instruction can also indicate the purpose of the first data acquisition request sent by the second device, clarifying the second device's needs for the first device. Alternatively, the first instruction could be an instruction to request data for model training.

[0195] Data type information indicates the type of data requested. This data type can be a specific data type, such as measurement data, auxiliary data, or positioning data; it can also be UE measurement data, Reference Signal Received Power (RSRP), Reference Signal Time Difference (RSTD), or Channel Impulse Response (CIR). Alternatively, this data type information can be represented by event ID, data ID, or analytics ID. It can also be indicated by other information, such as instructions requesting positioning data, positioning-related instructions, AI positioning-related instructions, data used for model training, or data used for AI positioning-related model training. It should be noted that data type information can also indicate the type of device generating the target data. For example, in UE measurement data, the data generator is the UE, but it could also be a PRU, RAN, etc. It can also be the device identification information of the data generating device, such as UEID or PRUID.

[0196] Time information is used to indicate the time range corresponding to the requested data. For example, it indicates the data collected by the first device within a certain time range, or it indicates the data generated by the first device within a certain time period.

[0197] Regional information is used to indicate the regional range corresponding to the requested data. For example, it may indicate data collected by a first device within a certain regional range, or data generated by a device that generates data within a certain regional range (or indicate the regional range corresponding to the generated data). The regional information may be a cell ID, tracking area ID (TPR), latitude and longitude information, etc.

[0198] Data granularity information is used to indicate the granularity of the requested data, such as: high, medium, low; large, medium, small; coarse, medium, fine; all, general (medium), part, etc. The specific terminology used to represent granularity may vary, but the meaning is similar: indicating data of different granularities or different types of data. Another method of representation may be through different data type information, for example, in location-related data acquisition, it might be: location-related data (coarser granularity), UE measurement data (medium granularity), UE location data (fineer granularity).

[0199] The authentication information can refer to the authentication information of a fourth device, which can be used to instruct the fourth device to sign a token. The second device may receive this authentication information when it receives a data acquisition request from the fourth device. This authentication information is used to indicate whether other devices are allowed to send messages to the fourth device, such as the fourth device allowing the first device to send a first response message. It should be noted that before sending the first response message to the fourth device, the first device can also verify this authentication information to determine whether it can send a response message to the fourth device. It should also be noted that the authentication information may carry timeliness information (valid time), identification information (device identification information, etc.), and required data information. The required data can be data constraint information, such as data type, time, region, granularity, etc. Specifically, the first device can verify the valid time (whether it is within the valid time), device information (whether it is authentication information sent by the fourth device), and required data (whether it is the requested data) in the authentication information.

[0200] Understandably, the data type, time, region, and data granularity information in the first data acquisition request can define the specific characteristics of the data requested by the second or fourth device, facilitating the first device to quickly determine the data requested by the second or fourth device and improving the processing efficiency of the first device in handling the first data acquisition request. Furthermore, when the first data acquisition request carries at least one of the data type, time, region, and data granularity information, the first device can only return at least one of the first data identifier, first storage identifier, and device identifier information corresponding to the target data that meets the corresponding characteristics in the first response message. That is, it only returns information corresponding to the data requested by the second or fourth device, and the second or fourth device can only obtain the requested data based on the first response message, unable to obtain other data, thus effectively ensuring data privacy.

[0201] The data acquisition method provided in this application embodiment allows a first device, acting as a data provider, to receive a first data acquisition request from a second device. Upon receiving the first data acquisition request, the first device sends a first response message to either the second or fourth device. The first response message carries at least one of first data identification information, first storage identification information, and device identification information. Based on the first response message, the second or fourth device can then acquire data from the data storage device. In this application embodiment, after the data provider stores the data in the data storage device, it can be used by other devices, expanding the scope of data use and improving data utilization.

[0202] Optionally, step 202, in which the first device sends a first response message to the second or fourth device, includes:

[0203] Step S11: The first device verifies at least one of the second device and the fourth device;

[0204] Step S12: If the verification is successful, the first device sends a first response message to the second device or the fourth device.

[0205] In this embodiment, after receiving a first data acquisition request from a second or fourth device, the first device can verify the second and / or fourth device to determine whether the second or fourth device has permission to acquire the target data. If the verification is successful, the device is considered to have permission to acquire the target data, and the first device sends a first response message to the second or fourth device, providing feedback on the data acquisition request result.

[0206] It should be noted that the target data mentioned above is data that satisfies the first data acquisition request, such as data type information that satisfies the first data acquisition request, and / or data granularity information that satisfies the first data acquisition request, etc.

[0207] It should be noted that the above-mentioned "satisfaction" refers to matching, being the same, etc. For example, the data type of the target data must match or be the same as the data type information in the first data retrieval request.

[0208] For example, the first device can authenticate the second device. When the second device is among the devices allowed to access the target data, the authentication is considered successful, and the second device is authorized to access the target data.

[0209] For example, the first device verifies the second device by using token information from a first data acquisition request from the second device. That is, the first device sends the second device's token, the requested service, message, data type, data granularity, etc., to the third device, requesting the third device to verify whether the token is complete and whether the second device is authorized.

[0210] In one possible application scenario of this application, the first device can be a terminal device with positioning capabilities. During movement, the terminal device continuously acquires location data and, upon receiving first information from a network-side device, labels the location data according to the instructions in the first information to obtain data tags, which are then stored in a data storage device, such as an ADRF (Advanced Data Retrieval System). The second or fourth device can be a network-side device. The network-side device requests model training data via a first data acquisition request, which may include the data type of the model training data required by the network-side device. The terminal device can match the data type requested by the network-side device with the data type of the data tags it has collected. If a match is found, the verification is considered successful, and the terminal device sends a first response message to the network-side device. The network-side device then retrieves the data tags from the data storage device based on the first response message, iteratively trains the machine learning model, and uses the trained machine learning model to execute target services, such as location services or information push services.

[0211] In another possible application scenario of this application, the first device can be a terminal device with model training capabilities. After the terminal device labels the collected location data to obtain data tags, it uses the data tags to iteratively train a machine learning model locally, and then uses the trained machine learning model to execute the target service. In this embodiment of the application, the target data is the execution result corresponding to the target service. After receiving a first data acquisition request sent by a second device or a fourth device (e.g., a network-side device or other terminal device), the terminal device verifies the second device and / or the fourth device. For example, the first data acquisition request may carry the requested service type. The terminal device matches the service type requested by the second device or the fourth device with the service type of the target service to be executed. If the match is successful, the verification is considered successful, and a first response message is sent to the second device or the fourth device. The second device or the fourth device obtains the execution result of the target service based on at least one of the first data identification information, first storage identification information, and device identification information carried in the first response message.

[0212] Alternatively, in this embodiment, the target data can be a trained machine learning model. Upon receiving and successfully verifying a first data acquisition request, the terminal device sends a first response message to a second or fourth device (e.g., a network-side device or other terminal device). The second or fourth device then acquires the trained machine learning model based on the first response message, and uses the trained machine learning model to execute the target service.

[0213] Optionally, the first device verifies at least one of the second device and the fourth device, including at least one of the following:

[0214] The first device authenticates the second device based on the first access token of the second device;

[0215] The first device verifies the fourth device based on the authentication information of the fourth device;

[0216] The first device verifies at least one of the second device and the fourth device based on the second network function instance list.

[0217] In this embodiment, the first device can verify the second device based on the first access token of the second device. The first access token refers to the token information used by the second device when initiating a first data acquisition request to the first device. This first access token can be an access token obtained by the second device through interaction with a third device.

[0218] The first device verifies the first access token of the second device, which can be done by interacting with a third device to determine the integrity of the first access token. If the verification is successful, the first device can send a first response message to the second device.

[0219] Furthermore, the first access token fed back by the third device to the second device may contain token information, as well as corresponding data granularity, data type, time information, and region information. When verifying the first access token, the first device can further verify whether the first access token contains the corresponding data granularity, data type, time information, and region information.

[0220] Optionally, the first data acquisition request carries the first access token and the data type information; the first device verifies the second device based on the first access token of the second device, including:

[0221] The first device verifies whether the first access token contains the data type information.

[0222] If the first device determines that the second device has passed verification if the first access token contains the data type information.

[0223] Optionally, the first data acquisition request carries the first access token and the data granularity information; the first device verifies the second device based on the first access token of the second device, including:

[0224] The first device verifies whether the first access token contains the data granularity information.

[0225] If the first device determines that the second device has passed verification when the first access token contains the data granularity information.

[0226] Optionally, the first data acquisition request carries the authentication information of the fourth device; the first device verifies the fourth device based on the authentication information of the fourth device, including:

[0227] The first device verifies the fourth device based on at least one of the fourth device's identification information, validity period, and required data in the fourth device's authentication information.

[0228] For example, the first device can verify the validity period (whether it is within the validity period), device information (whether it is the authentication information sent by the fourth device), and requested data (whether it is the requested data) in the authentication information. If the current time is within the validity period in the authentication information, it can be determined that the fourth device has passed the verification. Alternatively, if the authentication information carried in the first data acquisition request is the authentication information sent by the fourth device, it can be determined that the fourth device has passed the verification. Alternatively, if the requested data indicated in the authentication information is the data required by the fourth device, it can be determined that the fourth device has passed the verification.

[0229] Optionally, the first data acquisition request carries device information of the fourth device; the first device verifies at least one of the second device and the fourth device based on the second network function instance list, including:

[0230] The first device verifies whether the second network function instance list contains the device information of the fourth device.

[0231] If the first device contains the device information of the fourth device in the second network function instance list, the fourth device is determined to have passed the verification.

[0232] Optionally, the method further includes:

[0233] The first device updates the target data corresponding to the target network function instance list, and the target network function instance list includes the instance identifiers of the second device and / or the fourth device.

[0234] Before sending the first response message to the second device, the first device may reuse the data storage service to update the target network function instance list corresponding to the target data. The target network function instance list is used to indicate which devices the first device authorizes or agrees to access the target data. It is understood that the updated target network function instance list includes instance identifiers of the second device and / or the fourth device. The second network function instance list in this application can be the updated target network function instance list. The second network function instance list in this application may be the same as or different from the first function instance list.

[0235] For example, the first device can determine the target data based on the first indication data type information, time information, region information, data granularity information, etc., carried in the first data acquisition request. For instance, if the data type information indicates UE measurement data, the first device can determine the UE measurement data as the target data. Or, if the data type information is an event identifier, then data related to the event indicated by the event identifier can be determined as the target data. Or, if the first data acquisition request carries time information, the first device can determine the data collected within the time range indicated by the time information as the target data. Or, if the first data acquisition request carries region information, the first device can determine the data collected within the region indicated by the region information as the target data, and so on.

[0236] It is understandable that there is a mapping relationship between the target data and the network function instance list. The first device determines the target network function instance list corresponding to the target data based on the correspondence between the target data and the network function instance list, and then adds the instance identifiers of the second device and / or the fourth device to the target network function instance list to obtain the updated target function instance list.

[0237] It should be noted that the first device can also send a data storage request to the data storage device before sending the first response message to the second or fourth device, requesting the storage of the target data. That is, the first storage request can also be used in non-updating situations. Specifically, the first storage request can also be triggered and used when the first device decides to perform data storage based on its own logic or other reasons.

[0238] Optionally, the method further includes:

[0239] The first device sends a first storage request to the data storage device.

[0240] The first storage request carries at least one of the following:

[0241] The data that needs to be stored;

[0242] The device identifier of the first device;

[0243] Second data identification information;

[0244] Second storage identification information;

[0245] Data description information;

[0246] First list of network function examples.

[0247] In this embodiment, the first device stores the data in a data storage device. The data storage device refers to a device or network element with data storage functionality; for example, the data storage device may be an ADRF (Advanced Data Retrieval System) or other devices or network elements with data storage functionality.

[0248] For example, the first device can send a first storage request to the data storage device through services such as Nadrf_DataManagement_Storage Request. The first device can store data according to its own operational logic; for example, it can send a first storage request to the data storage device after collecting or generating data to store the collected or generated data in real time; or it can periodically send a first storage request to the data storage device according to a preset cycle; or the first device can be triggered by other devices to send a first storage request to the data storage device.

[0249] The first storage request may carry at least one of the following: the data to be stored, the device identifier of the first device, the second data identifier information, the second storage identifier information, the data description information, and the first network function instance list.

[0250] The second data identification information is used to indicate the tag corresponding to the data that needs to be stored. For example, the second data identification information may be a DataSetTag.

[0251] The second storage identifier is used to indicate the dataset corresponding to the data that needs to be stored. For example, the second storage identifier may be a Storage Transaction ID.

[0252] The data to be stored carried in the first storage request may include the target data or other data besides the target data. In other words, the second data identification information in the first storage request may be the same as or different from the first data identification information in the first data acquisition request received by the first device; the second storage identification information may be the same as or different from the first storage identification information. Specifically, before sending the first response message to the second device, the first device may send a first storage request to the data storage device to specifically store the target data in the data storage device. In this case, the first data identification information and the second data identification information are the same, and the first storage identification information and the second storage identification information are the same. In another possible scenario, the first device may also use the first storage request to store the target data together with other data in the data storage device. In this case, the first data identification information and the second data identification information are different, and the first storage identification information and the second storage identification information are different.

[0253] Optionally, the first network function instance list includes the updated target network function instance list.

[0254] In one possible application scenario of this application, after sending a first response message to the second device, the first device updates the first network function instance list corresponding to the target data and adds the instance identifier of the second device to the first network function instance list. Then, the first device sends a first storage request to the data storage device, the first storage request carrying storage identifier information.

[0255] It should be noted that the aforementioned list of first network function instances and target function instances can also refer to device lists, such as NFinstancelist, UEIDlist, RANIDlist, etc.

[0256] Optionally, the first network function instance list includes a list of devices that the first device has authorized or agreed to access data.

[0257] It should be noted that the aforementioned list of devices authorized or uniformly acquiring data by the first device indicates that the list of network function instances can be in the form of a device list, not limited to network function instances, but can also be other devices, such as UE, RAN, etc.; it also indicates that the data in the device list can acquire the relevant data.

[0258] It is understood that, in the embodiments of this application, if the first network function instance list is the updated target network function instance list, then the first network function instance list and the second network function instance list are the same list. If the first network function instance list is not the updated target network function instance list, for example, it is the network function instance list sent by the first device to the data storage device when initially storing the target data, then the first network function instance list and the second network function instance list may not be the same list.

[0259] Optionally, the device list includes at least one of device identification information and manufacturer information.

[0260] It should be noted that manufacturer information can refer to manufacturer identification information, etc.

[0261] Optionally, the method further includes:

[0262] The first device receives data storage results from the data storage device.

[0263] After the first device sends a storage request to the data storage device, the data storage device will return the data storage result to the first device based on the data storage situation.

[0264] Optionally, the data storage result includes at least one of the following:

[0265] At least one third-party data identifier;

[0266] Third, store identification information.

[0267] The third data identification information is used to indicate the tag corresponding to the stored data, and the third storage identification information is used to indicate the dataset corresponding to the stored data.

[0268] It should be noted that the third data identifier information in the data storage result received by the first device may be the same as or different from the second data identifier information in the first storage request sent by the first device. Similarly, the third storage identifier information may be the same as or different from the second storage identifier. Likewise, the data identifier information may be the same as or different from the first data identifier information. Likewise, the third storage identifier information may be the same as or different from the first storage identifier.

[0269] For example, the third data identification information may be a DataSetTag, and the third storage identification information may be a Storage Transaction ID. When the storage request from the first device does not carry a DataSetTag, the data storage device may return a Storage Transaction ID to identify the data; when the storage request from the first device carries a DataSetTag, the data storage device may use and return the DataSetTag as the data identifier. In this case, the third data identification information is the same as the second data identification information, that is, the same DataSetTag.

[0270] It should be noted that when the data storage request from the first device carries a DataSetTag, the data storage device may further split the data within a single DataSetTag based on the different data types and assign new DataSetTags. That is, it may receive one DataSetTag but return one or more DataSetTags in return. In this case, the third data identifier information differs from the second data identifier information. The third data identifier information (the new DataSetTag) received by the first device is the data identifier information that the data storage device has reassigned after splitting the data corresponding to the second data identifier information sent by the first device.

[0271] Optionally, the method further includes:

[0272] The first device generates the second data identification information based on the data to be stored.

[0273] When the first device needs to store data, it can generate second data identification information based on the data to be stored, so as to describe and identify the data when storing data in the future.

[0274] The data acquisition method provided in this application embodiment allows a first device, acting as a data provider, to receive a first data acquisition request from a second device. Upon receiving the first data acquisition request, the first device sends a first response message to either the second or fourth device. The first response message carries at least one of first data identification information, first storage identification information, and device identification information. Based on the first response message, the second or fourth device can then acquire data from the data storage device. In this application embodiment, after the data provider stores the data in the data storage device, it can be used by other devices, expanding the scope of data use and improving data utilization.

[0275] Referring to Figure 4, a flowchart of a data acquisition method provided in an embodiment of this application is shown. This method is applied to a second device. As shown in Figure 4, the method may specifically include:

[0276] Step 301: The second device sends a first data acquisition request to the first device; the first data acquisition request is used to request data acquisition.

[0277] It should be noted that, in this application embodiment, the first device refers to a data provider. The first device can collect and provide data. For example, in a model training scenario, the first device can provide training data, a trained AI / ML model, data to be analyzed, and analysis results output after analysis using the AI / ML model, etc. Alternatively, in a location analysis scenario, the first device can be a device assisting in location management, which can collect location information and positioning measurement information of terminal devices. Alternatively, the first device can also be a data storage network element, such as an ADRF. In this scenario, the ADRF, as the first device, can receive data acquisition requests from a second device (e.g., an LMF) and send a response message to a fourth device (e.g., an NWDAF or MTLF). It should be noted that the response message may also include the data corresponding to the data acquisition request.

[0278] For example, the first device can be a network-side device or a terminal device. The terminal device includes a conventional terminal device and / or a positioning reference unit (PRU). The conventional terminal device can be terminal device 11 in Figure 1. The positioning reference unit (PRU) can perform positioning measurements, such as RSTD, RSRP, UE Rx-Tx time difference measurement, etc., and store these measurement results in a data storage device, such as ADRF. Furthermore, the PRU can send a positioning reference signal (PRS) to the TRP, enabling the TRP to measure and report UL positioning measurements from the PRU at a known location, such as RTOA, UL-AoA, gNB Rx-Tx time difference, etc.

[0279] The network-side device can be the access network device shown in Figure 1, such as a base station or a newly defined artificial intelligence processing node on the access network side; it can also be the core network device shown in Figure 1, such as a Network Data Analytics Function (NWDAF), a Location Management Function (LMF), or a newly defined processing node on the core network side; or it can be a combination of multiple nodes mentioned above. In this embodiment, the first device can collect various data generated in the network, such as network management, service, network, and terminal data.

[0280] In this application, the second device refers to a data acquirer. The second device can be a device with model training capabilities, a device with specific data analysis capabilities, or other devices that need to acquire data. The second device can perform intelligent data analysis on the acquired data, ultimately generating corresponding data analysis results to detect or predict various events occurring in the network. For example, in the embodiments of this application, the second device can be an MTLF (Mobile Technology Provider Interface), responsible for training an AI / ML model using the acquired training data, performing data analysis using the trained model, and outputting the analysis results. Of course, the second device can also be other devices or network elements capable of collecting target data and performing data analysis, such as OAM (Online Security Management), or external security functions (such as firewalls, intrusion detection systems, intrusion prevention systems, etc.), and this application does not impose any limitations on this. For example, the second device in this application can be a communication device configured with an AI model, which is trained to implement network data analysis functions.

[0281] Alternatively, the second device in this application can also refer to a communication device that acquires data on behalf of the data acquirer, such as a GMLC, AMF, LMF, etc. It should be noted that when the second device is a communication device that acquires data on behalf of the data acquirer, before sending a data acquisition request to the first device, the second device will receive a data acquisition request from a fourth device (which can be a third data acquisition request). The third data acquisition request may carry at least one of the following:

[0282] Instructions for requesting data;

[0283] Instructions requesting data for model training;

[0284] Requesting instructions to obtain location-related data;

[0285] Data type information, which indicates the type of data requested;

[0286] Time information, which is used to indicate the time range corresponding to the requested data;

[0287] Regional information, which is used to indicate the regional range corresponding to the requested data;

[0288] Data granularity information, which is used to indicate the granularity of the requested data;

[0289] The equipment information of the fourth device, such as the device identification information and address information of the fourth device;

[0290] The fourth item includes the device's certification information, etc.

[0291] The device information of the fourth device can be represented through the notification address / endpoint. Authentication information refers to the token information signed by the fourth device, which allows other devices to send messages to the fourth device. For example, this authentication information could be a CCAClient credentials assertion. This authentication information can be generated by the data acquirer and carries the data acquirer's identification information, validity period, and / or the data they require. The required data can refer to a description of the data, such as its type, time, region, and granularity.

[0292] In this embodiment of the application, the second device sends a first data acquisition request to the first device, the first data acquisition request being used to request data acquisition.

[0293] Optionally, the first data acquisition request carries at least one of the following:

[0294] The first access token of the second device;

[0295] A first instruction, the first instruction being used to indicate a request to obtain data;

[0296] Data type information, which indicates the type of data requested;

[0297] Time information, which is used to indicate the time range corresponding to the requested data;

[0298] Regional information, which is used to indicate the regional range corresponding to the requested data;

[0299] Data granularity information, which is used to indicate the granularity of the requested data;

[0300] The fourth device's certification information;

[0301] The device information of the fourth device.

[0302] The first access token refers to the token information used by the second device when it initiates a first data acquisition request to the first device. This first access token can be an access token obtained by the second device through interaction with a third device. The first device can use the first access token in the first data acquisition request to verify the identity and authorization of the second and / or fourth devices. If the second and / or fourth devices do not have the permission to acquire the requested data, the first device may choose not to send a first response message to the second and / or fourth devices, or the first device may send a response message indicating that the request has been rejected, thereby protecting the data from being acquired by unauthorized devices.

[0303] Specifically, the first access token may carry device information of the second device and / or the fourth device, and the first device may determine whether it can send a first response message to the fourth device based on the device information of the second device and / or the fourth device in the first access token.

[0304] For example, the second device sends a token acquisition request to the third device. This request may include the second device's desired service information, its own device information, the target device information, and the desired data type information. The target device information refers to the device information corresponding to the data provider, such as device type information and device identification information. The second device's own device information may include its identification information and manufacturer information. After receiving the token acquisition request from the second device, the third device can determine whether the second device has permission to acquire the target data based on at least one of the following: the second device's own device information, desired service information, target device information, and desired data type information in the token acquisition request. If the second device has permission to acquire the target data, the third device will send a first access token or a second access token to the second device. The second device then initiates a first data acquisition request to the first device based on the acquired first access token. Alternatively, the second device initiates a second data acquisition request to the data storage device based on the second access token.

[0305] It should be noted that the first or second access token can be based on data type granularity. That is, the first access token can instruct the second device to retrieve the target data corresponding to the requested data type from the first device, but not to retrieve data corresponding to other data types. The second access token can instruct the second device to retrieve the target data corresponding to the requested data type from the data storage device, but not to retrieve target data corresponding to other data types.

[0306] It should be noted that, in this application embodiment, the third device refers to a device used for managing and storing NF registration information, or a device with authorization functions, or a device with token issuance functions, etc. For example, the third device can be a Network Storage Function (NRF). The NRF is used for NF registration, management, and status detection to achieve automated management of all NFs. Each NF must register with the NRF before it can provide services. Registration information includes NF type, address, service list, etc. Of course, the third device in this application embodiment can also be other network elements or devices with storage functions.

[0307] The first instruction is used to indicate a request to obtain data. For example, the first instruction could be an instruction to request location-related data. The first instruction can also indicate the purpose of the first data acquisition request sent by the second device, clarifying the second device's needs for the first device. Alternatively, the first instruction could be an instruction to request data for model training.

[0308] Data type information indicates the type of data requested. This data type can be a specific data type, such as measurement data, auxiliary data, or positioning data; it can also be UE measurement data, Reference Signal Received Power (RSRP), Reference Signal Time Difference (RSTD), Channel Impulse Response (CIR), etc. Alternatively, this data type information can be represented by event ID, data ID, or analytics ID. It can also be indicated by other information, such as instructions requesting positioning data, positioning-related instructions, or AI positioning-related instructions. It should be noted that data type information can also indicate the type of device generating the target data. For example, in UE measurement data, the data generator could be the UE, or it could be a PRU, RAN, etc. It can also be the device identification information of the data generating device, such as UE ID or PRU ID.

[0309] Time information is used to indicate the time range corresponding to the requested data. For example, it indicates the data collected by the first device within a certain time range, or it indicates the data generated by the first device within a certain time period.

[0310] Regional information is used to indicate the regional range corresponding to the requested data. For example, it may indicate data collected by a first device within a certain regional range, or data generated by a device that generates data within a certain regional range (or indicate the regional range corresponding to the generated data). The regional information may be a cell ID, tracking area ID (TPR), latitude and longitude information, etc.

[0311] Data granularity information is used to indicate the granularity of the requested data, such as: high, medium, low; large, medium, small; coarse, medium, fine; all, general (medium), part, etc. The specific terminology used to represent granularity may vary, but the meaning is similar: indicating data of different granularities or different types of data. Another method of representation may be through different data type information, for example, in location-related data acquisition, it might be: location-related data (coarser granularity), UE measurement data (medium granularity), UE location data (fineer granularity).

[0312] The authentication information can refer to the authentication information of a fourth device, which can be used to instruct the fourth device to sign a token. The second device may receive this authentication information when it receives a data acquisition request from the fourth device. This authentication information is used to indicate whether other devices are allowed to send messages to the fourth device, such as the fourth device allowing the first device to send a first response message. It should be noted that before sending the first response message to the fourth device, the first device can also verify this authentication information to determine whether it can send a response message to the fourth device. Specifically, the first device can verify the validity period (whether it is within the valid time), device information (whether it is authentication information sent by the fourth device), and requested data (whether it is the requested data), etc., in the authentication information.

[0313] It is understandable that the data type information, time information, region information, data granularity information, etc. in the first data acquisition request can limit the specific characteristics of the data requested by the second device, making it easier for the first device to quickly determine the data requested by the second device and improving the processing efficiency of the first device for the first data acquisition request.

[0314] Optionally, the method further includes:

[0315] The second device receives a first response message from the first device.

[0316] The first response message carries at least one of the following:

[0317] First data identification information, the data identification information being used to indicate the tag corresponding to the data requested by the second device;

[0318] First storage identification information, wherein the storage identifier is used to indicate the dataset corresponding to the data requested by the second device;

[0319] Device identification information, which is used to indicate the data storage device storing the data requested by the second device.

[0320] After receiving a first data acquisition request from a second device, the first device sends a first response message to the second device to provide feedback on the result of the data acquisition request. The second device can then acquire data from the data storage device based on at least one of the first data identifier information, first storage identifier information, and device identifier information carried in the first response message.

[0321] The first data identification information is used to indicate the tag corresponding to the data requested by the second device; for example, the first data identification information may be a DataSetTag. The first storage identification information is used to indicate the dataset corresponding to the data requested by the second device; for example, the first storage identification information may be a Storage Transaction ID. The device identification information is used to indicate the data storage device storing the data requested by the second device; the device identification information may be the identity identifier of the data storage device, for example, ADRFID.

[0322] For example, each of the first devices stores data in the same data storage device. When the first response message carries first data identification information, the second device can request the target data corresponding to the tag indicated by the first data identification information from the data storage device. For example, if the first data identification information indicates a location service, the second device can obtain data related to the location service from the data storage device based on the first data identification information. When the first response message carries first storage identification information, the second device can request the target data contained in the dataset indicated by the first storage identification information from the data storage device.

[0323] Alternatively, different first devices can store data in different data storage devices, each managed by a unified management device. When the first response message carries first data identification information, the second device can request target data under the topic indicated by the first data identification information from the management device. For example, if the first data identification information indicates the topic as location service, the second device can send a location service data acquisition request to the management device based on the first data identification information. After receiving the location service data acquisition request, the management device forwards the request to each managed data storage device, and the data storage device containing location service-related data feeds back the target data related to the location service to the second device. When the first response message carries first storage identification information, the second device can send a dataset acquisition request to the management device, requesting the target data contained in the dataset indicated by the first storage identification information. After receiving the dataset acquisition request, the management device forwards the request to each managed data storage device, and the data storage device of the dataset indicated by the first storage identification information feeds back the target data to the second device. If the first response message contains device identification information, the second device sends a data acquisition request to the management device, and includes the device identification information in the data acquisition request. The management device then directly notifies the data storage device corresponding to the device identification information to send the target data back to the second device.

[0324] Alternatively, different first devices can store data in different data storage devices. When the first response message carries first data identification information and / or first storage identification information, the second device sends a data acquisition request to each second device via broadcast. The data storage device storing the target data indicated by the first data identification information and / or the target data indicated by the first storage identification information then feeds back the target data to the second device. If the first response message carries device identification information, the second device can directly send a data acquisition request to the data storage device indicated by the device identification information to request the target data.

[0325] Optionally, the method further includes:

[0326] Step S31: The second device sends a token acquisition request to the third device; the token acquisition request is used to request access token information.

[0327] Step S32: The second device receives a first access token or a second access token from the third device.

[0328] Here, the first access token refers to the token information used by the second device when it initiates a first data acquisition request to the first device, and the second access token refers to the token information used by the second device when it initiates a second data acquisition request to the data storage device. The first access token and / or the second access token can be access token information requested by the second device through interaction with the third device.

[0329] It should be noted that the first access token and / or the second access token can be based on data type granularity, data granularity, time granularity, or region granularity. For example, the first access token and / or the second access token can be used to indicate that the second device can obtain target data corresponding to that data type from the first device, but cannot obtain data corresponding to other data types.

[0330] Furthermore, the first or second access token may contain at least one of the following: token information, data granularity, data type, time information, and region information.

[0331] It should be noted that the first or second access token can also be an indicator token, and at least one of the following: data granularity, data type, time information, and region information. For example, the first or second access token is token information, which includes at least one of the following: data granularity, data type, time information, and region information. It should be noted that the aforementioned data granularity, data type, time information, and region information can be the data granularity, data type, time information, and region information corresponding to the data that the second device can / is authorized to obtain.

[0332] For example, the second device sends a token acquisition request to the third device. This request may include the second device's desired service information, its own device information, and the target device information. The target device information refers to the device information corresponding to the data provider, such as device type information and device identification information. The second device's own device information may include its identification information and manufacturer information. After receiving the token acquisition request from the second device, the third device can determine whether the second device has permission to access the target data based on at least one of the following: the second device's own device information, desired service information, and target device information in the token acquisition request. If the second device has permission to access the target data, the third device will send a first access token or a second access token to the second device. The second device then initiates a data acquisition request to the data storage device based on the acquired first or second access token.

[0333] It should be noted that, in this application embodiment, the third device refers to a device used to manage and store NF registration information. For example, the third device can be a Network Storage Function (NRF). The NRF is used to register, manage, and detect the status of NFs, realizing automated management of all NFs. Each NF must register with the NRF upon startup to provide services. The registration information includes NF type, address, service list, etc. Of course, the third device in this application embodiment can also be other network elements or devices with storage functions.

[0334] Optionally, the method further includes:

[0335] The second device sends a second data acquisition request to the data storage device based on the second access token; the second data acquisition request is used to acquire data.

[0336] In this application embodiment, the data storage device refers to a device or network element with data storage function. For example, the data storage device may be an ADRF or other device or network element with data storage function.

[0337] Optionally, the second data acquisition request carries at least one of the following:

[0338] The device identification information of the second device;

[0339] The first data identification information;

[0340] The first access token;

[0341] The second access token.

[0342] For example, the second device can send a second data acquisition request to the data storage device through services such as Nadrf_DataManagement_RetrievalRequest Request. The second data acquisition request may carry at least one of the following: the second device's own device information (such as its own device identification information, type information, etc.), data identification information (such as DataSetTag, Storage Transaction ID, etc.), a first access token, a second access token (such as token information), etc.

[0343] Data storage devices can determine the data to be provided based on data identification information.

[0344] The data storage device can also determine whether the second device can obtain the target data based on the device identification information of the second device and the list of network function instances corresponding to the target data. If the list of network function instances corresponding to the target data contains the device identification information or instance identifier of the second device, it can be considered that the second device has the authority to obtain the target data, and the data storage device provides the target data to the second device.

[0345] The second access token can be used to verify the identity of the second device. For example, the data storage device can verify the integrity of the second access token by interacting with a third device. If verification is successful, the data storage device can provide the target data to the second device.

[0346] Optionally, the token acquisition request carries at least one of the following:

[0347] Device information of the second device;

[0348] Target device information;

[0349] Equipment information for the fourth device;

[0350] Desired service information, which indicates the type of desired service, such as data collection service, collection and open service, etc.

[0351] Expected data type information, which is used to indicate the type of expected data;

[0352] The desired data granularity information, which is used to indicate the desired granularity of the data.

[0353] The device information of the second or fourth device can include device identification information, address information, etc. For example, the device information of the second or fourth device can be represented by a notification address / endpoint.

[0354] The target device information refers to the device information corresponding to the data provider, such as device type information and device identification information. The second device's own device information may include its identification information and manufacturer information. After receiving the token acquisition request from the second device, the third device can determine whether the second device has the right to acquire the target data based on at least one of the second device's own device information, the desired service information, and the target device information in the token acquisition request. If the second device has the right to acquire the target data, the third device will send a first access token and / or a second access token to the second device. The second device initiates a first data acquisition request to the first device based on the acquired first access token, and sends a second data acquisition request to the data storage device based on the second access token.

[0355] It is understood that the first access token and the second access token in the embodiments of this application may be the same or different.

[0356] Optionally, the service information indicates a data acquisition service; the token acquisition request also carries at least one of the following:

[0357] Data granularity information, which is used to indicate the granularity of the requested data;

[0358] Data type information, which indicates the type of data requested;

[0359] Time information, which is used to indicate the time range corresponding to the requested data;

[0360] Regional information, which is used to indicate the regional range corresponding to the requested data.

[0361] Optionally,

[0362] The first data acquisition request carries at least one of the following:

[0363] The first access token of the second device;

[0364] A first instruction, the first instruction being used to indicate a request to obtain data;

[0365] Data type information, which indicates the type of data requested by the second device;

[0366] Time information, wherein the time information is used to indicate the time range corresponding to the data requested by the second device;

[0367] Regional information, wherein the regional information is used to indicate the regional range corresponding to the data requested by the second device;

[0368] Data granularity information, which is used to indicate the granularity of the data requested by the second device.

[0369] The first instruction is used to indicate a request to obtain data. For example, the first instruction may be an instruction to request location-related data.

[0370] Data type information indicates the type of requested data. This data type information can be a specific data type, such as UE measurement data, Reference Signal Received Power (RSRP), Reference Signal Time Difference (RSTD), Channel Impulse Response (CIR), etc. Alternatively, this data type information can also be represented by an event ID. It should be noted that data type information can also indicate the device that generated the data; for example, in UE measurement data, the data generator is the UE.

[0371] Time information is used to indicate the time range corresponding to the requested data, for example, indicating the data collected by the first device within a certain time range.

[0372] Regional information is used to indicate the regional range corresponding to the requested data, for example, indicating the data collected by the first device within a certain regional range. The regional information may include cell ID, tracking area identifier (TPR), latitude and longitude information, etc.

[0373] Data granularity information is used to indicate the granularity of the requested data, such as: high, medium, low; large, medium, small; coarse, medium, fine; all, general (medium), part, etc. The specific terminology used to represent granularity may vary, but the meaning is similar: indicating data of different granularities or different types of data. Another method of representation may be through different data type information, for example, in location-related data acquisition, it might be: location-related data (coarser granularity), UE measurement data (medium granularity), UE location data (fineer granularity).

[0374] The data acquisition method provided in this application embodiment allows a second device, acting as a data acquirer, to send a first data acquisition request to a first device (data provider) to request data collected by the first device. Upon receiving a first response message from the first device, the second device can retrieve data from a data storage device based on at least one of the data identification information, storage identification information, and device identification information carried in the first response message. In this application embodiment, the data acquirer can obtain data stored by other devices (data providers) from the data storage device, expanding the scope of data use and improving data utilization.

[0375] Referring to Figure 5, a flowchart of an information transmission method provided in an embodiment of this application is shown. This method is applied to a third device. As shown in Figure 5, the method may specifically include:

[0376] Step 401: The third device receives a search request message from the second device; the search request message is used to request the search of the first device.

[0377] Step 402: The third device determines at least one first device based on the search request message;

[0378] Step 403: The third device sends feedback information to the second device; the feedback information includes information about at least one first device.

[0379] The search request message includes at least one of the following:

[0380] First indication information, the first indication information being used to indicate the location of a first device with data collection capabilities;

[0381] The second instruction information is used to instruct the search for a first device with passive data collection capabilities;

[0382] The third instruction information is used to indicate the search for a first device with data openness capabilities;

[0383] The fourth instruction information is used to instruct the search for a first device that supports the data open service.

[0384] It should be noted that, in the embodiments of this application, the third device refers to a device used for managing and storing NF registration information, or a device with authorization functions, or a device with token issuance functions, etc. For example, the third device can be a Network Repository Function (NRF). The NRF is used for NF registration, management, and status detection to achieve automated management of all NFs. Each NF must register with the NRF before it can provide services. Registration information includes NF type, address, service list, etc. Of course, the third device in the embodiments of this application can also be other network elements or devices with storage functions. The first device refers to the data provider, which can collect and provide data. The second device refers to the data acquirer, which can be a device with model training capabilities, a device with specific data analysis capabilities, or other devices that need to acquire data.

[0385] Alternatively, the second device in this application can also refer to a communication device that acquires data on behalf of the data acquirer, such as a GMLC, AMF, LMF, etc. It should be noted that when the second device is a communication device that acquires data on behalf of the data acquirer, before sending a data acquisition request to the first device, the second device will receive a data acquisition request from a fourth device (which can be a third data acquisition request). The third data acquisition request may carry at least one of the following:

[0386] Instructions for requesting data;

[0387] Instructions requesting data for model training;

[0388] Requesting instructions to obtain location-related data;

[0389] Data type information, which indicates the type of data requested;

[0390] Time information, which is used to indicate the time range corresponding to the requested data;

[0391] Regional information, which is used to indicate the regional range corresponding to the requested data;

[0392] Data granularity information, which is used to indicate the granularity of the requested data;

[0393] The equipment information of the fourth device, such as the device identification information and address information of the fourth device;

[0394] The fourth item includes the device's certification information, etc.

[0395] In this embodiment, the second device can request to locate the first device by sending a search request message to the third device. After receiving the search request message, the third device identifies at least one first device and sends feedback information to the second device to inform it of the information of the at least one first device found.

[0396] Based on at least one piece of information from the first device in the received feedback information, the second device can send a data acquisition request to the first device to request data. The process by which the second device requests data from the first device can be referred to the method embodiments corresponding to Figures 3 and 4 above.

[0397] It should be noted that at least one of the first devices identified by the third device needs to support at least one of the following: data collection capability, passive data collection capability, data open capability, and data open service as indicated in the lookup request message.

[0398] Data collection capability refers to a device's ability to collect data for its own use or that of other devices. Passive data collection capability refers to a device's ability to collect data based on specific trigger conditions. Data openness capability refers to a device's ability to share its data for other devices to access. Data openness service is a service supported or provided by the device, meaning that other devices can obtain data through this service.

[0399] Optionally, passive data collection capability can also be called non-active data collection capability, passive collection capability, or data collection capability using a non-actively triggered positioning method, etc.

[0400] The first device supporting passive data collection capability does not require triggering additional interactions to collect data. For example, after receiving a data request message, the first device does not trigger additional interactions, such as location operations / location interactions, because of the data request message. Instead, it interacts based on corresponding triggering conditions (such as location interaction), and then collects location-related data generated during the interaction. The location interaction process can occur in historical time, current time, or future time, determined based on data-limiting information.

[0401] In this embodiment, the third device can determine the first device that meets the needs of the second device based on at least one of the first indication information, second indication information, third indication information, and fourth indication information carried in the received search request message, and feed back the information of the first device to the second device, so that the second device can send a data acquisition request to the first device based on the information of the first device. This can reduce communication overhead and improve the data acquisition efficiency of the second device because the second device may fail to send a data acquisition request to the first device that does not support data collection capabilities, passive data collection capabilities, data open capabilities, data open services, etc.

[0402] Optionally, the method further includes:

[0403] The third device receives a registration request message from at least one first device.

[0404] The registration request message includes at least one of the following:

[0405] The fifth indication information is used to indicate that the first device has data collection capabilities;

[0406] The sixth indication information is used to indicate that the first device has passive data collection capability;

[0407] The seventh indication information is used to indicate that the first device has data openness capability;

[0408] The eighth indication information is used to indicate that the first device supports data open services.

[0409] In this embodiment of the application, the first device may also inform the third device of its supported capabilities and / or services by sending a registration request message to the third device, so that the third device can determine the matching first device after receiving a search request message.

[0410] Referring to Figure 6, a flowchart of an information transmission method provided in an embodiment of this application is shown. The method is applied to a first device. As shown in Figure 6, the method may specifically include:

[0411] Step 501: The first device sends a registration request message to the third device.

[0412] The registration request message includes at least one of the following:

[0413] The fifth indication information is used to indicate that the first device has data collection capabilities;

[0414] The sixth indication information is used to indicate that the first device has passive data collection capability;

[0415] The seventh indication information is used to indicate that the first device has data openness capability;

[0416] The eighth indication information is used to indicate that the first device supports data open services.

[0417] In this embodiment of the application, the first device may also inform the third device of its supported capabilities and / or services by sending a registration request message to the third device, so that the third device can determine the matching first device after receiving a search request message.

[0418] Data collection capability refers to a device's ability to collect data for its own use or that of other devices. Passive data collection capability refers to a device's ability to collect data based on specific trigger conditions. Data openness capability refers to a device's ability to share its data for other devices to access. Data openness service is a service supported or provided by the device, meaning that other devices can obtain data through this service.

[0419] Optionally, passive data collection capability can also be called non-active data collection capability, passive collection capability, or data collection capability using a non-actively triggered positioning method, etc.

[0420] The first device supporting passive data collection capability does not require triggering additional interactions to collect data. For example, after receiving a data request message, the first device does not trigger additional interactions, such as location operations / location interactions, because of the data request message. Instead, it interacts based on corresponding triggering conditions (such as location interaction), and then collects location-related data generated during the interaction. The location interaction process can occur in historical time, current time, or future time, determined based on data-limiting information.

[0421] It should be noted that after step 501, the first device can also execute the steps in the embodiment corresponding to Figure 3. For details, please refer to the relevant descriptions in the foregoing embodiments, which will not be repeated here.

[0422] Referring to Figure 7, a flowchart of an information transmission method provided in an embodiment of this application is shown. The method is applied to a second device. As shown in Figure 7, the method may specifically include:

[0423] Step 601: The second device sends a search request message to the third device; the search request message is used to request the search of the first device;

[0424] Step 602: The second device receives feedback information from the third device; the feedback information includes information from at least one first device.

[0425] The search request message includes at least one of the following:

[0426] First indication information, the first indication information being used to indicate the location of a first device with data collection capabilities;

[0427] The second instruction information is used to instruct the search for a first device with passive data collection capabilities;

[0428] The third instruction information is used to indicate the search for a first device with data openness capabilities;

[0429] The fourth instruction information is used to instruct the search for a first device that supports the data open service.

[0430] In this embodiment, the second device can request to locate the first device by sending a search request message to the third device. After receiving the search request message, the third device identifies at least one first device and sends feedback information to the second device to inform it of the information of the at least one first device found.

[0431] Based on at least one piece of information from the first device in the received feedback information, the second device can send a data acquisition request to the first device to request the acquisition of target data. The process by which the second device requests data from the first device can be referred to the method embodiments corresponding to Figures 3 and 4 above.

[0432] The first device that the second device requests to locate the third device needs to support at least one of the following: data collection capability, passive data collection capability, data open capability, and data open service, as indicated in the lookup request message.

[0433] Data collection capability refers to a device's ability to collect data for its own use or that of other devices. Passive data collection capability refers to a device's ability to collect data based on specific trigger conditions. Data openness capability refers to a device's ability to share its data for other devices to access. Data openness service is a service supported or provided by the device, meaning that other devices can obtain data through this service.

[0434] Optionally, passive data collection capability can also be called non-active data collection capability, passive collection capability, or data collection capability using a non-actively triggered positioning method, etc.

[0435] The first device supporting passive data collection capability does not require triggering additional interactions to collect data. For example, after receiving a data request message, the first device does not trigger additional interactions, such as location operations / location interactions, because of the data request message. Instead, it interacts based on corresponding triggering conditions (such as location interaction), and then collects location-related data generated during the interaction. The location interaction process can occur in historical time, current time, or future time, determined based on data-limiting information.

[0436] After step 602, the second device can also execute the steps in the embodiment corresponding to Figure 4.

[0437] Referring to Figure 8, a flowchart of an information transmission method provided in an embodiment of this application is shown. The method is applied to a third device. As shown in Figure 8, the method may specifically include:

[0438] Step 701: The third device receives a token acquisition request from the second device, the token acquisition request being used to request access token information;

[0439] Step 702: The third device verifies the token acquisition request;

[0440] Step 703: The third device sends a first access token or a second access token to the second device.

[0441] It should be noted that, in the embodiments of this application, the third device refers to a device used for managing and storing NF registration information, or a device with authorization functions, or a device with token issuance functions, etc. For example, the third device can be a Network Repository Function (NRF). The NRF is used for NF registration, management, and status detection to achieve automated management of all NFs. Each NF must register with the NRF before it can provide services. Registration information includes NF type, address, service list, etc. Of course, the third device in the embodiments of this application can also be other network elements or devices with storage functions. The first device refers to the data provider, which can collect and provide data. The second device refers to the data acquirer, which can be a device with model training capabilities, a device with specific data analysis capabilities, or other devices that need to acquire data.

[0442] Alternatively, the second device in this application can also refer to a communication device that acquires data on behalf of the data acquirer, such as a GMLC, AMF, LMF, etc. It should be noted that when the second device is a communication device that acquires data on behalf of the data acquirer, before sending a data acquisition request to the first device, the second device will receive a data acquisition request from a fourth device (which can be a third data acquisition request). The third data acquisition request may carry at least one of the following:

[0443] Instructions for requesting data;

[0444] Instructions requesting data for model training;

[0445] Requesting instructions to obtain location-related data;

[0446] Data type information, which indicates the type of data requested;

[0447] Time information, which is used to indicate the time range corresponding to the requested data;

[0448] Regional information, which is used to indicate the regional range corresponding to the requested data;

[0449] Data granularity information, which is used to indicate the granularity of the requested data;

[0450] The equipment information of the fourth device, such as the device identification information and address information of the fourth device;

[0451] The fourth item includes the device's certification information, etc.

[0452] Upon receiving a token acquisition request from the second device, the third device can verify the received token acquisition request and, if the verification is successful, send a first access token or a second access token to the second device.

[0453] The third device verifies the token acquisition request, specifically by determining whether an access token can be sent to the second device based on the token acquisition request.

[0454] Optionally, the token acquisition request may also include indication information for requesting to acquire a token.

[0455] An access token is carried by the second device when sending a service to the target device. The target device uses the access token to determine whether the second device can / is authorized to use the service and the corresponding parameters of the service (such as data type, granularity, etc.).

[0456] The third device verifies the token acquisition request, which may be based on whether the information in the token acquisition request matches the information (pre-)reported by the target device. For example, the device information of the second or fourth device matches the interoperable device information reported by the target device; the expected service information matches the services offered by the target device; the expected data type and granularity match the data type and granularity offered by the target device, etc.

[0457] For example, the second device sends a token acquisition request to the third device. This request may include the second device's desired service information, its own device information, the target device information, and the desired data type information. The target device information refers to the device information corresponding to the data provider, such as device type information and device identification information. The second device's own device information may be its identification information, manufacturer information, etc. After receiving the token acquisition request from the second device, the third device can determine whether the second device has permission to access the target data, i.e., whether it can send an access token to the second device, based on at least one of the following in the token acquisition request: the second device's own device information, the desired service information, the target device information, and the desired data type information. If the second device has permission to access the target data, the third device will send a first access token or a second access token to the second device. The second device then initiates a first data acquisition request to the first device based on the acquired first access token. Alternatively, the second device initiates a second data acquisition request to the data storage device based on the second access token.

[0458] It should be noted that whether the second device has the corresponding permissions can refer to whether the second device can obtain relevant data from the target device, whether it can interact with it, etc. For example, the third device compares the information reported by the target device (such as the first device) to determine whether the second device can obtain a token. Specifically, the third device compares the manufacturer information that the target device reports as permissible for interaction with the second device's manufacturer information. If the manufacturer information that the first device can interact with includes the second device's manufacturer information, then the second device has the corresponding permissions and can perform the corresponding interactions. The specific determination method can be based on the third device's internal logic or information previously received by the third device.

[0459] It should be noted that the first or second access token can be based on data type granularity. That is, the first access token can instruct the second device to retrieve the target data corresponding to the requested data type from the first device, but not to retrieve data corresponding to other data types. The second access token can instruct the second device to retrieve the target data corresponding to the requested data type from the data storage device, but not to retrieve target data corresponding to other data types.

[0460] Optionally, the token acquisition request includes at least one of the following:

[0461] Device information of the second device;

[0462] Target device information;

[0463] Equipment information for the fourth device;

[0464] Expected service information;

[0465] Expected data type information

[0466] Expected data granularity information.

[0467] The device information of the second or fourth device can include device identification information, address information, etc. For example, the device information of the second or fourth device can be represented by a notification address / endpoint.

[0468] The target device information refers to the device information corresponding to the data provider, such as device type information and device identification information. The second device's own device information may include its identification information and manufacturer information. After receiving the token acquisition request from the second device, the third device can determine whether the second device has the right to acquire the target data based on at least one of the second device's own device information, the desired service information, and the target device information in the token acquisition request. If the second device has the right to acquire the target data, the third device will send a first access token and / or a second access token to the second device. The second device initiates a first data acquisition request to the first device based on the acquired first access token, and sends a second data acquisition request to the data storage device based on the second access token.

[0469] Optionally, the token acquisition request includes device information of the second device and expected data type information; the third device verifies the token acquisition request, including:

[0470] The third device verifies, based on the device information of the second device, whether the second device has the permission to obtain the data corresponding to the expected data type information.

[0471] Specifically, determining whether the second device possesses the permission to access the data corresponding to the desired data type information can include whether the second device can obtain the access token corresponding to the desired data type information. For example, this can be determined by comparing the device information of the second device, the desired data type information, and the information (pre-reported) by the target device.

[0472] Optionally, the token acquisition request includes device information of the second device and desired data granularity information; the third device verifies the token acquisition request, including:

[0473] The third device verifies, based on the device information of the second device, whether the second device has the permission to obtain the data corresponding to the desired data granularity information.

[0474] Optionally, the token acquisition request includes device information of the second device and device information of the fourth device; the third device verifies the token acquisition request, including:

[0475] The third device verifies whether the second device has the authority to obtain authorization for the fourth device based on the device information of the second device and the device information of the fourth device.

[0476] Optionally, the first access token or the second access token includes at least one of the following:

[0477] Device information of the second device;

[0478] Target device information;

[0479] Equipment information for the fourth device;

[0480] Expected service information;

[0481] Expected data type information;

[0482] Expected data granularity information.

[0483] It should be noted that the first or second access token may be in the form of a token, etc. The first or second access token may also carry token indication information, used to indicate that the information is token information, etc.

[0484] The interaction process between the first device, the second device, the third device, and the data storage device in this application embodiment is illustrated below with specific application scenarios. Referring to Figure 9, a schematic diagram of a device interaction process provided in this application embodiment is shown. As shown in Figure 9, the first device is LMF, the second device is NWDAF (MTLF), the data storage device is ADRF, and the third device is NRF.

[0485] It should be noted that NRF refers to the Network Repository Functional Network Element, but it can also refer to other network elements or devices with storage functions. NWDAF (MTLF) refers to the Model Training Logical Function (MTLF) within NWDAF, a device with model training capabilities, or other devices with model training capabilities, or other devices that need to acquire data. LMF refers to the Location Management Function, a device that assists in location management and can collect location information, or other devices that can provide data, such as NWDAF. ADRF refers to (Analytics Data Repository Functional Network Element), which can refer to devices with data storage capabilities.

[0486] Specifically, the data acquisition method provided in this application embodiment may include the following steps:

[0487] Step 0: LMF may generate a data identification information (such as DataSetTag) to describe and identify the data when storing it later.

[0488] Step 1: The LMF stores data in the ADRF. Specifically, the LMF may send a data storage request to the ADRF through services such as Nadrf_DataManagement_Storage Request, requesting that the data be stored in the ADRF. The LMF can, according to its own operational logic, send a data storage request to the ADRF after collecting or generating data to store the collected or generated data in real time; or, it can periodically send a data storage request to the ADRF according to a preset cycle; or, the LMF can be triggered by other devices to send a data storage request to the ADRF.

[0489] The data storage request may include the data to be stored, the LMF ID (i.e., the LMF's own device identification information), data identification information (such as DataSetTag), data description information, and a list of devices that can obtain the data (such as a list of network function instances). It should be noted that the list of devices that can obtain the data can also be a list of devices authorized / agreed to obtain the data by the LMF; on the other hand, this list can include identification information for multiple devices, or vendor information, etc.

[0490] Step 2: ADRF Feedback on Storage Results. After receiving a data storage request from LMF, ADRF feeds back the data storage result. Specifically, when the LMF's data storage request does not carry a DataSetTag, ADRF may feed back a Storage Transaction ID to identify the data; when the LMF's data storage request carries a DataSetTag, ADRF may use and feed back the DataSetTag as the data identifier.

[0491] It should be noted that when an LMF data storage request carries a DataSetTag, ADRF may further separate the data in a DataSetTag based on the different data and assign new DataSetTags. That is, it may receive one DataSetTag but return one or more DataSetTags.

[0492] Step 3: The NWDAF sends a network element lookup request to the NRF, requesting the discovery of network elements that can provide the required data. For example, the NWDAF can send a network element lookup request to the NRF through the Nnrf_NFDiscovery_Request service. This network element lookup request must carry at least one of the following: network element type (indicating the type of network element being searched, such as an LMF network element), area information (indicating the service range of the network element being searched), and capability information (possessing the ability to support providing location-related data, or data information that can be provided (such as supported event IDs)).

[0493] In addition, LMF registers its supported capabilities with NRF, such as data collection capabilities, passive data collection capabilities (which indicate that LMF supports passive data collection), and data openness capabilities.

[0494] Alternatively, the LMF can register the services it supports with the NRF, such as data collection services (which indicate that the LMF supports services related to other devices sending data acquisition requests to the LMF) and data open services (which indicate that the LMF supports other devices acquiring data through this service).

[0495] The NRF receives the LMF's registration information.

[0496] NRF storage LMF supports capabilities and services.

[0497] The NRF sends the registration result to the LMF to inform the LMF that it has received the registration message and stored the LMF's capability information, service information, etc.

[0498] When consumers such as NWDAF look up network elements (e.g., LMF) from the NRF, they can also use the indication information corresponding to at least one of the capabilities and services carried in the network element lookup request to allow the NRF to find network elements that support the corresponding capabilities and / or services.

[0499] Step 4: The NWDAF requests access token information by interacting with the NRF. For example, the NWDAF can send a token acquisition request to the NRF through the Nnrf_AccessToken_Get Request service. This token acquisition request can carry at least one of the following: desired service information (such as the service for which data is requested), its own device information (such as its own device identification information, its own device manufacturer information, etc.), and target device information (such as the type information of the other party's device, the identification information of the other party's device).

[0500] It should be noted that in certain cases, such as when the expected service information is related to data retrieval, the token acquisition request may also include at least one of the following:

[0501] Data granularity information indicates the granularity of the requested data, such as: high, medium, low; large, medium, small; coarse, medium, fine; all, general (medium), part, etc. Specific terminology for granularity may vary, but the meaning is similar: indicating data of different granularities or different types of data. Another method of representation might be through different data type information. For example, in location-related data acquisition, it could be: location-related data (coarser granularity), UE measurement data (medium granularity), UE location data (fineer granularity).

[0502] Data type information indicates the type of data to be requested. This data type can be a direct data type, such as UE measurement data, RSRP (Reference Signal Received Power), RSTD (Reference Signal Time Difference), CIR (Channel Impulse Response), etc., or it can be represented by event ID, etc. It should be noted that data type information can also indicate the device that generated the data, such as in UE measurement data, where the data generator is the UE.

[0503] Time information is used to indicate the time information of the requested data, such as data within a certain time range;

[0504] Regional information is used to indicate the geographic region of the requested data, such as data within a certain region; this region can be a cell ID, latitude and longitude information, etc.

[0505] Step 5: NRF sends out access token information. Specifically, NRF determines whether the device has permission to use the service based on the device information (NWDAF device information) and the desired service information in the token acquisition request from Step 4. If the device has permission to use the service, it will send token information back to NWDAF.

[0506] It should be noted that in certain cases, such as when the expected service information is a data acquisition-related service, the NRF will further determine whether the device has the permission to use the data acquisition service for information such as data granularity, data type, time, and region. If the device has the permission to use the service, it will send token information and / or the corresponding data granularity, data type, time, and region information back to the NWDAF.

[0507] If the device does not have the corresponding permissions, the NRF cannot authorize the NWDAF and may return the corresponding failure response information; or it may return the token information and / or data type, time, region, etc. within the scope of the NWDAF's permissions.

[0508] It should be noted that the aforementioned data granularity information, data category information, etc., can also be indicated by token information rather than individual information elements, i.e., implicit indication, such as a certain byte in the token information.

[0509] Step 6: NWDAF sends a data acquisition request message to LMF, requesting to acquire the target data. Specifically, this data acquisition request message can be an eventExpose-related service or a dedicated data acquisition service, etc. This message may carry at least one of the following:

[0510] Token information, the token information authorized by NRF in step 5;

[0511] Indication information for requesting data, used to indicate that the message is a request to obtain data, such as an indication information for requesting location-related data;

[0512] Data type information indicates the type of data requested. This data type can be a direct data type, such as UE measurement data, RSRP, RSTD, CIR, etc., or it can be represented by event ID, etc.

[0513] Time information is used to indicate the time information of the requested data, such as data within a certain time range;

[0514] Regional information is used to indicate the geographic region of the requested data, such as data within a certain region; this region can be a cell ID, latitude and longitude information, etc.

[0515] Data granularity information, used to indicate the granularity of the requested data.

[0516] Step 7: The LMF authenticates the NF service consumer. Specifically, the LMF verifies the access token, possibly by interacting with the NRF to determine the token's integrity and ensuring that the access token contains the specified data type and granularity.

[0517] If the verification is successful, LMF will determine the data that can be requested and store the NWDAF instance ID as part of the list of NF instances that can retrieve the data.

[0518] Steps 8-9: LMF reuses data storage services to update the list of devices that can access the data. The specific implementation process is as described in steps 1-2.

[0519] It should be noted that when updating the list of devices that can obtain data, the data storage request can include storage identification information, such as Storage Transaction ID.

[0520] Step 10: The LMF sends a response message to the NWDAF regarding the data request result. Specifically, the LMF sends a response message to the NWDAF, responding to the data request message. This response message can inform the NWDAF of the location where the requested data is stored, its corresponding identifier, etc.; this message can carry at least one of the following:

[0521] Data identification information can be used to identify a dataset. The specific form of this identification information can be called DataSetTag.

[0522] Store identification information, which can be used to identify a dataset, such as a Storage Transaction ID;

[0523] Device identification information is used to indicate data storage devices, such as ADRFID and ADRF identification information; this information can also be identification information for other devices, such as other data storage devices.

[0524] It should be noted that the data corresponding to DataSetTag and Storage Transaction ID may be distinguished by different granularities and different data types. For example, one DataSetTag / Storage Transaction ID may correspond to one data type. When the requested data is of multiple data types, multiple DataSetTag / Storage Transaction IDs can be returned.

[0525] Steps 11-12 are similar to steps 4-5. The NWDAF interacts with the NRF to obtain access token information that allows it to request data from the ADRF, so that it can subsequently send data retrieval requests to the ADRF to request data, etc.

[0526] Steps 13-14: NWDAF sends a data retrieval request to ADRF, requesting the data corresponding to the data identification information. Specifically, NWDAF can send a data retrieval request to ADRF through services such as Nadrf_DataManagement_RetrievalRequest Request, and can carry at least one of the following: its own device information (such as its own device identification information, type information, etc.), data identification information (such as DataSetTag, Storage Transaction ID, etc.), token information, etc.

[0527] ADRF can determine the data to be provided based on data identification information.

[0528] ADRF can also determine whether the NWDAF can acquire the data based on the device information of the NWDAF and the list of devices with available data in step 1 or step 8.

[0529] This token information can be used to verify the identity of the NWDAF device, etc.

[0530] Referring to Figure 10, another device interaction flow diagram provided by an embodiment of this application is shown. As shown in Figure 10, the first device is a device with data storage function, such as ADRF. The second device is a device for auxiliary location management, such as LMF. The fourth device is a device with model training capability, or it can be other devices that need to acquire data, such as NWDAF (MTLF). The third device is a network element or device with storage function, such as NRF.

[0531] Step 0: LMF may generate a data identification information (such as DataSetTag) to describe and identify the data when storing it later.

[0532] Step 1: The LMF stores data in the ADRF. Specifically, the LMF may send a data storage request to the ADRF through services such as Nadrf_DataManagement_Storage Request, requesting that the data be stored in the ADRF. The LMF can, according to its own operational logic, send a data storage request to the ADRF after collecting or generating data to store the collected or generated data in real time; or, it can periodically send a data storage request to the ADRF according to a preset cycle; or, the LMF can be triggered by other devices to send a data storage request to the ADRF.

[0533] The data storage request may include the data to be stored, the LMF ID (i.e., the LMF's own device identification information), data identification information (such as DataSetTag), data description information, and a list of devices that can obtain the data (such as a list of network function instances). It should be noted that the list of devices that can obtain the data can also be a list of devices authorized / agreed to obtain the data by the LMF; on the other hand, this list can include identification information for multiple devices, or vendor information, etc.

[0534] Step 2: ADRF Feedback on Storage Results. After receiving a data storage request from LMF, ADRF feeds back the data storage result. Specifically, when the LMF's data storage request does not carry a DataSetTag, ADRF may feed back a Storage Transaction ID to identify the data; when the LMF's data storage request carries a DataSetTag, ADRF may use and feed back the DataSetTag as the data identifier.

[0535] It should be noted that when an LMF data storage request carries a DataSetTag, ADRF may further separate the data in a DataSetTag based on the different data and assign new DataSetTags. That is, it may receive one DataSetTag but return one or more DataSetTags.

[0536] Step 3: The NWDAF sends a network element lookup request to the NRF, requesting the discovery of network elements that can provide the required data. For example, the NWDAF can send a network element lookup request to the NRF through the Nnrf_NFDiscovery_Request service. This network element lookup request must carry at least one of the following: network element type (indicating the type of network element being searched, such as an LMF network element), area information (indicating the service range of the network element being searched), and capability information (possessing the ability to support providing location-related data, or data information that can be provided (such as supported event IDs)).

[0537] In addition, LMF registers its supported capabilities with NRF, such as data collection capabilities, passive data collection capabilities (which indicate that LMF supports passive data collection), and data openness capabilities.

[0538] Alternatively, the LMF can register the services it supports with the NRF, such as data collection services (which indicate that the LMF supports services related to other devices sending data acquisition requests to the LMF) and data open services (which indicate that the LMF supports other devices acquiring data through this service).

[0539] The NRF receives the LMF's registration information.

[0540] NRF storage LMF supports capabilities and services.

[0541] The NRF sends the registration result to the LMF to inform the LMF that it has received the registration message and stored the LMF's capability information, service information, etc.

[0542] When consumers such as NWDAF look up network elements (e.g., LMF) from the NRF, they can also use the indication information corresponding to at least one of the capabilities and services carried in the network element lookup request to allow the NRF to find network elements that support the corresponding capabilities and / or services.

[0543] Step 4a: The NWDAF sends a data acquisition request to the GML / AMF to retrieve data. This data acquisition request may carry the NWDAF's device information, authentication information, etc. The authentication information may be the NWDAF's CCA information.

[0544] Step 4b: The NWDAF requests access token information by interacting with the NRF. For example, the NWDAF can send a token acquisition request to the NRF through the Nnrf_AccessToken_Get Request service. This token acquisition request can carry at least one of the following: desired service information (such as the service for which data is requested), its own device information (i.e., the NWDAF information in Figure 10, such as its own device identification information, its own device manufacturer information, etc.), and target device information (such as the type information of the other party's device, the identification information of the other party's device).

[0545] It should be noted that in certain cases, such as when the expected service information is related to data retrieval, the token acquisition request may also include at least one of the following:

[0546] Data granularity information indicates the granularity of the requested data, such as: high, medium, low; large, medium, small; coarse, medium, fine; all, general (medium), part, etc. Specific terminology for granularity may vary, but the meaning is similar: indicating data of different granularities or different types of data. Another method of representation might be through different data type information. For example, in location-related data acquisition, it could be: location-related data (coarser granularity), UE measurement data (medium granularity), UE location data (fineer granularity).

[0547] Data type information indicates the type of data to be requested. This data type can be a direct data type, such as UE measurement data, RSRP (Reference Signal Received Power), RSTD (Reference Signal Time Difference), CIR (Channel Impulse Response), etc., or it can be represented by event ID, etc. It should be noted that data type information can also indicate the device that generated the data, such as in UE measurement data, where the data generator is the UE.

[0548] Time information is used to indicate the time information of the requested data, such as data within a certain time range;

[0549] Regional information is used to indicate the geographic region of the requested data, such as data within a certain region; this region can be a cell ID, latitude and longitude information, etc.

[0550] Step 5: NRF sends out access token information. Specifically, NRF determines whether the device has permission to use the service based on the device information (NWDAF device information) and the desired service information in the token acquisition request from Step 4. If the device has permission to use the service, it will send token information back to NWDAF.

[0551] It should be noted that in certain cases, such as when the expected service information is a data acquisition-related service, the NRF will further determine whether the device has the permission to use the data acquisition service for information such as data granularity, data type, time, and region. If the device has the permission to use the service, it will send token information and / or the corresponding data granularity, data type, time, and region information back to the NWDAF.

[0552] If the device does not have the corresponding permissions, the NRF cannot authorize the NWDAF and may return the corresponding failure response information; or it may return the token information and / or data type, time, region, etc. within the scope of the NWDAF's permissions.

[0553] It should be noted that the aforementioned data granularity information, data category information, etc., can also be indicated by token information rather than individual information elements, i.e., implicit indication, such as a certain byte in the token information.

[0554] Step 6: NWDAF sends a data acquisition request message to LMF, requesting to acquire the target data. Specifically, this data acquisition request message can be an eventExpose-related service or a dedicated data acquisition service, etc. This message may carry at least one of the following:

[0555] Token information, the token information authorized by NRF in step 5;

[0556] Indication information for requesting data, used to indicate that the message is a request to obtain data, such as an indication information for requesting location-related data;

[0557] Data type information indicates the type of data requested. This data type can be a direct data type, such as UE measurement data, RSRP, RSTD, CIR, etc., or it can be represented by event ID, etc.

[0558] Time information is used to indicate the time information of the requested data, such as data within a certain time range;

[0559] Regional information is used to indicate the geographic region of the requested data, such as data within a certain region; this region can be a cell ID, latitude and longitude information, etc.

[0560] Data granularity information, used to indicate the granularity of the requested data;

[0561] NWDAF device information;

[0562] NWDAF certification information, such as CCA information.

[0563] Step 7: The LMF authenticates the NF service consumer. Specifically, the LMF verifies the access token, possibly by interacting with the NRF to determine the token's integrity and ensuring that the access token contains the specified data type and granularity.

[0564] If the verification is successful, LMF will determine the data that can be requested and store the NWDAF instance ID as part of the list of NF instances that can retrieve the data.

[0565] Steps 8-9: LMF reuses data storage services to update the list of devices that can access the data. The specific implementation process is as described in steps 1-2.

[0566] It should be noted that when updating the list of devices that can obtain data, the data storage request can include storage identification information, such as Storage Transaction ID.

[0567] Step 10: The LMF sends a response message to the NWDAF regarding the data request result. Specifically, the LMF sends a response message to the NWDAF, responding to the data request message. This response message can inform the NWDAF of the location where the requested data is stored, its corresponding identifier, etc.; this message can carry at least one of the following:

[0568] Data identification information can be used to identify a dataset. The specific form of this identification information can be called DataSetTag.

[0569] Store identification information, which can be used to identify a dataset, such as a Storage Transaction ID;

[0570] Device identification information is used to indicate data storage devices, such as ADRFID and ADRF identification information; this information can also be identification information for other devices, such as other data storage devices.

[0571] It should be noted that the data corresponding to DataSetTag and Storage Transaction ID may be distinguished by different granularities and different data types. For example, one DataSetTag / Storage Transaction ID may correspond to one data type. When the requested data is of multiple data types, multiple DataSetTag / Storage Transaction IDs can be returned.

[0572] Steps 11-12 are similar to steps 4-5. The NWDAF interacts with the NRF to obtain access token information that allows it to request data from the ADRF, so that it can subsequently send data retrieval requests to the ADRF to request data, etc.

[0573] Steps 13-14: NWDAF sends a data retrieval request to ADRF, requesting the data corresponding to the data identification information. Specifically, NWDAF can send a data retrieval request to ADRF through services such as Nadrf_DataManagement_RetrievalRequest Request, and can carry at least one of the following: its own device information (such as its own device identification information, type information, etc.), data identification information (such as DataSetTag, Storage Transaction ID, etc.), token information, etc.

[0574] ADRF can determine the data to be provided based on data identification information.

[0575] ADRF can also determine whether the NWDAF can acquire the data based on the device information of the NWDAF and the list of devices with available data in step 1 or step 8.

[0576] This token information can be used to verify the identity of the NWDAF device, etc.

[0577] In summary, this application provides a data acquisition method. A first device, acting as a data provider, can receive a first data acquisition request from a second device. After receiving the first data acquisition request, the first device sends a first response message to either the second or fourth device. The first response message carries at least one of data identification information, storage identification information, and device identification information. Based on the first response message, the second or fourth device can obtain the target data from the data storage device. In this application embodiment, after the data provider stores the data in the data storage device, it can be used by other devices, expanding the scope of data use and improving data utilization.

[0578] The data acquisition method provided in this application can be executed by a data acquisition device. This application uses an example of a data acquisition device executing the data acquisition method to illustrate the data acquisition device provided in this application.

[0579] Referring to FIG11, a structural block diagram of a data acquisition device provided in an embodiment of this application is shown. This device can be applied to a first device. As shown in FIG11, the device may specifically include:

[0580] The first data acquisition request receiving module 21 is used to receive a first data acquisition request from the second device; the first data acquisition request is used to request data acquisition.

[0581] The first response message sending module 22 is used to send a first response message to the second device or the fourth device;

[0582] The first response message carries at least one of the following:

[0583] First data identification information, which is used to indicate the tag corresponding to the data requested by the second device or the fourth device;

[0584] First storage identification information, which is used to indicate the dataset corresponding to the data requested by the second device or the fourth device;

[0585] Device identification information, which is used to indicate the data storage device corresponding to the data requested by the second device or the fourth device.

[0586] Optionally, the first data acquisition request carries at least one of the following:

[0587] The first access token of the second device;

[0588] A first instruction, the first instruction being used to indicate a request to obtain data;

[0589] Data type information, which indicates the type of data requested;

[0590] Time information, which is used to indicate the time range corresponding to the requested data;

[0591] Regional information, which is used to indicate the regional range corresponding to the requested data;

[0592] Data granularity information, which is used to indicate the granularity of the requested data;

[0593] The authentication information of the fourth device;

[0594] The device information of the fourth device.

[0595] Optionally, the device further includes:

[0596] The list update module is used to update the target network function instance list corresponding to the target data; the updated target network function instance list includes the instance identifiers of the second device and / or the fourth device.

[0597] Optionally, the device further includes:

[0598] The first storage request sending module is used to send a first storage request to the data storage device;

[0599] The first storage request carries at least one of the following:

[0600] The data that needs to be stored;

[0601] The device identifier of the first device;

[0602] Second data identification information;

[0603] Second storage identification information;

[0604] Data description information;

[0605] First list of network function examples.

[0606] Optionally, the first network function instance list includes the updated target network function instance list.

[0607] Optionally, the first network function instance list includes a list of devices that the first device has authorized or agreed to access data.

[0608] Optionally, the device further includes:

[0609] The data storage result receiving module is used to receive data storage results from the data storage device.

[0610] Optionally, the data storage result includes at least one of the following:

[0611] At least one third-party data identifier;

[0612] Third, store identification information.

[0613] Optionally, the device further includes:

[0614] The information generation module is used to generate the second data identification information based on the data to be stored.

[0615] Optionally, the first response message sending module includes:

[0616] A verification submodule is used to verify at least one of the second device and the fourth device;

[0617] The sending submodule is used to send a first response message to the second device or the fourth device if the verification is successful.

[0618] Optionally, the verification submodule includes at least one of the following:

[0619] The first verification unit is used to verify the second device based on the first access token of the second device;

[0620] The second verification unit is used to verify the fourth device based on the authentication information of the fourth device;

[0621] The third verification unit is used to verify at least one of the second device and the fourth device based on the second network function instance list.

[0622] Optionally, the first data acquisition request carries the first access token and the data type information; the first verification unit is specifically used for:

[0623] Verify whether the first access token contains the data type information;

[0624] If the first access token contains the data type information, it is determined that the second device has passed authentication.

[0625] Optionally, the first data acquisition request carries the first access token and the data granularity information; the first verification unit is specifically used for:

[0626] Verify whether the first access token contains the data granularity information;

[0627] If the first access token contains the data granularity information, it is determined that the second device has passed authentication.

[0628] Optionally, the first data acquisition request carries the authentication information of the fourth device; the second verification unit is specifically used for:

[0629] The fourth device is verified based on at least one of the following in the authentication information of the fourth device: the identification information of the fourth device, the validity period, and the required data.

[0630] Optionally, the first data acquisition request carries the device information of the fourth device; the third verification unit is specifically used for:

[0631] Verify whether the second network function instance list contains the device information of the fourth device;

[0632] If the device information of the fourth device is included in the second network function instance list, it is determined that the fourth device has passed verification.

[0633] Referring to FIG12, a structural block diagram of another data acquisition device provided in an embodiment of this application is shown. This device can be applied to a second device. As shown in FIG12, the device may specifically include:

[0634] The first data acquisition request sending module 31 is used to send a first data acquisition request to the first device; the first data acquisition request is used to request data acquisition.

[0635] Optionally, the device further includes:

[0636] The first response message receiving module is used to receive a first response message from the first device;

[0637] The first response message carries at least one of the following:

[0638] First data identification information, the data identification information being used to indicate the topic corresponding to the data requested by the second device;

[0639] First storage identification information, wherein the storage identifier is used to indicate the dataset corresponding to the data requested by the second device;

[0640] Device identification information, which is used to indicate the data storage device storing the data requested by the second device.

[0641] Optionally, the first data acquisition request carries at least one of the following:

[0642] The first access token of the second device;

[0643] A first instruction, the first instruction being used to indicate a request to obtain data;

[0644] Data type information, which indicates the type of data requested;

[0645] Time information, which is used to indicate the time range corresponding to the requested data;

[0646] Regional information, which is used to indicate the regional range corresponding to the requested data;

[0647] Data granularity information, which is used to indicate the granularity of the requested data;

[0648] The fourth device's certification information;

[0649] The device information of the fourth device.

[0650] Optionally, the device further includes:

[0651] The token acquisition request sending module is used to send a token acquisition request to a third device; the token acquisition request is used to request access token information.

[0652] The token receiving module is used to receive a first access token or a second access token from the third device.

[0653] Optionally, the device further includes:

[0654] The second data acquisition request sending module is used to send a second data acquisition request to the data storage device; the second data acquisition request is used to request data acquisition.

[0655] Optionally, the second data acquisition request carries at least one of the following:

[0656] The device identification information of the second device;

[0657] The first data identification information;

[0658] The first access token;

[0659] The second access token.

[0660] Optionally, the token acquisition request carries at least one of the following:

[0661] Device information of the second device;

[0662] Target device information;

[0663] Equipment information for the fourth device;

[0664] Expected service information;

[0665] Expected data type information

[0666] Expected data granularity information.

[0667] Optionally, the service information indicates a data acquisition service; the token acquisition request also carries at least one of the following:

[0668] Data granularity information, which is used to indicate the granularity of the requested data;

[0669] Data type information, which indicates the type of data requested;

[0670] Time information, which is used to indicate the time range corresponding to the requested data;

[0671] Regional information, which is used to indicate the regional range corresponding to the requested data.

[0672] The data acquisition device in this application embodiment can be an electronic device, such as an electronic device with an operating system, or a component in an electronic device, such as an integrated circuit or a chip. The electronic device can be a terminal device. For example, the terminal device can include, but is not limited to, the types of terminal devices 11 listed above.

[0673] The data acquisition device provided in this application embodiment can implement the various processes of the foregoing method embodiments and achieve the same technical effect. To avoid repetition, it will not be described again here.

[0674] The information transmission method provided in this application can be executed by an information transmission device. This application uses an information transmission device executing the information transmission method as an example to illustrate the information transmission device provided in this application.

[0675] Referring to FIG13, a structural block diagram of an information transmission device provided in an embodiment of this application is shown. This device can be applied to a third device. As shown in FIG13, the device may specifically include:

[0676] The search request message receiving module 41 is used to receive a search request message from the second device; the search request message is used to request the search of the first device.

[0677] Determining module 42 is used to determine at least one first device based on the search request message;

[0678] Feedback information sending module 43 is used to send feedback information to the second device; the feedback information includes information of at least one first device;

[0679] The search request message includes at least one of the following:

[0680] First indication information, the first indication information being used to indicate the location of a first device with data collection capabilities;

[0681] The second instruction information is used to instruct the search for a first device with passive data collection capabilities;

[0682] The third instruction information is used to indicate the search for a first device with data openness capabilities;

[0683] The fourth instruction information is used to instruct the search for a first device that supports the data open service.

[0684] Optionally, the device further includes:

[0685] The registration request message receiving module is used to receive registration request messages from at least one first device;

[0686] The registration request message includes at least one of the following:

[0687] The fifth indication information is used to indicate that the first device has data collection capabilities;

[0688] The sixth indication information is used to indicate that the first device has passive data collection capability;

[0689] The seventh indication information is used to indicate that the first device has data openness capability;

[0690] The eighth indication information is used to indicate that the first device supports data open services.

[0691] Referring to FIG14, a structural block diagram of another information transmission device provided in an embodiment of this application is shown. This device can be applied to a first device. As shown in FIG14, the device may specifically include:

[0692] The registration request message sending module 51 is used to send a registration request message to a third device;

[0693] The registration request message includes at least one of the following:

[0694] The fifth indication information is used to indicate that the first device has data collection capabilities;

[0695] The sixth indication information is used to indicate that the first device has passive data collection capability;

[0696] The seventh indication information is used to indicate that the first device has data openness capability;

[0697] The eighth indication information is used to indicate that the first device supports data open services.

[0698] Referring to FIG15, a structural block diagram of another information transmission device provided in an embodiment of this application is shown. This device can be applied to a second device. As shown in FIG15, the device may specifically include:

[0699] The lookup request message sending module 61 is used to send a lookup request message to a third device; the lookup request message is used to request the lookup of the first device;

[0700] Feedback information receiving module 62 is used to receive feedback information from the third device; the feedback information includes information from at least one first device;

[0701] The search request message includes at least one of the following:

[0702] First indication information, the first indication information being used to indicate the location of a first device with data collection capabilities;

[0703] The second instruction information is used to instruct the search for a first device with passive data collection capabilities;

[0704] The third instruction information is used to indicate the search for a first device with data openness capabilities;

[0705] The fourth instruction information is used to instruct the search for a first device that supports the data open service.

[0706] Referring to FIG16, a structural block diagram of another information transmission device provided in an embodiment of this application is shown. This device can be applied to a third device. As shown in FIG16, the device may specifically include:

[0707] The token acquisition request verification module 71 is used to receive a token acquisition request from the second device, wherein the token acquisition request is used to request access token information.

[0708] The token acquisition request verification module 72 is used to verify the token acquisition request;

[0709] The access token sending module 73 is used to send a first access token or a second access token to the second device.

[0710] Optionally, the token acquisition request includes at least one of the following:

[0711] Device information of the second device;

[0712] Target device information;

[0713] Equipment information for the fourth device;

[0714] Expected service information;

[0715] Expected data type information

[0716] Expected data granularity information.

[0717] Optionally, the token acquisition request includes device information of the second device and expected data type information; the token acquisition request verification module includes:

[0718] The first permission verification submodule is used to verify whether the second device has the permission to obtain the data corresponding to the expected data type information based on the device information of the second device.

[0719] Optionally, the token acquisition request includes device information of the second device and desired data granularity information; the token acquisition request verification module includes:

[0720] The second permission verification submodule is used to verify whether the second device has the permission to obtain the data corresponding to the expected data granularity information, based on the device information of the second device.

[0721] Optionally, the token acquisition request includes device information of the second device and device information of the fourth device; the token acquisition request verification module includes:

[0722] The third permission verification submodule is used to verify whether the second device has the permission to obtain authorization for the fourth device based on the device information of the second device and the device information of the fourth device.

[0723] Optionally, the first access token or the second access token includes at least one of the following:

[0724] Device information of the second device;

[0725] Target device information;

[0726] Equipment information for the fourth device;

[0727] Expected service information;

[0728] Expected data type information;

[0729] Expected data granularity information.

[0730] The information transmission device in this application embodiment can be an electronic device, such as an electronic device with an operating system, or a component in an electronic device, such as an integrated circuit or a chip. The electronic device can be a terminal device. For example, the terminal device can include, but is not limited to, the types of terminal devices 11 listed above.

[0731] The information transmission device provided in this application embodiment can implement the various processes of the foregoing method embodiments and achieve the same technical effect. To avoid repetition, it will not be described again here.

[0732] Optionally, as shown in FIG17, this application embodiment also provides a communication device 900, including a processor 901 and a memory 902. The memory 902 stores a program or instructions that can run on the processor 901. For example, when the communication device 900 is a network-side device, when the program or instructions are executed by the processor 901, they implement the various steps of the data acquisition method embodiments described in the first or second aspect above, or implement the various steps of the information transmission method embodiments described in any one of the third, fourth, and fifth aspects above, and can achieve the same technical effect. When the communication device 900 is a terminal device, when the program or instructions are executed by the processor 901, they implement the various steps of the data acquisition method embodiments described in the first or second aspect above, or implement the various steps of the information transmission method embodiments described in the fourth or fifth aspect above, and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0733] Figure 18 shows a schematic diagram of the hardware structure of a terminal device that implements an embodiment of this application.

[0734] The terminal device 1000 includes, but is not limited to, at least some of the following components: radio frequency unit 1001, network module 1002, audio output unit 1003, input unit 1004, sensor 1005, display unit 1006, user input unit 1007, interface unit 1008, memory 1009, and processor 1010.

[0735] Those skilled in the art will understand that the terminal device 1000 may also include a power supply (such as a battery) for powering various components. The power supply can be logically connected to the processor 1010 through a power management system, thereby enabling functions such as charging, discharging, and power consumption management through the power management system. The terminal device structure shown in Figure 18 does not constitute a limitation on the terminal device. The terminal device may include more or fewer components than shown, or combine certain components, or have different component arrangements, which will not be elaborated here.

[0736] It should be understood that, in this embodiment, the input unit 1004 may include a graphics processing unit (GPU) 10041 and a microphone 10042. The GPU 10041 processes image data of still images or videos obtained by an image capture device (such as a camera) in video capture mode or image capture mode. The display unit 1006 may include a display panel 10061, which may be configured in the form of a liquid crystal display, an organic light-emitting diode, or the like. The user input unit 1007 includes a touch panel 10071 and at least one of other input devices 10072. The touch panel 10071 is also called a touch screen. The touch panel 10071 may include a touch detection device and a touch controller. Other input devices 10072 may include, but are not limited to, physical keyboards, function keys (such as volume control buttons, power buttons, etc.), trackballs, mice, and joysticks, which will not be described in detail here.

[0737] In this embodiment, after receiving downlink data from the network-side device, the radio frequency unit 1001 can transmit it to the processor 1010 for processing; in addition, the radio frequency unit 1001 can send uplink data to the network-side device. Typically, the radio frequency unit 1001 includes, but is not limited to, antennas, amplifiers, transceivers, couplers, low-noise amplifiers, duplexers, etc.

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

[0739] The processor 1010 may include one or more processing units; optionally, the processor 1010 integrates an application processor and a modem processor, wherein the application processor mainly handles operations involving the operating system, user interface, and applications, and the modem processor mainly handles wireless communication signals, such as a baseband processor. It is understood that the aforementioned modem processor may also not be integrated into the processor 1010.

[0740] In one optional embodiment of this application, the radio frequency unit 1001 is used for:

[0741] Receive a first data acquisition request from a second device; the first data acquisition request is used to request data acquisition.

[0742] Send a first response message to the second or fourth device;

[0743] The first response message carries at least one of the following:

[0744] First data identification information, which is used to indicate the tag corresponding to the data requested by the second device or the fourth device;

[0745] First storage identification information, which is used to indicate the dataset corresponding to the data requested by the second device or the fourth device;

[0746] Device identification information, which is used to indicate the data storage device corresponding to the data requested by the second device or the fourth device.

[0747] In another optional embodiment of this application, the radio frequency unit 1001 is used for:

[0748] Send a first data acquisition request to the first device; the first data acquisition request is used to request data acquisition;

[0749] Receive the first response message from the first device;

[0750] The first response message carries at least one of the following:

[0751] First data identification information, the data identification information being used to indicate the topic corresponding to the data requested by the second device;

[0752] First storage identification information, wherein the storage identifier is used to indicate the dataset corresponding to the data requested by the second device;

[0753] Device identification information, which is used to indicate the data storage device storing the data requested by the second device.

[0754] In one optional embodiment of this application, the radio frequency unit 1001 is used for:

[0755] Send a registration request message to the third device;

[0756] The registration request message includes at least one of the following:

[0757] The fifth indication information is used to indicate that the first device has data collection capabilities;

[0758] The sixth indication information is used to indicate that the first device has passive data collection capability;

[0759] The seventh indication information is used to indicate that the first device has data openness capability;

[0760] The eighth indication information is used to indicate that the first device supports data open services.

[0761] In another optional embodiment of this application, the radio frequency unit 1001 is used for:

[0762] Send a search request message to a third device; the search request message is used to request the search of the first device;

[0763] The second device receives feedback information from the third device; the feedback information includes information from at least one first device.

[0764] The search request message includes at least one of the following:

[0765] First indication information, the first indication information being used to indicate the location of a first device with data collection capabilities;

[0766] The second instruction information is used to instruct the search for a first device with passive data collection capabilities;

[0767] The third instruction information is used to indicate the search for a first device with data openness capabilities;

[0768] The fourth instruction information is used to instruct the search for a first device that supports the data open service.

[0769] This application also provides a network-side device, including a processor and a communication interface. The communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the steps of the aforementioned method embodiments. This network-side device embodiment corresponds to the above-described network-side device method embodiments. All implementation processes and methods of the above-described method embodiments can be applied to this network-side device embodiment and achieve the same technical effects.

[0770] Specifically, this application embodiment also provides a network-side device, as shown in FIG19. The network-side device 1100 includes: an antenna 111, a radio frequency device 112, a baseband device 113, a processor 114, and a memory 115. The antenna 111 is connected to the radio frequency device 112. In the uplink direction, the radio frequency device 112 receives information through the antenna 111 and sends the received information to the baseband device 113 for processing. In the downlink direction, the baseband device 113 processes the information to be transmitted and sends it to the radio frequency device 112. The radio frequency device 112 processes the received information and transmits it through the antenna 111.

[0771] The method executed by the network-side device in the above embodiments can be implemented in the baseband device 113, which includes a baseband processor.

[0772] The baseband device 113 may include at least one baseband board, on which multiple chips are disposed, as shown in FIG19. One of the chips is, for example, a baseband processor, which is connected to the memory 115 via a bus interface to call the program in the memory 115 and execute the network device operation shown in the above method embodiment.

[0773] The network-side device may also include a network interface 116, such as a common public radio interface (CPRI).

[0774] Specifically, the network-side device 1100 of this embodiment of the invention further includes: instructions or programs stored in memory 115 and executable on processor 114. The processor 114 calls the instructions or programs in memory 115 to execute the methods executed by each module shown in any one of Figures 11 to 15 and achieve the same technical effect. To avoid repetition, it will not be described in detail here.

[0775] This application also provides a network-side device. As shown in FIG20, the network-side device 1200 includes: a processor 1201, a network interface 1202, and a memory 1203. The network interface 1202 is, for example, a common public radio interface (CPRI).

[0776] Specifically, the network-side device 1200 of this embodiment of the invention further includes: instructions or programs stored in memory 1203 and executable on processor 1201. The processor 1201 calls the instructions or programs in memory 1203 to execute the methods executed by each module shown in any one of Figures 11 to 15 and achieve the same technical effect. To avoid repetition, it will not be described in detail here.

[0777] This application also provides a readable storage medium storing a program or instructions. When the program or instructions are executed by a processor, they implement the various processes of the above-described data acquisition method embodiments and achieve the same technical effects. To avoid repetition, they will not be described again here.

[0778] The processor is the processor in the terminal device described in the above embodiments. The readable storage medium includes computer-readable storage media, such as computer read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk.

[0779] This application embodiment also provides a chip, which includes a processor and a communication interface. The communication interface is coupled to the processor. The processor is used to run programs or instructions to implement the various processes of the above data acquisition method embodiments and can achieve the same technical effect. To avoid repetition, it will not be described again here.

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

[0781] This application also provides a computer program / program product, which is stored in a storage medium and executed by at least one processor to implement the various processes of the above-described data acquisition method embodiments, and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0782] This application also provides a data acquisition system, including a network-side device and a terminal device. The network-side device can be used to perform the steps of the information transmission method as described in the third aspect above, and the terminal device can be used to perform the steps of the data acquisition method as described in the fourth or fifth aspect above.

[0783] This application also provides an information transmission system, including a terminal device and a network-side device. The terminal device can be used to perform the steps of the data acquisition method as described in the first or second aspect above, and the network-side device can be used to perform the steps of the data acquisition method as described in the second or first aspect above.

[0784] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element. Furthermore, it should be noted that the scope of the methods and apparatuses in the embodiments of this application is not limited to performing functions in the order shown or discussed, but may also include performing functions substantially simultaneously or in the reverse order, depending on the functions involved. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

[0785] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a computer software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal (which may be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in the various embodiments of this application.

[0786] The embodiments of this application have been described above with reference to the accompanying drawings. However, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other forms under the guidance of this application without departing from the spirit and scope of the claims, and all of these forms are within the protection scope of this application.

Claims

1. A data acquisition method, wherein, The method includes: The first device receives a first data acquisition request from the second device; the first data acquisition request is used to request data acquisition. The first device sends a first response message to the second or fourth device; The first response message carries at least one of the following: First data identification information, which is used to indicate the tag corresponding to the data requested by the second device or the fourth device; First storage identification information, which is used to indicate the dataset corresponding to the data requested by the second device or the fourth device; Device identification information, which is used to indicate the data storage device corresponding to the data requested by the second device or the fourth device.

2. The method according to claim 1, wherein, The first data acquisition request carries at least one of the following: The first access token of the second device; A first instruction, the first instruction being used to indicate a request to obtain data; Data type information, which indicates the type of data requested; Time information, which is used to indicate the time range corresponding to the requested data; Regional information, which is used to indicate the regional range corresponding to the requested data; Data granularity information, which is used to indicate the granularity of the requested data; The authentication information of the fourth device; The device information of the fourth device.

3. The method according to claim 1, wherein, The method further includes: The first device updates the target network function instance list corresponding to the target data; the updated target network function instance list includes the instance identifiers of the second device and / or the fourth device.

4. The method according to any one of claims 1 to 3, wherein, The method further includes: The first device sends a first storage request to the data storage device; The first storage request carries at least one of the following: The data that needs to be stored; The device identifier of the first device; Second data identification information; Second storage identification information; Data description information; First list of network function examples.

5. The method according to claim 4, wherein, The first network function instance list includes the updated target network function instance list.

6. The method according to claim 4, wherein, The first network function instance list includes a list of devices that the first device has authorized or agreed to access data.

7. The method according to claim 4, wherein, The method further includes: The first device receives data storage results from the data storage device.

8. The method according to claim 7, wherein, The data storage result includes at least one of the following: At least one third-party data identifier; Third, store identification information.

9. The method according to claim 4, wherein, The method further includes: The first device generates the second data identification information based on the data to be stored.

10. The method according to any one of claims 2 to 9, wherein, The first device sends a first response message to the second or fourth device, including: The first device verifies at least one of the second device and the fourth device; If the verification is successful, the first device sends a first response message to the second device or the fourth device.

11. The method according to claim 10, wherein, The first device verifies at least one of the second device and the fourth device, including at least one of the following: The first device authenticates the second device based on the first access token of the second device; The first device verifies the fourth device based on the authentication information of the fourth device; The first device verifies at least one of the second device and the fourth device based on the second network function instance list.

12. The method according to claim 11, wherein, The first data acquisition request carries the first access token and the data type information; The first device authenticates the second device based on the first access token of the second device, including: The first device verifies whether the first access token contains the data type information.

13. The method according to claim 11, wherein, The first data acquisition request carries the first access token and the data granularity information; The first device authenticates the second device based on the first access token of the second device, including: The first device verifies whether the first access token contains the data granularity information.

14. The method according to claim 11, wherein, The first data acquisition request carries the authentication information of the fourth device; The first device verifies the fourth device based on the authentication information of the fourth device, including: The first device verifies the fourth device based on at least one of the fourth device's identification information, validity period, and required data in the fourth device's authentication information.

15. The method according to claim 11, wherein, The first data acquisition request carries device information of the fourth device; the first device verifies at least one of the second device and the fourth device based on the second network function instance list, including: The first device verifies whether the second network function instance list contains the device information of the fourth device.

16. A data acquisition method, wherein, The method includes: The second device sends a first data acquisition request to the first device; the first data acquisition request is used to request data acquisition.

17. The method according to claim 16, wherein, The method further includes: The second device receives a first response message from the first device; The first response message carries at least one of the following: First data identification information, the data identification information being used to indicate the topic corresponding to the data requested by the second device; First storage identification information, wherein the storage identifier is used to indicate the dataset corresponding to the data requested by the second device; Device identification information, which is used to indicate the data storage device storing the data requested by the second device.

18. The method according to claim 16, wherein, The first data acquisition request carries at least one of the following: The first access token of the second device; A first instruction, the first instruction being used to indicate a request to obtain data; Data type information, which indicates the type of data requested; Time information, which is used to indicate the time range corresponding to the requested data; Regional information, which is used to indicate the regional range corresponding to the requested data; Data granularity information, which is used to indicate the granularity of the requested data; The fourth device's certification information; The device information of the fourth device.

19. The method of claim 16, wherein, The method further includes: The second device sends a token acquisition request to the third device; the token acquisition request is used to request access token information. The second device receives a first access token or a second access token from the third device; 20. The method according to claim 19, wherein, The method further includes: The second device sends a second data acquisition request to the data storage device; the second data acquisition request is used to request data acquisition.

21. The method according to claim 20, wherein, The second data retrieval request includes at least one of the following: The device identification information of the second device; The first data identification information; The first access token; The second access token.

22. The method according to claim 19, wherein, The token acquisition request carries at least one of the following: Device information of the second device; Target device information; Equipment information for the fourth device; Expected service information; Expected data type information Expected data granularity information.

23. The method according to claim 22, wherein, The service information indicates a data acquisition service; the token acquisition request also carries at least one of the following: Data granularity information, which is used to indicate the granularity of the requested data; Data type information, which indicates the type of data requested; Time information, which is used to indicate the time range corresponding to the requested data; Regional information, which is used to indicate the regional range corresponding to the requested data.

24. An information transmission method, wherein, Applied to a third device, the method includes: The third device receives a token acquisition request from the second device, the token acquisition request being used to request access token information; The third device verifies the token acquisition request; The third device sends a first access token or a second access token to the second device.

25. The method according to claim 24, wherein, The token acquisition request includes at least one of the following: Device information of the second device; Target device information; Equipment information for the fourth device; Expected service information; Expected data type information Expected data granularity information.

26. The method according to claim 24 or 25, wherein, The token acquisition request includes the device information of the second device and the expected data type information; The third device verifies the token acquisition request, including: The third device verifies, based on the device information of the second device, whether the second device has the permission to obtain the data corresponding to the expected data type information.

27. The method according to claim 24 or 25, wherein, The token acquisition request includes the device information of the second device and the desired data granularity information; The third device verifies the token acquisition request, including: The third device verifies, based on the device information of the second device, whether the second device has the permission to obtain the data corresponding to the desired data granularity information.

28. The method according to claim 24 or 25, wherein, The token acquisition request includes device information of the second device and device information of the fourth device; The third device verifies the token acquisition request, including: The third device verifies whether the second device has the authority to obtain authorization for the fourth device based on the device information of the second device and the device information of the fourth device.

29. The method according to claim 24, wherein, The first access token or the second access token includes at least one of the following: Device information of the second device; Target device information; Equipment information for the fourth device; Expected service information; Expected data type information; Expected data granularity information.

30. An information transmission method, wherein, The method includes: The third device receives a search request message from the second device; the search request message is used to request the search of the first device. The third device determines at least one first device based on the search request message; The third device sends feedback information to the second device; the feedback information includes information about at least one first device. The search request message includes at least one of the following: First indication information, the first indication information being used to indicate the location of a first device with data collection capabilities; The second instruction information is used to instruct the search for a first device with passive data collection capabilities; The third instruction information is used to indicate the search for a first device with data openness capabilities; The fourth instruction information is used to instruct the search for a first device that supports the data open service.

31. The method according to claim 30, wherein, The method further includes: The third device receives a registration request message from at least one first device; The registration request message includes at least one of the following: The fifth indication information is used to indicate that the first device has data collection capabilities; The sixth indication information is used to indicate that the first device has passive data collection capability; The seventh indication information is used to indicate that the first device has data openness capability; The eighth indication information is used to indicate that the first device supports data open services.

32. An information transmission method, wherein, include: The first device sends a registration request message to the third device; The registration request message includes at least one of the following: The fifth indication information is used to indicate that the first device has data collection capabilities; The sixth indication information is used to indicate that the first device has passive data collection capability; The seventh indication information is used to indicate that the first device has data openness capability; The eighth indication information is used to indicate that the first device supports data open services.

33. An information transmission method, wherein, include: The second device sends a search request message to the third device; The search request message is used to request the search for the first device; The second device receives feedback information from the third device; the feedback information includes information from at least one first device. The search request message includes at least one of the following: First indication information, the first indication information being used to indicate the location of a first device with data collection capabilities; The second instruction information is used to instruct the search for a first device with passive data collection capabilities; The third instruction information is used to indicate the search for a first device with data openness capabilities; The fourth instruction information is used to instruct the search for a first device that supports the data open service.

34. A data acquisition device, wherein, Applied to a first device, the device includes: The first data acquisition request receiving module is used to receive a first data acquisition request from the second device; the first data acquisition request is used to request data acquisition. The first response message sending module is used to send a first response message to the second device or the fourth device; The first response message carries at least one of the following: First data identification information, which is used to indicate the tag corresponding to the data requested by the second device or the fourth device; First storage identification information, which is used to indicate the dataset corresponding to the data requested by the second device or the fourth device; Device identification information, which is used to indicate the data storage device corresponding to the data requested by the second device or the fourth device.

35. The apparatus according to claim 34, wherein, The first data acquisition request carries at least one of the following: The first access token of the second device; A first instruction, the first instruction being used to indicate a request to obtain data; Data type information, which indicates the type of data requested; Time information, which is used to indicate the time range corresponding to the requested data; Regional information, which is used to indicate the regional range corresponding to the requested data; Data granularity information, which is used to indicate the granularity of the requested data; The authentication information of the fourth device; The device information of the fourth device.

36. A data acquisition device, wherein, Applied to a second device, the device includes: The first data acquisition request sending module is used to send a first data acquisition request to the first device; the first data acquisition request is used to request data acquisition.

37. The apparatus according to claim 36, wherein, The device further includes: The first response message receiving module is used to receive a first response message from the first device; The first response message carries at least one of the following: First data identification information, the data identification information being used to indicate the topic corresponding to the data requested by the second device; First storage identification information, wherein the storage identifier is used to indicate the dataset corresponding to the data requested by the second device; Device identification information, which is used to indicate the data storage device storing the data requested by the second device.

38. An information transmission device, wherein, Applied to a third device, the device includes: The token acquisition request verification module is used to receive a token acquisition request from the second device, wherein the token acquisition request is used to request access token information. The token acquisition request verification module is used to verify the token acquisition request; The access token sending module is used to send a first access token or a second access token to the second device.

39. An information transmission device, wherein, Applied to a third device, the device includes: The search request message receiving module is used to receive search request messages from the second device; the search request message is used to request the search of the first device. The determining module is configured to determine at least one first device based on the search request message; A feedback information sending module is used to send feedback information to the second device; the feedback information includes information about at least one first device; The search request message includes at least one of the following: First indication information, the first indication information being used to indicate the location of a first device with data collection capabilities; The second instruction information is used to instruct the search for a first device with passive data collection capabilities; The third instruction information is used to indicate the search for a first device with data openness capabilities; The fourth instruction information is used to instruct the search for a first device that supports the data open service.

40. The apparatus according to claim 39, wherein, The device further includes: The registration request message receiving module is used to receive registration request messages from at least one first device; The registration request message includes at least one of the following: The fifth indication information is used to indicate that the first device has data collection capabilities; The sixth indication information is used to indicate that the first device has passive data collection capability; The seventh indication information is used to indicate that the first device has data openness capability; The eighth indication information is used to indicate that the first device supports data open services.

41. An information transmission device, wherein, Applied to a first device, the device includes: The registration request message sending module is used to send registration request messages to third-party devices; The registration request message includes at least one of the following: The fifth indication information is used to indicate that the first device has data collection capabilities; The sixth indication information is used to indicate that the first device has passive data collection capability; The seventh indication information is used to indicate that the first device has data openness capability; The eighth indication information is used to indicate that the first device supports data open services.

42. An information transmission device, wherein, Applied to a second device, the device includes: The lookup request message sending module is used to send a lookup request message to a third device; the lookup request message is used to request the lookup of the first device; A feedback information receiving module is used to receive feedback information from the third device; the feedback information includes information from at least one first device. The search request message includes at least one of the following: First indication information, the first indication information being used to indicate the location of a first device with data collection capabilities; The second instruction information is used to instruct the search for a first device with passive data collection capabilities; The third instruction information is used to indicate the search for a first device with data openness capabilities; The fourth instruction information is used to instruct the search for a first device that supports the data open service.

43. A terminal device, wherein, It includes a processor and a memory, the memory storing a program or instructions that can run on the processor, the program or instructions being executed by the processor to implement the steps of the data acquisition method as described in any one of claims 1 to 15 or 16 to 23, or to implement the steps of the information transmission method as described in claim 32 or 33.

44. A network-side device, wherein, It includes a processor and a memory, the memory storing a program or instructions that can run on the processor, the program or instructions being executed by the processor to implement the steps of the data acquisition method as described in any one of claims 1 to 15 or 16 to 23, or to implement the steps of the information transmission method as described in any one of claims 24 to 31.

45. A readable storage medium, wherein, The readable storage medium stores a program or instructions that, when executed by a processor, implement the steps of the data acquisition method as described in any one of claims 1 to 15 or 16 to 23, or the steps of the information transmission method as described in any one of claims 24 to 33.

Images