Wireless communication method and communication device

Abstract

Provided are a wireless communication method and a communication device. The method comprises: a first device sends a first message to a data plane device, wherein the first message comprises first data of the first device, and the data plane device is used for sending the first data to a second device. The data plane device can realize data interaction between the first device and the second device. For example, when the first device comprises a terminal device, the data plane device can send the first data of the terminal device to the second device. The second device can perform operations such as data analysis on the basis of the received first data, thereby improving the performance of a communication system.

Description

Wireless communication methods and communication devices Technical Field

[0001] This application relates to the field of communication technology, and more specifically, to a wireless communication method and a communication device. Background Technology

[0002] With the development of technology, communication systems have an increasing demand for data. Data analysis and other operations can be performed based on this data. However, practical experience in the intelligentization of communication system networks shows that data acquisition is extremely difficult.

[0003] Summary of the Invention

[0004] This application provides a wireless communication method and a communication device. The various aspects covered by this application are described below.

[0005] In a first aspect, a wireless communication method is provided, the method comprising: a first device sending a first message to a data plane device; wherein the first message includes first data of the first device, and the data plane device is used to send the first data to a second device.

[0006] In a second aspect, a wireless communication method is provided, the method comprising: a data plane device receiving a first message sent by a first device; wherein the first message includes first data of the first device, and the data plane device is used to send the first data to a second device.

[0007] Thirdly, a wireless communication method is provided, the method comprising: a second device receiving first data sent by a data plane device; wherein the first data belongs to a first device, and the data plane device is used to acquire the first data.

[0008] Fourthly, a communication device is provided, which is a first device. The communication device includes: a first transmitting unit, configured to transmit a first message to a data plane device; wherein the first message includes first data of the first device, and the data plane device is configured to transmit the first data to a second device.

[0009] Fifthly, a communication device is provided, which is a data plane device. The communication device includes: a first receiving unit for receiving a first message sent by a first device; wherein the first message includes first data of the first device, and the data plane device is used to send the first data to a second device.

[0010] In a sixth aspect, a communication device is provided, which is a second device, comprising: a second receiving unit for receiving first data sent by a data plane device; wherein the first data belongs to the first device, and the data plane device is used to acquire the first data.

[0011] A seventh aspect provides a communication device including a transceiver, a processor, and a memory, the memory for storing one or more computer programs, the processor for invoking the computer programs in the memory to cause the communication device to perform some or all of the steps of the methods of the first aspect, the second aspect, or the third aspect.

[0012] Eighthly, embodiments of this application provide a communication system including the aforementioned communication device. In another possible design, the system may further include other devices that interact with the communication device as described in the embodiments of this application.

[0013] Ninthly, embodiments of this application provide a computer-readable storage medium storing a computer program that causes a communication device to perform some or all of the steps in the methods described above.

[0014] In a tenth aspect, embodiments of this application provide a computer program product, wherein the computer program product includes a non-transitory computer-readable storage medium storing a computer program operable to cause a communication device to perform some or all of the steps of the methods described in the foregoing aspects. In some implementations, the computer program product may be a software installation package.

[0015] In one aspect, embodiments of this application provide a chip including a memory and a processor, the processor being able to call and run a computer program from the memory to implement some or all of the steps described in the methods of the foregoing aspects.

[0016] Data plane devices enable data interaction between a first device and a second device. For example, if the first device includes a terminal device, the data plane device can send the terminal device's first data to the second device. The second device can then perform operations such as data analysis based on the received first data, thereby improving the performance of the communication system. Attached Figure Description

[0017] Figure 1 is a schematic diagram of the wireless communication system used in the embodiments of this application.

[0018] Figure 2 is a schematic diagram of a network architecture.

[0019] Figure 3 is a schematic diagram of a network architecture provided in an embodiment of this application.

[0020] Figure 4 is a schematic flowchart of a wireless communication method provided in an embodiment of this application.

[0021] Figure 5 is a schematic flowchart of a wireless communication method provided in Embodiment 1 of this application.

[0022] Figure 6 is a schematic flowchart of a wireless communication method provided in Embodiment 2 of this application.

[0023] Figure 7 is a schematic structural diagram of a communication device provided in an embodiment of this application.

[0024] Figure 8 is a schematic structural diagram of another communication device provided in an embodiment of this application.

[0025] Figure 9 is a schematic structural diagram of another communication device provided in an embodiment of this application.

[0026] Figure 10 is a schematic structural diagram of a communication device provided in an embodiment of this application. Detailed Implementation

[0027] The technical solutions in this application will now be described with reference to the accompanying drawings.

[0028] Communication system

[0029] Figure 1 illustrates a wireless communication system 100 according to an embodiment of this application. The wireless communication system 100 may include communication devices. These communication devices may include a network device 110 and a terminal device 120. The network device 110 may be a device that communicates with the terminal device 120.

[0030] Figure 1 illustrates an exemplary network device and two terminals. Optionally, the wireless communication system 100 may include multiple network devices, and each network device may include other terminal devices within its coverage area. This application embodiment does not limit this.

[0031] Optionally, the wireless communication system 100 may also include other network entities such as a network controller and a mobility management entity, which is not limited in this embodiment.

[0032] It should be understood that the technical solutions of the embodiments of this application can be applied to various communication systems, such as: 5th generation (5G) systems or new radio (NR), long term evolution (LTE) systems, LTE frequency division duplex (FDD) systems, LTE time division duplex (TDD) systems, etc. The technical solutions provided in this application can also be applied to future communication systems, such as 6th generation mobile communication systems, satellite communication systems, and so on.

[0033] The terminal device in this application embodiment can also be referred to as user equipment (UE), access terminal, user unit, user station, mobile station, mobile station (MS), mobile terminal (MT), remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent, or user device. The terminal device in this application embodiment can be a device that provides voice and / or data connectivity to a user, and can be used to connect people, objects, and machines, such as a handheld device with wireless connectivity, vehicle-mounted device, etc. The terminal device in the embodiments of this application can be a mobile phone, tablet computer, laptop computer, PDA, mobile internet device (MID), wearable device, virtual reality (VR) device, augmented reality (AR) device, wireless terminal in industrial control, wireless terminal in self-driving, wireless terminal in remote medical surgery, wireless terminal in smart grid, wireless terminal in transportation safety, wireless terminal in smart city, wireless terminal in smart home, etc. Optionally, the UE can be used to act as a base station. For example, the UE can act as a scheduling entity, providing sidelink signals between UEs in vehicle-to-everything (V2X) or device-to-device (D2D) communication. For example, cellular phones and cars communicate with each other using sidelink signals. Cellular phones and smart home devices communicate without relaying communication signals through a base station.

[0034] The network device in this application embodiment can be a device for communicating with terminal devices. The network device may also include an access network device. The access network device can provide communication coverage for a specific geographical area and can communicate with the terminal device 120 located within that coverage area. The access network device can also be called a wireless access network device or a base station, etc. In this application embodiment, the access network device can refer to a radio access network (RAN) node (or device) that connects the terminal device to the wireless network. Access network equipment can broadly encompass various names listed below, or be interchangeable with them, such as: NodeB, evolved NodeB (eNB), next-generation NodeB (gNB), relay station, transmitting and receiving point (TRP), transmitting point (TP), master eNB (MeNB), secondary eNB (SeNB), multi-standard radio (MSR) node, home base station, network controller, access node, wireless node, access point (AP), transmission node, transceiver node, baseband unit (BBU), remote radio unit (RRU), active antenna unit (AAU), remote radio head (RRH), central unit (CU), distributed unit (DU), positioning node, etc. Base stations can be macro base stations, micro base stations, relay nodes, donor nodes, or similar entities, or combinations thereof. A base station can also refer to a communication module, modem, or chip installed within the aforementioned equipment or apparatus. A base station can also be a mobile switching center, a device that performs base station functions in D2D, V2X, and machine-to-machine (M2M) communications, a network-side device in a 6G network, or a device that performs base station functions in future communication systems. A base station can support networks using the same or different access technologies. The embodiments of this application do not limit the specific technologies or device forms used in the access network equipment.

[0035] Base stations can be fixed or mobile. For example, a helicopter or drone can be configured to act as a mobile base station, and one or more cells can move depending on the location of the mobile base station. In other examples, a helicopter or drone can be configured as a device to communicate with another base station.

[0036] Wireless communication systems involve communication equipment that can include not only access network equipment and terminal equipment, but also core network elements. Core network elements can be implemented through devices; that is, core network elements are core network devices. It can be understood that core network devices can also be a type of network device.

[0037] The core network elements in this embodiment may include network elements that process and forward user signaling and data. For example, core network equipment may include core access and mobility management functions (AMF), session management functions (SMF), user plane gateways, location management functions (LMF), and other core network equipment. The user plane gateway may be a server with functions such as mobility management, routing, and forwarding of user plane data, generally located on the network side, such as a serving gateway (SGW), packet data network gateway (PGW), or user plane function (UPF). Of course, the core network may also include other network elements, which are not listed here.

[0038] In some deployments, the network device in this application embodiment may refer to a CU or a DU, or the network device may include both a CU and a DU. The gNB may also include an AAU.

[0039] Network devices and terminal devices can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; and they can also be deployed in the air on airplanes, balloons, and satellites. This application does not limit the scenario in which the network devices and terminal devices are located.

[0040] It should be understood that all or part of the functions of the communication device in this application can also be implemented by software functions running on hardware, or by virtualization functions instantiated on a platform (e.g., a cloud platform).

[0041] Mobile network system architecture

[0042] Figure 2 is a schematic diagram of a network architecture. This network architecture may include terminal devices, access network (AN) elements, and core network elements.

[0043] The core network elements can be categorized into several types, including user plane function (UPF) elements, access and mobility management function (AMF) elements, session management function (SMF) elements, policy control function (PCF) elements, application function (AF) elements, data network (DN) elements, network slice selection function (NSSF) elements, authentication server function (AUSF) elements, unified data management (UDM) elements, network exposure function (NEF) elements, network repository function (NRF) elements, and network slice-specific authentication and authorization function (NSSAAF). Among these, UPF elements are primarily responsible for user data transmission. The other elements, which can be referred to as control plane function elements, are mainly responsible for authentication, authorization, registration management, session management, mobility management, and policy control to ensure reliable and stable user data transmission.

[0044] UPF network elements can be used to forward and receive data from terminals. For example, a UPF network element can receive service data from the data network and transmit it to the terminal through access network equipment; a UPF network element can also receive user data from the terminal through access network equipment and forward it to the data network. The transmission resources allocated and scheduled by the UPF network element for the terminal are managed and controlled by the SMF network element. The bearer between the terminal and the UPF network element can include: the user plane connection between the UPF network element and the access network equipment, and the establishment of a channel between the access network equipment and the terminal. The user plane connection is where a QoS flow (transmission flow) for data transmission can be established between the UPF network element and the access network equipment.

[0045] AMF network elements can be used to manage terminal access to the core network, such as terminal location updates, network registration, access control, terminal mobility management, and terminal attachment and detachment. When providing services for a terminal's session, AMF network elements can also provide control plane storage resources for that session to store session identifiers and the associated SMF network element identifiers.

[0046] SMF network elements can be used to select user plane network elements for terminals, redirect user plane network elements for terminals, assign Internet Protocol (IP) addresses to terminals, establish bearers (also known as sessions) between terminals and UPF network elements, modify and release sessions, and perform QoS control.

