Data collection and communication

Abstract

Certain aspects of the present disclosure provide techniques for wireless communication by an apparatus. The method includes: receiving an encryption configuration for data collection, the encryption configuration indicating one or more types of data to be collected by the device; decrypting the encrypted configuration for data collection; and transmitting data corresponding to the one or more types of data.

Description

[0001] INTRODUCTION TECHNICAL FIELD

[0002] Aspects of the disclosure relate to wireless communications, and more particularly, to techniques for data collection and communication.

[0003] RELATED ART

[0004] Wireless communications systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, broadcasts, or other similar types of services. These wireless communications systems can employ multiple-access technologies capable of supporting communication with multiple users by sharing available system resources. Examples of such multiple-access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single-carrier frequency division multiple access (SC-FDMA) systems, time division synchronous code division multiple access (TD-SCDMA) systems, and other similar technologies.

[0005] Despite the tremendous technological advancements in wireless communications systems over the years, challenges remain. For example, complex and dynamic environments can still attenuate or block signals between wireless transmitters and wireless receivers. Thus, there is a continuing desire to improve the technical performance of wireless communications systems, including, for example: improving the speed and data carrying capacity of communications, improving the efficiency of use of shared communications media, reducing the power used by transmitters and receivers in performing communications, improving the reliability of wireless communications, avoiding redundant transmissions and / or receptions and related processing, improving the coverage area of wireless communications, increasing the number and types of devices that can access wireless communications systems, increasing the ability of different types of devices to communicate with each other, increasing the number and types of wireless communications media that can be used, etc. Thus, there is a need to further improve wireless communications systems to overcome the aforementioned technical challenges and others.

[0006] Minimization of drive tests (MDT) is a standardized mechanism that enables wireless communication network operators to collect mobile network data using user equipment (UE) in the network and, thus, reduce the need for additional drive tests, which are associated with high cost and time investment and only provide a partial view of the network because testing is limited to locations with vehicle access. The mobile network data can be used, for example, to perform different types of network optimization.

[0007] Machine learning models are also used to enhance wireless communication networks. For example, machine learning models are used for various different use cases, such as beam prediction, mobility management, positioning, channel state information (CSI) prediction, CSI feedback, discontinuous reception (DRX) enhancements, DRX prediction, traffic prediction, interference management, etc. The training of such machine learning models can be performed at one or more devices, such as a UE, a network entity of the wireless communication network, a neutral site (e.g., a server, such as a third party server outside of the wireless communication network, an over-the-top (OTT) server, a server within the wireless communication network, etc.), etc.

[0008] To train a machine learning model, data can need to be collected, such as from UEs and / or other network entities (e.g., base stations, distributed units, central units, etc.). Further, the data can need to be communicated to a device that trains the machine learning model. Thus, techniques for data collection and communication can be needed. It should be noted that the techniques for data collection and communication described herein can be used for use cases other than training a machine learning model. SUMMARY

[0009] One aspect provides a method for wireless communication by an apparatus. The method includes receiving an encrypted configuration for data collection that indicates one or more types of data for the apparatus to collect, decrypting the encrypted configuration for data collection, and transmitting data corresponding to the one or more types of data. The technical effect of the encrypted configuration for data collection is that the types of data collected can be kept secret / secure, such as preventing other devices from learning proprietary types of data collected, such as types of data used to train proprietary machine learning models.

[0010] Another aspect provides a method for wireless communication by one or more apparatuses. The method includes receiving, by a first apparatus of the one or more apparatuses, information identifying one or more user equipment (UEs), and transmitting, by the first apparatus to the one or more UEs, an encrypted configuration for data collection that indicates one or more types of data for each UE of the one or more UEs to collect. The technical effect of the encrypted configuration for data collection is that the types of data collected can be kept secret / secure, such as preventing other devices from learning proprietary types of data collected, such as types of data used to train proprietary machine learning models.

[0011] Another aspect provides a method for wireless communication by an apparatus. The method includes receiving information about a data collection service, receiving, from the data collection service, a configuration for data collection that indicates one or more types of data for the apparatus to collect, and transmitting, to the data collection service, data corresponding to the one or more types of data. The technical effect of using a separate data collection service to configure data collection can be to flexibly provide different data collection services for collecting different data for different purposes, such as training different machine learning models.

[0012] Another aspect provides a method for wireless communication by one or more apparatuses. The method includes transmitting, by a data collection service to a UE, a configuration for data collection, the configuration indicating one or more types of data for the UE to collect, where the one or more apparatuses include the data collection service; and receiving, by the data collection service from the UE, data corresponding to the one or more types of data. The technical effect of using a separate data collection service to configure data collection can be to flexibly provide different data collection services for collecting different data for different purposes, such as training different machine learning models.

[0013] Other aspects provide one or more apparatuses that are capable of, configured for, or otherwise adapted to perform any portion of any of the methods described herein (e.g., such that execution can be implemented by only one apparatus or in a distributed manner across multiple apparatuses); one or more non-transitory computer-readable media comprising instructions to cause one or more processors of one or more apparatuses to perform any portion of any of the methods described herein (e.g., such that the instructions can be included in only one computer-readable medium or in a distributed manner across multiple computer-readable media, such that the instructions can be executed only by one processor or by multiple processors in a distributed manner, such that each of the one or more apparatuses can include one processor or multiple processors, and / or such that execution can be implemented by only one apparatus or in a distributed manner across multiple apparatuses); one or more computer program products embodied on one or more computer-readable storage media comprising code for performing any portion of any of the methods described herein (e.g., such that the code can be stored in only one computer-readable medium or in a distributed manner across multiple computer-readable media); and / or one or more apparatuses comprising one or more means for performing any portion of any of the methods described herein (e.g., such that execution will be implemented by only one apparatus or in a distributed manner across multiple apparatuses). By way of example, an apparatus can include a processing system, a device that has a processing system, or a processing system that is coordinated across one or more networks.

[0014] The following description and drawings are illustrative of certain aspects. BRIEF DESCRIPTION OF DRAWINGS

[0015] The attached drawings illustrate certain aspects of the various aspects described herein and are a part of the specification. The aspects described herein are illustrated by way of example in the accompanying drawings in which:

[0016] FIG. 1 An example wireless communication network is depicted.

[0017] FIG. 2 An example disaggregated base station architecture is depicted.

[0018] FIG. 3 Aspects of an example base station and an example user equipment (UE) are depicted.

[0019] FIG. 4A 、 FIG. 4B 、 FIG. 4C And FIG. 4D Various example aspects of data structures for a wireless communication network are depicted.

[0020] FIG. 5 A call flow diagram illustrating a call flow for performing signaling-based minimization of drive tests (MDT) is depicted.

[0021] FIG. 6 A call flow diagram illustrating a call flow for performing signaling-based MDT is depicted.

[0022] FIG. 7 A call flow diagram illustrating a call flow for performing signaling-based MDT is depicted.

[0023] FIG. 8 A call flow diagram illustrating a call flow for performing signaling-based MDT is depicted.

[0024] FIG. 9 A call flow diagram illustrating a call flow for performing signaling-based MDT is depicted.

[0025] FIG. 10 A call flow diagram illustrating a call flow for performing management-based MDT is depicted.

[0026] FIG. 11 A call flow diagram illustrating a call flow for performing management-based MDT is depicted.

[0027] FIG. 12 A call flow diagram illustrating a call flow for performing reporting of collected data is depicted.

[0028] FIG. 13 A call flow diagram illustrating a call flow for performing reporting of collected data is depicted.

[0029] FIG. 14 A call flow diagram illustrating a call flow for performing reporting of collected data is depicted.

[0030] FIG. 15 A call flow diagram illustrating a call flow for performing data collection by a data collection service is depicted.

[0031] FIG. 16A call flow diagram illustrating a call flow for performing data collection by a data collection service is depicted.

[0032] FIG. 17 A method for wireless communication is described.

[0033] FIG. 18 Another method for wireless communication is described.

[0034] FIG. 19 Another method for wireless communication is described.

[0035] FIG. 20 Another method for wireless communication is described.

[0036] FIG. 21 Various aspects of the example communication device are described.

[0037] FIG. 22 Various aspects of the example communication device are described.

[0038] FIG. 23 Various aspects of the example communication device are described.

[0039] FIG. 24 Various aspects of the example communication device are described. Detailed Implementation

[0040] This disclosure provides apparatus, methods, processing systems, and computer-readable media for data collection and communication.

[0041] In some respects, MDT techniques can be used as part of data collection and communication. UE data collected using standard MDT techniques can be referred to as normalized data and may include measurements of, for example, cell power, interference, call interruptions, throughput, etc. However, for use cases such as training machine learning models, collecting only normalized data may not be sufficient. For example, other data (also referred to as non-normalized data) may also be useful for training machine learning models, such as UE battery state, UE computational state (e.g., labels used for measurement samples), Doppler spread as measured at the UE, delay spread as measured at the UE, UE resource constraints, other internal UE conditions, and other external conditions (such as radio environment, parameters used for feature engineering), etc. Furthermore, data collected from one or more network entities may also be useful for training machine learning models, such as data measured by the network or other data used to assist the UE, which may be referred to as ancillary information, such as codebook indexes, antenna patterns, etc. Standard MDT techniques may not collect this type of data. Such data collected from one or more network entities can also be non-normalized data. Therefore, the techniques described herein allow (e.g., including non-normalized) data collection and further allow the communication of such collected data. The techniques described in this paper can provide the technical effect of allowing the collection and communication of non-standardized data, which can help in the training of machine learning models.

[0042] Furthermore, the techniques discussed herein allow for the secure communication of both the collection of data and the data itself. Specifically, entities (e.g., network operators) may wish to maintain confidentiality regarding the types of data they are collecting and the actual data being collected. The data type can be any specific data collected, such as battery status, computing status, Doppler spread, or Doppler delay. Therefore, the techniques discussed herein allow for the secure communication of both the configuration data used to configure devices for data collection and the data itself. The technical effect of securely communicating the configuration data used to configure devices for data collection is that the type of data collected can be kept confidential / secure. The technical effect of securely communicating the data itself is that the actual data collected can also be kept confidential / secure.

[0043] INTRODUCTION TO WIRELESS COMMUNICATION NETWORK

[0044] The techniques and methods described herein can be used in a variety of wireless communication networks. While aspects may be described herein using terms commonly associated with 3G, 4G, and / or 5G wireless technologies, aspects of this disclosure are equally applicable to other communication systems and standards not explicitly mentioned herein.

[0045] FIG. 1 An example of a wireless communication network 100 in which the aspects described herein can be implemented is depicted.

[0046] Generally, wireless communication network 100 includes various network entities (optionally, network elements or network nodes). Network entities are typically communication devices and / or communication functions performed by communication devices (e.g., user equipment (UE), base station (BS), components of the BS, servers, etc.). Since such communication devices are part of wireless communication network 100 and facilitate wireless communication, they may be referred to as wireless communication devices. For example, various functions of the network and various devices associated with and interacting with the network may be considered network entities. Furthermore, wireless communication network 100 includes terrestrial and non-terrestrial aspects. The terrestrial aspect includes ground-based network entities (e.g., BS 102), and the non-terrestrial aspect includes satellite 140 and aircraft 145, which may include onboard network entities (e.g., one or more BSs) capable of communicating with other network elements (e.g., terrestrial BSs) and UEs.

[0047] In the depicted example, wireless communication network 100 includes BS 102, UE 104 and one or more core networks (such as Evolved Packet Core (EPC) 160 and 5G Core (5GC) network 190) that interoperate to provide communication services over various communication links, including wired and wireless links.

[0048] FIG. 1 Various example UEs 104 are described, which may more generally include: cellular phones, smartphones, Session Initiation Protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radios, GPS devices, multimedia devices, video devices, digital audio players, cameras, game consoles, tablets, smart devices, wearable devices, vehicles, electricity meters, air pumps, large or small kitchen appliances, healthcare devices, implants, sensors / actuators, displays, Internet of Things (IoT) devices, always-on (AON) devices, edge processing devices, or other similar devices. UE 104 may also be more generally referred to as mobile devices, wireless devices, stations, mobile stations, subscriber stations, mobile subscriber stations, mobile units, subscriber units, wireless units, remote units, remote devices, access terminals, mobile terminals, wireless terminals, remote terminals, mobile phones, and others.

[0049] BS 102 communicates wirelessly with UE 104 via communication link 120 (e.g., transmitting or receiving signals to or from UE 104). Communication link 120 between BS 102 and UE 104 may include uplink (UL) (also known as reverse link) transmission from UE 104 to BS 102 and / or downlink (DL) (also known as forward link) transmission from BS 102 to UE 104. In various aspects, communication link 120 may utilize multiple-input multiple-output (MIMO) antenna techniques, including spatial multiplexing, beamforming, and / or transmit diversity.

[0050] BS 102 may typically include: NodeB, enhanced NodeB (eNB), next-generation enhanced NodeB (ng-eNB), next-generation NodeB (gNB or gNodeB), access point, transceiver base station, radio base station, radio transceiver, transceiver functionality, transmit / receive point, and / or others. Each of BS 102 provides communication coverage for a corresponding coverage area 110, which may sometimes be referred to as a cell, and in some cases may overlap (e.g., a small cell 102' may have a coverage area 110' that overlaps with the coverage area 110 of a macro cell). For example, BS may provide communication coverage for macro cells (covering relatively large geographic areas), pico cells (covering relatively small geographic areas, such as stadiums), femtocells (relatively small geographic areas (e.g., homes)), and / or other types of cells.

[0051] Although BS 102 is described as a single communication device in various aspects, it can be implemented in a variety of configurations. For example, to give a few examples, one or more components of the base station can be decomposed, including a central unit (CU), one or more distributed units (DU), one or more radio units (RU), a near real-time (near RT) RAN intelligent controller (RIC), or a non-real-time (non-RT) RIC. In another example, various aspects of the base station can be virtualized. More generally, a base station (e.g., BS 102) can include components located at a single physical location or components located at various physical locations. In examples where the base station includes components located at various physical locations, the various components can each perform functions, such that the various components collectively achieve functionality similar to a base station located at a single physical location. In some aspects, a base station including components located at various physical locations can be referred to as a decomposed radio access network architecture (such as an open RAN (O-RAN) or virtualized RAN (VRAN) architecture). FIG. 2 An example decomposed base station architecture is depicted and described.

[0052] Different BSs 102 within the wireless communication network 100 can also be configured to support different radio access technologies (such as 3G, 4G, and / or 5G). For example, a BS 102 configured for 4G LTE (collectively referred to as Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) can interface with EPC 160 via a first backhaul link 132 (e.g., S1 interface). A BS 102 configured for 5G (e.g., 5G NR or Next Generation RAN (NG-RAN)) can interface with 5GC 190 via a second backhaul link 184. BSs 102 can communicate directly or indirectly with each other (e.g., via EPC 160 or 5GC 190) via a third backhaul link 134 (e.g., X2 interface), which can be wired or wireless.

[0053] Wireless communication network 100 can subdivide the electromagnetic spectrum into various categories, bands, channels, or other characteristics. In some aspects, subdivision is provided based on wavelength and frequency, where frequency may also be referred to as carrier, subcarrier, channel, tone, or subband. For example, 3GPP currently defines frequency range 1 (FR1) as including 410MHz to 7125MHz, which is often (interchangeably) referred to as “sub-6GHz”. Similarly, 3GPP currently defines frequency range 2 (FR2) as including 24,250MHz to 52,600MHz, which is sometimes (interchangeably) referred to as “millimeter wave” (“mmW” or “mmWave”). Base stations configured to communicate using mmWave / near mmWave radio bands (e.g., mmWave base stations such as BS 180) can utilize beamforming (e.g., 182) with UEs (e.g., 104) to improve path loss and range.

[0054] The communication link 120 between BS 102 and, for example, UE 104 can be via one or more carriers, which may have different bandwidths (e.g., 5MHz, 10MHz, 15MHz, 20MHz, 100MHz, 400MHz and / or other MHz) and may be aggregated in various ways. The carriers may be adjacent to each other or may not be adjacent to each other. The allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated to DL compared to UL).

