Wireless communication method, terminal device and network device

Abstract

Provided are a wireless communication method, a terminal device and a network device. The wireless communication method comprises: a terminal device sending first data to a first network element on the basis of a first connection of a control plane, wherein the first network element is used for collecting data of the terminal device.

Description

Wireless communication methods, terminal devices, and network devices Technical Field

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

[0002] In certain scenarios, the core network or third-party servers may need to use data from terminal devices. For example, when a model is deployed on the core network or a third-party server, the core network or third-party server may need to use data from terminal devices for model training. Therefore, how the core network or third-party servers collect data from terminal devices becomes a pressing issue that needs to be addressed. Summary of the Invention

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

[0004] In a first aspect, a wireless communication method is provided, comprising: a terminal device transmitting first data to a first network element based on a first connection of a control plane, wherein the first network element is used to collect data from the terminal device.

[0005] In a second aspect, a wireless communication method is provided, comprising: a first network element receiving first data sent by a terminal device based on a first connection of a control plane, wherein the first network element is used to collect data from the terminal device.

[0006] Thirdly, a terminal device is provided, comprising: a transmitting module, configured to transmit first data to a first network element based on a first connection of the control plane, wherein the first network element is configured to collect data from the terminal device.

[0007] Fourthly, a network device is provided, the network device being a first network element, the network device comprising: a first receiving module, configured to receive first data sent by a terminal device based on a first connection of the control plane, the first network element being configured to collect data from the terminal device.

[0008] Fifthly, a terminal device is provided, including a processor, a memory, and a communication interface, wherein the memory is used to store one or more computer programs, and the processor is used to invoke the computer programs in the memory to cause the terminal device to perform some or all of the steps in the method of the first aspect.

[0009] In a sixth aspect, a network device is provided, including a processor, a memory, and a communication interface, wherein the memory is used to store one or more computer programs, and the processor is used to invoke the computer programs in the memory to cause the network device to perform some or all of the steps in the method of the second aspect.

[0010] Seventhly, embodiments of this application provide a communication system including the aforementioned terminal device and / or network device. In another possible design, the system may further include other devices that interact with the terminal device or network device as described in the embodiments of this application.

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

[0012] Ninthly, 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 computer 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.

[0013] In a tenth 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.

[0014] In this embodiment, the first network element can collect data from the terminal device based on the first connection of the control plane, which is beneficial for achieving complete visibility and controllability of the collected data from the core network. Furthermore, the fact that the first network element collects data from the terminal device based on the first connection of the control plane helps ensure the reliability of the collected data. Attached Figure Description

[0015] Figure 1 is an example diagram of the system architecture of a wireless communication system applicable to embodiments of this application.

[0016] Figure 2 is an example diagram of the interaction between the network data analytics function (NWDAF) and other network elements.

[0017] Figure 3 is an example diagram of the process of transferring data through the data collection coordination function (DCCF).

[0018] Figure 4 is another example diagram of the system architecture of a wireless communication system to which embodiments of this application are applicable.

[0019] Figure 5 is an example diagram of the protocol stack applicable to the embodiments of this application.

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

[0021] Figure 7 is a flowchart illustrating a wireless communication method provided in another embodiment of this application.

[0022] Figure 8 is a schematic diagram of the structure of the terminal device provided in the embodiment of this application.

[0023] Figure 9 is a schematic diagram of the structure of the network device provided in an embodiment of this application.

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

[0025] Communication system architecture

[0026] The technical solutions of this application embodiment can be applied to various communication systems, such as: Global System for Mobile Communication (GSM) system, Code Division Multiple Access (CDMA) system, Wideband Code Division Multiple Access (WCDMA) system, General Packet Radio Service (GPRS), Long Term Evolution (LTE) system, Advanced Long Term Evolution (LTE-A) system, LTE Frequency Division Duplex (FDD) system, LTE Time Division Duplex (TDD) system, New Radio (NR) system, NR system evolution system, LTE-based access to unlicensed spectrum (LTE-U) system, NR-based access to unlicensed spectrum (NR-U) system, non-terrestrial networks (NTN) system, terrestrial networks (TN) system, and Universal Mobile Telecommunications (UMT) system. The technologies provided in this application include UMTS (Underground Universe Telecommunications System), wireless local area networks (WLAN), wireless fidelity (WIFI), and 5G (5th generation) systems. The technical solutions provided in this application can also be applied to other communication systems, such as future communication systems like 6th generation mobile communication systems and satellite communication systems.

[0027] Traditional communication systems typically support a limited number of connections and are easy to implement. However, with the development of communication technology, mobile communication systems will not only support traditional communication but also, for example, device-to-device (D2D) communication, machine-to-machine (M2M) communication, machine-type communication (MTC), vehicle-to-vehicle (V2V) communication, or vehicle-to-everything (V2X) communication. The embodiments of this application can also be applied to these communication systems.

[0028] The communication system in this application embodiment can be applied to carrier aggregation (CA) scenarios, dual connectivity (DC) scenarios, and standalone (SA) network deployment scenarios.

[0029] The communication system in this application embodiment can be applied to unlicensed spectrum, which can also be considered as shared spectrum; or, the communication system in this application embodiment can also be applied to licensed spectrum, which can also be considered as dedicated spectrum.

[0030] A key feature of communication system architecture (such as 5G system architecture) is that it can be a service-oriented architecture, meaning that network elements (service providers) in the core network can provide specific services and make them available to other network elements (consumers) through predefined API interfaces.

[0031] Figure 1 exemplarily illustrates a system architecture example of a wireless communication system to which embodiments of this application can be applied. Taking this communication system as a 5G system architecture as an example, one of the most important features of the 5G network architecture is its service-oriented architecture, meaning that core network elements (service providers) can provide specific services and allow other network elements (consumers) to call them through predefined API interfaces. The wireless communication system shown in Figure 1 may include multiple network elements, nodes, or devices, such as terminal devices, access network (AN) devices, UPF network elements, access and mobility management function (AMF) network elements, session management function (SMF) network elements, policy control function (PCF) network elements, and application function (AF) network elements. The wireless communication system may also include DN, etc.

[0032] The functions of each part or network element involved in the wireless communication system in the 5G network are illustrated below.

[0033] Terminal equipment: Terminal equipment 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 equipment, user agent, or user device. In the embodiments of this application, the terminal equipment 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 handheld devices with wireless connectivity, vehicle-mounted devices, etc. The terminal devices in the embodiments of this application may be mobile phones, tablets, laptops, handheld computers, mobile internet devices (MIDs), wearable devices, vehicle devices, virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in remote medical surgery, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, etc.

[0034] Access network equipment: Access network equipment provides network access functionality for authorized terminal devices in a specific area and can use transmission channels of different quality according to the terminal device's level and service requirements. Access network equipment manages radio resources, provides access services to terminal devices, and thus completes the forwarding of control signals and data between the terminal devices and the core network.

[0035] Access network equipment can be a device in a wireless network. Access network equipment can also be called radio access network (RAN) equipment or network equipment; for example, access network equipment can be a base station. In the embodiments of this application, access network equipment can refer to a radio access network (RAN) node (or device) that connects a terminal device to a wireless network. A base station can broadly encompass, or be replaced by, various names including: NodeB, evolved NodeB (eNB), next-generation NodeB (gNB), relay station, transmitting and receiving point (TRP), transmitting point (TP), master MeNB, auxiliary SeNB, multi-mode 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. A base station can be a macro base station, micro base station, relay node, donor node, or similar, or a combination thereof. A base station can also refer to a communication module, modem, or chip installed within the aforementioned equipment or apparatus. Base stations can also be mobile switching centers, devices that perform base station functions in device-to-device (D2D), vehicle-to-everything (V2X), and machine-to-machine (M2M) communications, network-side devices in 6G networks, and devices that perform base station functions in future communication systems. Base stations 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.

[0036] 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.

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

[0038] Access network equipment and terminal equipment 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 embodiment does not limit the scenario in which the access network equipment and terminal equipment are located.

[0039] UPF (User Plane Function) element: The UPF is a user plane function in the core network, responsible for forwarding and receiving user data (such as service data streams) from terminal devices. The UPF can connect to access network devices (such as base stations) and external data networks for data transmission. For example, the UPF can receive user data from the DN (Digital Network Node) and transmit it to the terminal device through the access network device; alternatively, the UPF can also receive user data from the terminal device through the access network device and then forward it to the DN. The transmission resources and scheduling functions providing services to the terminal device in the UPF are managed and controlled by the SMF (Service Provider Function). In some embodiments, the UPF can be divided into intermediate-UPF (I-UPF) and anchor-UPF (A-UPF). The I-UPF is connected to the access network, and the A-UPF is a session anchor UPF, also known as a PDU session anchor (PSA).

[0040] AMF (Active Mobile Element): The AMF is the mobility management function in the core network. It can be used to implement functions other than session management in the mobility management entity (MME), such as lawful interception or access authorization (or authentication). In some embodiments, in addition to performing mobility management on terminal devices, the AMF can also be responsible for forwarding session management-related messages between the terminal device and the SMF.

[0041] SMF Network Element: SMF is the session management function in the core network. It is mainly responsible for session management, allocation and management of Internet Protocol (IP) addresses for terminal devices, selection of endpoints for manageable user plane functions, policy control, or charging function interfaces, downlink data notification, and configuration of routing information for user plane functions.

[0042] PCF Network Element: The PCF is a policy management function in the core network, responsible for formulating policies related to mobility management, session management, and charging of terminal devices. Specifically, the PCF can provide policy rule information to control plane functional network elements (such as AMF, SMF, etc.) to manage and control the mobility management and session management of terminal devices.