[0047] PCF network elements are used to provide policies to AMF and SMF network elements, such as QoS policies and slice selection policies.

[0048] AF network elements are used to interact with 3GPP core network elements to support the routing of application-affected data, access network exposure functions, and interact with PCF network elements for policy control, etc.

[0049] A Data Network (DN) can provide data services to users for networks such as IP Multimedia Service (IMS) and the Internet. A DN can contain various application servers (AS) that provide different application services, such as carrier services, Internet access, or third-party services. The AS can implement the functions of an Application Server (AF).

[0050] NSSF is used for network slice selection and supports the following functions: selecting the set of network slice instances to serve the UE; determining allowed Network Slice Selection Assistance Information (NSSAI), and, when necessary, determining the mapping to the subscribed Single-Network Slice Selection Assistance Information (S-NSSAI); determining the configured NSSAI, and, when necessary, determining the mapping to the subscribed S-NSSAI; determining the set of AMFs that may be used to query the UE, or determining a list of candidate AMFs based on configuration.

[0051] AUSF is used to receive AMF requests for terminal authentication. It requests a key from UDM and then forwards the issued key to AMF for authentication processing.

[0052] UDM includes functions such as generating and storing user subscription data and managing authentication data, and supports interaction with external third-party servers.

[0053] NEF is used for capability exposure, meaning that based on NEF, network capabilities can be exported to external networks. Untrusted external applications can access core network data through NEF to ensure network security. NEF can provide functions such as QoS capability exposure for external applications, event subscription, and AF request distribution.

[0054] The Network Request Forwarder (NRF) is used for the registration, management, and status detection of core network elements, thereby achieving automated management of core network elements. When a core network element starts up, it must register with the NRF before it can provide services. Registration information may include, for example, the type, address, and service list of the core network element.

[0055] It should be noted that in some communication systems (such as 5G systems), core network elements can also be called network functions (NFs).

[0056] With the development of technology, the functions of network elements have become more diversified.

[0057] For example, some communication protocols or proposals (such as 3GPP Rel-18 and 3GPP TS23.288) define network elements such as the network data analytics function (NWDAF), data collection coordination function (DCCF), and analytics data repository function (ADRF). Based on NWDAF, devices can collect data from various network elements in the core network and network management systems, and perform big data statistics, analysis, or intelligent data analysis to obtain network-side analysis or predictive data. This, in turn, assists various network elements in more effectively controlling terminal device access based on the data analysis results.

[0058] For example, some communication protocols or proposals (such as 3GPP TS28.104, TS28.537, and TS28.622) define data service capabilities and manage data analytics frameworks, including the management data analytics function (MDAF). This focuses on collecting data and providing data analytics reports to data consumers.

[0059] However, the architecture of communication systems still needs improvement. For example, the DCCF and ADRF mentioned above are specifically designed for collecting data from network elements (NFs) within the communication system. As the 3GPP mobile network architecture evolves to become more data- and content-centric, it requires more flexible and distributed capabilities across the cloud, edge, and core to support local artificial intelligence (AI) and sensing services. The aforementioned network elements are insufficient to support this demand.

[0060] To address the aforementioned issues, this application proposes a technical solution based on data plane (DP) services.

[0061] Data plane services can be implemented through data plane network elements. Data plane network elements can be used for one or more of the following functions: data collection, data storage, data access, data sharing, data tracking, and data openness. For example, a data plane network element can collect and / or store data from a data source. It can also send data from a data source to a data consumer. Furthermore, it can share data from a data source with a data consumer. It can control data consumer access to data from a data source. Finally, it can store data from a data source.

[0062] To make it easier to understand, we will first explain the data source and the data consumer.

[0063] A data source can provide data. A data source can be any mobile communication system entity. For example, a data source may include one or more of the following: terminal equipment, core network elements, RAN, OAM, third-party servers, etc.

[0064] Data from a data source can refer to data generated, perceived, or acquired by the data source. It's important to note that the data itself can also be called metadata. For example, data from a data source can be referred to as the metadata of the data source.

[0065] Data consumers can access and / or use data from data sources. Data consumers can be any mobile communication system entity. For example, data consumers may include one or more of the following: terminal equipment, RAN, OAM, third-party servers, etc.

[0066] Both the provision of data by a data source and the acquisition of data by a data consumer can be termed a data transaction. This application proposes that data transactions can be implemented through data plane network elements.

[0067] It should be noted that "data plane" is just an example name. "Data plane" can also be called "data surface", "user data plane", "distributed data plane", etc.

[0068] The following provides an example of a data plane network element.

[0069] In some embodiments, a data plane network element may include a data plane control network element or a data plane access controller (DPAC). The data plane control network element or DPAC may perform one or more of the following functions: data collection, management of data sources and / or data consumers, authentication of data sources and / or data consumers, data processing, data sharing, interaction with data plane storage network elements, data tracking, etc.

[0070] For example, the data transactions described above can be implemented through a DPAC. For instance, a data transaction may include one or more of the following: a data service between a data source or data consumer and a DPAC. Data services may include, for example, data storage and / or data retrieval.

[0071] Alternatively, DPAC can be a newly defined network element. Alternatively, DPAC can be obtained by enhancing the functionality of network elements in related technologies. For example, DPAC can be obtained by enhancing the DCCF.

[0072] It should be noted that DPAC is merely an example name for this network element, which can also be referred to by other names. For example, this network element can be called a data plane management network element, a data plane interface, a data plane control network element, etc.

[0073] In some embodiments, a data plane network element may include a data plane storage network element. The data plane storage network element can be used to store data from a data source.

[0074] This application does not limit the name of the data plane storage network element. For example, the data plane storage network element can also be called a data plane repository function (DPRF), data storage function, database function, distributed data plane storage function, distributed data storage function, etc.

[0075] Optionally, the data plane can be a distributed architecture. Data sources or data consumers can choose to connect to a data plane that is closest to them. For example, the data plane storage network elements can be distributed, meaning they can be implemented using distributed devices. For instance, the data plane storage network elements can be implemented using blockchain technology.

[0076] Figure 3 is a schematic diagram of a mobile communication system architecture supporting data plane services provided in an embodiment of this application.

[0077] As shown in Figure 3, data plane network elements can include DPAC and DPRF.

[0078] The data plane service offers two possible options for communicating with the terminal device: Option 1 and Option 2. Option 1 communicates via NAS signaling. Option 2 communicates via a service-based interface (SBI) signaling.

[0079] It should be noted that the network elements in Figure 3 can be network components in hardware devices, software functions running on dedicated hardware, or virtualization functions instantiated on a platform (e.g., a cloud platform). It should also be noted that the network architecture shown in Figure 3 is merely an illustrative representation of the network elements included in the overall network architecture. The embodiments of this application do not limit the network elements included in the entire network architecture.

[0080] Those skilled in the art will understand that the network architecture shown in Figure 3 does not constitute a limitation on the network architecture. In specific implementations, the network architecture may include more or fewer network elements than shown in Figure 3, or combine certain network elements, etc. In addition, it should be understood that AN or RAN is represented in Figure 3 as (R)AN.

[0081] Data plane network elements can be used not only to perform operations related to core network data, but also to perform data-related operations of communication devices such as terminal devices. Therefore, compared with related technologies, this application can realize more flexible and dedicated data plane functions to collect data from devices such as terminal devices. The collected data can be used for next-generation AI / ML and sensing operations, thereby improving the performance of the entire communication system.

[0082] Figure 4 is a schematic flowchart of a wireless communication method provided in an embodiment of this application. The method shown in Figure 4 can be executed by a first device, a second device, and a data plane device.

[0083] The method shown in Figure 4 may include step S410.

[0084] In step S410, the first device may send a first message to the data plane device. The first message may include first data from the first device. In other words, the data plane device can be used to acquire the first data.

[0085] The first data can be data generated, sensed, or acquired by the first device. As mentioned above, the data itself can be called metadata; therefore, the first data can also be called the first metadata.

[0086] This application does not limit the type of the first data. For example, the first data may include one or more of the following: service data, user data, network data, perceived data, external data, etc. User data may include, for example, the power consumption status of the terminal device, the quality of service (QoS) performance of the terminal device, etc.

[0087] The method shown in Figure 4 may also include step S420.

[0088] In step S420, the data plane device can send the first data to the second device. In other words, the data plane device can be used to send the first data to the second device.

[0089] As can be seen from the method shown in Figure 4, the first device may include the data source described above. The second device may include the data consumer described above. The data plane device may include the data plane network elements described above. For example, the data plane device may include a DPAC.

[0090] Understandably, data plane devices enable data interaction between a first device and a second device. For example, if the first device includes a terminal device, the data plane device can send the terminal device's first data to the second device. The second device can then perform operations such as data analysis based on the received first data, thereby improving the performance of the communication system.

[0091] In some embodiments, the first message may be a request sent by the data source to the data plane. For example, the request may include one or more of the following: a metadata transaction creation request sent by the data source to DPAC (e.g., it may be called DPAC_MetaTrans_Create_Request), and a metadata transaction update request sent by the data source to DPAC (e.g., it may be called DPAC_MetaTrans_Update_Request).

[0092] The first data in the first message can be encrypted by the first device. Alternatively, the first device may not encrypt the first data. Whether or not to encrypt the first data can be determined based on the privacy control methods described later.

[0093] Alternatively, if the first data is encrypted, the first device can encrypt the first data using the public key of the second device. The public key of the second device can be authorized by the data plane device. Therefore, only data consumers authorized by the data plane device can decrypt the encrypted first data to extract the data content.

[0094] In some embodiments, the first message may include first auxiliary information. The first auxiliary information may be related to the first data.

[0095] The first auxiliary information can be used to indicate any information related to the first data. For example, the first auxiliary information can indicate the characteristics of the first data. Exemplarily, the first auxiliary information may include one or more of the following: information related to the data source (i.e., the first device) of the first data, information related to the data consumer of the first data, information related to access control of the first data, and information related to the acquisition of the first data.

[0096] Understandably, based on the first auxiliary information, the data plane device can process the first data accordingly, so that the storage, access, and sharing of the first data meet the requirements.

[0097] For example, the first auxiliary information may indicate one or more of the following: the domain to which the first device belongs, the identification information of the first device, the anonymity information, the first service operation information, the first parameter, the first information, the first time window information, the privacy control information, the first type information, the first identification information, the valid information, the first indication information, etc.

[0098] The domain to which the communication device belongs can be any of the following: terminal device domain, OAM domain, RAN domain, third-party server domain, etc. Based on this, the first auxiliary information can indicate that the domain to which the first device belongs is a terminal device domain, OAM domain, RAN domain, or third-party server domain, etc.

[0099] Since the first device is the data source of the first data, the "domain to which the first device belongs" can also be called the "domain to which the data source belongs".

[0100] The identification information of the first device can be used to indicate the identity of the first device. The identification of a communication device can be used to distinguish that communication device from other communication devices. For example, the identification of a communication device can be unique within the communication system, or the identification of the communication device can be unique within the group to which the communication device belongs. The identification of a communication device can include one or more of the following: an identification specific to the communication device, or an identification of the group to which the communication device belongs. Therefore, the identification of the first device can include one or more of the following: an identification specific to the first device, or an identification of the group to which the first device belongs.

[0101] When the first device includes a terminal device, the identifier specific to the first device may include identifiers defined in the related art and / or newly defined identifiers. Identifiers defined in the related art may, for example, include a generic public subscription identifier (GPSI). Newly defined identifiers may, for example, be a 3GPP pseudo identity.