[0055] Compared to lower-frequency communication, communication using higher frequency bands can have higher path loss and shorter range. Therefore, some base stations (e.g., FIG. 1The beamforming 182 of the BS 180 (180) with the UE 104 can be used to improve path loss and range. For example, the BS 180 and UE 104 may each include multiple antennas, such as antenna elements, antenna panels, and / or antenna arrays, to facilitate beamforming. In some cases, the BS 180 may transmit beamformed signals to the UE 104 in one or more transmit directions 182''. The UE 104 may receive beamformed signals from the BS 180 in one or more receive directions 182''. The UE 104 may also transmit beamformed signals to the BS 180 in one or more transmit directions 182''. The BS 180 may also receive beamformed signals from the UE 104 in one or more receive directions 182''. The BS 180 and UE 104 may then perform beamforming training to determine the optimal receive and transmit directions for each of the BS 180 and UE 104. It is worth noting that the transmit and receive directions of the BS 180 may be the same or different. Similarly, the sending and receiving directions of UE 104 may be the same or different.

[0056] The wireless communication network 100 also includes a Wi-Fi AP 150 that communicates with a Wi-Fi station (STA) 152 via a communication link 154 in, for example, unlicensed spectrum in 2.4 GHz and / or 5 GHz.

[0057] Some UEs 104 may use device-to-device (D2D) communication links 158 to communicate with each other. The D2D communication link 158 may use one or more sidelink channels, such as physical sidelink broadcast channel (PSBCH), physical sidelink discovery channel (PSDCH), physical sidelink shared channel (PSSCH), physical sidelink control channel (PSCCH), and / or physical sidelink feedback channel (PSFCH).

[0058] EPC 160 may include various functional components, including: such as the Mobility Management Entity (MME) 162 in the illustrated example, other MMEs 164, Serving Gateway 166, Multimedia Broadcast Multicast Service (MBMS) Gateway 168, Broadcast Multicast Service Center (BM-SC) 170, and / or Packet Data Network (PDN) Gateway 172. MME 162 can communicate with Home Subscriber Server (HSS) 174. MME 162 is the control node that handles signaling between UE 104 and EPC 160. Generally, MME 162 provides bearer and connectivity management.

[0059] Generally, user Internet Protocol (IP) packets are transmitted through Serving Gateway 166, which is itself connected to PDN Gateway 172. PDN Gateway 172 provides UE IP address allocation and other functions. PDN Gateway 172 and BM-SC 170 are connected to IP service 176, which may include, for example, the Internet, intranet, IP Multimedia Subsystem (IMS), packet switching (PS) streaming service, and / or other IP services.

[0060] The BM-SC 170 provides functions for MBMS user service dispatch and delivery. The BM-SC 170 can serve as an entry point for content provider MBMS transmissions, can authorize and initiate MBMS bearer services within a Public Land Mobile Network (PLMN), and / or can schedule MBMS transmissions. The MBMS gateway 168 can distribute MBMS services to BS 102 in a Broadcast-Specific Service Single Frequency Network (MBSFN) area, and / or can be responsible for session management (start / stop) and collecting eMBMS-related billing information.

[0061] 5GC 190 may include various functional components, including: Access and Mobility Management Function (AMF) 192, other AMFs 193, Session Management Function (SMF) 194, and User Plane Function (UPF) 195. AMF 192 can communicate with Unified Data Management (UDM) 196.

[0062] AMF 192 is the control node that handles signaling between UE 104 and 5GC 190. AMF 192 provides services such as Quality of Service (QoS) flow and session management.

[0063] Internet Protocol (IP) packets are transmitted via UPF 195, which connects to IP service 197 and provides the UE with IP address allocation and other functions for 5GC 190. IP service 197 may include, for example, the Internet, intranet, IMS, PS streaming service, and / or other IP services.

[0064] In various aspects, to give a few examples, network entities or network nodes can be implemented as aggregated base stations, decomposed base stations, components of base stations, integrated access and backhaul (IAB) nodes, relay nodes, and sidelink nodes.

[0065] FIG. 2An example decomposed base station 200 architecture is depicted. The decomposed base station 200 architecture may include one or more central units (CUs) 210, which may communicate directly with the core network 220 via a backhaul link, or indirectly with the core network 220 via one or more decomposed base station units, such as a near real-time (near-RT) RAN Intelligent Controller (RIC) 225 via an E2 link, or a non-real-time (non-RT) RIC 215 associated with a Service Management and Orchestration (SMO) framework 205, or both. CUs 210 may communicate with one or more distributed units (DUs) 230 via corresponding midhaul links (such as F1 interfaces). DUs 230 may communicate with one or more radio units (RUs) 240 via corresponding fronthaul links. RUs 240 may communicate with a corresponding UE 104 via one or more radio frequency (RF) access links. In some specific implementations, UE 104 may be served simultaneously by multiple RUs 240.

[0066] Each unit in a cell (e.g., CU 210, DU 230, RU 240, and near-RT RIC 225, non-RT RIC 215, and SMO frame 205) may include or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via wired or wireless transmission media. Each unit in the cell, or an associated processor or controller providing instructions to the unit's communication interface, may be configured to communicate with one or more other units via transmission media. For example, these units may include wired interfaces configured to receive signals or transmit signals to one or more other units via wired transmission media. Additionally or alternatively, a unit may include a wireless interface that may include a receiver, transmitter, or transceiver (such as a radio frequency (RF) transceiver) configured to receive signals on a wireless transmission medium or transmit signals to one or more other units, or both.

[0067] In some aspects, CU 210 can host one or more higher-level control functions. Such control functions may include Radio Resource Control (RRC), Packet Data Convergence Protocol (PDCP), Serving Data Adaptation Protocol (SDAP), etc. Each control function can be implemented using an interface configured to signal to other control functions hosted by CU 210. CU 210 can be configured to handle user plane functions (e.g., Central Unit-User Plane (CU-UP)), control plane functions (e.g., Central Unit-Control Plane (CU-CP)), or combinations thereof. In some implementations, CU 210 can be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, CU-UP units can communicate bidirectionally with CU-CP units via an interface such as an E1 interface. CU 210 can be implemented to communicate with DU 230 for network control and signaling, as needed.

[0068] DU 230 may correspond to a logic unit that includes one or more base station functions for controlling the operation of one or more RU 240s. In some aspects, DU 230 may host one or more of the Radio Link Control (RLC) layer, Media Access Control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.) at least in part, according to functional splits (such as those defined by the 3rd Generation Partnership Project (3GPP). In some aspects, DU 230 may also host one or more low PHY layers. Each layer (or module) may be implemented using an interface configured to communicate signals with other layers (and modules) hosted by DU 230 or with control functions hosted by CU 210.

[0069] Lower-layer functionality can be implemented by one or more RU 240s. In some deployments, an RU240 controlled by a DU 230 may correspond to a logical node that hosts RF processing functions or low-PHY layer functions (such as performing Fast Fourier Transform (FFT), Inverse FFT (iFFT), digital beamforming, or Physical Random Access Channel (PRACH) extraction and filtering, or both, at least in part based on functional decomposition (such as lower-layer functional decomposition). In such architectures, the RU 240 may be implemented to handle over-the-air (OTA) communications with one or more UE 104s. In some specific implementations, the real-time and non-real-time aspects of control plane and user plane communications with the RU 240 may be controlled by the corresponding DU 230. In some scenarios, this configuration enables the DU 230 and CU 210 to be implemented in a cloud-based RAN architecture (such as a vRAN architecture).

[0070] SMO framework 205 can be configured to support RAN deployment and provisioning of both non-virtualized and virtualized network elements. For non-virtualized network elements, SMO framework 205 can be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via operation and maintenance interfaces such as the O1 interface. For virtualized network elements, SMO framework 205 can be configured to interact with a cloud computing platform such as Open Cloud (O-Cloud) 290 to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface such as the O2 interface. Such virtualized network elements may include, but are not limited to, CU 210, DU 230, RU 240, and near-RT RIC 225. In some implementations, SMO framework 205 can communicate with the hardware aspects of the 4G RAN (such as Open eNB (O-eNB) 211) via the O1 interface. Additionally, in some implementations, SMO framework 205 can communicate directly with one or more RU 240s via the O1 interface. SMO framework 205 may also include a non-RT RIC 215 configured to support the functionality of SMO framework 205.

[0071] The non-RT RIC 215 can be configured to include logical functions that enable non-real-time control and optimization of RAN elements and resources, including artificial intelligence / machine learning (AI / ML) workflows for model training and updates, or policy-based guidance for applications / features in the near-RT RIC 225. The non-RT RIC 215 can be coupled to or communicate with the near-RT RIC 225, such as via an A1 interface. The near-RT RIC 225 can be configured to include logical functions that enable near real-time control and optimization of RAN elements and resources via an interface, such as an E2 interface, through data collection and actions, connecting one or more CU 210s, one or more DU 230s, or both, and O-eNBs to the near-RT RIC 225.

[0072] In some implementations, to generate AI / ML models to be deployed in the near-RT RIC 225, the non-RT RIC 215 may receive parameters or external enrichment information from an external server. This information can be utilized by the near-RT RIC 225 and may be received from non-network data sources or network functions at the SMO framework 205 or the non-RT RIC 215. In some examples, the non-RT RIC 215 or the near-RT RIC 225 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 215 may monitor long-term trends and patterns in performance and employ AI / ML models to perform corrective actions via the SMO framework 205 (such as reconfiguration via O1) or via the creation of RAN management policies (such as A1 policies).

[0073] FIG. 3 Various aspects of examples BS 102 and UE 104 are described.

[0074] Generally, BS 102 includes various processors (e.g., 320, 330, 338, and 340), antennas 334a-334t (collectively referred to as 334), transceivers 332a-332t (collectively referred to as 332) including modulators and demodulators, and other aspects that enable the wireless transmission of data (e.g., data source 312) and the wireless reception of data (e.g., data sink 339). For example, BS 102 can transmit and receive data between BS 102 and UE 104. BS 102 includes a controller / processor 340 that can be configured to implement the various functions described herein related to wireless communication.

[0075] Generally, UE 104 includes various processors (e.g., 358, 364, 366, and 380), antennas 352a-352r (collectively referred to as 352), transceivers 354a-354r (collectively referred to as 354) including modulators and demodulators, and other aspects that enable the wireless transmission of data (e.g., retrieved from data source 362) and the wireless reception of data (e.g., provided to data sink 360). UE 104 includes a controller / processor 380 that can be configured to implement the various functions described herein related to wireless communication.

[0076] Regarding example downlink transmission, BS 102 includes a transmission processor 320 that can receive data from data source 312 and control information from controller / processor 340. This control information may be for a Physical Broadcast Channel (PBCH), Physical Control Format Indicator Channel (PCFICH), Physical Hybrid Automatic Repeat Request (HARQ) Indicator Channel (PHICH), Physical Downlink Control Channel (PDCCH), Group Common PDCCH (GC PDCCH), and / or others. In some examples, this data may be for a Physical Downlink Shared Channel (PDSCH).

[0077] The transmitter processor 320 can process (e.g., encode and symbol map) data and control information to obtain data symbols and control symbols, respectively. The transmitter processor 320 can also generate reference symbols (such as those for the primary synchronization signal (PSS), secondary synchronization signal (SSS), PBCH demodulation reference signal (DMRS), and channel state information reference signal (CSI-RS)).

[0078] The transmit (TX) multiple-input multiple-output (MIMO) processor 330 can perform spatial processing (e.g., pre-decoding) on ​​data symbols, control symbols, and / or reference symbols where applicable, and can provide the output symbol stream to the modulators (MODs) in transceivers 332a-332t. Each modulator in transceivers 332a-332t can process its corresponding output symbol stream to obtain an output sample stream. Each modulator can further process (e.g., convert to analog, amplify, filter, and up-convert) the output sample stream to obtain a downlink signal. The downlink signal from the modulators in transceivers 332a-332t can be transmitted via antennas 334a-334t respectively.

[0079] To receive downlink transmissions, UE 104 includes antennas 352a-352r that receive downlink signals from BS 102 and provide the received signals to demodulators (DEMODs) in transceivers 354a-354r respectively. Each demodulator in transceivers 354a-354r can adjust (e.g., filter, amplify, down-convert, and digitize) the corresponding received signal to obtain an input sample. Each demodulator can further process the input sample to obtain the received symbols.

[0080] The RX MIMO detector 356 acquires received symbols from all demodulators in transceivers 354a-354r, performs MIMO detection on the received symbols where applicable, and provides the detected symbols. The receive processor 358 processes (e.g., demodulates, deinterleaves, and decodes) the detected symbols, provides the decoded data for UE 104 to data sink 360, and provides the decoded control information to controller / processor 380.

[0081] Regarding example uplink transmission, UE 104 also includes a transmit processor 364 that receives and processes data from data source 362 (e.g., for PUSCH) and control information from controller / processor 380 (e.g., for Physical Uplink Control Channel (PUCCH)). Transmit processor 364 may also generate reference symbols for reference signals (e.g., for Sounding Reference Signal (SRS)). Symbols from transmit processor 364 may be pre-decoded by TX MIMO processor 366, where applicable, further processed by modulators in transceivers 354a-354r (e.g., for SC-FDM), and transmitted to BS 102.

[0082] At BS 102, uplink signals from UE 104 can be received by antennas 334a-334t, processed by demodulators in transceivers 332a-332t, detected where applicable by RX MIMO detector 336, and further processed by receiver processor 338 to obtain decoded data and control information transmitted by UE 104. Receiver processor 338 can provide the decoded data to data sink 339 and the decoded control information to controller / processor 340.

[0083] Memory 342 and memory 382 can store data and program code for BS 102 and UE 104, respectively.

[0084] Scheduler 344 can schedule UE to transmit data on the downlink and / or uplink.

[0085] In various respects, BS 102 can be described as transmitting and receiving various types of data associated with the methods described herein. In these contexts, "transmitting" can refer to various mechanisms that output data, such as from data source 312, scheduler 344, memory 342, transmit processor 320, controller / processor 340, TX MIMO processor 330, transceiver 332a-332t, antenna 334a-334t, and / or other aspects described herein. Similarly, "receiving" can refer to various mechanisms that acquire data, such as from antenna 334a-334t, transceiver 332a-332t, RX MIMO detector 336, controller / processor 340, receive processor 338, scheduler 344, memory 342, and / or other aspects described herein.

[0086] In various respects, UE 104 can also be described as transmitting and receiving various types of data associated with the methods described herein. In these contexts, “transmitting” can refer to various mechanisms that output data, such as from data source 362, memory 382, ​​transmit processor 364, controller / processor 380, TX MIMO processor 366, transceiver 354a-354t, antenna 352a-352t, and / or other aspects described herein. Similarly, “receiving” can refer to various mechanisms that acquire data, such as from antenna 352a-352t, transceiver 354a-354t, RX MIMO detector 356, controller / processor 380, receive processor 358, memory 382, ​​and / or other aspects described herein.

[0087] In some respects, the processor can be configured to perform various operations (such as those associated with the methods described herein) and to send (output) data to or receive data from another interface configured to send or receive data, respectively.

[0088] FIG. 4A , FIG. 4B , FIG. 4C and FIG. 4D Describes the use of wireless communication networks (such as FIG. 1 All aspects of the data structure of the wireless communication network 100.

[0089] Specifically, FIG. 4A Figure 400 is an example of the first subframe within a 5G (e.g., 5G NR) frame structure. FIG. 4B Figure 430 illustrates an example of a DL channel within a 5G subframe. FIG. 4C Figure 450 illustrates an example of the second subframe within a 5G frame structure, and FIG. 4DFigure 480 illustrates an example of a UL channel within a 5G subframe.

[0090] Wireless communication systems can utilize Orthogonal Frequency Division Multiplexing (OFDM) with a cyclic prefix (CP) on both the uplink and downlink. Such systems can also support half-duplex operation using Time Division Duplex (TDD). OFDM and Single-Carrier Frequency Division Multiplexing (SC-FDM) will (e.g., as...) FIG. 4B and FIG. 4D The system bandwidth (as depicted in the text) is divided into multiple orthogonal subcarriers. Each subcarrier can be modulated with data. Modulation symbols can be transmitted in the frequency domain using OFDM and / or in the time domain using SC-FDM.

[0091] Wireless communication frame structures can be frequency division duplex (FDD), where for a specific set of subcarriers, subframes within that set are dedicated to either deep (DL) or ultra-low (UL). Wireless communication frame structures can also be time division duplex (TDD), where for a specific set of subcarriers, subframes within that set are dedicated to both DL and UL.

[0092] exist FIG. 4A and FIG. 4C In this example, the wireless communication frame structure is TDD, where D stands for DL, U for UL, and X is flexibly used between DL and UL. The UE can configure the time slot format using the received Time Slot Format Indicator (SFI) (dynamically via DL Control Information (DCI) or semi-statically / statically via Radio Resource Control (RRC) signaling). In the depicted example, a 10ms frame is divided into 10 equal-sized 1ms subframes. Each subframe may include one or more time slots. In some examples, each time slot may include 7 or 14 symbols, depending on the time slot format. Subframes may also include micro-slots, which typically have fewer symbols than the entire time slot. Other wireless communication technologies may have different frame structures and / or different channels.

[0093] In some respects, the number of time slots within a subframe is based on the time slot configuration and parameter set. For example, for time slot configuration 0, different parameter sets (μ) 0 to 5 allow for 1, 2, 4, 8, 16, and 32 time slots per subframe, respectively. For time slot configuration 1, different parameter sets 0 to 2 allow for 2, 4, and 8 time slots per subframe, respectively. Therefore, for time slot configuration 0 and parameter set μ, there are 14 symbols per time slot and 2µ time slots per subframe. The subcarrier spacing and symbol length / duration are functions of the parameter set. The subcarrier spacing can be equal to... kHz, where μ is the parameter set from 0 to 5. Therefore, the parameter set... It has a subcarrier spacing of 15 kHz and a parameter set It has a subcarrier spacing of 480 kHz. The symbol length / duration is negatively correlated with the subcarrier spacing.FIG. 4A , FIG. 4B , FIG. 4C and FIG. 4D It provides slot configuration 0 with 14 symbols per slot and parameter set with 4 slots per subframe. Example: The time slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 μs.

[0094] like FIG. 4A , FIG. 4B , FIG. 4C and FIG. 4D As depicted, the resource grid can be used to represent the frame structure. Each time slot includes a resource block (RB) (also known as a physical RB (PRB)) extending for, for example, 12 consecutive subcarriers. The resource grid is divided into multiple resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0095] like FIG. 4A As illustrated in the example, some REs in the RE carry information for the UE (e.g., FIG. 1 and FIG. 3 The reference (pilot) signal (RS) for the UE (104) may include a demodulation RS (DMRS) and / or a channel state information reference signal (CSI-RS) for channel estimation at the UE. The RS may also include a beam measurement RS (BRS), a beam refinement RS (BRRS), and / or a phase tracking RS (PT-RS).

[0096] FIG. 4B Examples of various DL channels within a subframe of a frame are illustrated. The Physical Downlink Control Channel (PDCCH) carries the DCI within one or more Control Channel Elements (CCEs), each CCE comprising, for example, nine RE groups (REGs), each REG comprising, for example, four consecutive REs in an OFDM symbol.

[0097] The Primary Synchronization Signal (PSS) can be located within symbol 2 of a specific subframe of the frame. The PSS is generated by the UE (e.g., FIG. 1 and FIG. 3 104) is used to determine subframe / symbol timing and physical layer identifier.

[0098] The secondary synchronization signal (SSS) can be located in symbol 4 of a specific subframe of the frame. The SSS is used by the UE to determine the physical layer cell identifier group number and radio frame timing.

[0099] Based on the Physical Layer Identifier and Physical Layer Cell Identifier Group Number, the UE can determine the Physical Cell Identifier (PCI). Based on the PCI, the UE can determine the location of the aforementioned DMRS. The Physical Broadcast Channel (PBCH), carrying the Master Information Block (MIB), can be logically grouped with the PSS and SSS to form a Synchronization Signal (SS) / PBCH block. The MIB provides the System Frame Number (SFN) and the number of Restricted Frames (RBs) in the system bandwidth. The Physical Downlink Shared Channel (PDSCH) carries user data, broadcast system information (such as System Information Blocks (SIBs)) not transmitted via the PBCH, and / or paging messages.

[0100] like FIG. 4C As illustrated, some REs in the REs carry DMRS for channel estimation at the base station (indicated as R for a particular configuration, but other DMRS configurations are possible). The UE can transmit DMRS for PUCCH and DMRS for PUSCH. PUSCH DMRS can be transmitted, for example, in the first or second symbol before the PUSCH. PUCCH DMRS can be transmitted in different configurations depending on whether a short or long PUCCH is being transmitted and depending on the specific PUCCH format used. UE104 can transmit a Sounding Reference Signal (SRS). SRS can be transmitted, for example, in the last symbol of a subframe. SRS can have a comb structure, and the UE can transmit SRS on one of the comb teeth. SRS can be used by the base station for channel quality estimation to enable frequency-dependent scheduling of the UL.

[0101] FIG. 4D Examples of various UL channels within a subframe of a frame are illustrated. The PUCCH can be located as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicators (CQI), pre-decoding matrix indicators (PMI), rank indicators (RI), and HARQ ACK / NACK feedback. The PUSCH carries data and may additionally be used to carry buffer status reports (BSR), power clearance reports (PHR), and / or UCI.

[0102] ASPECTS RELATED TO SIGNALING-BASED MINIMIZATION OF DRIVE TEST (MDT)

[0103] FIG. 5 A call flow diagram illustrating a call flow 500 for performing a signaling-based MDT is depicted. FIG. 5 Operation, administration and maintenance (OAM) 510 is described, which can be FIG. 1 The functional components of the 5GC 190. For example, OAM 510 can refer to a network entity configured to manage a wireless communication network. FIG. 5 UDM 508 is further described, which corresponds to FIG. 1UDM 196. For example, UDM 508 can refer to a network entity configured to manage user data. FIG. 5 AMF 506 is further described, which corresponds to FIG. 1 AMF 192. FIG. 5 The radio access network (RAN) entity 504 is further described, which may correspond to a network entity, such as FIG. 1 and FIG. 3 BS 102 or as about FIG. 2 The decomposed base station under discussion. FIG. 5 UE 502 is further described, which can correspond to FIG. 1 and FIG. 3 UE 104.

[0104] As shown in the figure, at point 512, OAM 510 activates the tracking session by transmitting a tracking activation message to UDM 508. A tracking session is a session that configures UE 502 to collect data (such as the standardized data discussed). In some respects, the tracking activation message includes tracking control and configuration parameters, such as the identifier of UE 502, such as the Subscription Permanent Identifier (SUPI) and / or International Mobile Equipment Identifier Software Version (IMEISV), indications of parameters configured for UE data collection, etc. Therefore, UDM 508 can store the tracking control and configuration parameters.

[0105] At 514, AMF 506 receives a registration request from RAN 504. In some respects, UE 502 transmits the registration request to RAN 504, which then forwards it to AMF 506. For example, the registration request may be a request from UE 502 to register with the wireless communication network.

[0106] At point 516, for example, in response to a registration request, AMF 506 receives / retrieves tracking control and configuration parameters from UDM 508 by performing a Subscriber Data Management (SDM) acquisition process using UDM 508. Therefore, AMF 506 can store tracking control and configuration parameters.

[0107] At 518, AMF 506 initiates a tracking session based on the received tracking control and configuration parameters, such as by transmitting a start tracking message to RAN 504 (e.g., via the Ng interface). This start tracking message may include the tracking control and configuration parameters. Therefore, RAN 504 can store the tracking control and configuration parameters and initiate the tracking session.

[0108] At 520, RAN 504 transmits the MDT configuration to UE 502, instructing UE 502 to collect data (e.g., normalized data). For example, the MDT configuration may include at least a portion of tracking control and configuration parameters. Therefore, UE 502 stores at least a portion of the tracking control and configuration parameters and begins collecting data, such as performing measurements corresponding to that data. For example, UE 502 may perform a measurement of cell power by measuring one or more signals transmitted from RAN 504. Further, UE 502 may measure / track the number of call interruptions at UE 502. Further, UE 502 may measure / track, for example, the average throughput of data transmitted and / or received by UE 502 relative to RAN 504.

[0109] ASPECTS RELATED TO OAM-BASED DATA COLLECTION CONFIGURATION BY A NETWORK SERVER

[0110] FIG. 6 A call flow diagram illustrating a call flow 600 for performing a signaling-based MDT is depicted. FIG. 6 The OAM 610 is described, which can be FIG. 1 The functional components of 5GC 190. FIG. 6 UDM 608 is further described, which can correspond to FIG. 1 UDM 196. FIG. 6 AMF 606 is further described, which corresponds to FIG. 1 AMF 192. FIG. 6 RAN entity 604 is further described, which may correspond to network entities, such as FIG. 1 and FIG. 3 BS 102 or as about FIG. 2 The decomposed base station under discussion. FIG. 6 UE 602 is further described, which can correspond to FIG. 1 and FIG. 3 UE 104. FIG. 6 Server 609 is further described, which may correspond to a UE, a Data Collection Application Function (DCAF), an Application Function (AF), an Application Server (AS), an Application Service Provider (ASP), and / or any other network entity or server. In some respects, server 609 is located (e.g., hosted) on a wireless communication network (e.g., FIG. 1 The server 609 is located within the wireless communication network 100, rather than outside of it. For example, the server 609 may be part of the 5GC 190. In some respects, the server 609 is hosted by a UE vendor or a third party within the wireless communication network.

[0111] Call flow 600 illustrates an example of how a server within a wireless communication network can provide configuration for data collection to the OAM within that wireless communication network to configure the UE and / or network entities to perform data collection.

[0112] At 611, server 609 transmits to OAM 610 a configuration for data collection by one or more UEs, along with information identifying those UEs. In some aspects, the information identifying the one or more UEs includes one or more identifiers of the one or more UEs (including UE 602) for which server 609 requests data collection. For example, the UE identifier may include one or more of the UE's SUPI, UE's IMEISV, or another (e.g., permanent) identifier assigned to the UE. The configuration for data collection may include information indicating one or more types of data (e.g., non-normalized data) to be collected by each of the one or more UEs, such as UE battery status, UE computing status (e.g., markings for measurement samples), Doppler spread as measured at the UE, delay spread as measured at the UE, UE resource constraints, other internal UE conditions, and other external UE conditions (e.g., radio environment, parameters for feature engineering), etc. In some aspects, the one or more types of data collected are based on a Service Level Agreement (SLA) between an operator, UE vendor, network vendor, etc.

[0113] In some aspects, at 611, as a supplement or alternative to transmitting configuration for data collection by one or more UEs, server 609 transmits to OAM 610 configuration for data collection by one or more network entities (such as RAN 604). In some aspects, server 609 further transmits to OAM 610 information identifying the one or more network entities. In some aspects, the information identifying the one or more network entities includes one or more identifiers of the one or more network entities (including RAN 604) for which server 609 requests data collection. In some aspects, the information identifying the one or more network entities includes information identifying the one or more UEs, such that any RAN entity serving the one or more UEs is identified by the information identifying the one or more UEs. In some aspects, the configuration for data collection by one or more network entities may include information indicating one or more types of data (e.g., non-normalized data) to be collected by each of the one or more network entities, such as data measured by the network or other data used to assist the UE, which may be referred to as auxiliary information, such as codebook indexes, antenna patterns, etc. In some aspects, the one or more types of data collected are based on SLAs such as those between operators, UE vendors, network vendors, etc.

[0114] In some aspects, server 609 will transmit at least a portion of the information transmitted at 611 as encrypted data (e.g., containerized data) (such as encrypted configuration for data collection) to OAM 610. Any suitable cryptographic technique can be used to encrypt and decrypt the data, such as public-key cryptography, symmetric cryptography, asymmetric cryptography, etc. The key and / or type of the cryptographic technique used may be distributed to the entity at manufacturing time via separate signaling (e.g., over-the-air updates). For example, if server 609 is located in a trusted domain of a wireless communication network, the encrypted data may be trusted. For example, configurations for data collection performed by one or more UEs and / or for data collection performed by one or more network entities may be encrypted. In some aspects, information identifying the one or more UEs and / or the one or more network entities may not be encrypted. As discussed, encrypting the configuration for data collection can keep the type of data collected confidential. Not encrypting the information identifying the one or more UEs and / or the one or more network entities allows the network to identify to which UEs and / or network entities the configuration for data collection is transmitted.

[0115] In some respects, an entity or multiple entities configured solely through the corresponding configuration for data collection (such as one or more UEs and / or one or more network entities) have the ability to access (e.g., decrypt) the corresponding configuration for data collection (e.g., have a decryption key) to maintain information security.

[0116] In some respects, server 609 transmits information from 611 as unencrypted (e.g., without containerization, such as plaintext) to OAM 610, where server 609 is not necessarily located in a trusted domain of the wireless communication network. Therefore, OAM 610 can verify / authorize the information (e.g., check if the configuration for data collection complies with the SLA) before further distributing it within the network, which can beneficially provide security against malicious configurations. In some such respects, OAM 610 (or another network entity, such as under the guidance of OAM 610) encrypts at least a portion of the information (e.g., the configuration for data collection by one or more UEs and / or the configuration for data collection by one or more network entities) before further distributing it within the network.

[0117] In some respects, instead of server 609 transmitting information at 611, the information transmitted at OAM 610 may be configured or pre-configured at OAM 610 in some other way (e.g., during manufacturing, in the air, etc.). In some such respects, server 609 transmits instructions to OAM 610 for initiating a tracing session based on information configured or pre-configured at OAM 610.

[0118] At position 612, OAM 610 sends a tracking activation message to UDM 608, similar to... FIG. 5 Unlike 512, at 612, OAM 610 transmits the information of 611 (i.e., encrypted configuration for data collection by one or more UEs, information identifying the one or more UEs, encrypted / unencrypted configuration for data collection by one or more network entities, and / or information identifying the one or more network entities) together with the tracking activation message (e.g., separately or as part of the tracking activation message). UDM 608 stores tracking control and configuration parameters as well as the information of 611.

[0119] At position 614, AMF 606 receives a registration request from RAN 604, similar to... FIG. 5 514, such as a request for UE 602 to register with the wireless communication network.

[0120] At point 616, such as in response to a registration request, similar to... FIG. 5 At 516, AMF 606 receives / retrieves tracking control and configuration parameters from UDM 608, such as by performing an SDM acquisition process using UDM 608. Unlike 516, at 616, AMF 606 also receives / retrieves information from UDM 608, such as information from 611, as part of the SDM acquisition process. Therefore, AMF 606 can store tracking control and configuration parameters as well as information from 611.

[0121] At point 618, similar to FIG. 5 At 518, AMF 606 initiates a tracking session based on received tracking control and configuration parameters, such as by transmitting a start tracking message to RAN 604. This start tracking message may include tracking control and configuration parameters. Unlike 518, at 618, AMF 606 may transmit the information of 611 to RAN 604, such as in a start tracking message or in a separate message. Therefore, RAN 504 may store the tracking control and configuration parameters, as well as the information of 611, and initiate a tracking session. In some aspects, instead of transmitting all the information of 611 to RAN 604, AMF 606 changes the information identifying the one or more UEs from one or more permanent identifiers of the one or more UEs (e.g., SUPI, IMEISV, etc.) to one or more temporary identifiers of the one or more UEs, and alternatively transmits the one or more temporary identifiers of the one or more UEs. By using the one or more temporary identifiers of the one or more UEs, more sensitive information (such as one or more permanent identifiers) can be masked to RAN 604.

[0122] In some respects, where the information in 611 includes an encrypted / unencrypted configuration for data collection by one or more network entities, RAN 604 (e.g., after decrypting the configuration for data collection by one or more network entities) is identified as performing data collection such as by means of information identifying the one or more network entities, and is then used to perform measurements of the data type indicated in the configuration for data collection by one or more network entities.

[0123] At position 620, similar to FIG. 5 In step 520, RAN 604 transmits an MDT configuration to UE 602 (and any other UE served by RAN 604, such as those identified in the information in step 611 by identifying the one or more UEs), instructing UE 602 to collect data. For example, the MDT configuration may include at least a portion of tracking control and configuration parameters. The MDT configuration may further include an encrypted configuration for data collection by the one or more UEs. Therefore, UE 602 stores at least a portion of the tracking control and configuration parameters, and / or the configuration for data collection by the one or more UEs (e.g., after UE 602 decrypts the encrypted configuration for data collection by the one or more UEs). Further, UE 602 begins collecting data, such as performing measurements corresponding to the data types indicated in the configuration for data collection by the one or more UEs. UE 602 may further transmit this data, such as as referenced herein. FIG. 12 to FIG. 14 Further discussion.

[0124] ASPECTS RELATED TO AMF-BASED DATA COLLECTION CONFIGURATION BY A NETWORK SERVER

[0125] FIG. 7 A call flow diagram illustrating a call flow 700 for performing a signaling-based MDT is depicted. FIG. 7 The OAM 710 is described, and the OAM can be FIG. 1 The functional components of 5GC 190. FIG. 7 The UDM 708 is further described, which corresponds to FIG. 1 UDM 196. FIG. 7 AMF 706 is further described, which corresponds to FIG. 1 AMF 192. FIG. 7 RAN entity 704 is further described, which may correspond to network entities, such as FIG. 1 and FIG. 3 BS 102 or as about FIG. 2 The decomposed base station under discussion. FIG. 7 UE 702 is further described, which can correspond to FIG. 1 and FIG. 3UE 104. FIG. 7 Server 709 is further described, which may correspond to a UE, DCAF, AF, AS, ASP, and / or any other network entity or server. In some respects, server 709 is located (e.g., hosted) on a wireless communication network (e.g., FIG. 1 The server 709 is located within the wireless communication network 100, rather than outside of it. For example, the server 709 may be part of the 5GC 190. In some respects, the server 709 is hosted by a UE vendor or a third party within the wireless communication network.

[0126] Call flow 700 illustrates an example of how a server within a wireless communication network can provide configuration for data collection to an AMF within that wireless communication network to configure a UE and / or network entity to perform data collection. Call flow 700 may be similar to... FIG. 6 Call flow 600, except that the encrypted / unencrypted configuration for data collection by one or more UEs, information identifying the one or more UEs, the encrypted / unencrypted configuration for data collection by one or more network entities, and / or information identifying the one or more network entities are transmitted to AMF 706 (instead of OAM 710), is configured or pre-configured at that AMF.

[0127] The call process 700 can be partially similar to FIG. 6 The call process is 600, and is partially similar to... FIG. 5 The call process is 500. Specifically, 711 can be similar to... FIG. 6 The call flow 611, except that server 709 transmits the information of 611 (encrypted / unencrypted configuration for data collection by one or more UEs, information identifying the one or more UEs, encrypted / unencrypted configuration for data collection by one or more network entities, and / or information identifying the one or more network entities) to AMF 706, or this information is configured or pre-configured at AMF 706 instead of OAM 710. Therefore, in some respects, similar to what has been discussed with respect to OAM 610, AMF 706 may encrypt or cause another entity to encrypt at least a portion of this information. Furthermore, 712, 714, and 716 are respectively similar to... FIG. 5 The numbers 512, 514, and 516. Furthermore, 718 is similar to... FIG. 6 For example, AMF 706 uses information from 711 (e.g., information similar to 611 as discussed) to begin (e.g., modify) a tracing session. Further, 720 is similar to... FIG. 6 620.

[0128] ASPECTS RELATED TO OAM-BASED DATA COLLECTION CONFIGURATION BY A NON-NETWORK SERVER

[0129] FIG. 8 A call flow diagram illustrating a call flow 800 for performing a signaling-based MDT is depicted. FIG. 8 The OAM 810 is described, which can be FIG. 1 The functional components of 5GC 190. FIG. 8 The UDM 808 is further described, which corresponds to FIG. 1 UDM 196. FIG. 8 AMF 806 is further described, which corresponds to FIG. 1 AMF 192. FIG. 8 RAN entity 804 is further described, which may correspond to network entities such as FIG. 1 and FIG. 3 BS 102 or as about FIG. 2 The decomposed base station under discussion. FIG. 8 UE 802 is further described, which can correspond to FIG. 1 and FIG. 3 UE 104. FIG. 8 Server 809 is further described, which may correspond to a UE, a third-party server outside the wireless communication network, an edge cloud, a UE vendor cloud, a network vendor cloud, a public cloud, a private cloud, and an OTT server, and / or any other server. In some respects, server 809 is located (e.g., hosted) on a wireless communication network (e.g., FIG. 1 The wireless communication network 100 is located outside of it, rather than inside it. FIG. 8 The Network Open Function (NEF) 807 is further described, which can be... FIG. 1 The 5GC 190's functional components. In some respects, the NEF 807 exposes core network capabilities (such as those of the 5GC 190) outside the wireless communication network, such as to third parties.

[0130] Call flow 800 illustrates an example of how a server outside a wireless communication network can provide configuration for data collection to the OAM within that wireless communication network to configure the UE and / or network entities to perform data collection. FIG. 6 The call process is 600.

[0131] Specifically, 811 can be similar to FIG. 6In call flow 611, in addition to server 809 transmitting information (e.g., unencrypted configuration for data collection by one or more UEs, information identifying the one or more UEs, unencrypted configuration for data collection by one or more network entities, and / or information identifying the one or more network entities) to NEF 807, this information may be configured or pre-configured at OAM 810, and server 809 may transmit an instruction to NEF 807 to initiate a tracking session, which is an example of an instruction to start data collection. Further, since server 809 is located outside the network, the configuration for data collection by one or more UEs and / or the configuration for data collection by one or more network entities may be transmitted as unencrypted data. Therefore, similar to OAM 610, NEF 807 may verify / authorize this information and further encrypt at least a portion of it.

[0132] At 812, if the unencrypted configuration for data collection by one or more UEs, information identifying the one or more UEs, the unencrypted configuration for data collection by one or more network entities, and / or the information identifying the one or more network entities are received from server 809, NEF 807 transmits the encrypted configuration for data collection by one or more UEs, information identifying the one or more UEs, and the encrypted configuration for data collection by one or more network entities, and / or the information identifying the one or more network entities, to OAM 810. At 812, if this information is configured or pre-configured at OAM 810 and server 809 transmits an instruction to NEF 807 to start a tracking session, NEF 807 transmits an instruction to OAM 810 to start a tracking session; this is an example of an instruction to begin data collection. At 815, NEF 807 transmits the following response to server 809: the unencrypted configuration for data collection by one or more UEs, information identifying the one or more UEs, the unencrypted configuration for data collection by one or more network entities, and / or the information identifying the one or more network entities were received from server 809. Furthermore, 813, 814, 816, 818, and 820 are respectively similar to FIG. 6 The numbers 612, 614, 616, 618, and 620.

[0133] ASPECTS RELATED TO AMF-BASED DATA COLLECTION CONFIGURATION BY A NON-NETWORK SERVER

[0134] FIG. 9 A call flow diagram illustrating a call flow 900 for performing a signaling-based MDT is depicted. FIG. 9 The OAM 910 is described, which can be FIG. 1 The functional components of 5GC 190. FIG. 9The UDM 908 is further described, which corresponds to FIG. 1 UDM 196. FIG. 9 AMF 906 is further described, which corresponds to FIG. 1 AMF 192. FIG. 9 RAN entity 904 is further described, which may correspond to network entities such as FIG. 1 and FIG. 3 BS 102 or as about FIG. 2 The decomposed base station under discussion. FIG. 9 UE 902 is further described, which can correspond to FIG. 1 and FIG. 3 UE 104. FIG. 9 Server 909 is further described, which may correspond to a UE, a third-party server outside the wireless communication network, an edge cloud, a UE vendor cloud, a network vendor cloud, a public cloud, a private cloud, and an OTT server, and / or any other server. In some respects, server 909 is located (e.g., hosted) on a wireless communication network (e.g., FIG. 1 The wireless communication network 100 is located outside of it, rather than inside it. FIG. 9 The NEF 907 was further described, and the NEF could be... FIG. 1 The functional components of 5GC 190.

[0135] Call flow 900 illustrates an example of how a server outside a wireless communication network can provide configuration for data collection to an AMF within that wireless communication network to configure the UE and / or network entities to perform data collection. Call flow 900 can be similar in some ways to... FIG. 8 The call process is 800, and in some way similar to... FIG. 7 The call flow 700 is as discussed.

[0136] Specifically, 911 can be similar to FIG. 8 Except when configured or pre-configured, this information is configured or pre-configured at AMF 906 instead of OAM 910.

[0137] At 912, if the unencrypted configuration for data collection by one or more UEs, information identifying the one or more UEs, the unencrypted configuration for data collection by one or more network entities, and / or information identifying the one or more network entities are received from server 909, NEF 907 transmits the encrypted configuration for data collection by one or more UEs, information identifying the one or more UEs, and encrypted configuration for data collection by one or more network entities, and / or information identifying the one or more network entities to AMF 906. At 912, if this information is configured or pre-configured at AMF 906 and server 909 transmits an instruction to NEF 907 to initiate a tracking session, NEF 907 transmits an instruction to AMF 906 to initiate a tracking session. In some aspects, at 912, an appropriate AMF or multiple AMFs (including AMF 906) are selected to transmit the aforementioned information from NEF 907 to the AMF or multiple AMFs. For example, information identifying one or more UEs can be used to determine which AMFs serve one or more UEs, and such AMFs can be selected to transmit the aforementioned information from NEF 907 to the AMF or multiple AMFs. In some respects, the selection of AMFs and / or communication from NEF 90y to the AMFs is accomplished individually or jointly by one or more of NEF 907, OAM 910, and / or UDM 908.

[0138] Furthermore, 914 and 915 can be respectively similar to FIG. 8 814 and 815. Furthermore, 918 and 920 can be similar to... FIG. 7 718 and 720.

[0139] ASPECTS RELATED TO MANAGEMENT-BASED MINIMIZATION OF DRIVE TEST (MDT)

[0140] FIG. 10 A call flow diagram illustrating a call flow 1000 for performing a management-based MDT is depicted. FIG. 10 OAM 1010 is described, which can be FIG. 1 The functional components of 5GC 190. FIG. 10 AMF 1006 is further described, which corresponds to FIG. 1 AMF 192. FIG. 10 RAN entity 1004 is further described, which may correspond to network entities, such as FIG. 1 and FIG. 3 BS 102 or as about FIG. 2 The decomposed base station under discussion. FIG. 10 UE 1002 is further described, which can correspond to FIG. 1 and FIG. 3UE 104.

[0141] As shown in the figure, at 1012, AMF 1006 transmits information identifying one or more UEs to RAN 1004. This information may include one or more identifiers of one or more PLMNs, such as one or more PLMNs that allow data collection. Therefore, this information identifies one or more UEs operating on / within that one or more PLMNs. For example, the information identifying one or more UEs may be transmitted in an initial context establishment request or handover request. RAN 1004 may store the information identifying one or more UEs, such as storing it as a UE context that allows managed MDT-based operations.

[0142] Furthermore, as shown at 1014, OAM 1010 transmits an MDT activation command to RAN 1004. The MDT activation command includes tracking control and configuration parameters, such as indications of parameters configured for UE data collection. The MDT activation command can activate a tracking session to configure UE 1002 to collect data, such as the standardized data discussed. RAN 1004 can store the tracking control and configuration parameters.

[0143] At 1016, RAN 1004 uses information identifying one or more UEs to select those UEs for data collection. For example, RAN 1004 may determine which UEs operate on one or more PLMNs identified in the information identifying one or more UEs. RAN 1004 may additionally or alternatively identify the one or more UEs based on additional information in tracking control and configuration parameters that may identify certain UE criteria, such that one or more UEs conforming to such UE criteria and / or located within one or more PLMNs identified in the information identifying one or more UEs are selected. In this example, at least UE 1002 is selected.

[0144] At 1018, RAN 1004 transmits MDT activation / configuration to UE 1002, instructing UE 1002 to collect data (e.g., normalized data). For example, MDT activation may include at least a portion of tracking control and configuration parameters. Therefore, UE 1002 stores this at least portion of the tracking control and configuration parameters and begins collecting data, such as performing measurements corresponding to that data.

[0145] ASPECTS RELATED TO DATA COLLECTION CONFIGURATION FOR MANAGEMENT-BASED MDT

[0146] FIG. 11 A call flow diagram illustrating a call flow 1100 for performing a management-based MDT is depicted. FIG. 11 OAM 1110 is described, which can be FIG. 1The functional components of 5GC 190. FIG. 11 AMF 1106 is further described, which corresponds to FIG. 1 AMF 192. FIG. 11 RAN entity 1104 is further described, which may correspond to network entities, such as FIG. 1 and FIG. 3 BS 102 or as about FIG. 2 The decomposed base station under discussion. FIG. 11 UE 1102 is further described, which can correspond to FIG. 1 and FIG. 3 UE 104.

[0147] Although FIG. 11 Not shown, such as before 1111, call flow 1100 may include, respectively, according to FIG. 6 to FIG. 9 Any of the call procedures 600 to 900 performs the following action: providing encrypted / unencrypted configuration for data collection by one or more UEs, information identifying the one or more UEs, encrypted / unencrypted configuration for data collection by one or more network entities, and / or information identifying the one or more network entities to OAM 1110 and / or AMF1106. For example, it may perform... FIG. 6 611. In another example, it is executable. FIG. 7 711. In another example, it is executable. FIG. 8 811 and 812. In another example, it is executable. FIG. 9 9 / 11 and 9 / 12. However, in some respects, with FIG. 6 to FIG. 9 The call flow 600 to 900 differs from the previous one, replacing the explicit identifier of one or more UEs with information that identifies the one or more UEs, which may instead include one or more identifiers of one or more providers (such as UE providers).

[0148] Further, as shown in the figure, at 1111, UE 1102 transmits UE vendor information to RAN 1104 that indicates the UE's vendor. In some respects, UE 1102 transmits UE vendor information as part of a connection establishment, connection reconstruction, recovery, or reconfiguration process (e.g., as part of one or more messages).

[0149] As shown in the figure, at 1112, AMF 1106 transmits one or more identifiers of one or more PLMNs (such as one or more PLMNs that allow data collection) to RAN 1104. For example, these one or more identifiers of the one or more PLMNs are transmitted in an initial context establishment request or handover request. In some aspects, at 1112, AMF 1106 transmits information identifying one or more UEs, such as one or more identifiers of one or more vendors, to RAN 1104 in the same or different messages. RAN 1104 may store these one or more identifiers of one or more PLMNs and one or more identifiers of one or more vendors. In some aspects, instead of AMF 1106 transmitting these one or more identifiers of one or more vendors to RAN 1104 at 1112, OAM 1110 transmits these one or more identifiers of one or more vendors to RAN 1104 at 1114. In some respects, at 1112, AMF 1106 transmits to RAN 1104, or alternatively at 1114, OAM 1110 transmits to RAN 1104, encryption configuration for data collection by one or more UEs, information identifying the one or more UEs, encryption configuration for data collection by one or more network entities, and / or information identifying the one or more network entities.

[0150] As shown at 1114, OAM 1110 transmits an MDT activation command to RAN 1104. The MDT activation command includes tracking control and configuration parameters, such as indications of parameters configured for UE data collection. The MDT activation command can activate a tracking session to configure UE 1102 for data collection. RAN 1104 can store the tracking control and configuration parameters. In some aspects, as discussed, the MDT activation command may include encrypted configurations for data collection by one or more UEs, information identifying the one or more UEs, encrypted configurations for data collection by one or more network entities, and / or information identifying the one or more network entities.

[0151] At 1116, RAN 1104 uses information identifying one or more UEs (e.g., one or more identifiers of one or more vendors) and, in some cases, one or more identifiers of one or more PLMNs to select the one or more UEs for data collection. For example, based on UE vendor information received at 1111 from one or more UEs (including UE 1102), RAN 1104 may select one or more UEs with UE vendor information matching the one or more identifiers of one or more vendors, such as one or more UEs manufactured by or otherwise associated with the one or more vendors. In some aspects, the one or more UEs are further identified as UEs operating on the one or more PLMNs. For example, the selected one or more UEs may be UEs that both operate on the one or more PLMNs and are associated with the one or more vendors. In this example, at least UE 1102 is selected.

[0152] In some respects, when RAN 1104 is provided with an encrypted / unencrypted configuration for data collection by one or more network entities, RAN 1104 (e.g., after decrypting the configuration for data collection by one or more network entities) is identified as performing data collection such as by means of information identifying the one or more network entities, and is then used to perform measurements of the data type indicated in the configuration for data collection by one or more network entities.

[0153] At 1118, RAN 1104 transmits MDT activation / configuration to UE 1102 (and any other UEs selected at 1116 and served by RAN 1104), instructing UE 1102 to collect data. For example, MDT activation may include at least a portion of tracking control and configuration parameters. MDT activation may further include an encrypted configuration for data collection by one or more UEs. Therefore, UE 1102 stores at least a portion of the tracking control and configuration parameters, and / or the configuration for data collection by one or more UEs (e.g., after UE 1102 decrypts the encrypted configuration for data collection by one or more UEs). Further, UE 1102 begins collecting data, such as performing measurements corresponding to the data types indicated in the configuration for data collection by one or more UEs.

[0154] ASPECTS RELATED TO REPORTING COLLECTED DATA

[0155] In some respects, as discussed, data collected by the UE and / or network entities, such as based on configurations for data collection by one or more UEs and / or configurations for data collection by one or more network entities, may be reported or transmitted back to the server (e.g., FIG. 6 to FIG. 9 The collected data may be transmitted end-to-end encrypted (e.g., containerized). In some aspects, the configuration for data collection by one or more UEs and / or for data collection by one or more network entities may include the address of the server, which can be used to report the collected data back to the server. In some aspects, the collected data is encrypted (e.g., by the UE and / or network entity) and transmitted to the server directly or via one or more additional entities.

[0156] In some respects, the UE can directly transmit the data collected by itself to a server, such as where the server is a Tracking Collection Entity (TCE) (which can be an entity of the wireless communication network, such as...). FIG. 1 (5GC 190). In some respects, a network entity may transmit data collected by it directly to a server, such as when the server is a TCE.

[0157] In some respects, a UE may transmit data collected by itself to another entity, such as a TCE. In other respects, a network entity may transmit data collected by itself to another entity, such as a TCE. A TCE may transmit data collected by the UE and / or a network entity to a server.

[0158] In some respects, a network entity may transmit data collected by it to a UE. A UE may transmit data collected by itself and data collected by the network entity to a server or to another entity (such as a TCE) that transmits the data collected by itself and the data collected by the network entity to the server. For example, a UE may establish a Packet Data Unit (PDU) session with a server based on the server's address in a configuration used for data collection by one or more UEs, and after establishing the PDU session, transmit the data collected by itself and the data collected by the network entity to the server.

[0159] FIG. 12 A call flow diagram illustrating a call flow 1200 for executing a report on the collected data is shown. FIG. 12 RAN entity 1204 is described, which can correspond to network entities such as FIG. 1 and FIG. 3 BS 102 or as about FIG. 2 The decomposed base station under discussion. FIG. 12UE 1202 is further described, which can correspond to FIG. 1 and FIG. 3 UE 104. FIG. 12 Server 1209 is further described, which can correspond to FIG. 6 to FIG. 9 Any of the servers 609 to 909. FIG. 12 TCE 1207 was further described.

[0160] At 1212, UE 1202 transmits (e.g., encrypted) data collected by UE 1202 to RAN 1204. At 1214, if RAN 1204 has data collected by RAN 1204, RAN 1204 combines the data collected by UE 1202 with the (e.g., encrypted) data collected by RAN 1204. At 1216, RAN 1204 transmits the data collected by UE 1202, and in some cases, the data collected by RAN 1204, to TCE 1207. In some aspects, TCE 1207 corresponds to server 1209. In some aspects, TCE 1207 is separate from server 1209, and therefore, at 1218, TCE 1207 transmits the data collected by UE 1202, and in some cases, the data collected by RAN 1204, to server 1209.

[0161] FIG. 13 A call flow diagram illustrating a call flow 1300 for executing a report on the collected data is depicted. FIG. 13 RAN entity 1304 is described, which can correspond to network entities such as FIG. 1 and FIG. 3 BS 102 or as about FIG. 2 The decomposed base station under discussion. FIG. 13 UE 1302 is further described, which can correspond to FIG. 1 and FIG. 3 UE 104. FIG. 13 Server 1309 is further described, which can correspond to FIG. 6 to FIG. 9 Any of the servers 609 to 909. FIG. 13 TCE 1307 was further described.

[0162] At 1312, RAN 1304 transmits (e.g., encrypted) data collected by RAN 1304 to UE 1302. At 1314, UE 1302 combines (e.g., encrypted) data collected by UE 1302 with additional data collected by RAN 1304. At 1316, UE 1302 transmits the data collected by UE 1302 and the additional data collected by RAN 1304 to TCE 1307. In some aspects, TCE 1307 corresponds to server 1309. In some aspects, TCE 1307 is separate from server 1309, and therefore, at 1318, TCE 1307 transmits the data collected by UE 1302 and the additional data collected by RAN 1304 to server 1309.

[0163] FIG. 14 A call flow diagram illustrating a call flow 1400 for executing a report on the collected data is depicted. FIG. 14 RAN entity 1404 is described, which can correspond to network entities such as FIG. 1 and FIG. 3 BS 102 or as about FIG. 2 The decomposed base station under discussion. FIG. 14 UE 1402 is further described, which can correspond to FIG. 1 and FIG. 3 UE 104. FIG. 14 Server 1409 is further described, which can correspond to FIG. 6 to FIG. 9 Any of the servers 609 to 909. FIG. 14 TCE 1407 was further described.

[0164] At 1412, UE 1402 transmits the data collected by UE 1402 to TCE 1407. At 1416, RAN 1404 transmits the data collected by RAN 1404 to TCE 1407. In some respects, TCE 1407 corresponds to server 1409. In other respects, TCE 1407 is separate from server 1409, and accordingly, at 1418, TCE 1407 transmits the data collected by UE 1402 and the data collected by RAN 1404 to server 1409.

[0165] ASPECTS RELATED TO DATA COLLECTION BY A DATA COLLECTION SERVICE WITH A DISCOVERY SERVICE

[0166] FIG. 15 A call flow diagram illustrating a call flow 1500 for performing data collection by a data collection service is depicted.

[0167] FIG. 15A data collection service 1509 is described, which can be FIG. 1 The 5GC 190 is a functional component. The data collection service 1509 can be a service or process running on one or more servers configured to collect data (e.g., one or more types of data). Although one data collection service is shown, additional data collection services (e.g., configured to collect different types of data) may exist. In some aspects, the data collection service 1509 is configured to implement SLAs between suppliers, operators, etc.

[0168] FIG. 15 The discovery service 1507 is further described, and this discovery service can be FIG. 1 The 5GC 190 is a functional component. The discovery service 1507 can be a service or process running on one or more servers, configured to, for example, provide the UE with information about a data collection service to allow the UE to connect to that data collection service.

[0169] FIG. 15 RAN entity 1504 is further described, which may correspond to network entities, such as FIG. 1 and FIG. 3 BS 102 or as about FIG. 2 The decomposed base station under discussion. FIG. 11 UE 1502 is further described, which can correspond to FIG. 1 and FIG. 3 UE 104.

[0170] Optionally, at 1512, the data collection service 1509 transmits information about itself to the discovery service 1507, such as routing information of the data collection service 1509, vendor information instructing a UE from a vendor to collect data, and instructions for the purpose of data collection (e.g., for ad hoc networks / MDT, for artificial intelligence or machine learning functions, for another artificial intelligence or machine learning function, for quality of experience, etc.). In some other aspects, instead of the data collection service 1509 transmitting information about itself to the discovery service 1507, information about itself can be configured or pre-configured at the discovery service 1507 in another manner.

[0171] At 1514, RAN 1504 transmits discovery service information about discovery service 1507 to UE 1502. The discovery service information may include routing information for discovery service 1507. In some aspects, the discovery service information is transmitted to UE 1502 in a System Information Block (SIB) or dedicated signaling. In some aspects, the discovery service information is broadcast by RAN 1504. In some aspects, the discovery service information is multicast by RAN 1504. In some aspects, the discovery service information is unicast by RAN 1504 (e.g., on demand).

[0172] At 1516, UE 1502 uses the routing information of discovery service 1507 to send a request to discovery service 1507 for information about one or more data collection services.

[0173] At 1518, in response to a request for information regarding one or more data collection services, discovery service 1507 transmits information about one or more data collection services to UE 1502, including information about data collection service 1509. In some aspects, UE 1502 determines which of the one or more data collection services it will communicate with based on the information about the data collection services. For example, UE 1502 may determine whether its vendor is the same as a vendor indicated by vendor information that a UE from that vendor will collect data included in the information about the data collection services. If UE 1502's vendor is the same as the vendor indicated by the vendor information, the UE may communicate with the data collection services. If UE 1502's vendor is different from the vendor indicated by the vendor information, the UE may not communicate with the data collection services.

[0174] At 1520, such as based on the determination to communicate with the data collection service 1509 as discussed, the UE 1502 transmits a connection establishment request to the data collection service 1509 to establish a connection with the data collection service 1509. In some aspects, the connection establishment request includes one or more of the following: vendor information indicating the vendor of the UE 1502, the identifier of the UE 1502, etc.

[0175] At 1522, in response to a connection establishment request, data collection service 1509 transmits a configuration for data collection to UE 1502, indicating one or more types of data the UE intends to collect. In some aspects, the one or more types of data the UE intends to collect are determined based on the vendor and / or identifier of UE 1502. In some aspects, UE 1502 begins collecting data, such as performing measurements corresponding to the data types indicated in the configuration for data collection. In some aspects, at 1522, data collection service 1509 further transmits a second configuration for data collection to RAN 1504, indicating one or more types of data the RAN 1504 intends to collect.

[0176] At 1524, UE 1502 transmits data to data collection service 1509 corresponding to one or more types of data indicated in a configuration for data collection, which indicates one or more types of data that the UE wants to collect.

[0177] In some respects, at 1524, RAN 1504 transmits to data collection service 1509 data corresponding to one or more types of data indicated in a second configuration for data collection, the second configuration indicating one or more types of data to be collected by RAN 1504.

[0178] In some respects, at 1524, RAN 1504 transmits to UE 1502 data corresponding to one or more types of data indicated in a second configuration for data collection, the second configuration indicating one or more types of data to be collected by RAN 1504, and UE 1502 includes such data in the data transmitted to data collection service 1509.

[0179] ASPECTS RELATED TO DATA COLLECTION BY A DATA COLLECTION SERVICE WITHOUT A DISCOVERY SERVICE

[0180] FIG. 16 A call flow diagram illustrating a call flow 1600 for performing data collection by a data collection service is depicted.

[0181] FIG. 16 A data collection service 1609 is described, which can be FIG. 1 The 5GC 190 is a functional component. Data collection service 1609 can be a service running on one or more servers configured to collect data (e.g., one or more types of data). Although one data collection service is shown, additional data collection services (e.g., configured to collect different types of data) may exist. In some aspects, data collection service 1609 is configured to implement SLAs between suppliers, operators, etc.

[0182] FIG. 16 RAN entity 1604 is further described, which may correspond to network entities such as FIG. 1 and FIG. 3 BS 102 or as about FIG. 2 The decomposed base station under discussion. FIG. 11 UE 1602 is further described, which can correspond to FIG. 1 and FIG. 3 UE 104.

[0183] At 1612, the data collection service 1609 transmits information about the data collection service 1609 to the RAN 1604, such as routing information of the data collection service 1609, supplier information instructing UEs from suppliers to collect data, and instructions for the purpose of collecting data (e.g., for self-organizing networks / MDT, for artificial intelligence or machine learning functions, for another artificial intelligence or machine learning function, for quality of experience, etc.).

[0184] At 1614, RAN 1604 transmits information to UE 1602 regarding one or more data collection services, including information regarding data collection service 1609. In some aspects, information regarding one or more data collection services is transmitted to UE 1502 in a System Information Block (SIB) or dedicated signaling. In some aspects, information regarding one or more data collection services is broadcast by RAN 1504. In some aspects, information regarding one or more data collection services is multicast by RAN 1504. In some aspects, information regarding one or more data collection services is unicast by RAN 1504 (e.g., on demand).

[0185] In some respects, UE 1602 determines which of the one or more data collection services it will communicate with based on information about those services. For example, UE 1602 may determine whether its vendor is the same as that indicated by vendor information, which specifies that a UE from that vendor will collect data included in the information about the data collection services. If UE 1602's vendor is the same as that indicated by the vendor information, the UE may communicate with the data collection services. If UE 1602's vendor is different from that indicated by the vendor information, the UE may not communicate with the data collection services.

[0186] At 1616, such as based on the determination to communicate with the data collection service 1609 as discussed, the UE 1602 transmits a connection establishment request to the data collection service 1609 to establish a connection with the data collection service 1609. In some aspects, the connection establishment request includes one or more of the following: vendor information indicating the vendor of the UE 1602, the identifier of the UE 1602, etc.

[0187] At 1618, in response to a connection establishment request, data collection service 1609 transmits a configuration for data collection to UE 1602, indicating one or more types of data the UE intends to collect. In some aspects, the one or more types of data the UE intends to collect are determined based on the vendor and / or identifier of UE 1602. In some aspects, UE 1602 begins collecting data, such as performing measurements corresponding to the data types indicated in the configuration for data collection. In some aspects, at 1618, data collection service 1609 further transmits a second configuration for data collection to RAN 1604, indicating one or more types of data the RAN 1604 intends to collect.

[0188] At 1620, UE 1602 transmits data to data collection service 1609 corresponding to one or more types of data indicated in a configuration for data collection, which indicates one or more types of data that the UE wants to collect.

[0189] In some respects, at 1620, RAN 1604 transmits to data collection service 1609 data corresponding to one or more types of data indicated in a second configuration for data collection, the second configuration indicating one or more types of data to be collected by RAN 1604.

[0190] In some respects, at 1620, RAN 1604 transmits to UE 1602 data corresponding to one or more types of data indicated in a second configuration for data collection, the second configuration indicating one or more types of data to be collected by RAN 1604, and UE 1602 includes such data in the data transmitted to data collection service 1609.

[0191] EXAMPLE OPERATION

[0192] FIG. 17 It shows a device (such as) FIG. 1 and FIG. 3 Method 1700 for wireless communication of UE 104.

[0193] Method 1700 begins at step 1705, wherein an encryption configuration for data collection is received, the encryption configuration indicating one or more types of data that the device intends to collect.

[0194] Then method 1700 proceeds to step 1710, where the encrypted configuration used for data collection is decrypted.

[0195] Then method 1700 proceeds to step 1715, in which data corresponding to the one or more types of data is transmitted.

[0196] In some respects, the data of one or more types may include one or more of the following: the device’s battery status; the device’s computing status; Doppler spread; or Doppler delay.

[0197] In some respects, step 1715 may include: encrypting the data; and transmitting the encrypted data.

[0198] In some respects, step 1715 may include transmitting the data to at least one of: a network entity; a tracking and collection entity; or a device outside of the wireless communication network in which the device operates.

[0199] In some aspects, method 1700 may further include receiving additional data from a network entity corresponding to data collected by the network entity. Step 1715 may include transmitting the data and the additional data.

[0200] In some respects, method 1700 may further include: transmitting the supplier information of the device to the network entity.

[0201] In some respects, step 1705 may include: receiving the encryption configuration from the network entity.

[0202] In some respects, method 1700 or any aspect thereof may be made by means of a device (such as...) FIG. 21 The communication device 2100 performs the method, which includes various components operable to, configured to, or adapted to perform the method 1700. The communication device 2100 is described in more detail below.

[0203] It should be noted that FIG. 17 This is merely one example of a method, and other methods consistent with this disclosure, including fewer, additional, or alternative steps, are possible and can be combined in any way to provide the foregoing aspects.

[0204] FIG. 18 It shows a device for use by one or more devices (such as FIG. 1 and FIG. 3 BS 102 or as about FIG. 2The method for wireless communication using the decomposed base station discussed in the article 1800.

[0205] Method 1800 begins at step 1805, wherein information identifying one or more UEs is received by a first device among the one or more devices.

[0206] Then method 1800 proceeds to step 1810, in which the first device transmits an encryption configuration for data collection to the one or more UEs, the encryption configuration indicating one or more types of data to be collected by each of the one or more UEs.

[0207] In some respects, the data of one or more types may include one or more of the following: battery status; computing status; Doppler expansion; or Doppler delay.

[0208] In some respects, method 1800 may further include: receiving a second configuration for data by the first device, the second configuration indicating one or more second types of data to be collected by the first device.

[0209] In some aspects, method 1800 may further include: transmitting data corresponding to the one or more second types of data by the first device to at least one of the following: at least one of the one or more UEs; a tracking collection entity; or a device outside the wireless communication network in which the first device operates.

[0210] In some respects, step 1810 may include: encrypting the data corresponding to the one or more second types of data by the first device; and transmitting the encrypted data.

[0211] In some aspects, the one or more devices may include a tracking and collection entity. Method 1800 may further include: receiving, by the tracking and collection entity, data corresponding to the one or more second types of data; and transmitting, by the tracking and collection entity, the data corresponding to the one or more second types of data to the device.

[0212] In some respects, method 1800 may further include: the first device receiving data corresponding to the one or more types of data from the one or more UEs.

[0213] In some respects, method 1800 may further include: transmitting by the first device the data corresponding to the one or more types of data to at least one of: a tracking collection entity; or a device outside of a wireless communication network in which the first device operates.

[0214] In some aspects, the one or more devices may include a tracking and collection entity. Method 1800 may further include: receiving, by the tracking and collection entity, data corresponding to the one or more types of data; and transmitting, by the tracking and collection entity, the data corresponding to the one or more types of data to the device.

[0215] In some respects, the information identifying the one or more UEs may include an explicit identifier for each of the one or more UEs.

[0216] In some aspects, the information identifying the one or more UEs may include one or more identifiers of one or more vendors. Method 1800 may further include: receiving corresponding vendor information for each of the one or more UEs, wherein each of the one or more UEs is associated with one of the one or more vendors.

[0217] In some respects, method 1800 may further include: receiving the cryptographic configuration for data collection from the server.

[0218] In some respects, method 1800 may further include: receiving the configuration for data collection from the server.

[0219] In some respects, method 1800 may further include: encrypting the configuration used for data collection.

[0220] In some aspects, the one or more devices may include an OAM, a UDM, or an AMF. The first device may include a radio access network entity. The method may further include: transmitting the encryption configuration for data collection from the OAM to the UDM; transmitting the encryption configuration for data collection from the UDM to the AMF; and transmitting the encryption configuration for data collection from the AMF to the first device.

[0221] In some respects, method 1800 may further include: the OAM receiving the cryptographic configuration for data collection from the server.

[0222] In some respects, method 1800 may further include: the OAM receiving the configuration for data collection from the server.

[0223] In some respects, method 1800 may further include: the configuration used for data collection encrypted by the OAM.

[0224] In some respects, method 1800 may further include: receiving one or more identifiers of the one or more UEs by the AMF.

[0225] In some aspects, method 1800 may further include: transmitting the information identifying the one or more UEs from the AMF to the first device. The information identifying the one or more UEs may include one or more second identifiers of the one or more UEs that are different from the one or more identifiers of the one or more UEs.

[0226] In some aspects, the one or more devices may include a NEF. Method 1800 may further include: receiving the configuration for data collection from a server by the NEF; encrypting the configuration for data collection by the NEF; and transmitting the encrypted configuration for data collection to the OAM by the NEF.

[0227] In some respects, the one or more devices may include a NEF. Method 1800 may further include: receiving an instruction to begin data collection from the NEF; and transmitting the instruction to begin data collection from the NEF to the OAM.

[0228] In some aspects, the one or more devices may include an AMF. The first device may include a radio access network entity. Method 1800 may further include: transmitting the encryption configuration for data collection from the AMF to the first device.

[0229] In some respects, method 1800 may further include: the AMF receiving the cryptographic configuration for data collection from the server.

[0230] In some respects, method 1800 may further include: the AMF receiving the configuration for data collection from the server.

[0231] In some respects, method 1800 may further include: the configuration used for data collection being encrypted by the AMF.

[0232] In some aspects, the one or more devices may include a NEF. Method 1800 may further include: receiving the configuration for data collection from a server by the NEF; encrypting the configuration for data collection by the NEF; and transmitting the encrypted configuration for data collection to the AMF by the NEF.

[0233] In some respects, the one or more devices may include a NEF. Method 1800 may further include: receiving an instruction to begin data collection from the NEF; and transmitting the instruction to begin data collection from the NEF to the AMF.

[0234] In some respects, method 1800 or any aspect thereof may be made by means of a device (such as...) FIG. 22 The communication device 2200 performs the method, which includes various components operable to, configured to, or adapted to perform the method 1800. The communication device 2200 is described in more detail below.

[0235] It should be noted that FIG. 18 This is merely one example of a method, and other methods consistent with this disclosure, including fewer, additional, or alternative steps, are possible and can be combined in any way to provide the foregoing aspects.

[0236] FIG. 19 It shows a device (such as) FIG. 1 and FIG. 3 Method 1900 for wireless communication of UE 104.

[0237] Method 1900 begins at step 1905, where information about the data collection service is received.

[0238] Method 1900 then proceeds to step 1910, wherein a configuration for data collection is received from the data collection service, the configuration indicating one or more types of data that the device wishes to collect.

[0239] Method 1900 then proceeds to step 1915, in which data corresponding to the one or more types of data is transmitted to the data collection service.

[0240] In some respects, the information regarding the data collection service may include one or more of the following: routing information for one or more data collection services including the data collection service; supplier information instructing a device from a supplier to collect data; or instructions for the purpose of collecting the data.

[0241] In some respects, method 1900 may further include receiving signaling that includes routing information for discovering services.

[0242] In some aspects, method 1900 may further include: transmitting a request to the discovery service for information about the data collection service. Receiving the information about the data collection service may include receiving the information about the data collection service from the discovery service.

[0243] In some respects, step 1905 may include: receiving information about the data collection service from a first device among one or more devices, either from an SIB or a dedicated signaling system.

[0244] In some respects, method 1900 may further include transmitting to the data collection service one or more of the following: supplier information indicating the supplier of the device; or the identifier of the device.

[0245] In some aspects, method 1900 may further include receiving additional data from a network entity corresponding to data collected by the network entity. Step 1915 may include transmitting the data and the additional data.

[0246] In some respects, method 1900 or any aspect thereof may be made by means of a device (such as...) FIG. 23 The communication device 2300 performs the method, which includes various components operable to, configured to, or adapted to perform the method 1900. The communication device 2300 is described in more detail below.

[0247] It should be noted that FIG. 19 This is merely one example of a method, and other methods consistent with this disclosure, including fewer, additional, or alternative steps, are possible and can be combined in any way to provide the foregoing aspects.

[0248] FIG. 20 It shows a device for use by one or more devices (such as FIG. 1 and FIG. 3 BS 102 or as about FIG. 2 The method for wireless communication using the decomposed base station discussed in 2000.

[0249] Method 2000 begins at step 2005, wherein a data collection service transmits a configuration for data collection to the UE, the configuration indicating one or more types of data to be collected by the UE, wherein the one or more devices include the data collection service.

[0250] Then method 2000 continues to step 2010, wherein the data collection service receives data from the UE corresponding to the one or more types of data.

[0251] In some aspects, method 2000 may further include: transmitting to the UE information about the data collection service, the information including one or more of the following: routing information of the data collection service; supplier information instructing the UE from a supplier to collect data; or an instruction for the purpose of collecting data.

[0252] In some aspects, the one or more devices may include a discovery service. Method 2000 may further include: transmitting signaling including routing information for the discovery service from the data collection service; and receiving a request from the UE at the discovery service for the information regarding the data collection service. Transmitting the information regarding the data collection service may include transmitting the information regarding the data collection service from the discovery service.

[0253] In some respects, transmitting information about the data collection service may include transmitting information about the data collection service in SIB or dedicated signaling from a first device among the one or more devices.

[0254] In some respects, method 2000 may further include: transmitting information about the data collection service from the data collection service to the first device.

[0255] In some aspects, method 2000 may further include: receiving one or more of the following from the UE by the data collection service: supplier information indicating the supplier of the UE; or the identifier of the UE.

[0256] In some aspects, method 2000 may further include: a first device among the one or more devices receiving a second configuration for data from the data collection service, the second configuration indicating one or more second types of data to be collected by the first device.

[0257] In some respects, method 2000 may further include: the first device transmitting data corresponding to the one or more second types of data to at least one of: the UE; or the data collection service.

[0258] In some respects, method 2000 or any aspect thereof may be made possible by means of a device (such as...) FIG. 24 The communication device 2400 performs the method, which includes various components operable to, configured to, or adapted to perform the method 2000. The communication device 2400 is described in more detail below.

[0259] It should be noted that FIG. 20 This is merely one example of a method, and other methods consistent with this disclosure, including fewer, additional, or alternative steps, are possible and can be combined in any way to provide the foregoing aspects.

[0260] EXAMPLE COMMUNICATION DEVICE

[0261] FIG. 21 Various aspects of the example communication device 2100 are described. In some aspects, the communication device 2100 is user equipment, such as those described above for... FIG. 1 and FIG. 3 The UE 104 described.

[0262] Communication device 2100 includes a processing system 2105 coupled to transceiver 2155 (e.g., transmitter and / or receiver). Transceiver 2155 is configured to transmit and receive signals for communication device 2100 via antenna 2160, such as the various signals described herein. Processing system 2105 may be configured to perform processing functions of communication device 2100, including processing signals received by communication device 2100 and / or to be transmitted by the communication device.

[0263] Processing system 2105 includes one or more processors 2110. In various aspects, the one or more processors 2110 may represent one or more of a receive processor 358, a transmit processor 364, a TX MIMO processor 366, and / or a controller / processor 380, as per [reference to...].FIG. 3 As described. One or more processors 2110 are coupled to a computer-readable medium / memory 2130 via a bus 2150. In some aspects, the computer-readable medium / memory 2130 is configured to store instructions (e.g., computer-executable code) that, when executed by one or more processors 2110, enable one or more processors 2110 to execute and cause the one or more processors to perform actions related to... FIG. 17 The described method 1700 or any aspect related to the method, including regarding FIG. 17 Any additional steps or sub-steps described; and regarding FIG. 19 The described method 1900 or any aspect related to the method, including regarding FIG. 19 Any additional steps or sub-steps described. Note that references to processors performing the functions of communication device 2100 may include one or more processors, such as those performing the functions of communication device 2100 in a distributed manner.

[0264] In the depicted example, computer-readable medium / memory 2130 stores code 2135 for receiving, code 2140 for decryption, and code 2145 for transmission. Processing of codes 2135-2145 enables communication device 2100 to execute and perform actions related to... FIG. 17 The described method 1700 or any aspect related to that method; and regarding FIG. 19 The method described in 1900 or any aspect thereof.

[0265] One or more processors 2110 include circuitry configured to implement (e.g., execute) code stored in computer-readable medium / memory 2130, including circuitry 2115 for receiving, circuitry 2120 for decryption, and circuitry 2125 for transmission. Processing using circuitry 2115-2125 enables communication device 2100 to execute and perform actions related to... FIG. 17 The described method 1700 or any aspect related to that method; and regarding FIG. 19 The method described in 1900 or any aspect thereof.

[0266] More generally, components used for conveying, sending, transmitting, or outputting for transmission may include FIG. 3 The UE104 illustrated includes a transceiver 354, an antenna 352, a transmit processor 364, a TX MIMO processor 366, and / or a controller / processor 380. FIG. 21 The transceiver 2155 and / or antenna 2160 of the communication device 2100 in the middle FIG. 21One or more processors 2110 of the communication device 2100. Components for transmitting, receiving, or acquiring may include... FIG. 3 The UE 104 illustrated includes a transceiver 354, an antenna 352, a receiver processor 358, and / or a controller / processor 380. FIG. 21 The transceiver 2155 and / or antenna 2160 of the communication device 2100 in the middle FIG. 21 One or more processors 2110 of the communication device 2100 in the middle.

[0267] FIG. 22 Various aspects of the example communication device 2200 are described. In some aspects, the communication device 2200 is a network entity, such as... FIG. 1 and FIG. 3 BS 102 or as about FIG. 2 The decomposed base station under discussion.

[0268] Communication device 2200 includes a processing system 2205 coupled to a transceiver 2255 (e.g., a transmitter and / or receiver) and / or a network interface 2265. The transceiver 2255 is configured to transmit and receive signals for communication device 2200 via an antenna 2260, such as various signals as described herein. The network interface 2265 is configured to transmit via a communication link (such as those described herein, etc.). FIG. 2 The described backhaul link, midhaul link, and / or fronthaul link are used to acquire and transmit signals for the communication device 2200. The processing system 2205 can be configured to perform the processing functions of the communication device 2200, including processing signals received by the communication device 2200 and / or to be transmitted by the communication device.

[0269] Processing system 2205 includes one or more processors 2210. In various aspects, the one or more processors 2210 may represent one or more of a receive processor 338, a transmit processor 320, a TX MIMO processor 330, and / or a controller / processor 340, as per [reference to...]. FIG. 3 As described. One or more processors 2210 are coupled to a computer-readable medium / memory 2230 via a bus 2250. In some aspects, the computer-readable medium / memory 2230 is configured to store instructions (e.g., computer-executable code) that, when executed by one or more processors 2210, enable one or more processors 2210 to execute and cause the one or more processors to perform actions related to... Figure 18 The described method 1800 or any aspect thereof, including relative to the method, Figure 18 Any additional steps or sub-steps described; and regarding Figure 20 The described method 2000 or any aspect related to the method, including regarding Figure 20Any additional steps or sub-steps described. Note that references to the processor of the communication device 2200 performing the function may include one or more processors of the communication device 2200, such as those performing the function in a distributed manner.

[0270] In the depicted example, computer-readable medium / memory 2230 stores code 2235 for receiving, code 2240 for transmitting, and code 2245 for encryption. Processing of codes 2235-2245 enables communication device 2200 to execute and perform actions related to... Figure 18 The described method 1800 or any aspect related to that method; and regarding Figure 20 The method described in 2000 or any aspect thereof.

[0271] One or more processors 2210 include circuitry configured to implement (e.g., execute) code stored in computer-readable medium / memory 2230, including circuitry 2215 for receiving, circuitry 2220 for transmitting, and circuitry 2225 for encryption. Processing using circuitry 2215-2225 enables communication device 2200 to execute and perform operations related to... Figure 18 The described method 1800 or any aspect related to that method; and regarding Figure 20 The method described in 2000 or any aspect thereof.

[0272] More generally, components used for conveying, sending, transmitting, or outputting for transmission may include Figure 3 The BS102 illustrated includes a transceiver 332, an antenna 334, a transmit processor 320, a TX MIMO processor 330, and / or a controller / processor 340. Figure 22 The transceiver 2255 and / or antenna 2260 of the communication device 2200 in the middle Figure 22 One or more processors 2210 of the communication device 2200. Components for transmitting, receiving, or acquiring may include... Figure 3 The BS 102 illustrated includes transceiver 332, antenna 334, receiver processor 338, and / or controller / processor 340. Figure 22 The transceiver 2255 and / or antenna 2260 of the communication device 2200 in the middle Figure 22 One or more processors 2210 of the communication device 2200 in the middle.

[0273] Figure 23 Various aspects of the example communication device 2300 are described. In some aspects, the communication device 2300 is user equipment, such as those described above. Figure 1 and Figure 3 The UE 104 described.

[0274] Communication device 2300 includes a processing system 2305 coupled to transceiver 2345 (e.g., transmitter and / or receiver). Transceiver 2345 is configured to transmit and receive signals for communication device 2300 via antenna 2350, such as the various signals described herein. Processing system 2305 may be configured to perform processing functions of communication device 2300, including processing signals received by communication device 2300 and / or to be transmitted by communication device.

[0275] Processing system 2305 includes one or more processors 2310. In various aspects, the one or more processors 2310 may represent one or more of a receive processor 358, a transmit processor 364, a TX MIMO processor 366, and / or a controller / processor 380, as per [reference to...]. Figure 3 As described. One or more processors 2310 are coupled to a computer-readable medium / memory 2325 via a bus 2340. In some aspects, the computer-readable medium / memory 2325 is configured to store instructions (e.g., computer-executable code) that, when executed by one or more processors 2310, enable one or more processors 2310 to execute and cause the one or more processors to perform actions related to... Figure 17 The described method 1700 or any aspect related to the method, including regarding Figure 17 Any additional steps or sub-steps described; and regarding Figure 19 The described method 1900 or any aspect related to the method, including regarding Figure 19 Any additional steps or sub-steps described. Note that references to processors performing the functions of communication device 2300 may include one or more processors, such as those performing the functions of communication device 2300 in a distributed manner.

[0276] In the depicted example, computer-readable medium / memory 2325 stores code 2330 for receiving and code 2335 for transmitting. Processing of codes 2330 and 2335 enables communication device 2300 to execute and perform actions related to... Figure 17 The described method 1700, or any aspect thereof; and regarding Figure 19 The method described in 1900 or any aspect thereof.

[0277] One or more processors 2310 include circuitry configured to implement (e.g., execute) code stored in a computer-readable medium / memory 2325, including circuitry 2315 for receiving and circuitry 2320 for transmitting. Processing using circuitry 2315 to 2320 enables communication device 2300 to execute and perform actions related to...Figure 17 The described method 1700, or any aspect thereof; and regarding Figure 19 The method described in 1900 or any aspect thereof.

[0278] More generally, components used for conveying, sending, transmitting, or outputting for transmission may include Figure 3 The UE104 illustrated includes a transceiver 354, an antenna 352, a transmit processor 364, a TX MIMO processor 366, and / or a controller / processor 380. Figure 23 The transceiver 2345 and / or antenna 2350 of the communication device 2300 in the middle. Figure 23 One or more processors 2310 of the communication device 2300. Components for transmitting, receiving, or acquiring may include... Figure 3 The UE 104 illustrated includes a transceiver 354, an antenna 352, a receiver processor 358, and / or a controller / processor 380. Figure 23 The transceiver 2345 and / or antenna 2350 of the communication device 2300 in the middle. Figure 23 One or more processors 2310 of the communication device 2300 in the middle.

[0279] Figure 24 Various aspects of the example communication device 2400 are described. In some aspects, the communication device 2400 is a network entity, such as... Figure 1 and Figure 3 BS 102 or as about Figure 2 The decomposed base station under discussion.

[0280] Communication device 2400 includes a processing system 2405 coupled to a transceiver 2445 (e.g., a transmitter and / or receiver) and / or a network interface 2455. The transceiver 2445 is configured to transmit and receive signals for communication device 2400 via antenna 2450, such as various signals as described herein. The network interface 2455 is configured to transmit via a communication link (such as those described herein, etc.). Figure 2 The described backhaul link, midhaul link, and / or fronthaul link are used to acquire and transmit signals for the communication device 2400. The processing system 2405 can be configured to perform the processing functions of the communication device 2400, including processing signals received by the communication device 2400 and / or to be transmitted by the communication device.

[0281] Processing system 2405 includes one or more processors 2410. In various aspects, the one or more processors 2410 may represent one or more of a receive processor 338, a transmit processor 320, a TX MIMO processor 330, and / or a controller / processor 340, as per [reference to...]. Figure 3As described. One or more processors 2410 are coupled to a computer-readable medium / memory 2425 via a bus 2440. In some aspects, the computer-readable medium / memory 2425 is configured to store instructions (e.g., computer-executable code) that, when executed by one or more processors 2410, enable one or more processors 2410 to execute and cause the one or more processors to perform actions related to... Figure 18 The described method 1800 or any aspect related to the method, including regarding Figure 18 Any additional steps or sub-steps described; and regarding Figure 20 The described method 2000 or any aspect related to the method, including regarding Figure 20 Any additional steps or sub-steps described. Note that references to the processor of the communication device 2400 performing the function may include one or more processors of the communication device 2400, such as those performing the function in a distributed manner.

[0282] In the depicted example, computer-readable medium / memory 2425 stores code 2430 for transmission and code 2435 for reception. Processing of codes 2430 and 2435 enables communication device 2400 to perform and allow the communication device to execute [specific actions]. Figure 18 The described method 1800, or any aspect thereof; and regarding Figure 20 The method described in 2000 or any aspect thereof.

[0283] One or more processors 2410 include circuitry configured to implement (e.g., execute) code stored in a computer-readable medium / memory 2425, the circuitry including circuitry 2415 for transmission and circuitry 2420 for reception. Processing using circuitry 2415 to 2420 enables communication device 2400 to perform and allow the communication device to perform actions related to… Figure 18 The described method 1800, or any aspect thereof; and regarding Figure 20 The method described in 2000 or any aspect thereof.

[0284] More generally, components used for conveying, sending, transmitting, or outputting for transmission may include Figure 3 The BS102 illustrated includes a transceiver 332, an antenna 334, a transmit processor 320, a TX MIMO processor 330, and / or a controller / processor 340. Figure 24 The transceiver 2445 and / or antenna 2450 of the communication device 2400 in the middle. Figure 24 One or more processors 2410 of the communication device 2400. Components for transmitting, receiving, or acquiring may include... Figure 3The BS 102 illustrated includes transceiver 332, antenna 334, receiver processor 338, and / or controller / processor 340. Figure 24 The transceiver 2445 and / or antenna 2450 of the communication device 2400 in the middle. Figure 24 One or more processors 2410 of the communication device 2400 in the middle.

[0285] Example Clause

[0286] Specific implementation examples are described in the following numbered clauses: Clause 1: A method for wireless communication by a device, the method comprising: receiving an encryption configuration for data collection, the encryption configuration indicating one or more types of data to be collected by the device; decrypting the encryption configuration for data collection; and transmitting data corresponding to the one or more types of data.

[0287] Clause 2: According to the method described in Clause 1, the one or more types of data include one or more of the following: the battery state of the device; the computing state of the device; Doppler spread; or Doppler delay.

[0288] Clause 3: The method according to any one of Clauses 1 to 2, wherein transmitting the data comprises: encrypting the data; and transmitting the encrypted data.

[0289] Clause 4: The method according to any one of Clauses 1 to 3, wherein transmitting the data comprises: transmitting the data to at least one of: a network entity; a tracking and collection entity; or a device outside of a wireless communication network in which the device operates.

[0290] Clause 5: The method according to any one of Clauses 1 to 4, the method further comprising receiving additional data from a network entity corresponding to data collected by the network entity, wherein transmitting the data comprises: transmitting the data and the additional data.

[0291] Clause 6: The method according to any one of Clauses 1 to 5, the method further comprising: transmitting supplier information of the device to a network entity.

[0292] Clause 7: The method according to any one of Clauses 1 to 6, wherein receiving the encryption configuration comprises: receiving the encryption configuration from a network entity.

[0293] Clause 8: A method for wireless communication by one or more devices, the method comprising: receiving, by a first device of the one or more devices, information identifying one or more UEs; and transmitting, by the first device, an encryption configuration for data collection to the one or more UEs, the encryption configuration indicating one or more types of data to be collected by each of the one or more UEs.

[0294] Clause 9: The method described in Clause 8, wherein the one or more types of data include one or more of the following: battery state; computing state; Doppler spread; or Doppler delay.

[0295] Clause 10: The method according to any one of Clauses 8 to 9, the method further comprising: receiving by the first device a second configuration for data, the second configuration indicating one or more second types of data to be collected by the first device; and transmitting by the first device data corresponding to the one or more second types of data to at least one of: at least one of the one or more UEs; a tracking collection entity; or a device outside of a wireless communication network in which the first device operates.

[0296] Clause 11: The method according to Clause 10, wherein transmitting the data comprises: encrypting the data corresponding to the one or more second types of data by the first device; and transmitting the encrypted data.

[0297] Clause 12: The method according to Clause 10, wherein the one or more devices include the tracking collection entity, and wherein the method further includes: receiving, by the tracking collection entity, the data corresponding to the one or more second types of data; and transmitting, by the tracking collection entity, the data corresponding to the one or more second types of data to the device.

[0298] Clause 13: The method according to any one of Clauses 8 to 12, the method further comprising: receiving data corresponding to the one or more types of data from the one or more UEs by the first device; and transmitting the data corresponding to the one or more types of data to at least one of: a tracking collection entity; or a device outside of a wireless communication network in which the first device operates.

[0299] Clause 14: The method according to Clause 13, wherein the one or more devices include the tracking collection entity, and wherein the method further includes: receiving, by the tracking collection entity, the data corresponding to the one or more types of data; and transmitting, by the tracking collection entity, the data corresponding to the one or more types of data to the device.

[0300] Clause 15: The method according to any one of Clauses 8 to 14, wherein the information identifying the one or more UEs includes an explicit identifier for each of the one or more UEs.

[0301] Clause 16: The method according to any one of Clauses 8 to 15, wherein the information identifying the one or more UEs includes one or more identifiers of one or more vendors, and wherein the method further includes: receiving corresponding vendor information of each of the one or more UEs, wherein each of the one or more UEs is associated with one of the one or more vendors.

[0302] Clause 17: The method according to any one of Clauses 8 to 16, the method further comprising: receiving the cryptographic configuration for data collection from the server.

[0303] Clause 18: The method according to any one of Clauses 8 to 17, the method further comprising: receiving the configuration for data collection from a server; and encrypting the configuration for data collection.

[0304] Clause 19: The method according to any one of Clauses 8 to 18, wherein the one or more devices include OAM, UDM, AMF, wherein the first device includes a radio access network entity, and wherein the method further includes: transmitting the encryption configuration for data collection from the OAM to the UDM; transmitting the encryption configuration for data collection from the UDM to the AMF; and transmitting the encryption configuration for data collection from the AMF to the first device.

[0305] Clause 20: The method according to Clause 19 further includes: the OAM receiving the cryptographic configuration for data collection from the server.

[0306] Clause 21: The method according to Clause 19 further includes: receiving the configuration for data collection from the server by the OAM; and encrypting the configuration for data collection by the OAM.

[0307] Clause 22: The method according to Clause 19 further comprises: receiving one or more identifiers of the one or more UEs by the AMF; and transmitting the information identifying the one or more UEs to the first device by the AMF, wherein the information identifying the one or more UEs includes one or more second identifiers of the one or more UEs that are different from the one or more identifiers of the one or more UEs.

[0308] Clause 23: The method according to Clause 19, wherein the one or more devices include a NEF, and wherein the method further comprises: receiving, by the NEF, the configuration for data collection from a server; encrypting, by the NEF, the configuration for data collection; and transmitting, by the NEF, the encrypted configuration for data collection to the OAM.

[0309] Clause 24: The method according to Clause 19, wherein the one or more devices include a NEF, and wherein the method further includes: receiving an instruction to start data collection by the NEF; and transmitting the instruction to start data collection by the NEF to the OAM.

[0310] Clause 25: The method according to any one of Clauses 8 to 24, wherein the one or more devices include an AMF, wherein the first device includes a radio access network entity, and wherein the method further includes: transmitting the encryption configuration for data collection from the AMF to the first device.

[0311] Clause 26: The method according to Clause 25 further includes: the AMF receiving the cryptographic configuration for data collection from the server.

[0312] Clause 27: The method according to Clause 25 further includes: receiving the configuration for data collection from the server by the AMF; and encrypting the configuration for data collection by the AMF.

[0313] Clause 28: The method according to Clause 25, wherein the one or more devices include a NEF, and wherein the method further comprises: receiving, by the NEF, the configuration for data collection from a server; encrypting, by the NEF, the configuration for data collection; and transmitting, by the NEF, the encrypted configuration for data collection to the AMF.

[0314] Clause 29: The method according to Clause 25, wherein the one or more devices include a NEF, and wherein the method further includes: receiving an instruction to begin data collection by the NEF; and transmitting the instruction to begin data collection by the NEF to the AMF.

[0315] Clause 30: A method for wireless communication by a device, the method comprising: receiving information about a data collection service; receiving from the data collection service a configuration for data collection, the configuration indicating one or more types of data to be collected by the device; and transmitting to the data collection service data corresponding to the one or more types of data.

[0316] Clause 31: The method according to Clause 30, wherein the information regarding the data collection service includes one or more of the following: routing information for one or more data collection services including the data collection service; supplier information instructing a device from a supplier to collect data; or instructions for the purpose of collecting data.

[0317] Clause 32: The method according to any one of Clauses 30 to 31, the method further comprising: receiving signaling including routing information for a discovery service; and transmitting to the discovery service a request for information regarding the data collection service, wherein receiving the information regarding the data collection service includes receiving the information regarding the data collection service from the discovery service.

[0318] Clause 33: The method according to any one of Clauses 30 to 32, wherein receiving the information about the data collection service includes receiving the information about the data collection service from a first device of the one or more devices in SIB or dedicated signaling.

[0319] Clause 34: The method according to any one of Clauses 30 to 33 further comprises: transmitting to the data collection service one or more of the following: supplier information indicating the supplier of the device; or the identifier of the device.

[0320] Clause 35: The method according to any one of Clauses 30 to 34, the method further comprising receiving additional data from a network entity corresponding to data collected by the network entity, wherein transmitting the data includes transmitting the data and the additional data.

[0321] Clause 36: A method for wireless communication by one or more devices, the method comprising: transmitting a configuration for data collection to a UE by a data collection service, the configuration indicating one or more types of data to be collected by the UE, wherein the one or more devices include the data collection service; and receiving data corresponding to the one or more types of data from the UE by the data collection service.

[0322] Clause 37: The method according to Clause 36 further comprises: transmitting to the UE information about the data collection service, the information including one or more of the following: routing information of the data collection service; supplier information instructing the UE from a supplier to collect data; or an instruction for the purpose of collecting data.

[0323] Clause 38: The method according to Clause 37, wherein the one or more means include a discovery service, and wherein the method further includes: transmitting signaling including routing information for the discovery service by the data collection service; and receiving a request from the UE at the discovery service for information about the data collection service, wherein transmitting the information about the data collection service includes transmitting the information about the data collection service from the discovery service.

[0324] Clause 39: The method according to Clause 37, wherein transmitting the information about the data collection service includes transmitting the information about the data collection service in SIB or dedicated signaling from a first device of the one or more devices.

[0325] Clause 40: The method according to Clause 39 further includes: transmitting the information about the data collection service from the data collection service to the first device.

[0326] Clause 41: The method according to any one of Clauses 36 to 40, the method further comprising: receiving from the UE one or more of the following by the data collection service: supplier information indicating the supplier of the UE; or the identifier of the UE.

[0327] Clause 42: The method according to any one of Clauses 36 to 41, the method further comprising: receiving, by a first device of the one or more devices, a second configuration for data from the data collection service, the second configuration indicating one or more second types of data to be collected by the first device; and transmitting, by the first device, data corresponding to the one or more second types of data to at least one of: the UE; or the data collection service.

[0328] Clause 43: One or more apparatuses comprising: one or more memories including executable instructions; and one or more processors configured to execute the executable instructions and cause the one or more apparatuses to perform the method according to any one of Clauses 1 to 42.

[0329] Clause 44: One or more apparatuses, said apparatuses comprising components for performing the method according to any one of Clauses 1 to 42.

[0330] Clause 45: One or more non-transitory computer-readable media, the one or more non-transitory computer-readable media comprising executable instructions that, when executed by one or more processors of one or more devices, cause the one or more devices to perform the method according to any one of Clauses 1 to 42.

[0331] Clause 46: One or more computer program products embodied on one or more computer-readable storage media, said one or more computer-readable storage media including code for performing the method according to any one of Clauses 1 to 42.

[0332] Additional Notes

[0333] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. The examples discussed herein do not limit the scope, applicability, or aspects set forth in the claims. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. For example, the function and arrangement of the elements discussed may be changed without departing from the scope of this disclosure. Various processes or components may be omitted, substituted, or added as appropriate in various examples. For example, the described methods may be performed in a different order than described, and various actions may be added, omitted, or combined. Furthermore, features described with respect to some examples may be combined in some other examples. For example, any number of aspects set forth herein may be used to implement an apparatus or practice. Moreover, the scope of this disclosure is intended to cover such apparatuses or methods practiced using other structures, functionalities, or structures and functionalities that complement or replace the various aspects of this disclosure set forth herein. It should be understood that any aspect of the disclosure herein may be embodied by one or more elements of these claims.

[0334] The various exemplary logic blocks, modules, and circuits described in this disclosure can be implemented or executed using a general-purpose processor, digital signal processor (DSP), ASIC, field-programmable gate array (FPGA) or other programmable logic device (PLD), discrete gate or transistor logic device, discrete hardware component, or any combination thereof designed to perform the functions described herein. While the general-purpose processor may be a microprocessor, in alternative embodiments, the processor may be any commercially available processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors working in conjunction with a DSP core, a system-on-a-chip (SoC), or any other such configuration.

[0335] As used in this article, the phrase “at least one of” in a list of items refers to any combination of these entries, including a single member. As an example, “at least one of a, b, or c” is intended to cover: a, b, c, ab, ac, bc, and abc, as well as any combination with multiple identical elements (e.g., aa, aaa, aab, aac, abb, acc, bb, bbb, bbb, bbc, cc, and ccc, or any other ordering of a, b, and c).

[0336] As used herein, the term "determine" encompasses a wide variety of actions. For example, "determine" can include calculation, operation, processing, deduction, investigation, lookup (e.g., searching in a table, database, or other data structure), assertion, and so on. Additionally, "determine" can include receiving (e.g., receiving information), accessing (e.g., accessing data in memory), and so on. Furthermore, "determine" can include parsing, selecting, picking, building, and so on.

[0337] As used herein, unless otherwise stated, “coupled to” and “coupled with” generally encompass both direct and indirect coupling (e.g., including intermediate aspects of coupling). For example, stating that a processor is coupled to memory allows for direct coupling or coupling via an intermediate aspect such as a bus.

[0338] The methods disclosed herein include one or more actions for implementing the methods. These actions may be interchanged without departing from the scope of the claims. In other words, unless a specific order of actions is specified, the order and / or use of specific actions may be modified without departing from the scope of the claims. Furthermore, the various operations of the methods described above may be performed by any suitable component capable of performing the corresponding function. This component may include various hardware and / or software components and / or modules, including but not limited to circuits, application-specific integrated circuits (ASICs), or processors.

[0339] The following claims are not intended to be limited to the aspects shown herein, but should be given the full scope consistent with the language of the claims. References to elements in the singular form are not intended to mean “only one” (unless specifically stated otherwise), but rather “one or more”. For example, unless specifically stated otherwise, references to elements (e.g., “processor,” “controller,” “memory,” etc.) should be understood to mean one or more elements (e.g., “one or more processors,” “one or more controllers,” “one or more memories,” etc.). The terms “set” and “group” are intended to include one or more elements and may be used interchangeably with “one or more.” In the case of references to one or more elements performing a function (e.g., steps of a method), one element may perform all the functions, or more than one element may perform these functions collectively. When more than one element performs these functions collectively, each function does not need to be performed by every single element (e.g., different functions may be performed by different elements), and / or each function does not need to be performed by only one element overall (e.g., different elements may perform different sub-functions of a function). Similarly, when referring to one or more elements configured to cause another element (e.g., a device) to perform a function, one element may be configured to cause the other element to perform all functions, or more than one element may be collectively configured to cause the other element to perform those functions. Unless otherwise specifically stated, the term "some" refers to one or more. All structural and functional equivalents of the elements of the various aspects described throughout this disclosure that are currently or hereafter known to those skilled in the art are intended to be covered by the claims. Furthermore, nothing disclosed herein is intended to be offered to the public, whether or not such disclosure is explicitly stated in the claims.

Claims

1. An apparatus configured for wireless communication, the apparatus comprising: One or more memories, the one or more memories including processor-executable instructions; and one or more processors, said one or more processors being configured to execute processor-executable instructions and cause the device to: Receive an encryption configuration for data collection, the encryption configuration indicating one or more types of data that the device intends to collect; Decrypt the encryption configuration used for data collection; as well as Transmit data corresponding to the one or more types of data.

2. The apparatus of claim 1, wherein the one or more types of data include one or more of the following: The battery status of the device; The calculation status of the device; Doppler extension; or Doppler delay.

3. The apparatus according to claim 1, wherein, In order to transmit the data, the one or more processors are configured to execute processor-executable instructions and cause the device to: Encrypt the data; and Transmit encrypted data.

4. The apparatus according to claim 1, wherein, In order to transmit the data, the one or more processors are configured to execute processor-executable instructions and cause the device to: The data shall be transmitted to at least one of the following: Network entities; Track and collect entities; or The device is a device outside of a wireless communication network that operates within it.

5. The apparatus according to claim 1, wherein: The one or more processors are configured to execute processor-executable instructions and cause the device to: Receive additional data from the network entity corresponding to the data collected by the network entity; and In order to transmit the data, the one or more processors are configured to execute processor-executable instructions and cause the device to: Transmit the data and the additional data.

6. The apparatus of claim 1, wherein the one or more processors are configured to execute processor-executable instructions and cause the apparatus to: The supplier information of the device is transmitted to the network entity.

7. The apparatus according to claim 1, wherein, In order to receive the encryption configuration, the one or more processors are configured to execute processor-executable instructions and cause the device to: Receive the encryption configuration from the network entity.

8. One or more means configured for wireless communication, said means comprising: One or more memories, the one or more memories including processor-executable instructions; and one or more processors, said one or more processors being configured to execute processor-executable instructions and cause said one or more means: The first device among the one or more devices receives information identifying one or more user equipment (UE); as well as The first device transmits an encryption configuration for data collection to the one or more UEs, the encryption configuration indicating one or more types of data to be collected by each of the one or more UEs.

9. The apparatus of claim 8 or more, wherein the one or more types of data include one or more of the following: Battery status; Calculation status; Doppler extension; or Doppler delay.

10. One or more apparatuses according to claim 8, wherein the one or more processors are configured to execute processor-executable instructions and cause the one or more apparatuses to: The first device receives a second configuration for data, the second configuration indicating one or more second types of data that the first device wants to collect; and The first device transmits data corresponding to one or more of the second types of data to at least one of the following: At least one of the one or more UEs; Track and collect entities; or The first device is a device outside of a wireless communication network in which it operates.

11. One or more devices according to claim 10, wherein, In order to transmit the data, the one or more processors are configured to execute processor-executable instructions and cause the one or more devices to: The data corresponding to one or more second types of data is encrypted by the first device; and Transmit encrypted data.

12. The apparatus of claim 10, wherein the apparatus includes the tracking and collection entity, and wherein the processor is configured to execute processor-executable instructions and cause the apparatus to: The tracking and collecting entity receives the data corresponding to the one or more second types of data; and The tracking and collecting entity transmits the data corresponding to the one or more second types of data to the device.

13. One or more apparatuses according to claim 8, wherein the one or more processors are configured to execute processor-executable instructions and cause the one or more apparatuses to: The first device receives data corresponding to the one or more types of data from the one or more UEs; and The first device transmits the data corresponding to the one or more types of data to at least one of the following: Track and collect entities; or The first device is a device outside of a wireless communication network in which it operates.

14. The apparatus of claim 13, wherein the apparatus includes the tracking and collection entity, and wherein the processor is configured to execute processor-executable instructions and cause the apparatus to: The tracking and collection entity receives the data corresponding to the one or more types of data; and The tracking and collection entity transmits the data corresponding to the one or more types of data to the device.

15. One or more apparatuses according to claim 8, wherein the information identifying the one or more UEs includes an explicit identifier for each of the one or more UEs.

16. One or more devices according to claim 8, wherein: The information identifying the one or more UEs includes one or more identifiers from one or more vendors; and The one or more processors are configured to execute processor-executable instructions and to enable the one or more devices: Receive corresponding vendor information for each of the one or more UEs, wherein each of the one or more UEs is associated with one of the one or more vendors.

17. One or more apparatuses according to claim 8, wherein the one or more processors are configured to execute processor-executable instructions and cause the one or more apparatuses to: Receive the encryption configuration for data collection from the server.

18. One or more apparatuses according to claim 8, wherein the one or more processors are configured to execute processor-executable instructions and cause the one or more apparatuses to: Receive the configuration for data collection from the server; and The configuration used for data collection is encrypted.

19. One or more devices according to claim 8, wherein: The one or more devices include Operation, Administration and Maintenance (OAM), Unified Data Management (UDM), and Access and Mobility Functions (AMF); The first device includes a radio access network entity; and The one or more processors are configured to execute processor-executable instructions and to enable the one or more devices: The OAM transmits the encryption configuration for data collection to the UDM; The UDM transmits the encryption configuration for data collection to the AMF; as well as The encryption configuration for data collection is transmitted from the AMF to the first device.

20. The apparatus of claim 19, wherein the one or more processors are configured to execute processor-executable instructions and cause the one or more apparatuses to: The OAM receives the encryption configuration for data collection from the server.

21. The apparatus of claim 19, wherein the one or more processors are configured to execute processor-executable instructions and cause the one or more apparatuses to: The configuration for data collection is received by the OAM from the server; and The configuration used for data collection is encrypted by the OAM.

22. The apparatus of claim 19, wherein the one or more processors are configured to execute processor-executable instructions and cause the one or more apparatuses to: The AMF receives one or more identifiers from the one or more UEs; and The AMF transmits the information identifying the one or more UEs to the first device, wherein the information identifying the one or more UEs includes one or more second identifiers of the one or more UEs that are different from the one or more identifiers of the one or more UEs.

23. The apparatus of claim 19, wherein the apparatus includes a Network Open Function (NEF), and wherein the processor is configured to execute processor-executable instructions and cause the apparatus to: The NEF receives the configuration for data collection from the server; The configuration used for data collection is encrypted by the NEF; as well as The NEF transmits the encryption configuration for data collection to the OAM.

24. The apparatus of claim 19, wherein the apparatus includes a Network Open Function (NEF), and wherein the processor is configured to execute processor-executable instructions and cause the apparatus to: The NEF receives an instruction to begin data collection; and The NEF transmits the instruction to the OAM to begin data collection.

25. One or more devices according to claim 8, wherein: The one or more devices include Access and Mobility Functions (AMF); The first device includes a radio access network entity; and The one or more processors are configured to execute processor-executable instructions and to enable the one or more devices: The encryption configuration for data collection is transmitted from the AMF to the first device.

26. The apparatus of claim 25, wherein the one or more processors are configured to execute processor-executable instructions and cause the one or more apparatuses to: The AMF receives the encryption configuration for data collection from the server.

27. The apparatus of claim 25, wherein the one or more processors are configured to execute processor-executable instructions and cause the one or more apparatuses to: The AMF receives the configuration for data collection from the server; and The configuration used for data collection is encrypted by the AMF.

28. The apparatus of claim 25, wherein the apparatus includes a Network Open Function (NEF), and wherein the processor is configured to execute processor-executable instructions and cause the apparatus to: The NEF receives the configuration for data collection from the server; The configuration used for data collection is encrypted by the NEF; and The NEF transmits the encryption configuration for data collection to the AMF.

29. The apparatus of claim 25, wherein the apparatus includes a Network Open Function (NEF), and wherein the processor is configured to execute processor-executable instructions and cause the apparatus to: The NEF receives an instruction to begin data collection; and The NEF transmits the instruction to the AMF to begin data collection.

30. An apparatus configured for wireless communication, the apparatus comprising: One or more memories, the one or more memories including processor-executable instructions; and one or more processors, said one or more processors being configured to execute processor-executable instructions and cause the device to: Receive information about data collection services; The device receives a configuration for data collection from the data collection service, the configuration indicating one or more types of data to be collected. as well as Transmit data corresponding to the one or more types of data to the data collection service.

31. The apparatus of claim 30, wherein the information regarding the data collection service includes one or more of the following: This includes routing information for one or more data collection services, including the data collection service itself. Supplier information indicating that the device from the supplier will collect data; or Instructions for the purpose of collecting data.

32. The apparatus of claim 30, wherein the one or more processors are configured to execute processor-executable instructions and cause the apparatus to: Receive signaling including routing information for service discovery; and A request for information regarding the data collection service is transmitted to the discovery service, wherein, In order to receive the information about the data collection service, the one or more processors are configured to execute processor-executable instructions and cause the device to receive the information about the data collection service from the discovery service.

33. The apparatus of claim 30, wherein, in order to receive the information regarding the data collection service, the one or more processors are configured to execute processor-executable instructions and cause the apparatus to receive the information regarding the data collection service from another apparatus in a System Information Block (SIB) or dedicated signaling.

34. The apparatus of claim 30, wherein the one or more processors are configured to execute processor-executable instructions and cause the apparatus to: Send one or more of the following to the data collection service: Supplier information indicating the supplier of the device; or The identifier of the device.

35. The apparatus of claim 30, wherein the one or more processors are configured to execute processor-executable instructions and cause the apparatus to receive additional data from a network entity corresponding to data collected by the network entity, and wherein, In order to transmit the data, the one or more processors are configured to execute processor-executable instructions and cause the device to transmit the data and the additional data.

36. One or more means configured for wireless communication, the means comprising: One or more memories, the one or more memories including processor-executable instructions; and one or more processors, said one or more processors being configured to execute processor-executable instructions and cause said one or more means: A data collection service transmits a configuration for data collection to a user equipment (UE), the configuration indicating one or more types of data to be collected by the UE, wherein the one or more devices include the data collection service; as well as The data collection service receives data from the UE corresponding to one or more types of data.

37. The apparatus of claim 36, wherein the one or more processors are configured to execute processor-executable instructions and cause the one or more apparatuses to: The information is transmitted to the UE regarding the data collection service, the information including one or more of the following: Routing information for the data collection service; The UE will be instructed to collect data from the supplier's supplier information; or Instructions for the purpose of collecting data.

38. The apparatus of claim 37, wherein the apparatus includes a discovery service, and wherein the processor is configured to execute processor-executable instructions and cause the apparatus to: The data collection service transmits signaling including routing information for the discovery service; and The discovery service receives a request from the UE for information regarding the data collection service, wherein... In order to transmit the information about the data collection service, the one or more processors are configured to execute processor-executable instructions and cause the one or more devices to transmit the information about the data collection service from the discovery service.

39. One or more devices according to claim 37, wherein, In order to transmit the information about the data collection service, the one or more processors are configured to execute processor-executable instructions and cause the one or more devices to transmit the information about the data collection service from a first device of the one or more devices in a system information block (SIB) or dedicated signaling.

40. The apparatus of claim 39, wherein the one or more processors are configured to execute processor-executable instructions and cause the one or more apparatuses to: The information about the data collection service is transmitted from the data collection service to the first device.

41. The apparatus of claim 36, wherein the one or more processors are configured to execute processor-executable instructions and cause the one or more apparatuses to: The data collection service receives one or more of the following from the UE: The supplier information of the UE's supplier; or The identifier of the UE.

42. The apparatus of claim 36, wherein the one or more processors are configured to execute processor-executable instructions and cause the one or more apparatuses to: A first device of the one or more devices receives a second configuration for data from the data collection service, the second configuration indicating one or more second types of data to be collected by the first device; and The first device transmits data corresponding to one or more of the second types of data to at least one of the following: The UE; or The data collection service.

43. A method for wireless communication by a device, the method comprising: Receive an encryption configuration for data collection, the encryption configuration indicating one or more types of data that the device intends to collect; Decrypt the encryption configuration used for data collection; as well as Transmit data corresponding to one or more of the aforementioned data types.

44. The method of claim 43, wherein the one or more types of data include one or more of the following: The battery status of the device; The calculation status of the device; Doppler extension; or Doppler delay.

45. The method of claim 43, wherein transmitting the data comprises: Encrypt the data; as well as Transmit encrypted data.

46. ​​The method of claim 43, wherein transmitting the data comprises: The data shall be transmitted to at least one of the following: Network entities; Track and collect entities; or The device is a device outside of a wireless communication network that operates within it.

47. The method of claim 43, further comprising: Receive additional data from a network entity corresponding to the data collected by the network entity, wherein transmitting the data includes: Transmit the data and the additional data.

48. The method of claim 43, further comprising: The supplier information of the device is transmitted to the network entity.

49. The method of claim 43, wherein receiving the encryption configuration comprises: Receive the encryption configuration from the network entity.

50. A method for wireless communication by one or more devices, the method comprising: The first device among the one or more devices receives information identifying one or more user equipment (UE); as well as The first device transmits an encryption configuration for data collection to the one or more UEs, the encryption configuration indicating one or more types of data to be collected by each of the one or more UEs.

51. The method of claim 50, wherein the one or more types of data include one or more of the following: Battery status; Calculation status; Doppler extension; or Doppler delay.

52. The method of claim 50, further comprising: The first device receives a second configuration for data, the second configuration indicating one or more second types of data that the first device wants to collect; as well as The first device transmits data corresponding to one or more of the second types of data to at least one of the following: At least one of the one or more UEs; Track and collect entities; or The first device is a device outside of a wireless communication network in which it operates.

53. The method of claim 52, wherein transmitting the data comprises: The first device encrypts the data corresponding to one or more of the second types of data; as well as Transmit encrypted data.

54. The method of claim 52, wherein the one or more means include the tracking and collecting entity, and wherein the method further comprises: The tracking and collecting entity receives the data corresponding to the one or more second types of data; as well as The tracking and collecting entity transmits the data corresponding to the one or more second types of data to the device.

55. The method of claim 50, further comprising: The first device receives data corresponding to the one or more types of data from the one or more UEs; as well as The first device transmits the data corresponding to the one or more types of data to at least one of the following: Track and collect entities; or The first device is a device outside of a wireless communication network in which it operates.

56. The method of claim 55, wherein the one or more means include the tracking and collecting entity, and wherein the method further comprises: The tracking and collecting entity receives the data corresponding to the one or more types of data; as well as The tracking and collection entity transmits the data corresponding to the one or more types of data to the device.

57. The method of claim 50, wherein the information identifying the one or more UEs includes an explicit identifier for each of the one or more UEs.

58. The method of claim 50, wherein the information identifying the one or more UEs includes one or more identifiers of one or more suppliers, and wherein the method further comprises: Receive corresponding vendor information for each of the one or more UEs, wherein each of the one or more UEs is associated with one of the one or more vendors.

59. The method of claim 50, further comprising: Receive the encryption configuration for data collection from the server.

60. The method of claim 50, further comprising: Receive the configuration for data collection from the server; as well as The configuration used for data collection is encrypted.

61. The method of claim 50, wherein the one or more means include Operation, Administration and Maintenance (OAM), Unified Data Management (UDM), Access and Mobility Function (AMF), wherein the first means includes a radio access network entity, and wherein the method further includes: The OAM transmits the encryption configuration for data collection to the UDM; The UDM transmits the encryption configuration for data collection to the AMF; as well as The encryption configuration for data collection is transmitted from the AMF to the first device.

62. The method according to claim 61, further comprising: The OAM receives the encryption configuration for data collection from the server.

63. The method according to claim 61, further comprising: The OAM receives the configuration for data collection from the server; as well as The configuration used for data collection is encrypted by the OAM.

64. The method according to claim 61, further comprising: The AMF receives one or more identifiers from the one or more UEs; as well as The AMF transmits the information identifying the one or more UEs to the first device, wherein the information identifying the one or more UEs includes one or more second identifiers of the one or more UEs that are different from the one or more identifiers of the one or more UEs.

65. The method of claim 61, wherein the one or more means include Network Open Function (NEF), and wherein the method further comprises: The NEF receives the configuration for data collection from the server; The configuration used for data collection is encrypted by the NEF; as well as The NEF transmits the encryption configuration for data collection to the OAM.

66. The method of claim 61, wherein the one or more means include Network Open Function (NEF), and wherein the method further comprises: The NEF receives an instruction to begin data collection; as well as The NEF transmits the instruction to the OAM to begin data collection.

67. The method of claim 50, wherein the one or more means include an Access and Mobility Function (AMF), wherein the first means includes a Radio Access Network Entity, and wherein the method further comprises: The encryption configuration for data collection is transmitted from the AMF to the first device.

68. The method of claim 67, further comprising: The AMF receives the encryption configuration for data collection from the server.

69. The method of claim 67, further comprising: The AMF receives the configuration for data collection from the server; as well as The configuration used for data collection is encrypted by the AMF.

70. The method of claim 67, wherein the one or more means include Network Open Function (NEF), and wherein the method further comprises: The NEF receives the configuration for data collection from the server; The configuration used for data collection is encrypted by the NEF; as well as The NEF transmits the encryption configuration for data collection to the AMF.

71. The method of claim 67, wherein the one or more means include Network Open Function (NEF), and wherein the method further comprises: The NEF receives an instruction to begin data collection; as well as The NEF transmits the instruction to the AMF to begin data collection.

72. A method for wireless communication by a device, the method comprising: Receive information about data collection services; The device receives a configuration for data collection from the data collection service, the configuration indicating one or more types of data to be collected. as well as Transmit data corresponding to the one or more types of data to the data collection service.

73. The method of claim 72, wherein the information regarding the data collection service includes one or more of the following: This includes routing information for one or more data collection services, including the data collection service itself. Supplier information indicating that the device from the supplier will collect data; or Instructions for the purpose of collecting data.

74. The method according to claim 72, further comprising: Receive signaling including routing information for service discovery; as well as Sending a request for information about the data collection service to the discovery service, wherein receiving the information about the data collection service includes receiving the information about the data collection service from the discovery service.

75. The method of claim 72, wherein receiving the information about the data collection service comprises receiving the information about the data collection service from a system information block (SIB) or dedicated signaling from another device.

76. The method according to claim 72, further comprising: Send one or more of the following to the data collection service: Supplier information indicating the supplier of the device; or The identifier of the device.

77. The method of claim 72, the method further comprising receiving additional data from a network entity corresponding to data collected by the network entity, wherein transmitting the data includes transmitting the data and the additional data.

78. A method for wireless communication by one or more devices, the method comprising: A data collection service transmits a configuration for data collection to a user equipment (UE), the configuration indicating one or more types of data to be collected by the UE, wherein the one or more devices include the data collection service; as well as The data collection service receives data from the UE corresponding to one or more types of data.

79. The method according to claim 78, further comprising: The information is transmitted to the UE regarding the data collection service, the information including one or more of the following: Routing information for the data collection service; The UE will be instructed to collect data from the supplier's supplier information; or Instructions for the purpose of collecting data.

80. The method of claim 79, wherein the one or more means include a discovery service, and wherein the method further comprises: The data collection service transmits signaling including routing information for service discovery; as well as The discovery service receives a request from the UE for information about the data collection service, wherein transmitting the information about the data collection service includes transmitting the information about the data collection service from the discovery service.

81. The method of claim 79, wherein transmitting the information about the data collection service comprises transmitting the information about the data collection service in a system information block (SIB) or dedicated signaling from a first device among the one or more devices.

82. The method according to claim 81, further comprising: The information about the data collection service is transmitted from the data collection service to the first device.

83. The method according to claim 78, further comprising: The data collection service receives one or more of the following from the UE: The supplier information of the supplier of the UE is indicated; or The identifier of the UE.

84. The method according to claim 78, wherein the method further comprises: A first device among the one or more devices receives a second configuration for data from the data collection service, the second configuration indicating one or more second types of data that the first device wants to collect; as well as The first device transmits data corresponding to one or more of the second types of data to at least one of the following: The UE; or The data collection service.

Images