[0043] AF (Action Frame) network elements: AFs primarily support interaction with the 3rd Generation Partnership Project (3GPP) core network to provide services, such as influencing data routing decisions, policy control functions, or providing third-party services to the network side. In other words, AFs can primarily be used to convey application-side requests to the network side. In some embodiments, an AF can be an internal operator application, such as IP Multimedia Subsystem (IMS) technology. In some embodiments, an AF can be understood as a third-party server, such as an application server on the Internet, providing relevant service information, including providing the PCF (Physical Processing Function) with service-related Quality of Service (QoS) requirement information and sending user plane data information of the service to the A-UPF (Application-Planner Filter). In some embodiments, an AF can also be a content provider (CP). In some embodiments, if the AF is an internal operator AF and is within a trusted domain with other network functions (NFs), it can directly interact and access other NFs; if the AF is not within a trusted domain, it needs to access other NFs through other network elements (e.g., NEF network elements hereinafter referred to as NEF network elements).

[0044] DN: DN refers to a network that can be used to provide data transmission. DN can be a private network, such as a local area network (LAN), an external network not controlled by an operator, such as the Internet, or a proprietary network jointly deployed by operators, such as a network providing IMS services.

[0045] It should be understood that the various network elements mentioned above in the core network can also be referred to as functional entities, and this application does not limit this. For example, a UPF network element can also be referred to as a UPF entity, and an AMF network element can also be referred to as an AMF entity, etc. It should also be understood that in some embodiments, xx network element or xx functional entity can also be directly abbreviated as xx, for example, a UPF network element (or UPF entity) can be abbreviated as UPF, and an AMF network element (or AMF entity) can be abbreviated as AMF. For ease of description, xx (such as UPF, AMF, etc.) mentioned in the embodiments of this application can refer to xx network element or xx entity, which will not be repeated hereafter.

[0046] Optionally, the wireless communication system may also include other network elements such as unified data management (UDM), authentication server function (AUSF), network slice selection function (NSSF), network exposure function (NEF), and NWDAF. This application embodiment does not limit this.

[0047] UDM network elements are subscription databases in the core network, used for generating and storing user subscription data in the network (e.g., 5G network), managing authentication data, and other functions. UDM network elements can support interaction with external third-party servers.

[0048] The AUSF network element can be used to receive AMF requests for authentication of terminal devices, request a key from the UDM, and then forward the issued key to the AMF for authentication processing.

[0049] NSSF network elements can be used for network slicing selection.

[0050] The NEF (Network Element) can manage the network data exposed by the 5G network element. External untrusted applications need to access the core network's internal data through the NEF to ensure the security of the 3GPP network. In some embodiments, the NEF can also provide functions such as opening QoS capabilities for external applications, event subscription, and AF (Active Front-End) request distribution.

[0051] The NWDAF network element can collect data from various network elements and network management systems in the core network for big data statistics, analysis, or intelligent data analysis to obtain network-side analysis results or network-side predictive data. This enables various network elements to more effectively control terminal devices based on the data analysis results. Specifically, the NWDAF network element can collect data from other network elements for big data analysis. To this end, interfaces between the NWDAF network element and other network elements are defined. Referring to Figure 2, other network elements can request an analysis result (such as an analysis identifier) ​​from the NWDAF network element through the Nnwdaf interface; conversely, when the NWDAF network element sends an analysis result to other network elements, it can do so through the service-oriented interface provided by those other network elements.

[0052] In the wireless communication system shown in Figure 1, various parts or network elements can communicate with each other through interfaces. For example, terminal devices can connect to the AN (Access Layer) via the Uu interface to exchange access layer messages and wireless data transmission; terminal devices can connect to the AMF (Non-Access Stratum, NAS) via the N1 interface to exchange NAS messages; the AN can connect to the AMF via the N2 interface to transmit radio bearer control information from the core network side to the AN; the UPF can transmit data with the AN via the N3 interface and with the DN (Network Node) via the N6 interface, etc. Other interfaces connecting parts or network elements can be found in Figure 1 and will not be described further here.

[0053] It should be understood that the network elements such as terminal equipment, access network equipment, SMF, and PCF shown in Figure 1 are merely names, and the names do not limit the equipment itself. In 5G networks and other future networks, the network elements corresponding to terminal equipment, access network equipment, SMF, and PCF may also have other names, and this application embodiment does not specifically limit them.

[0054] It should be understood that the above communication system is illustrated using a 5G system as an example. Of course, this application can also be applied to other 3GPP communication systems, such as 4G communication systems or future 3GPP communication systems. The embodiments of this application are not limited in this respect.

[0055] 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).

[0056] It should be understood that the system architecture described in the embodiments of this application is for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and does not constitute a limitation on the technical solutions provided in the embodiments of this application. Those skilled in the art will know that with the evolution of network architecture, the embodiments of this application can also be applied to similar technical problems.

[0057] DCCF

[0058] The data transmission process via DCCF is shown in Figure 3. Referring to Figure 3, each piece of data received from the data source network element is sent to the DCCF. The DCCF then delivers the received data to all consumer / notification endpoints specified by the data consumer or determined by the DCCF. Each data consumer can specify one or more notification endpoints in its request to the DCCF. These notification endpoints may include the requesting data consumer, analytical data repository function (ADRF), NRF, UDM, binding support function (BSF), or other network elements. The DCCF can also select ADRF or other notification endpoints based on its configuration.

[0059] DCCF supports data formatting and processing for each data consumer / notification endpoint to ensure that the data format conforms to the data request received from each data consumer network element.

[0060] When DCCF determines the data collection status of a data request, if the requested data has not yet been collected from the data source, DCCF sends a new subscription / request to the data source and specifies DCCF as the notification target; if the requested data is partially covered by an existing subscription of the data source, DCCF sends a request to the data source to modify the subscription and / or creates a new subscription for new requested data that cannot be provided by the current data source; if the requested data has already been collected from the data source, DCCF determines that there is no need to create or modify a subscription to the data source.

[0061] When DCCF receives a notification, it processes it according to the formatting and processing instructions for each data consumer and / or notification endpoint. Subsequently, DCCF sends the notification to the data consumer and / or notification endpoint via the Ndccf_DataManagement service.

[0062] Artificial intelligence (AI) and wireless communication

[0063] Current wireless communication systems offer greater flexibility than their predecessors, emphasizing broad applicability to various scenarios and full utilization of limited resources. However, most current systems are still based on theoretical modeling of actual communication environments or simple parameter selection. The gains from this approach are gradually diminishing in changing scenarios and complex communication environments. Therefore, it is necessary to adopt new methods and approaches, combining them with traditional wireless communication theories and systems, to find alternative paths, break through performance bottlenecks, and further improve the performance of wireless communication systems.

[0064] The R18 RAN1 project (RP-212708) aims to study AI / ML-enabled wireless air interface technologies. The main research use cases include: AI + channel state information (CSI) feedback use cases, AI + beam management use cases, and AI + positioning technology use cases.

[0065] In AI+CSI feedback use cases, AI / ML technologies can be used to compress and decompress CSI data, reducing air interface transmission overhead and improving the accuracy of CSI feedback information. In AI+beam management use cases, AI / ML technologies can be used to predict beam information in the time and spatial domains, reducing measurement overhead and latency and improving beam selection accuracy. In AI+positioning technology use cases, AI / ML technologies can be used to predict the location information of terminal devices, improving the accuracy of terminal device location information in non-line-of-sight (NLOS) scenarios.

[0066] Building upon the RAN1 use cases, RAN2 focuses on the lifecycle management of AI models, including model generation, deployment, transmission, monitoring, and updates. Current discussions on RAN2 include options for model generation on the core network or third-party servers. In this scenario, the core network or third-party servers need to collect measurement data from terminal devices for model training.

[0067] Current research is exploring how to collect data from terminal devices onto the core network. This would allow the core network or third-party servers to use the collected data to train AI models and deploy them on the terminal devices, thereby enabling the aforementioned AI use cases (such as AI+CSI feedback). Therefore, how to collect data from terminal devices is a key issue in these scenarios.

[0068] To address the aforementioned issues, embodiments of this application can utilize a first network element to collect data from terminal devices, thereby facilitating complete visibility and control of the collected data from the core network.

[0069] For ease of understanding, the first network element of this application will be introduced below.

[0070] In this embodiment, the first network element is used for data collection from the terminal device. In other words, the first network element can be used to collect data from the terminal device. In this way, the core network and / or a third-party server can collect data from the terminal device through the first network element.

[0071] In some embodiments, the first network element can be used not only to collect data from terminal devices, but also to process and / or aggregate the collected data.

[0072] In some embodiments, the first network element is a network element in the core network. Using the core network to collect data from terminal devices facilitates centralized data collection, avoiding repeated data collection when different data consumers request the same data. Furthermore, data collection through the core network, using a peer-to-peer protocol stack, ensures complete parsing and control of the terminal device's data, facilitating network control and access to the data.

[0073] However, the embodiments of this application do not limit the first network element to a network element in the core network. For example, the first network element can also be a third-party server.

[0074] This application embodiment does not limit the functions supported by the first network element. For example, the first network element may support one or more of the following functions: receiving a data collection request sent by a data consumer, determining the data collection method of the terminal device's data (such as the first data), determining the terminal device that needs to collect data (such as the terminal device corresponding to the first data), determining the protocol used to collect the data of the terminal device (such as the first data), sending a data collection configuration (such as the first configuration below) to the terminal device, receiving the data of the terminal device sent by the terminal device, and sending the collected data of the terminal device to the data consumer.