[0102] Considering that the first device is the data source of the first data, the "identification information of the first device" can also be called the "identification information of the data source".

[0103] Anonymous information can be used to indicate whether to disclose that the first data belongs to the first device. In other words, anonymous information can be used to indicate whether to disclose the data source of the first data. If the data source of the first data is disclosed, the data consumer (e.g., the second device) can know that the data source of the first data is the first device. If the data source of the first data is not disclosed, the data consumer cannot know that the data source of the first data is the first device.

[0104] For example, if the anonymous information indicates "yes (Y)", the identifier of the data source for the first data cannot be disclosed to the data consumer. If the anonymous information indicates "no (N)", the identifier of the data source for the first data can be disclosed to the data consumer.

[0105] It is understandable that when the data plane device provides the first data to the second data device, the data plane device can control whether to disclose the data source of the first data to the second device based on the anonymity information, thereby ensuring the privacy of the first data.

[0106] For example, if the anonymous information indicates Y, then if the second device specifies that it wants to obtain data from the first device, the data consumer's request for that data will be rejected. In other words, if the second device does not specify the first device as the data source, it may be able to obtain the first data; however, if it specifies the first device as the data source, it will be difficult to obtain the first data.

[0107] Understandably, when a data consumer requests to obtain the first data from the first device, the data plane device can determine whether to send the first data to the second device based on the anonymity information, thereby ensuring that the data source of the first data is not known.

[0108] The first service operation information is used to indicate the first service operation on which the first device obtains the first data.

[0109] Understandably, in a service-based architecture (SBA), data acquisition can be achieved based on service operations. The first service operation information can indicate which service operation the first device used to acquire the first data.

[0110] For example, the first service operation may include Namf_EventExposure_Subscribe or Nnwdaf_AnalyticsSubscription_Subscribe, etc.

[0111] The first parameter can be used to indicate parameters of the first service operation. The first parameter can be used to indicate one or more parameters. The first parameter can indicate some or all of the parameters of the first service operation. For example, the first parameter can indicate one or more of the following: event ID(s) and analytics ID(s) etc.

[0112] It should be noted that the first parameter can also be used as a parameter for one or more service operations. These one or more service operations can be the service operations upon which the acquisition of the first data is based. Therefore, the first parameter can indicate one or more parameters of the same type. For example, the first parameter can indicate one or more event identifiers.

[0113] The first information can be used to indicate whether the first data was actively sent by the first device. "The first data was actively sent by the first device" means that no other device needs to send a request to the first device to request the first data; that is, the first device sends the first data on its own. For example, under certain conditions (such as the third condition described later), the first device can actively send the first data. "The first data was not actively sent by the first device" means that other devices need to send a request to the first device to request the first data to be sent. For example, a data plane device can send a first request to the first device to request the acquisition of the first data.

[0114] First time window information can be used to indicate the time range for collecting initial data. The time range can include one or more of the following: a specific month within a year, a specific period of a specific day, etc.

[0115] Privacy control information can be used to indicate how privacy controls are applied to primary data.

[0116] Privacy control methods may include one or more of the following: no privacy control, first method, second method, and third method.

[0117] Without privacy controls, any device can access the primary data. In other words, the primary data is public. Or, to put it another way, the primary data is transparent to data consumers.

[0118] In the first approach, the first device may delegate the determination of access permissions for the first data to a data plane device. For example, the data plane device may determine the access permissions for the first data based on one or more of the operator's policies, the location and environment of the data consumer, and local data protection regulations.

[0119] It should be noted that in this application, "delegation" can be understood as request, instruction, authorization, etc. For example, "the first device may delegate the data plane device to determine the access rights of the first data" can be understood as: the first device instructs the data plane device to determine the access rights of the first data, or the first device requests the data plane device to determine the access rights of the first data.

[0120] In the first approach, the first device can delegate the determination of access permissions for the first data entirely to the data plane. That is, the first device does not need to restrict access permissions for the first data. Therefore, the first approach can also be called a full delegation of privacy control approach.

[0121] In the second approach, the first device delegates the authority of the data plane device to determine the access rights to the first data within a subset of the devices. For example, the data plane device may determine the access rights to the first data for one or more devices within the subset of devices based on one or more of the operator's policies, the location and environment of the data consumer, and local data protection regulations.

[0122] In the second approach, the first device can partially delegate access permissions for the first data to the data plane. That is, the first device can restrict access to the first data to only a subset of communication devices. The data plane can further determine which communication devices(s) among these have access to the first data. These subset of communication devices can belong to a specific group of data consumers.

[0123] Based on this, the second approach can also be called the partial delegation of privacy control approach.

[0124] In the third approach, the first device needs to obtain information from the second device to determine access rights to the first data. This information may include the second device's authentication information, such as a data plane-assigned digital signature and / or the second device's public key.

[0125] In some embodiments, the third approach may also be referred to as explicit privacy control.

[0126] It should be noted that in the third method, the first device cannot proactively report the first data. That is, the first device can only report the first data after being requested by the second device. This is because if the first device proactively reports the first data, it cannot obtain the verification information of the second data and therefore cannot perform privacy control over the display of the first data.

[0127] It should be noted that, under the first, second, or third method, the first data may or may not be transparent to the data surface.

[0128] The first type information can be used to indicate the type of device capable of using the first data. In other words, the first type information can indicate the type of data consumer capable of accessing the first data. The type of device capable of using the first data may include one or more of the following: any type, terminal equipment, core network NF, RAN functional component, AF, etc.

[0129] Optionally, the first type of information can be used to support privacy control methods.

[0130] The first identification information can be used to indicate the identifier of a device (i.e., a data consumer) capable of using the first data. For example, in the third approach, the first data can only be accessed by the device indicated by the first identification information. It should be noted that there can be one or more devices capable of using the first data. Therefore, the first identification information can indicate the identifier of one or more devices.

[0131] Validity information can be used to indicate the valid time range of the first data. That is, validity information can indicate the validity period of the first data before automatic obsolescence. It should be noted that validity information can indicate when the first data is valid and / or invalid; whether the first data is deleted from the storage device is irrelevant to the validity information. For example, the first data can still be stored in the storage device during its invalid period. Alternatively, the storage device can delete the first data if it is invalid.

[0132] The first indication information can be used to indicate whether it is necessary to notify the first device of a first situation. The first situation can be used to indicate the situation where the second device receives the first data. In other words, the first indication information can be used to indicate whether it is necessary to notify the data source consumer of the situation where data has been received.

[0133] For example, if the first indication information indicates Y, then a notification needs to be sent to the data source whenever the data consumer successfully receives data from the data source. If the first indication information indicates N, then a notification does not need to be sent to the data source when the data consumer successfully receives data from the data source.

[0134] In some embodiments, the first message may include multiple data items and multiple pieces of auxiliary information. The multiple pieces of auxiliary information may correspond one-to-one with the multiple data items. The first piece of auxiliary information may be any one of the multiple pieces of auxiliary information. For example, the first message may include first data and second data, and the first message may also include first auxiliary information and second auxiliary information. The first auxiliary information may be related to the first data, and the second auxiliary information may be related to the second data.

[0135] In some embodiments, the data plane device may send a first request to the first device. The first request may be used to request the acquisition of first data. In response to receiving the first request, the first device may send the first data to the data plane device. That is, the sending of the first data may be based on a solicitation.

[0136] The first request can be sent if the first condition is met. That is, the first request is sent if the first condition is met. In other words, the data plane device can only request the first device to send the first data if the first condition is met.

[0137] Optionally, the first condition may be related to one or more of the following: a second request, or the storage device storing the first data.

[0138] The second request can be sent by the second device to the data plane device. The second request can be used by the second device to request the acquisition of the first data from the first device. For example, the second request can be a data transaction subscription request (e.g., DPAC_MetaTrans_Subscribe_Request) sent by the second device to the data plane. DPAC_MetaTrans_Subscribe_Request can be used to subscribe to or acquire specified data.

[0139] For example, the first condition may include: the second request sent by the second device has been verified. The verification of the second request may include one or more of the following: verification of the identity of the second device, verification of the legality of the second device's access, verification of whether the second device is an authorized data plane member, etc. Verification may be based on one or more of the following: the identifier of the second device, the data plane identifier corresponding to the second device, and the digital signature of the second device.

[0140] In some embodiments, the data plane device may verify the second request. If the second request is successfully verified, the data plane device may send the first request to the first device. If the second request fails to verify, the data plane device will not send the first request to the first device. Optionally, if the second request fails to verify, the data plane device may send a notification of verification failure to the second device. This notification may indicate the reason for the verification failure.

[0141] Optionally, the second request may include one or more of the following: a data plane identifier corresponding to the second device, an identifier of the second device, a digital signature of the second device, a public key of the second device, an association identifier of the second device, second instruction information, and third auxiliary information. The data plane device may verify the second request based on some or all of the above information. The above information will be described in detail later and will not be repeated here.

[0142] The storage device storing the first data may include whether the storage device already stores the first data. The storage device can be a data plane storage device. For example, the storage device may include a Data Plane RF (DPRF). The DPRF may or may not be a data plane device as described above.

[0143] For example, the first condition may include that the storage device does not store the first data. That is, if the storage device does not store the first data, the data plane device may send a first request to request the acquisition of the first data.

[0144] When the first data is stored on the storage device, the data plane device may not send a first request, but instead retrieve the first data from the storage device.

[0145] Optionally, the data plane device may send a third request to the storage device. The third request may be used to request the acquisition of first data from the first device. Sending the third request may satisfy a second condition. The second condition may be related to the storage device storing the first data and / or the second request. For example, the second condition may include that the storage device stores the first data, and / or that the second request has been verified. That is, if the storage device stores the first data, and / or the second request has been verified, the data plane device may send a third request to the storage device.

[0146] In some embodiments, the data plane device may send a second message to the first device. The second message may be used to instruct the data plane device to store the first device in a storage device. It is understood that the second message may be a response to the first message.

[0147] If the first message includes one or more of the following: DPAC_MetaTrans_Create_Request, DPAC_MetaTrans_Update_Request, then the second message may accordingly include: a metadata transaction creation response sent by DPAC to the data source (e.g., which may be referred to as DPAC_MetaTrans_Create_Response) or a metadata transaction update response sent by the data source to DPAC (e.g., which may be referred to as DPAC_MetaTrans_Update_Response).

[0148] Optionally, the data plane device may send the first data to the storage device. If the storage device successfully stores the first data, it may send a first response message to the data plane device. In response to receiving the first response message from the storage device, the data plane device sends a second message to the first device. That is, the data plane device can only send the second message to the first device after receiving the first response message from the storage device.

[0149] In some embodiments, the data plane device may determine its behavior in response to the first message based on whether the storage device stores the first data. For example, if the storage device stores the first data, the data plane device may not respond to or reject the first message. Alternatively, if the storage device stores the first data, the data plane device may not store the first data, thereby avoiding storing duplicate data. Or, if the storage device does not store the first data, the data plane device may send the aforementioned second message to the first device.

[0150] In dynamic environments, data plane devices may collect the same data multiple times. Similarly, the same data may be requested multiple times from different data consumers. In these cases, the data plane may already have copies of the data stored in storage devices. The technical solution proposed in this application, which determines the behavior of a data plane device based on whether the storage device stores the first data, can prevent the processing of duplicate data collection requests to the data source or the response to multiple subscription requests for the same data from different data consumers.