[0075] In some embodiments, the first network element may support one of the functions described above. For example, the first network element may support receiving data collection requests sent by data consumers. Another example is that the first network element may support determining the data collection method for data from the terminal device. Yet another example is that the first network element may support sending data collection configuration to the terminal device.

[0076] In some embodiments, the first network element may support multiple of the functions described above. For example, the first network element supports: receiving a data collection request sent by a data consumer, and sending the collected data from the terminal device to the data consumer. As another example, the first network element supports: receiving a data collection request sent by a data consumer, and determining the terminal device from which data needs to be collected. As another example, the first network element supports: receiving a data collection request sent by a data consumer, sending a data collection configuration to the terminal device, receiving data from the terminal device sent by the terminal device, and sending the collected data from the terminal device to the data consumer. As another example, the first network element supports: receiving a data collection request sent by a data consumer, determining the protocol used to collect data from the terminal device, and sending a data collection configuration to the terminal device. As yet another example, the first network element supports: receiving a data collection request sent by a data consumer, determining the data collection method for the terminal device's data, determining the terminal device from which data needs to be collected, determining the protocol used to collect the data from the terminal device, sending a data collection configuration to the terminal device, receiving data from the terminal device sent by the terminal device, and sending the collected data from the terminal device to the data consumer.

[0077] It should be noted that the above examples are for illustrative purposes only. The first network element can support any one or more of the above functions. For the sake of brevity, they will not be listed here one by one.

[0078] In some embodiments, the data collection request sent by the data consumer described above can be used to request data from one or more terminal devices.

[0079] In some embodiments, the first network element determining the data collection method of the terminal device means that the first network element can determine which method to use to collect the data of the terminal device. This application does not limit the data collection method of the terminal device. For example, the data collection method of the terminal device may include one or more of the following: collecting data of the terminal device based on a user plane connection, collecting data of the terminal device based on a control plane connection, and collecting data of the terminal device based on a data plane connection.

[0080] In some embodiments, the first network element supporting the determination of terminal devices from which data needs to be collected means that the first network element can determine from which terminal devices(s) data needs to be collected. For example, after receiving a data collection request sent by a data consumer, the first network element can determine from which terminal devices(s) the data requested by the data consumer needs to be collected.

[0081] In some embodiments, after receiving a data collection request from a data consumer, the first network element needs to determine the protocol used to collect data from the terminal device. A description of the protocol used to collect data from the terminal device is provided below and will not be detailed here.

[0082] In some embodiments, the data collected by the first network element from the terminal device is data measured by the terminal device. For example, after performing radio resource management (RRM) measurements, the terminal device can send the measured data to the first network element. As another example, after performing CSI measurements, the terminal device can send the measured data to the first network element. As yet another example, after performing beamforming measurements, the terminal device can send the measured data to the first network element. As yet another example, after performing positioning measurements, the terminal device can send the measured data to the first network element.

[0083] In some embodiments, the first network element can interact with other network elements through a service-oriented interface. Taking the first network element as an example in the core network, the first network element can interact with other network elements through a service-oriented interface. Figure 4 shows an example diagram of a network architecture including the first network element. As shown in Figure 4, the first network element is connected to the core network through a bus and interacts with other network elements through a service-oriented interface (such as Ndcf).

[0084] In some embodiments, the first network element may provide one or more of the above functions by providing services and / or requesting services from other network elements. For example, a data consumer may request the first network element to collect data from the terminal device by invoking a service supported by the first network element. As another example, the first network element may send the collected data from the terminal device to the data consumer by invoking a service supported by the data consumer.

[0085] This application does not limit the name of the service supported by the first network element. For example, the service supported by the first network element may be Ndcf_UEDataCollection. Another example is Ndcf_UEDataExposure.

[0086] In some embodiments, the first network element may be a newly introduced network element for the purpose of collecting data from terminal devices. In other embodiments, the first network element may be an enhanced version of an existing network element (such as DCCF, NWDAF, etc.).

[0087] The name of the first network element is not limited in the embodiments of this application. For example, the first network element can be called a data collection function (DCF) network element. As another example, the first network element can be called DCCF (if the first network element is a network element that enhances DCCF, the first network element can be called DCCF).

[0088] The first network element has been introduced above. The following section will introduce the protocol used to collect data from terminal devices.

[0089] In some embodiments, to achieve complete network visibility and control over the data of the terminal device, the terminal device and the first network element need to support peer-to-peer protocols. This application does not limit the protocols supported by the terminal device and / or the first network element, as long as the protocol is used for interaction between the first network element and the terminal device to collect data from the terminal device. For example, the terminal device and / or the first network element may support one or more of the following protocols: a first protocol, a radio resource control (RRC) layer protocol.

[0090] In some embodiments, the first protocol is dedicated to data collection from the terminal device.

[0091] In some embodiments, the first protocol is a newly introduced protocol on the network.

[0092] This application embodiment does not limit the content carried (or included) by the first protocol. For example, the first protocol may carry one or more of the following: data collection configuration corresponding to the data of the terminal device (such as the first data), definition of the data of the terminal device (such as the first data), data format of the data of the terminal device (such as the first data), data reported by the terminal device (such as the reported first data), and the first capability of the terminal device.

[0093] In some embodiments, the first protocol may carry one of the above-described features. For example, the first protocol carries a data collection configuration corresponding to the data of the terminal device. Another example is that the first protocol carries a definition of the data of the terminal device. Yet another example is that the first protocol carries a first capability of the terminal device.

[0094] In some embodiments, the first protocol may carry multiple of the above-described features. For example, the first protocol carries the data collection configuration corresponding to the data of the terminal device and the definition of the data of the terminal device. Another example is that the first protocol carries the definition and data format of the data of the terminal device. Yet another example is that the first protocol carries the definition, data format, and data reported by the terminal device. Yet another example is that the first protocol carries the data collection configuration corresponding to the data of the terminal device, the definition, data format, and data reported by the terminal device, as well as the first capability of the terminal device.

[0095] In some embodiments, the above data collection configuration may include the measurement configuration that the first network element needs to perform on the terminal device in order to collect data from the terminal device.

[0096] In some embodiments, the definition and / or format of the data on the terminal device may include the specific definition and format specification of the data parameters on the terminal device side by the first network element. This application embodiment does not limit the data parameters on the terminal device side. For example, the data parameters on the terminal device side may include one or more of the following: data parameters related to CSI feedback, data parameters related to beam management, and data parameters related to positioning.

[0097] In some embodiments, the aforementioned first capability may be used to indicate whether the terminal device supports measurements related to data collection of the terminal device, such as whether it supports first data-related measurements of the terminal device.

[0098] It should be noted that the above examples are merely illustrations, and the first protocol can carry any one or more of the above. For the sake of brevity, they will not be listed here one by one.

[0099] The embodiments of this application do not limit the name of the first protocol. For example, the first protocol may be called a data collection protocol (DCP). Or, for example, the first protocol may be called a terminal device data collection protocol, etc.

[0100] When the first protocol is used in the embodiments of this application, a clear data collection format and parameters can be defined for a specific use case, which can avoid affecting the RRC layer protocol and prevent the development of the RRC layer protocol from becoming complicated. Furthermore, using the first protocol can better distinguish different terminal devices. That is, some terminal devices may not support the first protocol, while others may, thus differentiating terminal devices based on their capabilities. In this way, the embodiments of this application can select only some terminal devices for data collection in certain use cases.

[0101] In some embodiments, considering that the access network device and the terminal device can perform measurement configuration of the terminal device's data through the RRC layer protocol, the terminal device can carry the data that needs to be reported through the RRC layer protocol. Therefore, embodiments of this application can consider that the terminal device and the first network element support the RRC layer protocol to communicate through the RRC layer protocol. Based on this, the first network element can support the corresponding RRC layer protocol, thereby enabling the parsing of the data reported by the terminal device.

[0102] The RRC layer protocol is a fundamental protocol that every terminal device needs to support. Using the RRC layer protocol for data collection by the terminal device and the first network element helps avoid introducing new protocols for specific use cases, thus reducing protocol design complexity. Furthermore, without the RRC layer protocol, the terminal device might need to support different protocols for unused (or unsupported) use cases, increasing its complexity.

[0103] It should be noted that, in addition to existing protocols such as the RRC layer protocol, the terminal equipment and the first network element can also use other existing peer-to-peer protocols, and this application embodiment does not limit this.

[0104] In some embodiments, when the terminal device and the first network element communicate through a control plane connection (hereinafter referred to as the first connection), a first protocol (or RRC layer protocol) can be used to carry communication information. Figure 5 shows an example diagram of a protocol stack for communication between the terminal device and the first network element using the first protocol and / or the RRC layer protocol. As shown in Figure 5, the terminal device includes one or more of the following protocol layers: first protocol layer (or RRC layer), NAS layer, RRC layer, packet data convergence protocol (PDCP) layer, radio link control (RLC) layer, medium access control (MAC) layer, and physical layer. The first network element includes one or more of the following protocol layers: first protocol layer (or RRC layer), application layer, secure connection layer, transport layer, IP layer, layer 2 (or MAC layer), and layer 1 (or physical layer). In this way, when the terminal device interacts with the first network element through the control plane, the interaction between the first network element and the mobility management network element is based on a service-oriented interface. For example, the first network element can send its data collection configuration, data format, and other information defined by the first protocol or RRC layer protocol to the mobility management network element by calling the Namf_Communication_N1N2MessageTransfer method. Then, the mobility management network element can send the first network element's information to the terminal device via a NAS message. The terminal device parses the first network element's information carried in the NAS message to perform corresponding data measurement, collection, and subsequent data reporting.

[0105] In some embodiments, the first protocol is located at the first protocol layer.

[0106] It should be noted that because the mobility management network element does not support the first protocol or the RRC layer protocol, it cannot parse information defined by the first protocol or the RRC layer protocol. In other words, the mobility management network element only acts as a forwarding node, using the messages from the first network element (such as messages encapsulated by the first protocol or messages encapsulated by the RRC layer protocol) as NAS containers, and sending them to the terminal device within NAS messages.

[0107] In some embodiments, the application layer may include, for example, an HTTP / 2 protocol layer or an HTTP protocol layer.

[0108] In some embodiments, the secure connection layer may include, for example, a transport layer security (TLS) protocol layer. In some embodiments, the secure connection layer is an optional protocol layer.

[0109] In some embodiments, the transport layer may include, for example, the transmission control protocol (TCP) layer.

[0110] This application embodiment does not limit the communication information carried by the first protocol or RRC layer protocol. The communication information carried by the first protocol or RRC layer protocol may include one or more of the following: data collection configuration corresponding to the terminal device's data (such as the first data), definition of the terminal device's data (such as the first data), data format of the terminal device's data (such as the first data), data reported by the terminal device (such as the reported first data), and the terminal device's first capability. For a description of the communication information carried by the first protocol layer or RRC layer protocol, please refer to the above description of the content carried by the first protocol layer; for the sake of brevity, it will not be repeated here.

[0111] Based on the above introduction of the first network element and the protocol stack between the first network element and the terminal device, the following describes the data collection process of the embodiments of this application.

[0112] Figure 6 is a schematic flowchart of a wireless communication method provided in an embodiment of this application. The method shown in Figure 6 includes step S610, which will be described below.

[0113] In step S610, the terminal device sends the first data to the first network element.

[0114] In some embodiments, the terminal device can send first data to the first network element via a first connection on the control plane. When the terminal device sends the first data to the first network element via the first connection on the control plane, the NAS protocol can be reused as the bearer of the first protocol or the RRC layer protocol between the terminal device and the mobility management network element. Between the mobility management network element and the first network element, the services supported by the mobility management network element can be reused, and interaction can be performed through service-based interfaces. Therefore, collecting data from the terminal device via the first connection on the control plane requires minimal modification. Furthermore, collecting data from the terminal device via the first connection on the control plane helps ensure the reliability of data collection.

[0115] However, the embodiments of this application are not limited to this. For example, the terminal device may send the first data to the first network element based on the user plane connection or the data plane connection.

[0116] In some embodiments, the first data may be measured by the terminal device. Exemplarily, the first data may be obtained by the terminal device performing one or more of the following measurements: RRM measurement, CSI measurement, beamforming measurement, positioning measurement, etc. As an example, the first data is obtained by the terminal device performing an RRM measurement. As another example, the first data is obtained by the terminal device performing a positioning measurement. As yet another example, the first data is obtained by the terminal device performing both RRM and beamforming measurements. As yet another example, the first data is obtained by the terminal device performing RRM, CSI, and positioning measurements.

[0117] In some embodiments, after receiving the first data, the first network element can send the first data to the data consumer. This application does not limit the data consumer. For example, the data consumer can be a network element in the core network, such as NWDAF, PCF, etc. Another example is that the data consumer can be a third-party server, such as AF, etc.

[0118] In some embodiments, the data consumer can be a node that performs model training. For example, if model training is performed by network elements in the core network, the data consumer can be a network element in the core network. Alternatively, if model training is performed by a third-party server, the data consumer can be a third-party server.

[0119] In some embodiments, before sending the received first data to the data consumer, the first network element may perform format processing on the first data according to the data consumer's requirements, so as to send the first data that conforms to the data consumer's format requirements to the data consumer. For example, after receiving the first data, the first network element may parse the first data. If the parsed first data does not conform to the data consumer's format requirements, it may perform format processing on the first data according to the data consumer's format requirements, and then send the processed first data to the data consumer.

[0120] The embodiments of this application do not limit the purpose of the first data collected by the first network element. For example, the first data can be used by the data consumer for model training. That is, after collecting the first data, the first network element can send the first data to the data consumer so that the data consumer can perform model training. As another example, the first data can be used for data analysis in the core network, such as for NWDAF (Network Data Analyzer).

[0121] In some embodiments, the first data is sent by the terminal device to the mobility management network element (MLE) via a NAS message, and then forwarded to the first network element by the MLE via a first message. As one implementation, the terminal device can carry the first data in a message (such as a DCP message) and send this message to the MLE via a NAS message. After receiving the NAS message from the terminal device, the MLE forwards the first data carried in the NAS message to the first network element via the first message.

[0122] This application does not limit the mobility management network element. For example, the mobility management network element may include the AMF (Active Mobility Function). As another example, the mobility management network may include network elements in future communication systems that have the same or similar functions as the AMF.

[0123] In some embodiments, the mobility management element forwards the first data transparently, meaning that the mobility management element does not parse the content of the first data.

[0124] In some embodiments, the first message is sent by the mobility management network element to the first network element through a service interface.

[0125] In some embodiments, the first message is a service message provided by the mobility management network element. For example, the first message may be a Namf_Communication_N1InfoNotify message. That is, after receiving the NAS message sent by the terminal device, the mobility management network element can send the first data in the NAS message to the first network element through the Namf_Communication_N1InfoNotify message.

[0126] In some embodiments, the first message may include a first identifier. The first identifier can be used to associate a terminal device with a first network element. Alternatively, the first identifier can associate the terminal device and the first network element being in the same data collection task. Therefore, in some embodiments, the first identifier can also be called or understood as a data collection association identifier. In this way, it is possible to determine which data collection task the data reported by the terminal device is for based on the first identifier.

[0127] In some embodiments, the first identifier is configured at the granularity of the terminal device, that is, the first identifier is configured per terminal device.

[0128] In other embodiments, the first identifier is configured at the granularity of the data collection task, i.e., the first identifier is configured per data collection task. When the first identifier is configured at the granularity of the data collection task, the number of bits occupied by the first identifier is smaller, which helps to reduce signaling overhead.

[0129] In some embodiments, if there is only one terminal device that needs to collect data in a data collection task, then the first identifier configured per terminal device can also be understood as configured per data collection task.

[0130] In some embodiments, if multiple terminal devices need to collect data in a data collection task, the first identifier can be configured per terminal device, or the first identifier can be configured per data collection task. That is, when there are multiple terminal devices needing to collect data, each of these multiple terminal devices can be configured with a different first identifier, or the multiple terminal devices can be configured with the same first identifier. Of course, some of the multiple terminal devices can be configured with the same first identifier, while others can be configured with different first identifiers; this application embodiment does not limit this.

[0131] This application does not limit the allocator of the first identifier in its embodiments. For example, the first identifier may be allocated by a first network element. Another example is that the first identifier may be allocated by a mobility management network element. In some embodiments, after allocating the first identifier, the first network element can send the first identifier to the mobility management network element so that the mobility management network element can associate the terminal device with the first network element based on the first identifier, that is, associate the terminal device and the first network element into the same data collection task. In some embodiments, after allocating the first identifier, the mobility management network element can send the first identifier to the first network element so that when the first network element needs to collect data from the terminal device later, it can associate the terminal device with the first network element into the same data collection task through the first identifier.

[0132] In some embodiments, the NAS message carrying first data sent by the terminal device to the mobility management network element may include a second identifier in addition to the message carrying the first data. The second identifier can be used to associate the terminal device with the first network element. Alternatively, the second identifier can be used to associate the terminal device and the first network element as being in the same data collection task. In this way, when the mobility management network element receives the NAS message carrying the first data, it can know which first network element to send the first data to. That is, after receiving the NAS message carrying the first data, the mobility management network element can forward the first data to the first network element via a first message based on the second identifier in the NAS message.

[0133] In some embodiments, the second identifier is determined based on the first identifier, or in other words, the second identifier is generated based on the first identifier. For example, the second identifier is the same as the first identifier. Alternatively, there may be a one-to-one correspondence between the second identifier and the first identifier, meaning the second identifier is different from the first identifier, but a mapping relationship exists between them. The difference between the second identifier and the first identifier facilitates privacy isolation or security domain isolation, ensuring secure communication within the network.

[0134] In some embodiments, the second identifier is determined (or generated) by the mobility management network element based on the first identifier after the first network element or mobility management network element has assigned the first identifier.

[0135] In some embodiments, the second identifier corresponds one-to-one with a terminal device, meaning the second identifier is configured for each terminal device. In other words, different terminal devices may have different second identifiers.

[0136] In other embodiments, the second identifier corresponds to multiple terminal devices. For example, the second identifiers corresponding to multiple terminal devices for the same data collection task may be the same.

[0137] In some embodiments, a terminal device may be associated with one second identifier. In some embodiments, a terminal device may be associated with multiple second identifiers. For example, in a scenario where a terminal device corresponds to multiple data collection tasks, a terminal device may be associated with multiple second identifiers.

[0138] Referring again to Figure 6, in some embodiments, the method shown in Figure 6 may further include step S604. In step S604, the first network element sends first information to the terminal device based on the first connection (i.e., the first connection of the control plane). Correspondingly, the terminal device receives the first information sent by the first network element based on the first connection.

[0139] In some embodiments, the first information includes one or more of the following: data collection configuration corresponding to the first data, definition of the first data, data format of the first data, and indication information for requesting the first capability of the terminal device.

[0140] In some embodiments, the first information may include one of the above-described features. For example, the first information may include a data collection configuration corresponding to the first data. Another example is that the first information may include a definition of the first data. Yet another example is that the first information may include the data format of the first data. Still another example is that the first information may include indication information requesting a first capability of the terminal device.