[0151] In some embodiments, whether the storage device stores the first data can be recorded in a data catalogue. The data catalogue can be used to record data stored in the storage device. For example, whether data requested by a second device has already been stored in the storage device can be determined by querying the data catalogue. Similarly, whether data requested by a first device to be sent to a data plane has already been stored in the storage device can be determined by querying the data catalogue.

[0152] Optionally, the data catalog can be maintained by the data plane device. In other words, one or more of the following operations—adding, deleting, modifying, and querying the data catalog—can be performed by the data plane device.

[0153] Optionally, the data directory may include first auxiliary information. If the first auxiliary information exists in the data directory, it can be assumed that the first data is stored in the storage device.

[0154] Optionally, the data catalog may include a timestamp of the first data. The timestamp of the first data can indicate the time when the first device stored the data on the storage device. Information stored in the data catalog can be sorted by timestamp. For example, auxiliary information used to describe the data can be sorted by timestamp. Sorted information makes it easier to query, thereby more quickly determining whether certain data is stored on the storage device.

[0155] In some embodiments, an update to the data catalog can be triggered when the first data is stored on the storage device. That is, the data catalog can be updated in response to the first data being stored on the storage device. Updating the data catalog may, for example, include recording first auxiliary information in the data catalog.

[0156] The first request, the second request, and the third request can all be used to request a data transaction. Therefore, the first request, the second request, and the third request can all be referred to as a data transaction request or a transaction request.

[0157] In some embodiments, the first request, the second request, or the third request may include third auxiliary information, which may be related to the first data. That is, a request to obtain the first data may include third auxiliary information related to the first data.

[0158] It should be noted that when both the first request and the second request include third auxiliary information, the third auxiliary information included in the first request and the third auxiliary information included in the second request may be the same or different. For example, the third auxiliary information included in the first request may be some or all of the information in the third auxiliary information included in the second request.

[0159] It should be noted that when both the third request and the second request include third auxiliary information, the third auxiliary information included in the third request and the third auxiliary information included in the second request may be the same or different. For example, the third auxiliary information included in the third request may be some or all of the information in the third auxiliary information included in the second request.

[0160] The third auxiliary information may include one or more of the following: the domain to which the first device belongs, the identification information of the first device, the second service operation information, the second parameter, the second time window, the second type information, and the second identification information. These will be explained below.

[0161] The second service operation information can be used to indicate the second service operation on which the second device requests the first data. The second service operation information can indicate on which service operation the second device requests the data to be obtained.

[0162] For example, the second service operation may include Namf_EventExposure_Subscribe or Nnwdaf_AnalyticsSubscription_Subscribe, etc.

[0163] The second parameter can be used to indicate parameters of the second service operation. The second parameter can be used to indicate one or more parameters. The second parameter can indicate some or all of the parameters of the second service operation. For example, the second parameter can indicate one or more of the following: event identifier, analysis identifier, etc.

[0164] It should be noted that the second parameter can also be used as a parameter for one or more service operations. These one or more service operations can be the service operations upon which the acquisition of the second data is based. Therefore, the second parameter can indicate one or more parameters of the same type. For example, the second parameter can indicate one or more event identifiers.

[0165] The second time window information can be used to indicate the time range within which the second device requests the collection of the first data. The time range may include one or more of the following: a certain month within a year, a certain period of a certain day, etc.

[0166] The second type of information can be used to indicate the type of the second device. This second type of information can also be called data consumer type information.

[0167] The second identification information can be used to indicate the identifier of the second device. The identifier of the second device may include one or more of the following: an identifier specific to the second device, or an identifier of the group to which the second device belongs. The second identification information may also be referred to as data consumer identification information.

[0168] In some embodiments, one or more of the first auxiliary information, the second auxiliary information, and the third auxiliary information may all be referred to as auxiliary information for the first data. The auxiliary information can be used to indicate any information related to the data. The data can be data corresponding to the auxiliary information. For example, the auxiliary information can indicate the characteristics of the data. Alternatively, the auxiliary information can be used to describe the data. Exemplarily, the auxiliary information may include one or more of the following: information related to the data's data source, information related to the data's data consumer, information related to data access control, and information related to data acquisition. Furthermore, the auxiliary information can be used for verification. Exemplarily, a data plane device can verify whether the data plane can store the data from the data source based on the auxiliary information sent by the data source. Exemplarily, a data plane device can verify whether the data consumer can request the corresponding data based on the auxiliary information sent by the data consumer.

[0169] Auxiliary information can be carried in a metadata profile.

[0170] Metadata configuration files can be standardized data description files. They are used to describe the characteristics of data (such as terminal power consumption status, terminal QoS performance, etc.) provided by a data source to a data consumer when predefined events occur. A data transaction request or response may contain one or more metadata configuration files and their corresponding data.

[0171] Each metadata profile can be associated with a metadata profile template ID (MPTID). The metadata profile template ID can be used to indicate: the metadata profile template, and / or the values ​​of parameters in the metadata profile template.

[0172] Metadata profile templates can be used to indicate what information or parameters are required when defining a metadata profile. The parameters in the metadata profiles may differ for data transaction requests submitted by data sources, data consumers, and data plane devices; therefore, the metadata profile templates may also vary.

[0173] In some embodiments, the metadata configuration file template may include one or more of the following parameters: data source domain, data source identifier(s), data source anonymity, data source service operation, data source service operation specific parameter(s), data source service operation autonomous exposure, data source service operation time window, privacy control options, data consumer type, data consumer identifier(s), data life-time validity, and data access control notification.

[0174] The parameter “data source domain” can be used to indicate the domain described in the first device mentioned above.

[0175] The parameter "Data Source Identifier" can be used to indicate the identification information of the first device mentioned above. The data source identifier may include a unique identifier for the data source, the identifier of the group to which the data source belongs, or any other identifier.

[0176] It should be noted that if a specific terminal device is the data source, the terminal device's GPSI can serve as the identifier of the data source. Alternatively, a newly defined system identifier (such as 3GPP) can serve as the identifier of the data source. Digital signature verification of the terminal device can be used to verify the identity of the terminal device and can also be used to protect system data security.

[0177] The parameter "Data source anonymous" can be used to indicate the anonymity information described above. The value of "data source anonymous" can be Y or N. When the value of "data source anonymous" is Y, it means that the data source identifier is not disclosed to the data consumer. Alternatively, when the value of "data source anonymous" is Y, it means that if the data consumer specifies a particular data source, the data consumer's request for metadata will be rejected.

[0178] The parameter "Data Source Service Operation" can be used to indicate the first service operation information or the second service operation information described above. Data source service operations may include, for example, Namf_EventExposure_Subscribe or Nnwdaf_AnalyticsSubscription_Subscribe.

[0179] The parameter "Specific parameters for data source service operation" can be used to indicate either the first parameter or the second parameter mentioned above. Specific parameters for data source service operation may include one or more of the following: event ID(s), analytics ID(s), etc.

[0180] The parameter "Data Source Service Operation Active Reporting" can be used to indicate the first piece of information described above. The value of "Data Source Service Operation Active Reporting" can be Y or N. A value of Y indicates that when the conditions of a specific service operation parameter of the data source are met, the data source submits its data to the DPRF without any request from the data consumer.

[0181] The parameter "Data Source Service Operation Time Window" can be used to indicate the first time window information or the second time window information mentioned above. If a data source service operation time window is specified, this time window is the time range within which metadata will be collected or has been collected (e.g., a certain period of a certain month or day within a year).

[0182] The parameter "Privacy Control Options" can be used to indicate the privacy control information described above.

[0183] The parameter "Data Consumer Type" can be used to indicate either the first type of information or the second type of information described above. The data consumer type can be any type, such as UE, core network NF, RAN functional component type, AF, etc. The parameter "Data Consumer Type" needs to support the parameter "Privacy Control Options".

[0184] The parameter "Data Consumer Identifier" can be used to indicate either the first identification information or the second identification information described above. If the UE is a data consumer, it can use GPSI or the new 3GPP pseudo-identity. Alternatively, the UE's digital signature verification can be used to verify the UE's identity and protect the UE's confidentiality within the 3GPP system. If the privacy control option is a third method, the data consumer should provide its digital signature and public key in the transaction subscription request for metadata used by the data source to verify the data consumer's identity.

[0185] The parameter "Data validity lifespan" can be used to indicate the valid information described above. The data validity lifespan indicates the period of time metadata remains valid before it is obsolete (i.e., indicating that the metadata is no longer useful and / or valid). However, being no longer valid does not mean that the metadata has been removed from the DPRF.

[0186] The parameter "Data Access Control Notification" can be used to indicate the first indication information described above. The value of Data Access Control Notification can be Y or N. If the value of Data Access Control Notification is Y, then a notification needs to be sent to the data source whenever the data consumer successfully receives metadata from the data source.

[0187] Table 1 is an example of a metadata configuration file template provided in the embodiments of this application.

[0188] Table 1

[0189] It should be noted that some content in Table 1 can be implemented independently. That is, Table 1 can still be implemented even if some content is deleted. Alternatively, Table 1 can also include other content.

[0190] It should be noted that the second request can be used to request multiple data sets. That is, the data consumer can request multiple data sets. If the second device requests multiple data sets, the data plane device can integrate the collected data sets and feed them back to the second device.

[0191] In some embodiments, the second request can be a continuous request to acquire the first data. For example, by sending a single second request, the first data can be acquired multiple times. The content of the multiple first data acquisitions can be different. Furthermore, after the second device sends the second request, if the transaction status (or state) of the first data changes, the second device can receive a corresponding notification (e.g., DSx_MetaTrans_Subscribe_Notify). The change in status can include updates (i.e., modifications), obsolescence (i.e., invalidation), etc.

[0192] In some embodiments, the first request, second request, or third request may include information related to the second device. For example, the information related to the second device may include one or more of the following: a data plane identifier corresponding to the second device, an identifier of the second device, a digital signature of the second device, a public key of the second device, an association identifier of the second device, and second indication information. Based on the above information, the second device can be verified to determine whether to send the first data, thereby achieving trusted access to the data.

[0193] The data plane identifier corresponding to the second device can be obtained through DataConsumer. DPID This indicates that the data plane identifier is used to identify the member identifier assigned when a member registers with the data plane service.

[0194] The identification of the second device can be obtained through DataConsumer. ID This identifier can be used to identify 3GPP entities within the 3GPP system.

[0195] The digital signature of the second device can be represented by DataConsumerDigitalSignature. The public key of the second device can be represented by DataConsumer. PublicKey It indicates that DataConsumerDigitalSignature and DataConsumer PublicKey It can be used to verify the identity of a second device in order to achieve access control over the first data, thereby gaining support for data privacy and trustworthiness.

[0196] The association identifier can be a hash association identifier. The hash association identifier of the second device can be obtained through DataConsumer. hcorrID express.

[0197] The second indication information can be used to indicate whether to notify the second device when the data subscribed to by the second device changes. The second indication information can also be called a persistence indication.

[0198] In some embodiments, the first message may further include information related to the first device. The information related to the first device may include one or more of the following: a data plane identifier corresponding to the first device; an identifier of the first device; a digital signature of the first device; a public key of the first device; and an association identifier of the first device. For related explanations, please refer to the description of information related to the second device above.

[0199] The data plane identifier corresponding to the first device can be obtained through DataSource. DPID express.