[0141] In some embodiments, the first information may include a variety of the above-described features. For example, the first information may include a data collection configuration corresponding to the first data and a definition of the first data. Another example is that the first information may include a definition of the first data and a data format of the first data. Yet another example is that the first information may include a data collection configuration corresponding to the first data, a definition of the first data, and a data format of the first data. Yet another example is that the first information may include a data collection configuration corresponding to the first data, a definition of the first data, a data format of the first data, and indication information requesting a first capability of the terminal device.

[0142] It should be noted that the above examples are merely illustrations, and the first information can include any combination of the above. For the sake of brevity, they will not be listed one by one here.

[0143] In some embodiments, the data collection configuration corresponding to the first data is used by the terminal device to collect the first data. That is, the terminal device can collect data according to the data collection configuration corresponding to the first data and send the collected first data to the first network element.

[0144] This application does not limit the indication information for requesting the first capability of the terminal device in its embodiments. For example, the indication information for requesting the first capability of the terminal device may include a first value and a second value. When the indication information for requesting the first capability of the terminal device is a first value (e.g., 1), it indicates that the first capability of the terminal device is requested; when the indication information for requesting the first capability of the terminal device is a second value (e.g., 0) or a default value, it indicates that the first capability of the terminal device is not requested. As another example, the indication information for requesting the first capability of the terminal device may only include a first value. When the indication information for requesting the first capability of the terminal device is included, it indicates that the first capability of the terminal device is requested; when the indication information for the first capability is not included, it indicates that the first capability of the terminal device is not requested.

[0145] For an explanation of the definition of first data, its data format, and related information on first capabilities, please refer to the above text. For the sake of brevity, these will not be repeated here.

[0146] In some embodiments, the first information can be carried by a single message. For example, if the first information includes data collection configuration corresponding to the first data and indication information requesting the first capability of the terminal device, the data collection configuration corresponding to the first data and the indication information requesting the first capability of the terminal device can be carried by a single message.

[0147] In other embodiments, the first information can be carried by multiple messages. Continuing with the example where the first information includes the data collection configuration corresponding to the first data and the indication information requesting the first capability of the terminal device, the data collection configuration corresponding to the first data and the indication information requesting the first capability of the terminal device can be carried by different messages.

[0148] In some embodiments, the first information is sent by the first network element to the mobility management network element via a second message, and then forwarded to the terminal device by the mobility management network element via a NAS message.

[0149] This application does not limit the second message in its embodiments, as long as the second message is a service message provided by the mobility management network element. For example, the second message can be a Namf_Communication_N1N2MessageTransfer message.

[0150] In some embodiments, the second message may include other information besides the first information. For example, the second message may include one or more of the following: a first identifier, and an identifier of the terminal device associated with the first identifier. For instance, the second message includes the first identifier. Or, for another example, the second message includes the identifier of the terminal device associated with the first identifier. Or, for yet another example, the second message includes both the first identifier and the identifier of the terminal device associated with the first identifier.

[0151] For an introduction to the first identifier, please refer to the above text. For the sake of brevity, it will not be repeated here.

[0152] In some embodiments, when a mobility management network element forwards first information to a terminal device via a NAS message, the NAS message may include a second identifier. In some embodiments, the second identifier is determined based on the first identifier. For a description of the second identifier and how it is determined based on the first identifier, please refer to the above; for brevity, it will not be repeated here.

[0153] In some embodiments, after receiving a request from a data consumer (or data requester), the first network element can send first information to the terminal device based on the request, so that the terminal device can send first data to the first network element based on the first information. Referring again to FIG6, in some embodiments, the method shown in FIG6 may further include step S602, in which the data consumer sends a first request to the first network element. Correspondingly, the first network element receives the first request sent by the data consumer. The first request can be used to request the collection of second data.

[0154] In some embodiments, the second data includes the first data described above. For example, the second data is the same as the first data. Or, for another example, the first data is a subset of the second data.

[0155] This application does not limit the information included in the first request in the embodiments. Exemplarily, the first request may include one or more of the following information: a third identifier, a fourth identifier, first indication information, second indication information, third indication information, first time information, and second time information.

[0156] The aforementioned third identifier can be used to indicate one or more terminal devices corresponding to the second data. In other words, the third identifier can be used to determine from which terminal devices(s) the second data needs to be collected.

[0157] The aforementioned fourth identifier can be used to indicate the region of interest to the data consumer. For example, if a data consumer wants to collect data within a certain region (such as collecting data within a certain region for model training), the fourth identifier can be included in the first request.

[0158] In some embodiments, the first request may include one of a third identifier and a fourth identifier. However, this application is not limited to this, and the first request may include both the third identifier and the fourth identifier.

[0159] This application does not limit the method of identifying the area of ​​interest to the data consumer; that is, this application does not limit the fourth identifier. For example, the fourth identifier may include one or more of the following: a tracking area (TA) identifier, a cell identifier.

[0160] The aforementioned first instruction information can be used to indicate the data type and / or data format of the second data. Alternatively, the first instruction information can be used to indicate the data type and / or data format of the second data requested (or expected) by the data consumer.

[0161] The aforementioned second indication information can be used to indicate the number of terminal devices corresponding to the second data. In other words, the second indication information can be used to indicate the number of samples corresponding to the second data, so that the second data can be collected from these terminal devices (or samples).

[0162] The aforementioned third indication information can be used to indicate the data size and / or data quality of the second data. For example, the third indication information can indicate the data size of the second data (such as the amount of data or the number of data packets). As another example, the third indication information can indicate the data quality of the second data (such as data consistency, integrity, bias, etc.). Furthermore, the third indication information can indicate both the data size and data quality of the second data.

[0163] The aforementioned first time information can be used to indicate the time when a data consumer expects to collect the second data. This application does not limit the first time information. For example, the first time information can be a time period, meaning it can be used to indicate that the data consumer expects to collect the second data within that time period. As another example, the first time information can be a single moment (such as a start time and / or an end time), meaning it can be used to indicate that the data consumer expects to begin collecting the second data after a certain moment, and / or expects to collect the second data before a certain moment.

[0164] The aforementioned second time information can be used to indicate the time when the data consumer expects to receive the second data; that is, the second time information can be used to indicate the data response waiting time. The first network element needs to send the collected second data to the data consumer before the time indicated by the second time information. In some embodiments, the second time information can be a moment in time to indicate the expected reception of the second data before that moment.

[0165] In some embodiments, the first request may include one of the information described above. For example, the first request may include a third identifier. Or, for example, the first request may include a fourth identifier. Or, for example, the first request may include third indication information. Or, for example, the first request may include first time information.

[0166] In some embodiments, the first request may include multiple types of the information described above. For example, the first request may include a third identifier and first indication information. Another example is that the first request may include a third identifier, second indication information, and third indication information. Yet another example is that the first request may include a fourth identifier, second indication information, and third indication information. Yet another example is that the first request may include a third identifier, first indication information, second indication information, third indication information, first time information, and second time information. Yet another example is that the first request may include a fourth identifier, first indication information, second indication information, third indication information, first time information, and second time information.

[0167] It should be noted that the above examples are merely illustrations, and the first request may include any one or more of the above information. For the sake of brevity, they will not be listed here one by one.

[0168] In some embodiments, if the data consumer does not include a third identifier in the first request, the first network element may also omit the third identifier when sending the first data to the data consumer, and only include the data collected from the terminal device, in order to protect the privacy of the terminal device.

[0169] In some embodiments, the first request is sent by the data consumer to the first network element through a service interface. As one implementation, the data consumer can invoke a service provided by the first network element (such as calling Ndcf_UEDataCollection or Ndcf_UEDataExposure) to send the first request to the first network element.

[0170] In some embodiments, the first request can be used to request a first network element to collect and send second data in a single instance. That is, the service supported by the first network element can be based on requests and responses, i.e., it supports single data requests and responses.

[0171] In other embodiments, the first request can be used to request the first network element to continuously collect and send second data multiple times. That is, the service supported by the first network element can be based on subscription and notification; after the data consumer sends the first request, the first network element can continuously collect data from the terminal device and notify the data consumer multiple times. For example, after the data consumer sends the first request, the first network element can continuously collect data from the terminal device and notify the data consumer at regular intervals.

[0172] In some embodiments, the first network element can determine the terminal device corresponding to the first data (or second data). For example, after receiving a first request sent by a data consumer, the first network element can determine the terminal device corresponding to the first data. For instance, if the first request does not carry a third identifier, the first network element can determine the terminal device corresponding to the first data.

[0173] In some embodiments, the first network element can determine the data collection method corresponding to the first data (or second data). For example, the first network element can determine whether the first data is collected through a user plane connection or a control plane connection. This application embodiment does not limit the implementation of the first network element determining the data collection method corresponding to the first data. Exemplarily, the first network element can determine the data collection method corresponding to the first data based on one or more of the following: first indication information, second indication information, and third indication information. As one implementation, when the amount of data corresponding to the first data is large, the first data can be collected through a user plane connection; when the amount of data corresponding to the first data is small, the first data can be collected through a control plane connection. As another implementation, when the data quality corresponding to the first data is high, the first data can be collected through a control plane connection; when the data quality corresponding to the first data is low, the first data can be collected through a user plane connection.

[0174] In some embodiments, the first network element may determine the protocol used to collect the first data (or the second data). For example, the first network element may determine whether to use a first protocol or an RRC layer protocol to collect the first data.

[0175] It should be noted that the data collection method and / or protocol used to collect the first data may be specified by the protocol. For example, it may specify that the first data is collected through a control plane connection, and / or specify that the first data is collected using an RRC layer protocol. In this case, collection can be performed directly according to the protocol specifications. That is, the step of determining the first network element can be omitted, or in other words, the first network element determines the data collection method and / or protocol used to collect the first data according to the protocol specifications.

[0176] It should also be noted that the embodiments of this application do not limit the order of the processes by which the first network element determines the terminal device corresponding to the first data, the method for collecting the first data, and the protocol used to collect the first data. For example, the first network element may first determine the terminal device corresponding to the first data, then determine the method for collecting the first data, and then determine the protocol used to collect the first data. Alternatively, the first network element may first determine the terminal device corresponding to the first data, then determine the protocol used to collect the first data, and then determine the method for collecting the first data. Yet another example is that the first network element may simultaneously determine the terminal device corresponding to the first data, the method for collecting the first data, and the protocol used to collect the first data.

[0177] For ease of understanding, the flow of the method of this application is illustrated below with reference to Figure 7. It should be noted that the examples below are not intended to limit the technical solution of this application. It should also be noted that any content not described in detail below (such as the first request, the first identifier, the first information, etc.) can be found in the above description.

[0178] Figure 7 is a flowchart illustrating a wireless communication method according to another embodiment of this application. The method shown in Figure 7 may include steps S701 to S709.

[0179] In step S701, the data consumer sends a first request to the first network element.

[0180] Data consumers can send a first request to the first network element by calling the services provided by the first network element (such as calling Ndcf_UEDataCollection or Ndcf_UEDataExposure).

[0181] In some embodiments, the services supported by the first network element are based on requests and responses, that is, they support single data requests and responses.

[0182] In some embodiments, the services supported by the first network element are based on subscription and notification, that is, it supports continuous data collection and multiple notifications to data consumers.

[0183] In some embodiments, the first request may include one or more of the following information: a third identifier, a fourth identifier, first indication information, second indication information, third indication information, first time information, and second time information. For example, the first request may include: a third identifier, third indication information, first time information, and second time information. As another example, the first request may include: a fourth identifier, third indication information, first time information, and second time information.

[0184] In step S702, the first network element determines the terminal device that needs to collect data.

[0185] For example, if the first network element determines, based on the received first request, that the first request does not include a third identifier, then the first network element can determine the terminal device that needs to collect data.

[0186] In step S703, the first network element determines the data collection method and / or the protocol used for data collection.

[0187] It should be noted that steps S702 and S703 are optional. It should also be noted that the order of steps S702 and S703 is not restricted.

[0188] In step S704, the first network element sends first information to the mobility management network element. For example, the first network element sends the first information to the mobility management network element through a second message (such as the Namf_Communication_N1N2MessageTransfer message).

[0189] The first information may include one or more of the following: the data collection configuration corresponding to the first data, the data format of the first data, the definition of the first data, and the indication information for requesting the first capability of the terminal device.

[0190] Furthermore, in order to associate terminal devices and the first network element in the same data collection task, the first network element can assign a first identifier. In some embodiments, if there are multiple terminal devices that need to collect data, the first network element can assign a first identifier to each terminal device. In some embodiments, the first network element can assign the same first identifier to multiple terminal devices performing the same data collection task, or it can assign different first identifiers to multiple terminal devices performing the same data collection task.

[0191] The second message sent by the first network element to the mobility management network element may include one or more of the following: a first identifier, the identifier of the terminal device corresponding to the first identifier, and first information.

[0192] It should be noted that the first identifier can be assigned to each terminal device by the first network element as described in step S704. However, this embodiment is not limited to this; the first identifier can be assigned to each terminal device by the mobility management network element and sent to the first network element. In this case, the allocation of the first identifier by the mobility management network element to the terminal device and its sending to the first network element occurs before step S704. Therefore, in step S704, the second message sent by the first network element to the mobility management network element can still include the first identifier, the identifier of the terminal device corresponding to the first identifier, and the first information.

[0193] In step S705, the mobility management network element sends the second identifier and the first information to one or more terminal devices via a downlink NAS message.

[0194] For example, a mobility management network element can generate a second identifier based on a first identifier and send the second identifier and the first information to one or more terminal devices.

[0195] The second identifiers for multiple terminal devices can be the same or different. The purpose of the second identifier is to determine which first network element to forward the data sent by the terminal device to after the mobility management network element collects the first data sent by the terminal device.

[0196] In step S706, the terminal device performs data measurement and / or collection according to the data collection configuration corresponding to the first data. The data collection configuration corresponding to the first data is, for example, carried in the first information.

[0197] In step S707, the terminal device sends the collected first data to the mobility management network element via a NAS message.

[0198] The NAS message may include a second identifier and a message carrying the first data (such as a DCP message). The message carrying the first data includes the first data collected by the terminal device.

[0199] In step S708, the mobility management network element forwards the message carrying the first data to the first network element through the first message according to the second identifier.

[0200] For example, a mobility management network element can forward a message carrying first data to a first network element via a Namf_Communication_N1InfoNotify message based on a second identifier.

[0201] In some embodiments, the first message may include a first identifier and a message carrying first data.

[0202] In step S709, the first network element sends the collected data to the data consumer.

[0203] For example, the data collected by the first network element is formatted according to the data consumer's requirements, and then the processed data is sent to the data consumer.

[0204] In some embodiments, if the data consumer does not include the identifier of the terminal device when requesting data, the first network element may also omit the identifier of the terminal device when sending the first data to the data consumer, and only include the data collected from the terminal device, in order to protect the privacy of the terminal device.

[0205] The method embodiments of this application have been described in detail above with reference to Figures 1 to 7. The apparatus embodiments of this application will be described in detail below with reference to Figures 8 to 10. 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.

[0206] Figure 8 is a schematic diagram of the structure of a terminal device provided in an embodiment of this application. The terminal device 800 shown in Figure 8 includes a transmitting module 810. The transmitting module 810 can be used to transmit first data to a first network element based on a first connection of the control plane, wherein the first network element is used to collect data from the terminal device.

[0207] In some embodiments, the first data is sent by the terminal device to the mobility management network element via a NAS message, and then forwarded to the first network element by the mobility management network element via a first message.

[0208] In some embodiments, the first message includes a first identifier, which is used to associate the terminal device with the first network element.

[0209] In some embodiments, the first identifier is configured at the granularity of the terminal device, or the first identifier is configured at the granularity of the data collection task.

[0210] In some embodiments, the first identifier is assigned by the first network element, or the first identifier is assigned by the mobility management network element.

[0211] In some embodiments, the terminal device further includes: a receiving module 820, configured to receive first information sent by the first network element based on the first connection, the first information including one or more of the following: a data collection configuration corresponding to the first data; a definition of the first data; a data format of the first data; and indication information requesting a first capability of the terminal device, the first capability being used to indicate whether the terminal device supports measurements related to the first data.

[0212] In some embodiments, the first information is sent by the first network element to the mobility management network element via a second message, and then forwarded to the terminal device by the mobility management network element via a NAS message.

[0213] In some embodiments, the second message further includes one or more of the following: a first identifier, which is used to associate the terminal device with the first network element; and an identifier of the terminal device associated with the first identifier.

[0214] In some embodiments, the NAS message includes a second identifier, which is used to associate the terminal device with the first network element, and the second identifier is determined based on the first identifier.

[0215] In some embodiments, the second identifier corresponds one-to-one with the terminal device, or the second identifier corresponds to multiple terminal devices.

[0216] In some embodiments, the first network element supports one or more of the following functions: receiving a data collection request sent by a data consumer; determining the data collection method of the first data; determining the terminal device corresponding to the first data; determining the protocol used to collect the first data; sending the data collection configuration corresponding to the first data to the terminal device; receiving the first data; and sending the first data to the data consumer.

[0217] In some embodiments, the terminal device and / or the first network element supports one or more of the following protocols: a first protocol dedicated to data collection by the terminal device; and an RRC layer protocol.

[0218] In some embodiments, the first protocol carries one or more of the following: a data collection configuration corresponding to the first data; a definition of the first data; a data format of the first data; the first data reported by the terminal device; and a first capability of the terminal device, the first capability being used to indicate whether the terminal device supports measurements related to the first data.

[0219] In some embodiments, when the terminal device and the first network element communicate through the first connection, the first protocol and / or the RRC layer protocol are used to carry communication information.

[0220] In some embodiments, the first data is measured by the terminal device.

[0221] In some embodiments, the first data is used by the data consumer for model training.

[0222] In some embodiments, the transmitting module 810 may be a transceiver 1030. The terminal device 800 may also include a processor 1010 and a memory 1020, as shown in FIG10.

[0223] Figure 9 is a schematic diagram of the structure of a network device provided in an embodiment of this application. The network device 900 shown in Figure 9 is a first network element. The network device 900 includes a first receiving module 910. The first receiving module 910 can be used to receive first data sent by a terminal device based on a first connection of the control plane, and the first network element is used to collect data from the terminal device.

[0224] In some embodiments, the first data is sent by the terminal device to the mobility management network element via a NAS message, and then forwarded to the first network element by the mobility management network element via a first message.

[0225] In some embodiments, the first message includes a first identifier, which is used to associate the terminal device with the first network element.

[0226] In some embodiments, the first identifier is configured at the granularity of the terminal device, or the first identifier is configured at the granularity of the data collection task.

[0227] In some embodiments, the first identifier is assigned by the first network element, or the first identifier is assigned by the mobility management network element.