[0200] The association identifier of the first device can be obtained through DataSource hcorrID express.

[0201] The identifier of the first device can be obtained through DataSource ID express.

[0202] The digital signature of the first device can be represented by DataSourceDigitalSignature.

[0203] The public key of the first device can be accessed through DataSource. PublicKey express.

[0204] Based on information related to the first device, the data plane device can verify the first device, thereby achieving reliable data storage.

[0205] As mentioned above, a request-based data transaction process can be implemented based on a first request, a second request, or a third request. The following describes a non-request-based data transaction process.

[0206] In some embodiments, a non-requested data transaction process may refer to: a first device actively sending a first message to a data plane device.

[0207] Optionally, if the third condition is met, the first device may proactively send a first message to the data plane device. For example, the third condition may include: the time for reporting the first message has arrived. Exemplarily, the reporting of the first message may be periodic; when the reporting time corresponding to the reporting period arrives, the first device may send the first message. Furthermore, the third condition may be related to a specific service operation and / or specific service operation parameters. Exemplarily, if the specific service and / or specific service operation parameters are met, the first device may send the first message.

[0208] For ease of understanding, this application will be described below through Examples 1 and 2.

[0209] Example 1

[0210] Figure 5 is a schematic flowchart of a wireless communication method provided in Embodiment 1. The method shown in Figure 5 can be implemented by a data source, a data consumer, a DPAC, and a DPRF. The first device may include a data source. The second device may include a data consumer. The data plane device may include a DPAC. The storage device may include a DPRF.

[0211] The method shown in Figure 5 may include step S510.

[0212] In step S510, the data consumer sends a request DPAC_MetaTrans_Subscribe_Request to the DPAC. DPAC_MetaTrans_Subscribe_Request is used to request one or more metadata sources from one or more data sources. The parameters that DPAC_MetaTrans_Subscribe_Request may include are described below.

[0213] 1. Data plane ID of the data consumer (via DataConsumer) DPID (This is represented as an example). Among them, the data plane ID is used to identify the member identifier assigned when a member registers with the data plane service.

[0214] 2. Data Consumer ID (via DataConsumer) ID (This is indicated by the symbol). The ID is used to identify 3GPP entities within the 3GPP system.

[0215] 3. The data consumer's digital signature (represented by DataConsumerDigitalSignature) and the data consumer's public key (represented by DataConsumer). PublicKey (Represented). DataConsumerDigitalSignature and DataConsumer PublicKey Used to verify the identity of data consumers in order to achieve access control over metadata, thereby gaining support for data privacy and trust.

[0216] 4. One or more configuration files. These configuration files are used to define one or more metadata entries for data subscription requests or data storage requests.

[0217] 5. Data Consumer Hash Association Identifier (via DataConsumer) hcorrID (This is used to define specific data transactions initiated by data consumers and DPAC.)

[0218] 6. Persistence Indicator (value can be Y or N). The persistence indicator indicates whether the data consumer wants to continue receiving notifications when the subscribed data status changes.

[0219] The method shown in Figure 5 may also include step S520.

[0220] In step S520, DPAC performs a verification operation.

[0221] DPAC can verify the identity of the data consumer (i.e., DataConsumer). ID ).

[0222] DPAC can verify the legitimacy of data consumer access. For example, DPAC can inspect the DataConsumer. DPID It also verifies the DataConsumerDigitalSignature, specifically verifying whether the data consumer is an authorized registered data surface member.

[0223] DPAC can perform verification operations by referencing metadata configuration files.

[0224] If the verification passes, DPAC can continue to verify the corresponding metadata configuration file based on operator policies and local data protection rules determined by the location / environment of the terminal device.

[0225] If all the above verifications pass, DPAC can check the metadata configuration file based on the metadata catalog to determine whether the requested metadata has already been stored in the data plane.

[0226] If the data plane has already collected the metadata, DPAC can transform the request sent by the data consumer to DPAC into a request to DPRF to retrieve the metadata.

[0227] If the data plane has not yet collected the metadata, DPAC can identify the data source (e.g., via NRF). This data source can then provide metadata corresponding to the metadata profile based on the data consumer's requirements. Once identified, DPAC translates the data consumer's metadata transaction subscription request for itself into a metadata transaction subscription request from DPAC to the data source.

[0228] It should be noted that the same metadata transaction subscription requested by a data consumer may include one or more metadata profiles.

[0229] The method shown in Figure 5 may also include one or more of steps S530, S540, S550, and S560.

[0230] In step S530, if any verification fails in step S520, DPAC will respond to the data consumer with the reason for the failure and the data consumer's... hcorrIDNext, DPAC will terminate the metadata transaction subscription request from the data consumer. There are no further steps after step S530.

[0231] Step S540 may include steps S541, S542 and S543.

[0232] Step S541: If all verifications in step 520 have passed, and the requested metadata configuration file contains stored metadata, then DPAC will use the data consumer's digital signature (DataConsumerDigitalSignature) and the data consumer's public key (DataConsumer...) PublicKey ), DPAC hash association ID (DPAC hCorrID The metadata configuration file sends a DPRF_MetaTrans_Query_Request to the DPRF.

[0233] It should be noted that a single transaction request can contain multiple metadata configuration files.

[0234] Step S542: DPRF processes the DPRF_MetaTrans_Query_Request. Step S542 may involve executing a predefined smart contract on the requested metadata according to a pre-configured strategy. It should be noted that multiple metadata profiles (i.e., requesting multiple metadata) can be included in the same transaction request.

[0235] In step S543, if step S542 was successful, DPRF responds to DPAC with the requested metadata and the status of the metadata catalog. Then, proceed to step S560.

[0236] Step S550 includes steps S551 to S557.

[0237] Step S551: If all verifications in step S520 above have passed, and the requested metadata is not stored on the data plane, then DPAC will identify the data source for the requested metadata profile (the data source could be, for example, UE, RAN, Core NFs, or OAM). DPAC sends a DSx_MetaTrans_Subscribe_Request to the data source. The DSx_MetaTrans_Subscribe_Request includes the data consumer's digital signature (DataConsumerDigitalSignature), data consumer ID (DataConsumerID), and DPAC hash association ID (DPAC...). hCorrID ) and metadata configuration files.

[0238] In steps S552 and S553, the data source processes the DSx_MetaTrans_Subscribe_Request and determines whether the metadata access request can be granted to the data consumer. If verified, the data source can encrypt the metadata using the data consumer's public key. The data source then sends a DSx_MetaTrans_Subscribe_Response to the DPAC. The DSx_MetaTrans_Subscribe_Response includes the following parameters: DataSource DPID DPAC hcorrID DataSource ID DataSourceDigitalSignature and metadata (possibly encrypted using the data consumer's public key).

[0239] Step S554: DPAC verifies DPAC based on the corresponding metadata configuration file. hcorrID and DataSource ID If validation passes, DPAC will convert the data source's response into a parameterized metadata creation request (including DPAC). hcorrID The process involves taking the DataSourceDigitalSignature, DataSourcePublicKey, metadata configuration file, and metadata, and sending a request to the DPRF to store the metadata in the DPRF. This request is the DPRF_MetaTrans_Create_Request in step S555.

[0240] In step S555, DPAC sends DPRF_MetaTrans_Create_Request to DPRF.

[0241] Step S556: DPRF processes metadata transactions. These transactions may involve executing predefined smart contracts on metadata according to pre-set strategies to ensure the integrity of metadata across the entire system. If the metadata integrity is confirmed, the metadata catalog can be updated.

[0242] Step S557: If the operation in step S556 is successful, DPRF will send the data transaction status and data catalog back to DPAC via DPRF_MetaTrans_Create_Response.

[0243] In step S560, DPAC merges and processes all metadata collected in steps S540 and S550.

[0244] In step S570, DPAC sends the corresponding response DPAC_MetaTrans_Subscribe_Response to the data consumer. DPAC_MetaTrans_Subscribe_Response includes: Data_Consumer hcorrID Metadata and transaction status.

[0245] Step S580: If DPAC has previously obtained this metadata from the data source, it responds to the data source by sending a DSx_MetaTrans_Subscribe_Response, which includes DPAC's response. hcorrID And transaction status.

[0246] Example 2

[0247] Figure 6 is a schematic flowchart of a wireless communication method provided in Embodiment 2. The method shown in Figure 6 can be implemented by a data source, a DPAC, and a DPRF. The first device may include a data source. The data plane device may include a DPAC. The storage device may include a DPRF.

[0248] The method shown in Figure 6 may include step S610.

[0249] In step S610, the data source is configured to proactively store its metadata in the data plane once predefined conditions are met. The data source sends a DPAC_MetaTrans_Create / Update Request to the DPAC. The DPAC_MetaTrans_Create / Update Request includes: DataSource DPID DataSourcehcorr ID DataSource ID ,DataSourceDigitalSignature,DataSource PublicKey Metadata configuration files and metadata. The metadata can be encrypted using DPAC's public key.

[0250] Step S620: DPAC performs verification.

[0251] DPAC can verify the identity of the data source (i.e., DataSource). ID ).

[0252] DPAC can verify the legitimacy of data source access. For example, DPAC can inspect the DataSource. DPIDIt also verifies the DataSourceDigitalSignature, which means verifying whether the data source is an authorized registered data surface member.

[0253] DPAC can perform verification operations by referencing metadata configuration files.

[0254] If the verification passes, DPAC can check the metadata configuration file based on the metadata directory to confirm whether the metadata has been stored in DPRF.

[0255] If the metadata is not stored in the DPRF, the DPAC can convert the data source metadata transaction creation or update request into a data surface metadata transaction creation / update request in step S640.

[0256] Step S630 may include steps S631 and S632.

[0257] Step S631: DPAC provides DPAC_MetaTrans_Create / Update Responses. DPAC_MetaTrans_Create / Update Responses may include DataSourcerhcorrID.

[0258] And S632, DPAC provides feedback DPAC_MetaTrans_Response. DPAC_MetaTrans_Response may include DataSourcerhcorrID.

[0259] If any validation fails in step S620, DPAC can respond with possible reasons for rejection from the data source in steps S631 and S632. Rejection reasons may include: unauthorized access to DPAC, violation of data policy, duplicate metadata, or timeout. No further steps will follow.

[0260] Step S640 may include steps S641 to S643.

[0261] In step S641, the DPAC sends a DPRF_MetaTrans_Create / Update_Request to the DPRF. The DPRF_MetaTrans_Create / Update_Request may include information from the DPAC. hcorrID ,DataSourceDigitalSignature,DataSource PublicKey Metadata configuration files, metadata.

[0262] In step S642, DPRF processes metadata according to the smart contracts pre-configured by the metadata configuration file policy, ensuring the integrity of metadata across the entire system. If the metadata is successfully added to DPRF, the metadata catalog can be updated.

[0263] Step S643: If step S642 is successful, DPRF will use DPAC. hcorrID The transaction status and metadata catalog respond to DPAC with the result of the metadata transaction creation / update request (DPRF_MetaTrans_Create / Update Response).

[0264] In steps S650 and S660, DPAC processes DPRF responses related to the creation / update of metadata transactions in DPRF and responds accordingly to data sources related to transaction status.

[0265] The method embodiments of this application have been described in detail above. The apparatus embodiments of this application are described in detail below. It should be understood that the descriptions of the method embodiments correspond to the descriptions of the apparatus embodiments. Therefore, any parts not described in detail can be referred to the foregoing method embodiments.

[0266] Figure 7 is a schematic structural diagram of a communication device 700 provided in an embodiment of this application. The communication device 700 is a first device.

[0267] The communication device 700 includes a first transmitting unit 710.

[0268] The first sending unit 710 is used to send a first message to a data plane device; wherein the first message includes first data of the first device, and the data plane device is used to send the first data to a second device.

[0269] In some embodiments, the first message may further include first auxiliary information, which is related to the first data.

[0270] In some embodiments, the first auxiliary information includes one or more of the following: the domain to which the first device belongs; the identification information of the first device; anonymity information, used to indicate whether to disclose that the first data belongs to the first device; first service operation information, used to indicate the first service operation on which the first device obtains the first data; first parameters, used to indicate the parameters of the first service operation; first information, used to indicate whether the first data was actively sent by the first device; first time window information, used to indicate the time range for collecting the first data; privacy control information, used to indicate the privacy control method for the first data; first type information, used to indicate the type of device that can use the first data; first identification information, used to indicate the identification of the device that can use the first data; validity information, used to indicate the validity time range of the first data; and first indication information, used to indicate whether it is necessary to notify the first device of a first situation, wherein the first situation indicates the situation in which the second device receives the first data.

[0271] In some embodiments, the privacy control method includes one or more of the following: a method without privacy control; a first method, in which the first device delegates the data plane device to determine the access permissions of the first data; a second method, in which the first device delegates the data plane device to determine the access permissions of the first data in some devices; and a third method, in which the first device needs to obtain information from the second device to determine the access permissions of the first data.

[0272] In some embodiments, the first message further includes second data and second auxiliary information, wherein the second auxiliary information is related to the second data.

[0273] In some embodiments, the communication device 700 is further configured to: receive a first request sent by the data plane device, the first request being used to request the acquisition of the first data of the first device.

[0274] In some embodiments, the sending of the first request satisfies a first condition, and the first request is sent when the first condition is satisfied: a second request, for the second device to request to obtain the first data of the first device; and the case where the storage device stores the first data.

[0275] In some embodiments, the first condition includes: the second request sent by the second device is verified successfully; and / or, the storage device does not store the first data.

[0276] In some embodiments, the second request includes third auxiliary information, which is related to the first data.

[0277] In some embodiments, the storage device may store the first data record in a data directory.

[0278] In some embodiments, the update of the data directory is triggered when the first data is stored in the storage device.

[0279] In some embodiments, the first request includes third auxiliary information, which is related to the first data.

[0280] In some embodiments, the third auxiliary information includes one or more of the following: the domain to which the first device belongs; the identification information of the first device; second service operation information, used to indicate the second service operation on which the second device requests the first data; second parameters, used to indicate the parameters of the second service operation; second time window information, used to indicate the time range within which the second device requests to collect the first data; second type information, used to indicate the type of the second device; and second identification information, used to indicate the identification of the second device.

[0281] In some embodiments, the first request may further include one or more of the following: a data plane identifier corresponding to the second device; an identifier of the second device; a digital signature of the second device; a public key of the second device; an association identifier of the second device; and second indication information for indicating whether to notify the second device when the data subscribed to by the second device changes.

[0282] In some embodiments, the first sending unit 710 is configured to: actively send the first data to the data plane device.

[0283] In some embodiments, the first message may further include one or more of the following: a data plane identifier corresponding to the first device; an identifier of the first device; a digital signature of the first device; a public key of the first device; and an association identifier of the first device.

[0284] In some embodiments, the communication device is further configured to: receive a second message sent by the data plane device; wherein the second message is configured to notify the first device that the data plane device stores the first data in a storage device.

[0285] In some embodiments, the first device includes a terminal device.

[0286] In an optional embodiment, the first transmitting unit 710 may be a transceiver 1030. The communication device 700 may also include a processor 1010 and a memory 1020, as shown in FIG10.

[0287] Figure 8 is a schematic structural diagram of a communication device 800 provided in an embodiment of this application. The communication device 800 is a data plane device. The communication device 800 includes a first receiving unit 810.

[0288] The first receiving unit 810 is used to receive a first message sent by a first device; wherein the first message includes first data of the first device, and the data plane device is used to send the first data to a second device.

[0289] In some embodiments, the first message may further include first auxiliary information, which is related to the first data.

[0290] In some embodiments, the first auxiliary information includes one or more of the following: the domain to which the first device belongs; the identification information of the first device; anonymity information, used to indicate whether to disclose that the first data belongs to the first device; first service operation information, used to indicate the first service operation on which the first device obtains the first data; first parameters, used to indicate the parameters of the first service operation; first information, used to indicate whether the first data was actively sent by the first device; first time window information, used to indicate the time range for collecting the first data; privacy control information, used to indicate the privacy control method for the first data; first type information, used to indicate the type of device that can use the first data; first identification information, used to indicate the identification of the device that can use the first data; validity information, used to indicate the validity time range of the first data; and first indication information, used to indicate whether it is necessary to notify the first device of a first situation, wherein the first situation indicates the situation in which the second device receives the first data.

[0291] In some embodiments, the privacy control method includes one or more of the following: a method without privacy control; a first method, in which the first device delegates the data plane device to determine the access permissions of the first data; a second method, in which the first device delegates the data plane device to determine the access permissions of the first data in some devices; and a third method, in which the first device needs to obtain information from the second device to determine the access permissions of the first data.

[0292] In some embodiments, the first message further includes second data and second auxiliary information, wherein the second auxiliary information is related to the second data.

[0293] In some embodiments, the communication device 800 is further configured to: receive a first request sent by the data plane device, the first request being used to request the acquisition of the first data from the first device.

[0294] In some embodiments, the sending of the first request satisfies a first condition, and the first request is sent if the first condition is satisfied:

[0295] The second request is used for the second device to request the first data from the first device; in the case where the storage device stores the first data.

[0296] In some embodiments, the first condition includes: the second request sent by the second device is verified successfully; and / or, the storage device does not store the first data.

[0297] In some embodiments, the second request includes third auxiliary information, which is related to the first data.

[0298] In some embodiments, the communication device 800 is further configured to: send a third request to the storage device; wherein the third request is configured to request the acquisition of the first data from the first device.

[0299] In some embodiments, the sending of the third request satisfies a second condition, which is related to the storage device storing the first data.

[0300] In some embodiments, the second condition includes: the storage device stores the first data.

[0301] In some embodiments, the third request includes third auxiliary information, which is related to the first data.

[0302] In some embodiments, the storage device may store the first data record in a data directory.

[0303] In some embodiments, the update of the data directory is triggered when the first data is stored in the storage device.

[0304] In some embodiments, the first request includes third auxiliary information, which is related to the first data.

[0305] In some embodiments, the third auxiliary information includes one or more of the following: the domain of the first device; the identification information of the first device; the second service operation information, used to indicate the second service operation on which the second device requests the first data; the second parameter, used to indicate the parameter of the second service operation; the second time window information, used to indicate the time range within which the second device requests to collect the first data; the second type information, used to indicate the type of the second device; and the second identification information, used to indicate the identification of the second device.

[0306] In some embodiments, the first request may further include one or more of the following: a data plane identifier corresponding to the second device; an identifier of the second device; a digital signature of the second device; a public key of the second device; an association identifier of the second device; and second indication information for indicating whether to notify the second device when the data subscribed to by the second device changes.

[0307] In some embodiments, the first receiving unit is configured to: receive the first data actively sent by the first device.

[0308] In some embodiments, the first message may further include one or more of the following: a data plane identifier corresponding to the first device; an identifier of the first device; a digital signature of the first device; a public key of the first device; and an association identifier of the first device.

[0309] In some embodiments, the communication device 800 is further configured to: send a second message to the first device; wherein the second message is configured to notify the first device that the data plane device stores the first data in a storage device.

[0310] In some embodiments, sending a second message to the first device includes: in response to the data plane device receiving a first response message sent by the storage device, sending a second message to the first device; wherein the first response message is used to indicate that the storage device has successfully stored the first data.

[0311] In some embodiments, the first device includes a terminal device.

[0312] In an optional embodiment, the first receiving unit 810 may be a transceiver 1030. The communication device 800 may also include a processor 1010 and a memory 1020, as shown in FIG10.

[0313] Figure 9 is a schematic structural diagram of a communication device 900 provided in an embodiment of this application. The communication device 900 can be a second device. The communication device 900 includes a second receiving unit 910.

[0314] The second receiving unit 910 is used to receive first data sent by the data plane device; wherein the first data belongs to the first device, and the data plane device is used to acquire the first data.

[0315] In some embodiments, the communication device 900 is further configured to: send a second request to the data plane device; wherein the second request is used by the second device to request the acquisition of the first data from the first device.

[0316] In some embodiments, the second request includes third auxiliary information, which is related to the first data.

[0317] In some embodiments, the third auxiliary information includes one or more of the following: the domain of the first device; the identification information of the first device; the second service operation information, used to indicate the second service operation on which the second device requests the first data; the second parameter, used to indicate the parameter of the second service operation; the second time window information, used to indicate the time range within which the second device requests to collect the first data; the second type information, used to indicate the type of the second device; and the second identification information, used to indicate the identification of the second device.

[0318] In some embodiments, the second request is further configured to request the acquisition of second data, and the second request further includes second auxiliary information related to the second data.

[0319] In some embodiments, the second request may further include one or more of the following: a data plane identifier corresponding to the second device; an identifier of the second device; a digital signature of the second device; a public key of the second device; an association identifier of the second device; and second indication information for indicating whether to notify the second device when the data subscribed to by the second device changes.

[0320] In some embodiments, the first device includes a terminal device.

[0321] In an optional embodiment, the second transmitting unit 910 may be a transceiver 1030. The communication device 900 may also include a processor 1010 and a memory 1020, as shown in FIG10.

[0322] Figure 10 is a schematic structural diagram of a communication apparatus according to an embodiment of this application. The dashed lines in Figure 10 indicate that the unit or module is optional. This apparatus 1000 can be used to implement the methods described in the above method embodiments. The apparatus 1000 can be a chip, a terminal device, or a network device.

[0323] Apparatus 1000 may include one or more processors 1010. The processor 1010 may support apparatus 1000 in implementing the methods described in the preceding method embodiments. The processor 1010 may be a general-purpose processor or a special-purpose processor. For example, the processor may be a central processing unit (CPU). Alternatively, the processor may be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or any conventional processor.

[0324] The apparatus 1000 may further include one or more memories 1020. The memories 1020 store a program that can be executed by the processor 1010, causing the processor 1010 to perform the methods described in the preceding method embodiments. The memories 1020 may be independent of the processor 1010 or integrated within the processor 1010.

[0325] The device 1000 may also include a transceiver 1030. The processor 1010 can communicate with other devices or chips via the transceiver 1030. For example, the processor 1010 can send and receive data with other devices or chips via the transceiver 1030.

[0326] This application also provides a computer-readable storage medium for storing a program. This computer-readable storage medium can be applied to the communication device provided in this application, and the program causes a computer to execute the methods performed by the communication device in various embodiments of this application.

[0327] This application also provides a computer program product. The computer program product includes a program. The computer program product can be applied to the communication device provided in this application embodiment, and the program causes a computer to execute the methods performed by the communication device in various embodiments of this application.

[0328] This application also provides a computer program. This computer program can be applied to the communication device provided in this application, and causes the computer to execute the methods performed by the communication device in various embodiments of this application.