[0228] In some embodiments, the network device further includes: a first sending module 920, configured to send first information to the terminal device based on the first connection, the first information including one or more of the following: a data collection configuration corresponding to the first data; a definition of the first data; a data format of the first data; and indication information requesting a first capability of the terminal device, the first capability being used to indicate whether the terminal device supports measurements related to the first data.

[0229] In some embodiments, the first information is sent by the first network element to the mobility management network element via a second message, and then forwarded to the terminal device by the mobility management network element via a NAS message.

[0230] In some embodiments, the second message further includes one or more of the following: a first identifier, which is used to associate the terminal device with the first network element; and an identifier of the terminal device associated with the first identifier.

[0231] In some embodiments, the NAS message includes a second identifier, which is used to associate the terminal device with the first network element, and the second identifier is determined based on the first identifier.

[0232] In some embodiments, the second identifier corresponds one-to-one with the terminal device, or the second identifier corresponds to multiple terminal devices.

[0233] In some embodiments, the network device further includes: a second receiving module, configured to receive a first request sent by a data consumer, the first request being for requesting the collection of second data, the second data including the first data.

[0234] In some embodiments, the first request includes one or more of the following: a third identifier for indicating one or more terminal devices corresponding to the second data; a fourth identifier for indicating an identifier of the area of ​​interest of the data consumer; a first indication information for indicating the data type and / or data format of the second data; a second indication information for indicating the number of terminal devices corresponding to the second data; a third indication information for indicating the data size and / or data quality of the second data; a first time information for indicating the time the data consumer expects to collect the second data; and a second time information for indicating the time the data consumer expects to receive the second data.

[0235] In some embodiments, the first request is sent via a service-based interface.

[0236] In some embodiments, the first request is used to request the first network element to collect and send the second data once, or the first request is used to request the first network element to continuously collect and send the second data multiple times.

[0237] In some embodiments, the network device further includes a determining module, which is configured to: determine a terminal device corresponding to the first data; determine a data collection method for the first data; and determine a protocol used to collect the first data.

[0238] In some embodiments, the network device further includes a second sending module for sending the first data to a data consumer.

[0239] In some embodiments, the first network element supports one or more of the following functions: receiving a data collection request sent by a data consumer; determining the data collection method of the first data; determining the terminal device corresponding to the first data; determining the protocol used to collect the first data; sending the data collection configuration corresponding to the first data to the terminal device; receiving the first data; and sending the first data to the data consumer.

[0240] In some embodiments, the terminal device and / or the first network element supports one or more of the following protocols: a first protocol dedicated to data collection by the terminal device; and an RRC layer protocol.

[0241] In some embodiments, the first protocol carries one or more of the following: a data collection configuration corresponding to the first data; a definition of the first data; a format specification for the first data; the first data reported by the terminal device; and a first capability of the terminal device, the first capability being used to indicate whether the terminal device supports measurements related to the first data.

[0242] In some embodiments, when the terminal device and the first network element communicate through the first connection, the first protocol and / or the RRC layer protocol are used to carry communication information.

[0243] In some embodiments, the first data is measured by the terminal device.

[0244] In some embodiments, the first data is used by the data consumer for model training.

[0245] In some embodiments, the first receiving module 910 may be a transceiver 1030. The network device 900 may also include a processor 1010 and a memory 1020, as shown in FIG10.

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

[0247] 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.

[0248] 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.

[0249] 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.

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

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

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

[0253] 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.

[0254] 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.

[0255] 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.

[0256] 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.

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

[0258] 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.

[0259] 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.

[0260] 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.

[0261] 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.

[0262] 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.

[0263] 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.

[0264] 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.

[0265] 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.

[0266] 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 method for wireless communication, characterized in that, include: The terminal device sends first data to the first network element based on the first connection of the control plane, and the first network element is used to collect the data of the terminal device.

2. The method according to claim 1, characterized in that, The first data is sent by the terminal device to the mobility management network element via a non-access stratum (NAS) message, and then forwarded to the first network element by the mobility management network element via a first message.

3. The method according to claim 2, characterized in that, The first message includes a first identifier, which is used to associate the terminal device with the first network element.

4. The method according to claim 3, characterized in that, The first identifier is configured at the granularity of the terminal device, or the first identifier is configured at the granularity of the data collection task.

5. The method according to claim 3 or 4, characterized in that, The first identifier is assigned by the first network element, or the first identifier is assigned by the mobility management network element.

6. The method according to any one of claims 1-5, characterized in that, Before the terminal device sends the first data to the first network element based on the first connection of the control plane, the method further includes: The terminal device receives first information sent by the first network element based on the first connection, the first information including one or more of the following: The data collection configuration corresponding to the first data; Definition of the first data; The data format of the first data; The request includes indication information of a first capability of the terminal device, which indicates whether the terminal device supports the measurement related to the first data.

7. The method according to claim 6, characterized in that, The first information is sent by the first network element to the mobility management network element via the second message, and then forwarded to the terminal device by the mobility management network element via a NAS message.

8. The method according to claim 7, characterized in that, The second message also includes one or more of the following: A first identifier is used to associate the terminal device with the first network element; The identifier of the terminal device associated with the first identifier.

9. The method according to claim 8, characterized in that, The NAS message includes a second identifier, which is used to associate the terminal device with the first network element, and the second identifier is determined based on the first identifier.

10. The method according to claim 9, characterized in that, The second identifier corresponds one-to-one with the terminal device, or the second identifier corresponds to multiple terminal devices.

11. The method according to any one of claims 1-10, characterized in that, The first network element supports one or more of the following functions: Receive data collection requests sent by data consumers; Determine the data collection method for the first data; Determine the terminal device corresponding to the first data; Determine the protocol used to collect the first data; Send the data collection configuration corresponding to the first data to the terminal device; Receive the first data; The first data is sent to the data consumer.

12. The method according to any one of claims 1-11, characterized in that, The terminal device and / or the first network element supports one or more of the following protocols: A first protocol, the first protocol being specifically used for data collection by the terminal device; Radio Resource Control (RRC) layer protocol.

13. The method according to claim 12, characterized in that, The first protocol carries one or more of the following: The data collection configuration corresponding to the first data; Definition of the first data; The data format of the first data; The first data reported by the terminal device; The first capability of the terminal device, wherein the first capability is used to indicate whether the terminal device supports the measurement related to the first data.

14. The method according to claim 12 or 13, characterized in that, When the terminal device and the first network element communicate through the first connection, the first protocol and / or the RRC layer protocol are used to carry communication information.

15. The method according to any one of claims 1-14, characterized in that, The first data was measured by the terminal device.

16. The method according to any one of claims 1-15, characterized in that, The first data is used by the data consumer for model training.

17. A method for wireless communication, characterized in that, include: The first network element receives first data sent by the terminal device based on the first connection of the control plane. The first network element is used to collect data from the terminal device.

18. The method according to claim 17, characterized in that, The first data is sent by the terminal device to the mobility management network element via a non-access stratum (NAS) message, and then forwarded to the first network element by the mobility management network element via a first message.

19. The method according to claim 18, characterized in that, The first message includes a first identifier, which is used to associate the terminal device with the first network element.

20. The method according to claim 19, characterized in that, The first identifier is configured at the granularity of the terminal device, or the first identifier is configured at the granularity of the data collection task.

21. The method according to claim 19 or 20, characterized in that, The first identifier is assigned by the first network element, or the first identifier is assigned by the mobility management network element.

22. The method according to any one of claims 17-21, characterized in that, Before the first network element receives the first data sent by the first connection terminal device based on the control plane, the method further includes: The first network element sends first information to the terminal device based on the first connection, the first information including one or more of the following: The data collection configuration corresponding to the first data; Definition of the first data; The data format of the first data; The request includes indication information of a first capability of the terminal device, which indicates whether the terminal device supports the measurement related to the first data.

23. The method according to claim 22, characterized in that, The first information is sent by the first network element to the mobility management network element via the second message, and then forwarded to the terminal device by the mobility management network element via a NAS message.

24. The method according to claim 23, characterized in that, The second message also includes one or more of the following: A first identifier is used to associate the terminal device with the first network element; The identifier of the terminal device associated with the first identifier.

25. The method according to claim 24, characterized in that, The NAS message includes a second identifier, which is used to associate the terminal device with the first network element, and the second identifier is determined based on the first identifier.

26. The method according to claim 25, characterized in that, The second identifier corresponds one-to-one with the terminal device, or the second identifier corresponds to multiple terminal devices.

27. The method according to any one of claims 17-26, characterized in that, The method further includes: The first network element receives a first request sent by a data consumer, the first request being used to request the collection of second data, the second data including the first data.

28. The method according to claim 27, characterized in that, The first request includes one or more of the following: The third identifier is used to indicate one or more terminal devices corresponding to the second data; The fourth identifier is used to indicate the area of ​​interest to the data consumer; The first indication information is used to indicate the data type and / or data format of the second data; The second indication information is used to indicate the number of terminal devices corresponding to the second data; The third indication information is used to indicate the data size and / or data quality of the second data; First-time information, used to indicate the time when the data consumer expects to collect the second data; The second time information is used to indicate the time when the data consumer expects to receive the second data.

29. The method according to claim 27 or 28, characterized in that, The first request was sent through a service-oriented interface.

30. The method according to any one of claims 27-29, characterized in that, The first request is used to request the first network element to collect and send the second data once, or the first request is used to request the first network element to continuously collect and send the second data multiple times.

31. The method according to any one of claims 17-30, characterized in that, The method further includes one or more of the following steps: The first network element determines the terminal device corresponding to the first data; The first network element determines the data collection method for the first data; The first network element determines the protocol used to collect the first data.

32. The method according to any one of claims 17-31, characterized in that, After the first network element receives the first data sent by the terminal device based on the first connection of the control plane, the method further includes: The first network element sends the first data to the data consumer.

33. The method according to any one of claims 17-32, characterized in that, The first network element supports one or more of the following functions: Receive data collection requests sent by data consumers; Determine the data collection method for the first data; Determine the terminal device corresponding to the first data; Determine the protocol used to collect the first data; Send the data collection configuration corresponding to the first data to the terminal device; Receive the first data; The first data is sent to the data consumer.

34. The method according to any one of claims 17-33, characterized in that, The terminal device and / or the first network element supports one or more of the following protocols: A first protocol, the first protocol being specifically used for data collection by the terminal device; Radio Resource Control (RRC) layer protocol.

35. The method according to claim 34, characterized in that, The first protocol carries one or more of the following: The data collection configuration corresponding to the first data; Definition of the first data; The format of the first data is specified; The first data reported by the terminal device; The first capability of the terminal device, wherein the first capability is used to indicate whether the terminal device supports the measurement related to the first data.

36. The method according to claim 34 or 35, characterized in that, When the terminal device and the first network element communicate through the first connection, the first protocol and / or the RRC layer protocol are used to carry communication information.

37. The method according to any one of claims 17-36, characterized in that, The first data was measured by the terminal device.

38. The method according to any one of claims 17-37, characterized in that, The first data is used by the data consumer for model training.

39. A terminal device, characterized in that, include: The transmitting module is used to transmit first data to a first network element based on a first connection of the control plane, wherein the first network element is used to collect data from the terminal device.

40. The terminal device according to claim 39, characterized in that, The first data is sent by the terminal device to the mobility management network element via a non-access stratum (NAS) message, and then forwarded to the first network element by the mobility management network element via a first message.

41. The terminal device according to claim 40, characterized in that, The first message includes a first identifier, which is used to associate the terminal device with the first network element.

42. The terminal device according to claim 41, characterized in that, The first identifier is configured at the granularity of the terminal device, or the first identifier is configured at the granularity of the data collection task.

43. The terminal device according to claim 41 or 42, characterized in that, The first identifier is assigned by the first network element, or the first identifier is assigned by the mobility management network element.

44. The terminal device according to any one of claims 39-43, characterized in that, The terminal device also includes: The receiving module is configured to receive first information sent by the first network element based on the first connection, wherein the first information includes one or more of the following: The data collection configuration corresponding to the first data; Definition of the first data; The data format of the first data; The request includes indication information of a first capability of the terminal device, which indicates whether the terminal device supports the measurement related to the first data.

45. The terminal device according to claim 44, characterized in that, The first information is sent by the first network element to the mobility management network element via the second message, and then forwarded to the terminal device by the mobility management network element via a NAS message.

46. ​​The terminal device according to claim 45, characterized in that, The second message also includes one or more of the following: A first identifier is used to associate the terminal device with the first network element; The identifier of the terminal device associated with the first identifier.

47. The terminal device according to claim 46, characterized in that, The NAS message includes a second identifier, which is used to associate the terminal device with the first network element, and the second identifier is determined based on the first identifier.

48. The terminal device according to claim 47, characterized in that, The second identifier corresponds one-to-one with the terminal device, or the second identifier corresponds to multiple terminal devices.

49. The terminal device according to any one of claims 39-48, characterized in that, The first network element supports one or more of the following functions: Receive data collection requests sent by data consumers; Determine the data collection method for the first data; Determine the terminal device corresponding to the first data; Determine the protocol used to collect the first data; Send the data collection configuration corresponding to the first data to the terminal device; Receive the first data; The first data is sent to the data consumer.

50. The terminal device according to any one of claims 39-49, characterized in that, The terminal device and / or the first network element supports one or more of the following protocols: A first protocol, the first protocol being specifically used for data collection by the terminal device; Radio Resource Control (RRC) layer protocol.

51. The terminal device according to claim 50, characterized in that, The first protocol carries one or more of the following: The data collection configuration corresponding to the first data; Definition of the first data; The data format of the first data; The first data reported by the terminal device; The first capability of the terminal device, wherein the first capability is used to indicate whether the terminal device supports the measurement related to the first data.

52. The terminal device according to claim 50 or 51, characterized in that, When the terminal device and the first network element communicate through the first connection, the first protocol and / or the RRC layer protocol are used to carry communication information.

53. The terminal device according to any one of claims 39-52, characterized in that, The first data was measured by the terminal device.

54. The terminal device according to any one of claims 39-53, characterized in that, The first data is used by the data consumer for model training.

55. A network device, characterized in that, The network device is a first network element, and the network device includes: The first receiving module is used to receive first data sent by the terminal device based on the first connection of the control plane, and the first network element is used to collect data from the terminal device.

56. The network device according to claim 55, characterized in that, The first data is sent by the terminal device to the mobility management network element via a non-access stratum (NAS) message, and then forwarded to the first network element by the mobility management network element via a first message.

57. The network device according to claim 56, characterized in that, The first message includes a first identifier, which is used to associate the terminal device with the first network element.

58. The network device according to claim 57, characterized in that, The first identifier is configured at the granularity of the terminal device, or the first identifier is configured at the granularity of the data collection task.

59. The network device according to claim 57 or 58, characterized in that, The first identifier is assigned by the first network element, or the first identifier is assigned by the mobility management network element.

60. The network device according to any one of claims 55-59, characterized in that, The network device also includes: A first sending module is configured to send first information to the terminal device based on the first connection, the first information including one or more of the following: The data collection configuration corresponding to the first data; Definition of the first data; The data format of the first data; The request includes indication information of a first capability of the terminal device, which indicates whether the terminal device supports the measurement related to the first data.

61. The network device according to claim 60, characterized in that, The first information is sent by the first network element to the mobility management network element via the second message, and then forwarded to the terminal device by the mobility management network element via a NAS message.

62. The network device according to claim 61, characterized in that, The second message also includes one or more of the following: A first identifier is used to associate the terminal device with the first network element; The identifier of the terminal device associated with the first identifier.

63. The network device according to claim 62, characterized in that, The NAS message includes a second identifier, which is used to associate the terminal device with the first network element, and the second identifier is determined based on the first identifier.

64. The network device according to claim 63, characterized in that, The second identifier corresponds one-to-one with the terminal device, or the second identifier corresponds to multiple terminal devices.

65. The network device according to any one of claims 55-64, characterized in that, The network device also includes: The second receiving module is used to receive a first request sent by a data consumer, the first request being used to request the collection of second data, the second data including the first data.

66. The network device according to claim 65, characterized in that, The first request includes one or more of the following: The third identifier is used to indicate one or more terminal devices corresponding to the second data; The fourth identifier is used to indicate the area of ​​interest to the data consumer; The first indication information is used to indicate the data type and / or data format of the second data; The second indication information is used to indicate the number of terminal devices corresponding to the second data; The third indication information is used to indicate the data size and / or data quality of the second data; First-time information, used to indicate the time when the data consumer expects to collect the second data; The second time information is used to indicate the time when the data consumer expects to receive the second data.

67. The network device according to claim 65 or 66, characterized in that, The first request was sent through a service-oriented interface.

68. The network device according to any one of claims 65-67, characterized in that, The first request is used to request the first network element to collect and send the second data once, or the first request is used to request the first network element to continuously collect and send the second data multiple times.

69. The network device according to any one of claims 55-68, characterized in that, The network device further includes a determining module, the determining module being used for one or more of the following: Determine the terminal device corresponding to the first data; Determine the data collection method for the first data; Determine the protocol used to collect the first data.

70. The network device according to any one of claims 55-69, characterized in that, The network device also includes: The second sending module is used to send the first data to the data consumer.

71. The network device according to any one of claims 55-70, characterized in that, The first network element supports one or more of the following functions: Receive data collection requests sent by data consumers; Determine the data collection method for the first data; Determine the terminal device corresponding to the first data; Determine the protocol used to collect the first data; Send the data collection configuration corresponding to the first data to the terminal device; Receive the first data; The first data is sent to the data consumer.

72. The network device according to any one of claims 55-71, characterized in that, The terminal device and / or the first network element supports one or more of the following protocols: A first protocol, the first protocol being specifically used for data collection by the terminal device; Radio Resource Control (RRC) layer protocol.

73. The network device according to claim 72, characterized in that, The first protocol carries one or more of the following: The data collection configuration corresponding to the first data; Definition of the first data; The format of the first data is specified; The first data reported by the terminal device; The first capability of the terminal device, wherein the first capability is used to indicate whether the terminal device supports the measurement related to the first data.

74. The network device according to claim 72 or 73, characterized in that, When the terminal device and the first network element communicate through the first connection, the first protocol and / or the RRC layer protocol are used to carry communication information.

75. The network device according to any one of claims 55-74, characterized in that, The first data was measured by the terminal device.

76. The network device according to any one of claims 55-75, characterized in that, The first data is used by the data consumer for model training.

77. A terminal device, characterized in that, The device includes a transceiver, a memory, and a processor. The memory stores a program, and the processor invokes the program in the memory and controls the transceiver to receive or send signals so that the terminal device performs the method as described in any one of claims 1-16.

78. A network device, characterized in that, The device includes a transceiver, a memory, and a processor. The memory stores a program, and the processor invokes the program in the memory and controls the transceiver to receive or transmit signals so that the network device performs the method as described in any one of claims 17-38.

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

80. 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 17-38.

81. 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-16.

82. 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 17-38.

83. 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-16.

84. 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 17-38.

85. 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-16.

86. 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 17-38.

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

88. A computer program, characterized in that, The computer program causes the computer to perform the method as described in any one of claims 17-38.

Images