[0329] It should be understood that the terms "system" and "network" in this application can be used interchangeably. Furthermore, the terminology used in this application is only for explaining specific embodiments of the application and is not intended to limit the application. The terms "first," "second," "third," and "fourth," etc., in the specification, claims, and accompanying drawings of this application are used to distinguish different objects, not to describe a specific order. In addition, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion.

[0330] In the embodiments of this application, the term "instruction" can be a direct instruction, an indirect instruction, or an indication of a relationship. For example, A instructing B can mean that A directly instructs B, such as B being able to obtain information through A; it can also mean that A indirectly instructs B, such as A instructing C, so B can obtain information through C; or it can mean that there is a relationship between A and B.

[0331] In the embodiments of this application, "B corresponding to A" means that B is associated with A, and B can be determined based on A. However, it should also be understood that determining B based on A does not mean that B is determined solely based on A; B can also be determined based on A and / or other information.

[0332] In the embodiments of this application, the term "correspondence" can indicate a direct or indirect correspondence between two things, or an association between two things, or a relationship such as instruction and being instructed, configuration and being configured.

[0333] In this application embodiment, "predefined" or "preconfigured" can be implemented by pre-storing corresponding codes, tables, or other means that can be used to indicate relevant information in the device (e.g., including terminal devices and network devices). This application does not limit the specific implementation method. For example, predefined can refer to what is defined in the protocol.

[0334] In this application embodiment, the "protocol" may refer to a standard protocol in the field of communication, such as the LTE protocol, the NR protocol, and related protocols applied to future communication systems. This application does not limit this.

[0335] In the embodiments of this application, the term "and / or" is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. Additionally, the character " / " in this document generally indicates that the preceding and following related objects have an "or" relationship.

[0336] In the embodiments of this application, "comprising" can refer to direct inclusion or indirect inclusion. Optionally, "comprising" mentioned in the embodiments of this application can be replaced with "indicating" or "used to determine". For example, "A includes B" can be replaced with "A indicates B" or "A is used to determine B".

[0337] In the various embodiments of this application, the order of the above-mentioned processes does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

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

[0339] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0340] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0341] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can read or a data storage device such as a server or data center that integrates one or more available media. The available media may be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., digital video discs, DVDs) or semiconductor media (e.g., solid-state disks, SSDs), etc.

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

Claims

1. A wireless communication method, characterized in that, include: The first device sends a first message to the data plane device; The first message includes first data from the first device, and the data plane device is used to send the first data to the second device.

2. The method according to claim 1, characterized in that, The first message also includes first auxiliary information, which is related to the first data.

3. The method according to claim 2, characterized in that, The first auxiliary information includes one or more of the following: The domain to which the first device belongs; The identification information of the first device; Anonymous information is used to indicate whether to disclose that the first data belongs to the first device; First service operation information is used to indicate the first service operation on which the first device obtains the first data; The first parameter is used to indicate the parameters of the first service operation; The first information is used to indicate whether the first data was actively sent by the first device; First time window information is used to indicate the time range for collecting the first data; Privacy control information is used to indicate the privacy control measures applied to the primary data; First type of information, used to indicate the type of device capable of using the first data; First identification information is used to indicate the identifier of a device capable of using the first data; Valid information, used to indicate the valid time range of the first data; The first indication information is used to indicate whether it is necessary to notify the first device of a first situation, and the first situation is used to indicate the situation in which the second device receives the first data.

4. The method according to claim 3, characterized in that, The privacy control methods include one or more of the following: A method without privacy controls; In the first approach, the first device delegates the access permissions of the first data to the data plane device; In the second method, the first device delegates the data plane device to determine the access permissions of the first data in a subset of devices; In the third method, the first device needs to obtain information from the second device to determine the access rights to the first data.

5. The method according to any one of claims 2-4, characterized in that, The first message also includes second data and second auxiliary information, the second auxiliary information being related to the second data.

6. The method according to any one of claims 1-5, characterized in that, The method further includes: The first device receives a first request sent by the data plane device, the first request being used to request the acquisition of the first data from the first device.

7. The method according to claim 6, characterized in that, The first request is sent if a first condition is met, which is related to one or more of the following: The second request is used by the second device to request the first data from the first device; The storage device stores the first data.

8. The method according to claim 7, characterized in that, The first condition includes: The second request sent by the second device was verified; and / or, The storage device does not store the first data.

9. The method according to claim 7 or 8, characterized in that, The second request includes third auxiliary information, which is related to the first data.

10. The method according to any one of claims 7-9, characterized in that, Does the storage device store the first data record in the data directory? 11. The method according to claim 10, characterized in that, The update of the data directory is triggered when the first data is stored in the storage device.

12. The method according to any one of claims 6-11, characterized in that, The first request includes third auxiliary information, which is related to the first data.

13. The method according to claim 9 or 12, characterized in that, The third auxiliary information includes one or more of the following: The domain to which the first device belongs; The identification information of the first device; Second service operation information is used to indicate the second service operation on which the second device requests the first data; The second parameter is used to indicate the parameters of the second service operation; The second time window information is used to indicate the time range within which the second device requests to collect the first data; The second type of information is used to indicate the type of the second device; The second identification information is used to indicate the identification of the second device.

14. The method according to any one of claims 6-13, characterized in that, The first request also includes one or more of the following: The data plane identifier corresponding to the second device; The identifier of the second device; The digital signature of the second device; The public key of the second device; The associated identifier of the second device; The second indication information is used to indicate whether to notify the second device when the data subscribed to by the second device changes.

15. The method according to any one of claims 1-5, characterized in that, The first device sends a first message to the data plane device, including: The first device actively sends the first data to the data plane device.

16. The method according to any one of claims 1-15, characterized in that, The first message also includes one or more of the following: The data plane identifier corresponding to the first device; The identifier of the first device; The digital signature of the first device; The public key of the first device; The associated identifier of the first device.

17. The method according to any one of claims 1-16, characterized in that, The method further includes: The first device receives the second message sent by the data plane device; The second message is used to notify the first device that the data plane device will store the first data in the storage device.

18. The method according to any one of claims 1-17, characterized in that, The first device includes a terminal device.

19. A wireless communication method, characterized in that, include: The data plane device receives the first message sent by the first device; The first message includes first data from the first device, and the data plane device is used to send the first data to the second device.

20. The method according to claim 19, characterized in that, The first message also includes first auxiliary information, which is related to the first data.

21. The method according to claim 20, characterized in that, The first auxiliary information includes one or more of the following: The domain to which the first device belongs; The identification information of the first device; Anonymous information is used to indicate whether to disclose that the first data belongs to the first device; First service operation information is used to indicate the first service operation on which the first device obtains the first data; The first parameter is used to indicate the parameters of the first service operation; The first information is used to indicate whether the first data was actively sent by the first device; First time window information is used to indicate the time range for collecting the first data; Privacy control information is used to indicate the privacy control measures applied to the primary data; First type of information, used to indicate the type of device capable of using the first data; First identification information is used to indicate the identifier of a device capable of using the first data; Valid information, used to indicate the valid time range of the first data; The first indication information is used to indicate whether it is necessary to notify the first device of a first situation, and the first situation is used to indicate the situation in which the second device receives the first data.

22. The method according to claim 21, characterized in that, The privacy control methods include one or more of the following: A method without privacy controls; In the first approach, the first device delegates the access permissions of the first data to the data plane device; In the second method, the first device delegates the data plane device to determine the access permissions of the first data in a subset of devices; In the third method, the first device needs to obtain information from the second device to determine access permissions for the first data.

23. The method according to any one of claims 20-22, characterized in that, The first message also includes second data and second auxiliary information, the second auxiliary information being related to the second data.

24. The method according to any one of claims 19-23, characterized in that, The method further includes: The first device receives a first request sent by the data plane device, the first request being used to request the acquisition of the first data from the first device.

25. The method according to claim 24, characterized in that, The first request is sent if a first condition is met, which is related to one or more of the following: The second request is used by the second device to request the first data from the first device; The storage device stores the first data.

26. The method according to claim 25, characterized in that, The first condition includes: The second request sent by the second device was verified; and / or, The storage device does not store the first data.

27. The method according to claim 25 or 26, characterized in that, The second request includes third auxiliary information, which is related to the first data.

28. The method according to any one of claims 19-23, characterized in that, The method further includes: The data plane device sends a third request to the storage device; The third request is used to request the acquisition of the first data from the first device.

29. The method according to claim 28, characterized in that, The sending of the third request satisfies the second condition, which is related to the storage device storing the first data.

30. The method according to claim 29, characterized in that, The second condition includes: the storage device stores the first data.

31. The method according to any one of claims 28-29, characterized in that, The third request includes third auxiliary information, which is related to the first data.

32. The method according to any one of claims 25-31, characterized in that, Does the storage device store the first data record in the data directory? 33. The method according to claim 32, characterized in that, The update of the data directory is triggered when the first data is stored in the storage device.

34. The method according to any one of claims 24-33, characterized in that, The first request includes third auxiliary information, which is related to the first data.

35. The method according to claim 27, 31 or 34, characterized in that, The third auxiliary information includes one or more of the following: The domain described in the first device; The identification information of the first device; Second service operation information is used to indicate the second service operation on which the second device requests the first data; The second parameter is used to indicate the parameters of the second service operation; The second time window information is used to indicate the time range within which the second device requests to collect the first data; The second type of information is used to indicate the type of the second device; The second identification information is used to indicate the identification of the second device.

36. The method according to any one of claims 24-35, characterized in that, The first request also includes one or more of the following: The data plane identifier corresponding to the second device; The identifier of the second device; The digital signature of the second device; The public key of the second device; The associated identifier of the second device; The second indication information is used to indicate whether to notify the second device when the data subscribed to by the second device changes.

37. The method according to any one of claims 19-23, characterized in that, The data plane device receives the first message sent by the first device, including: The data plane device receives the first data actively sent by the first device.

38. The method according to any one of claims 19-37, characterized in that, The first message also includes one or more of the following: The data plane identifier corresponding to the first device; The identifier of the first device; The digital signature of the first device; The public key of the first device; The associated identifier of the first device.

39. The method according to any one of claims 19-38, characterized in that, The method further includes: The data plane device sends a second message to the first device; The second message is used to notify the first device that the data plane device will store the first data in the storage device.

40. The method according to claim 39, characterized in that, The data plane device sends a second message to the first device, including: In response to the data plane device receiving a first response message sent by the storage device, the data plane device sends a second message to the first device; The first response message is used to indicate that the storage device has successfully stored the first data.

41. The method according to any one of claims 19-40, characterized in that, The first device includes a terminal device.

42. A wireless communication method, characterized in that, include: The second device receives the first data sent by the data plane device; Wherein, the first data belongs to the first device, and the data plane device is used to acquire the first data.

43. The method according to claim 42, characterized in that, The method further includes: The second device sends a second request to the data plane device; The second request is used by the second device to request the first data from the first device.

44. The method according to claim 43, characterized in that, The second request includes third auxiliary information, which is related to the first data.

45. The method according to claim 44, characterized in that, The third auxiliary information includes one or more of the following: The domain described in the first device; The identification information of the first device; Second service operation information is used to indicate the second service operation on which the second device requests the first data; The second parameter is used to indicate the parameters of the second service operation; The second time window information is used to indicate the time range within which the second device requests to collect the first data; The second type of information is used to indicate the type of the second device; The second identification information is used to indicate the identification of the second device.

46. ​​The method according to any one of claims 43-45, characterized in that, The second request is also used to request the acquisition of second data, and the second request further includes second auxiliary information related to the second data.

47. The method according to any one of claims 43-46, characterized in that, The second request also includes one or more of the following: The data plane identifier corresponding to the second device; The identifier of the second device; The digital signature of the second device; The public key of the second device; The associated identifier of the second device; The second indication information is used to indicate whether to notify the second device when the data subscribed to by the second device changes.

48. The method according to any one of claims 42-47, characterized in that, The first device includes a terminal device.

49. A communication device, characterized in that, The communication device is a first device, and the communication device includes: The first sending unit is used to send a first message to the data plane device; The first message includes first data from the first device, and the data plane device is used to send the first data to the second device.

50. The communication device according to claim 49, characterized in that, The first message also includes first auxiliary information, which is related to the first data.

51. The communication device according to claim 50, characterized in that, The first auxiliary information includes one or more of the following: The domain to which the first device belongs; The identification information of the first device; Anonymous information is used to indicate whether to disclose that the first data belongs to the first device; First service operation information is used to indicate the first service operation on which the first device obtains the first data; The first parameter is used to indicate the parameters of the first service operation; The first information is used to indicate whether the first data was actively sent by the first device; First time window information is used to indicate the time range for collecting the first data; Privacy control information is used to indicate the privacy control measures applied to the primary data; First type of information, used to indicate the type of device capable of using the first data; First identification information is used to indicate the identifier of a device capable of using the first data; Valid information, used to indicate the valid time range of the first data; The first indication information is used to indicate whether it is necessary to notify the first device of a first situation, and the first situation is used to indicate the situation in which the second device receives the first data.

52. The communication device according to claim 51, characterized in that, The privacy control methods include one or more of the following: A method without privacy controls; In the first approach, the first device delegates the access permissions of the first data to the data plane device; In the second method, the first device delegates the data plane device to determine the access permissions of the first data in a subset of devices; In the third method, the first device needs to obtain information from the second device to determine access permissions for the first data.

53. The communication device according to any one of claims 49-52, characterized in that, The first message also includes second data and second auxiliary information, the second auxiliary information being related to the second data.

54. The communication device according to any one of claims 49-53, characterized in that, The communication device is also used for: The first device receives a first request sent by the data plane device, the first request being used to request the acquisition of the first data from the first device.

55. The communication device according to claim 54, characterized in that, The first request is sent if a first condition is met, which is related to one or more of the following: The second request is used by the second device to request the first data from the first device; The storage device stores the first data.

56. The communication device according to claim 55, characterized in that, The first condition includes: The second request sent by the second device was verified; and / or, The storage device does not store the first data.

57. The communication device according to claim 55 or 56, characterized in that, The second request includes third auxiliary information, which is related to the first data.

58. The communication device according to any one of claims 55-57, characterized in that, Does the storage device store the first data record in the data directory? 59. The communication device according to claim 58, characterized in that, The update of the data directory is triggered when the first data is stored in the storage device.

60. The communication device according to any one of claims 54-59, characterized in that, The first request includes third auxiliary information, which is related to the first data.

61. The communication device according to claim 57 or 60, characterized in that, The third auxiliary information includes one or more of the following: The domain to which the first device belongs; The identification information of the first device; Second service operation information is used to indicate the second service operation on which the second device requests the first data; The second parameter is used to indicate the parameters of the second service operation; The second time window information is used to indicate the time range within which the second device requests to collect the first data; The second type of information is used to indicate the type of the second device; The second identification information is used to indicate the identification of the second device.

62. The communication device according to any one of claims 54-61, characterized in that, The first request also includes one or more of the following: The data plane identifier corresponding to the second device; The identifier of the second device; The digital signature of the second device; The public key of the second device; The associated identifier of the second device; The second indication information is used to indicate whether to notify the second device when the data subscribed to by the second device changes.

63. The communication device according to any one of claims 49-53, characterized in that, The first transmitting unit is used for: The first data is actively sent to the data plane device.

64. The communication device according to any one of claims 59-63, characterized in that, The first message also includes one or more of the following: The data plane identifier corresponding to the first device; The identifier of the first device; The digital signature of the first device; The public key of the first device; The associated identifier of the first device.

65. The communication device according to any one of claims 49-64, characterized in that, The communication device is also used for: Receive the second message sent by the data plane device; The second message is used to notify the first device that the data plane device will store the first data in the storage device.

66. The communication device according to any one of claims 49-65, characterized in that, The first device includes a terminal device.

67. A communication device, characterized in that, The communication device is a data plane device, and the communication device includes: The first receiving unit is used to receive the first message sent by the first device; The first message includes first data from the first device, and the data plane device is used to send the first data to the second device.

68. The communication device according to claim 67, characterized in that, The first message also includes first auxiliary information, which is related to the first data.

69. The communication device according to claim 68, characterized in that, The first auxiliary information includes one or more of the following: The domain to which the first device belongs; The identification information of the first device; Anonymous information is provided to indicate whether to disclose that the first data belongs to the first device; First service operation information is used to indicate the first service operation on which the first device obtains the first data; The first parameter is used to indicate the parameters of the first service operation; The first information is used to indicate whether the first data was actively sent by the first device; First time window information is used to indicate the time range for collecting the first data; Privacy control information is used to indicate the privacy control measures applied to the primary data; First type of information, used to indicate the type of device capable of using the first data; First identification information is used to indicate the identifier of a device capable of using the first data; Valid information, used to indicate the valid time range of the first data; The first indication information is used to indicate whether it is necessary to notify the first device of a first situation, and the first situation is used to indicate the situation in which the second device receives the first data.

70. The communication device according to claim 69, characterized in that, The privacy control methods include one or more of the following: A method without privacy controls; In the first approach, the first device delegates the access permissions of the first data to the data plane device; In the second method, the first device delegates the data plane device to determine the access permissions of the first data in a subset of devices; In the third method, the first device needs to obtain information from the second device to determine the access rights to the first data.

71. The communication device according to any one of claims 68-70, characterized in that, The first message also includes second data and second auxiliary information, the second auxiliary information being related to the second data.

72. The communication device according to any one of claims 67-71, characterized in that, The communication device is also used for: The system receives a first request sent by the data plane device, the first request being used to request the acquisition of the first data from the first device.

73. The communication device according to claim 72, characterized in that, The first request is sent if a first condition is met, which is related to one or more of the following: The second request is used by the second device to request the first data from the first device; The storage device stores the first data.

74. The communication device according to claim 73, characterized in that, The first condition includes: The second request sent by the second device was verified; and / or, The storage device does not store the first data.

75. The communication device according to claim 73 or 74, characterized in that, The second request includes third auxiliary information, which is related to the first data.

76. The communication device according to any one of claims 67-75, characterized in that, The communication device is also used for: Send a third request to the storage device; The third request is used to request the acquisition of the first data from the first device.

77. The communication device according to claim 76, characterized in that, The sending of the third request satisfies the second condition, which is related to the storage device storing the first data.

78. The communication device according to claim 77, characterized in that, The second condition includes: the storage device stores the first data.

79. The communication device according to any one of claims 76-78, characterized in that, The third request includes third auxiliary information, which is related to the first data.

80. The communication device according to any one of claims 73-79, characterized in that, Does the storage device store the first data record in the data directory? 81. The communication device according to claim 80, characterized in that, The update of the data directory is triggered when the first data is stored in the storage device.

82. The communication device according to any one of claims 72-81, characterized in that, The first request includes third auxiliary information, which is related to the first data.

83. The communication device according to claim 75, 79 or 82, characterized in that, The third auxiliary information includes one or more of the following: The domain described in the first device; The identification information of the first device; Second service operation information is used to indicate the second service operation on which the second device requests the first data; The second parameter is used to indicate the parameters of the second service operation; The second time window information is used to indicate the time range within which the second device requests to collect the first data; The second type of information is used to indicate the type of the second device; The second identification information is used to indicate the identification of the second device.

84. The communication device according to any one of claims 72-83, characterized in that, The first request also includes one or more of the following: The data plane identifier corresponding to the second device; The identifier of the second device; The digital signature of the second device; The public key of the second device; The associated identifier of the second device; The second indication information is used to indicate whether to notify the second device when the data subscribed to by the second device changes.

85. The communication device according to any one of claims 67-71, characterized in that, The first receiving unit is used for: Receive the first data actively sent by the first device.

86. The communication device according to any one of claims 67-85, characterized in that, The first message also includes one or more of the following: The data plane identifier corresponding to the first device; The identifier of the first device; The digital signature of the first device; The public key of the first device; The associated identifier of the first device.

87. The communication device according to any one of claims 67-86, characterized in that, The communication device is also used for: Send a second message to the first device; The second message is used to notify the first device that the data plane device will store the first data in the storage device.

88. The communication device according to claim 87, characterized in that, Sending the second message to the first device includes: In response to the data plane device receiving a first response message sent by the storage device, a second message is sent to the first device; The first response message is used to indicate that the storage device has successfully stored the first data.

89. The communication device according to any one of claims 67-88, characterized in that, The first device includes a terminal device.

90. A communication device, characterized in that, The communication device is a second device, and the communication device includes: The second receiving unit is used to receive the first data sent by the data plane device; Wherein, the first data belongs to the first device, and the data plane device is used to acquire the first data.

91. The communication device according to claim 90, characterized in that, The communication device is also used for: Send a second request to the data plane device; The second request is used by the second device to request the first data from the first device.

92. The communication device according to claim 91, characterized in that, The second request includes third auxiliary information, which is related to the first data.

93. The communication device according to claim 92, characterized in that, The third auxiliary information includes one or more of the following: The domain described in the first device; The identification information of the first device; Second service operation information is used to indicate the second service operation on which the second device requests the first data; The second parameter is used to indicate the parameters of the second service operation; The second time window information is used to indicate the time range within which the second device requests to collect the first data; The second type of information is used to indicate the type of the second device; The second identification information is used to indicate the identification of the second device.

94. The communication device according to any one of claims 91-93, characterized in that, The second request is also used to request the acquisition of second data, and the second request further includes second auxiliary information related to the second data.

95. The communication device according to any one of claims 91-94, characterized in that, The second request also includes one or more of the following: The data plane identifier corresponding to the second device; The identifier of the second device; The digital signature of the second device; The public key of the second device; The associated identifier of the second device; The second indication information is used to indicate whether to notify the second device when the data subscribed to by the second device changes.

96. The communication device according to any one of claims 90-95, characterized in that, The first device includes a terminal device.

97. A communication device, characterized in that, It includes a memory and a processor, the memory being used to store a program, and the processor being used to invoke the program in the memory to cause the communication device to perform the method as described in any one of claims 1-48.

98. An apparatus, characterized in that, Includes a processor for calling a program from memory to cause the device to perform the method as described in any one of claims 1-48.

99. A chip, characterized in that, Includes a processor for calling a program from memory, causing a device on which the chip is mounted to perform the method as described in any one of claims 1-48.

100. A computer-readable storage medium, characterized in that, It contains a program that causes a computer to perform the method as described in any one of claims 1-48.

101. A computer program product, characterized in that, Includes a program that causes a computer to perform the method as described in any one of claims 1-48.

102. A computer program, characterized in that, The computer program causes the computer to perform the method as described in any one of claims 1-48.

Images