Data collection and communication

Abstract

Certain aspects of the present disclosure provide technology for wireless communication by a device. The method includes receiving an encrypted configuration for data collection 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 one or more types of data.

Description

Technical Field

[0001]

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

[0002] Description of Related Art

[0002] Wireless communication systems are widely deployed to provide various telecommunication services, such as telephony, video, data, messaging, broadcasting, or other similar types of services. These wireless communication systems can employ multiple access technologies that can support communication with multiple users by sharing available wireless communication system resources among the users.

[0003]

[0003] Although wireless communication systems have made significant technical advances over the years, challenges still exist. For example, complex and dynamic environments can still attenuate or block signals between wireless transmitters and wireless receivers. Therefore, continued improvements in the technical performance of wireless communication systems are desired, including, for example, improving communication speed and data carrying capacity, improving the usage efficiency of shared communication media, reducing power consumed by transmitters and receivers during communication operation, improving the reliability of wireless communication, avoiding redundant transmission and / or reception and associated processing, improving the coverage area of wireless communication, increasing the number and types of devices that can access a wireless communication system, improving the ability of different types of devices to communicate with each other, increasing the number and types of wireless communication media available for use, and the like. Accordingly, further improvements in wireless communication systems are needed to overcome the aforementioned technical problems and others.

[0004]

[0004] Minimizing Drive Tests (MDT) is a standardized mechanism to reduce the need for additional drive tests, which are associated with high cost and time commitments and provide only a partial view of the network because the tests are limited to locations with vehicle access. Mobile network data can be used, for example, to perform different types of network optimization.

[0005]

[0005] Machine learning models are also used to enhance wireless communication networks. For example, machine learning models are used for a variety of different use cases, such as beam prediction, mobility management, positioning, channel status information (CSI) prediction, CSI feedback, intermittent reception (DRX) augmentation, DRX prediction, traffic prediction, and interference management. Training of such machine learning models may be performed on one or more devices such as UEs, network entities of the wireless communication network, and neutral sites (e.g., servers such as third-party servers outside the wireless communication network, over-the-top (OTT) servers, and servers within the wireless communication network).

[0006]

[0006] To train a machine learning model, data may need to be collected from UEs and / or other network entities (e.g., base stations, distributed units, central units, etc.). Furthermore, the data may need to be communicated to the device(s) on which the machine learning model will be trained. Thus, technologies for data collection and communication may be required. It should be noted that the technologies for data collection and communication described herein may be used for use cases other than training machine learning models. [Overview of the Initiative]

[0007]

[0007] One embodiment provides a method for wireless communication by a device. The method includes receiving an encrypted configuration for data collection 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 one or more types of data. The technical effect of encrypting the configuration for data collection is that the types of data being collected can be kept secret / secure, such as preventing other devices from learning about proprietary types of data being collected, such as data of a type used to train a proprietary machine learning model.

[0008]

[0008] Another embodiment provides a method for wireless communication by one or more devices. The method includes: a first device of one or more devices receiving information identifying one or more user devices (UEs); and the first device transmitting to one or more UEs an encrypted configuration for data collection indicating one or more types of data that each of the one or more UEs should collect. The technical effect of encrypting the data collection configuration is that the types of data being collected can be kept secret / secure, such as preventing other devices from learning about proprietary types of data being collected, such as data of a type used to train a proprietary machine learning model.

[0009]

[0009] Another embodiment provides a method for wireless communication by the device. The method includes receiving information about a data collection service, receiving from the data collection service a configuration for data collection indicating one or more types of data to be collected by the device, and transmitting data corresponding to one or more types of data to the data collection service. The technical benefit of using separate data collection services to configure data collection may be the flexibility in providing different data collection services for collecting different data for different purposes, such as training different machine learning models.

[0010]

[0010] Another embodiment provides a method for wireless communication by one or more devices. The method includes transmitting a data collection configuration to the UE, which indicates one or more types of data for the UE to collect, and the data collection service receiving data from the UE corresponding to one or more types of data. The technical effect of using separate data collection services to configure data collection may be flexibility in providing different data collection services to collect different data for different purposes, such as training different machine learning models.

[0011]

[0011] Other embodiments include one or more devices that are operable, configured, or otherwise adapted to perform any part of any method described herein (for example, so that the execution may be performed by only one device or in a distributed manner across multiple devices), and which, when executed by one or more processors of one or more devices, include instructions causing one or more devices to perform any part of any method described herein (for example, so that the instructions may be included in only one computer-readable medium or in a distributed manner across multiple computer-readable mediums, so that the instructions may be executed by only one processor or in a distributed manner across multiple processors, with each device of one or more devices having one processor The present invention provides one or more computer program products embodied on one or more computer-readable storage media (for example, the code may be stored on one computer-readable medium or in a distributed manner across computer-readable media) containing code for executing any part of any method described herein, and / or providing one or more devices comprising one or more means for executing any part of any method described herein (for example, execution may be by one device or in a distributed manner across multiple devices). For example, the devices may include a processing system, a device having a processing system, or processing systems cooperating over one or more networks.

[0012]

[0012] The following description and attached figures illustrate specific features for illustrative purposes only. [Brief explanation of the drawing]

[0013]

[0013] The accompanying figures illustrate specific features of various embodiments described herein and should not be considered to limit the scope of this disclosure.

[0014] [Figure 1]

[0014] An exemplary wireless communication network is shown. [Figure 2]

[0015] This shows an exemplary isolated base station architecture. [Figure 3]

[0016] Exemplary base station and exemplary user equipment (UE) configurations are shown. [Figure 4]

[0017] This document illustrates various exemplary forms of data structures related to wireless communication networks. [Figure 5]

[0018] This shows a call flow diagram illustrating the call flow for performing signaling-based drive test minimization (MDT). [Figure 6]

[0019] A call flow diagram is shown illustrating the call flow for implementing signaling-based MDT. [Figure 7]

[0020] A call flow diagram is shown illustrating the call flow for implementing signaling-based MDT. [Figure 8]

[0021] A call flow diagram is shown illustrating the call flow for implementing signaling-based MDT. [Figure 9]

[0022] A call flow diagram is shown illustrating the call flow for implementing signaling-based MDT. [Figure 10]

[0023] This shows a call flow diagram illustrating the call flow for performing a management-based MDT. [Figure 11]

[0024] This shows a call flow diagram illustrating the call flow for performing a management-based MDT. [Figure 12]

[0025] A call flow diagram is shown illustrating the call flow for performing the reporting of collected data. [Figure 13]

[0026] A call flow diagram is shown illustrating the call flow for performing the reporting of collected data. [Figure 14]

[0027] shows a call flow diagram illustrating a call flow for performing reporting of collected data. [Figure 15]

[0028] shows a call flow diagram illustrating a call flow for performing data collection by a data collection service. [Figure 16]

[0029] shows a call flow diagram illustrating a call flow for performing data collection by a data collection service. [Figure 17]

[0030] illustrates a method for wireless communication. [Figure 18]

[0031] illustrates another method for wireless communication. [Figure 19]

[0032] illustrates another method for wireless communication. [Figure 20]

[0033] illustrates another method for wireless communication. [Figure 21]

[0034] illustrates aspects of an exemplary communication device. [Figure 22]

[0035] illustrates aspects of an exemplary communication device. [Figure 23]

[0036] illustrates aspects of an exemplary communication device. [Figure 24]

[0037] illustrates aspects of an exemplary communication device. DETAILED DESCRIPTION OF EMBODIMENTS

[0015]

[0038] Aspects of the present disclosure provide an apparatus, a method, a processing system, and a computer-readable medium for data collection and communication.

[0016]

[0039] In certain embodiments, MDT techniques may be used as part of data collection and communication. UE data collected using standard MDT techniques may be referred to as standardized data and may include, for example, measurements such as cell power, interference, call drop, and throughput. However, in use cases such as training machine learning models, collecting only standardized data may not be sufficient. Other data (also referred to as unstandardized data), such as UE battery status, UE computation status (e.g., for tagging measurement samples), Doppler spread measured at the UE, delayed spread measured at the UE, UE resource constraints, other internal UE states, other external states of the UE such as the radio environment, and parameters for feature engineering, may also be useful for training machine learning models. In addition, data collected from one or more network entities may be useful for training machine learning models, such as data measured by the network or other data to assist the UE, which may be referred to as supporting information such as codebook indexes and antenna patterns. Standard MDT techniques may not collect such data. Such data collected from one or more network entities may be unstandardized data. Therefore, technologies that can enable the collection of data (including, for example, unstandardized data) and, furthermore, the communication of such collected data are described herein. The technologies herein may provide technical effects that enable the collection and communication of unstandardized data, which can assist in the training of machine learning models.

[0017]

[0040] In addition, technologies that can enable the secure communication of data collection and the collected data itself are discussed herein. In particular, entities (e.g., network operators) may want to keep the type of data being collected, as well as the actual data being collected, proprietary. The type of data could be any specific data being collected, such as battery status, computation status, Doppler spread, or Doppler delay. Therefore, technologies that can enable the secure communication of configuration data used to configure a device to collect data, as well as the secure communication of the data itself, are discussed herein. The technical effect of securely communicating configuration data used to configure a device to collect data is that the type of data being collected can be kept secret / secure. The technical effect of securely communicating the data itself is that the actual data being collected can also be kept secure / secure.

[0018] Introduction to Wireless Communication Networks

[0041] The techniques and methods described herein can be used with respect to various wireless communication networks. While some embodiments may be described herein using terms generally associated with 3G, 4G, and / or 5G wireless technologies, embodiments of this disclosure may also be applicable to other communication systems and standards not expressly mentioned herein.

[0019]

[0042] Figure 1 shows one embodiment of a wireless communication network 100 that can realize the various embodiments described herein.

[0020]

[0043] Generally, the wireless communication network 100 includes various network entities (or network elements or network nodes). Network entities generally include communication devices and / or communication functions performed by communication devices (e.g., user equipment (UE), base station (BS), components of BS, servers, etc.). Such communication devices are part of the wireless communication network 100 and facilitate wireless communication, and are therefore sometimes referred to as wireless communication devices. For example, various functions of the network, as well as various devices associated with and interacting with the network, can be considered network entities. Furthermore, the wireless communication network 100 includes terrestrial configurations such as ground-based network entities (e.g., BS102) and non-terrestrial configurations such as satellites 140 and aircraft 145, which may include other network elements (e.g., terrestrial BS) and onboard network entities (e.g., one or more BS) capable of communicating with UE.

[0021]

[0044] In the illustrated embodiment, the wireless communication network 100 includes one or more core networks, such as BS102, UE104, and the Evolved Packet Core (EPC) 160 and 5G Core (5GC) networks 190, which are interoperated to provide communication services over various communication links, including wired links and wireless links.

[0022]

[0045] Figure 1 shows various exemplary UE104s, which may more commonly include cellular phones, smartphones, session initiation protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radios, global positioning systems, multimedia devices, video devices, digital audio players, cameras, game consoles, tablets, smart devices, wearable devices, vehicles, electric meters, gas 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. UE104 may also more commonly be 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, handsets, etc.

[0023]

[0046] BS102 communicates wirelessly with UE104 via communication link 120 (for example, by transmitting a signal to UE104 or receiving a signal from UE104). The communication link 120 between BS102 and UE104 may include uplink (UL) transmissions (also referred to as reverse links) from UE104 to BS102, and / or downlink (DL) transmissions (also referred to as forward links) from BS102 to UE104. Communication link 120 may utilize multiple-input and multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity in various forms.

[0024]

[0047] BS102 may generally include NodeBs, enhanced NodeBs (eNBs), next-generation enhanced NodeBs (ng-eNBs), next-generation NodeBs (gNBs or gNodeBs), access points, base transceiver stations, radio base stations, radio transceivers, transceiver functions, transmit / receive points, etc. Each of BS102 may provide communication coverage for a corresponding coverage area 110, which may be referred to as a cell and may overlap in some cases (for example, a small cell 102' may have a coverage area 110' that overlaps with the coverage area 110 of a macrocell). BS can provide communication coverage for, for example, macrocells (covering relatively large geographical areas), picocells (covering relatively smaller geographical areas such as sports stadiums), femtocells (covering relatively smaller geographical areas, such as homes), and / or other types of cells.

[0025]

[0048] Although BS102 is shown as an integrated communication device in various embodiments, BS102 can be implemented in various configurations. For example, one or more components of the base station can be separated, some examples of which include a central unit (CU), one or more distributed units (DUs), one or more radio units (RUs), a near-real-time (near-RT) RAN intelligent controller (RIC), or a non-real-time (non-RT) RIC. In another embodiment, various embodiments of the base station can be virtualized. More generally, a base station (e.g., BS102) may include components located in a single physical location, or components located in various physical locations. In embodiments in which the base station includes components located in various physical locations, each of these various components can perform functions so that they collectively achieve similar functions to a base station located in a single physical location. In some embodiments, a base station including components located at various physical locations may be referred to as a decoupled radio access network architecture, such as an Open RAN (O-RAN) architecture or a Virtualized RAN (VRAN) architecture. Figure 2 illustrates and describes an exemplary decoupled base station architecture.

[0026]

[0049] Different BS102 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 BS102 configured for 4G LTE (collectively referred to as the Evolved Universal Mobile Telecommunications System Terrestrial Radio Access Network, E-UTRAN) can interface with an EPC160 through a first backhaul link 132 (e.g., S1 interface). A BS102 configured for 5G (e.g., 5G NR or Next Generation RAN, NG-RAN) can interface with a 5GC190 through a second backhaul link 184. The BS102s can communicate directly with each other or indirectly with each other (e.g., through an EPC160 or 5GC190) via a third backhaul link 134 (e.g., X2 interface), which may be wired or wireless.

[0027]

[0050] A wireless communication network 100 can subdivide the electromagnetic spectrum into various classes, bands, channels, or other features. In some embodiments, this subdivision is provided based on wavelength and frequency, in which case frequency may also be referred to as carrier, subcarrier, frequency channel, tone, or subband. For example, 3GPP currently defines Frequency Range 1 (FR1) as encompassing 410 MHz to 7125 MHz, which is often (interchangeably) referred to as "sub-6 GHz". Similarly, 3GPP currently defines Frequency Range 2 (FR2) as encompassing 24,250 MHz to 52,600 MHz, which is sometimes (interchangeably) referred to as "millimeter wave" ("mmW" or "mm wave"). A base station configured to communicate using the mm-wave / quasi-mm-wave radio frequency band (e.g., a mm-wave base station such as BS180) can utilize beamforming (e.g., 182) with an UE (e.g., 104) to improve path loss and range.

[0028]

[0051] The communication link 120 between BS102 and, for example, UE104, can be via one or more carriers, which may have different bandwidths (e.g., 5, 10, 15, 20, 100, 400, and / or other MHz), and in various ways can be aggregated. The carriers may be adjacent to each other or not. The carrier allocation may be asymmetrical with respect to DL and UL (for example, DL may be allocated more or fewer carriers than UL).

[0029]

[0052] Communications using higher frequency bands may have higher path loss and shorter range compared to communications using lower frequencies. Therefore, a particular base station (e.g., BS180 in Figure 1) can utilize beamforming with UE104 to improve path loss and range. For example, BS180 and UE104 may each include multiple antennas, such as antenna elements, antenna panels, and / or antenna arrays, to facilitate beamforming. In some cases, BS180 can transmit a beamformed signal to UE104 in one or more transmit directions 182'. UE104 can receive its beamformed signal from BS180 in one or more receive directions 182''. UE104 can also transmit a beamformed signal to BS180 in one or more transmit directions 182''. BS180 can also receive its beamformed signal from UE104 in one or more receive directions 182'. In that case, BS180 and UE104 can perform beam training to determine the best receiving and transmitting directions for BS180 and UE104, respectively. In particular, the transmitting and receiving directions for BS180 may or may not be the same. Similarly, the transmitting and receiving directions for UE104 may or may not be the same.

[0030]

[0053] The wireless communication network 100 further includes a Wi-Fi AP 150 that communicates with Wi-Fi stations (STAs) 152 via a communication link 154, for example, in the unlicensed frequency spectrum of 2.4 GHz and / or 5 GHz.

[0031]

[0054] Certain UE104s can communicate with each other using a device-to-device (D2D) communication link 158. The D2D communication link 158 can use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH), a physical sidelink discovery channel (PSDCH), a physical sidelink shared channel (PSSCH), a physical sidelink control channel (PSCCH), and / or a physical sidelink feedback channel (PSFCH).

[0032]

[0055] EPC160 may include various functional components, such as a Mobility Management Entity (MME) 162, other MMEs 164, a serving gateway 166, a Multimedia Broadcast Multicast Service (MBMS) gateway 168, a Broadcast Multicast Service Center (BM-SC) 170, and / or a Packet Data Network (PDN) gateway 172, as shown in the illustrated embodiment. MME 162 may communicate with a Home Subscriber Server (HSS) 174. MME 162 is a control node that handles signaling between UE 104 and EPC160. Generally, MME 162 provides bearer and connection management.

[0033]

[0056] Generally, user Internet Protocol (IP) packets are forwarded through the serving gateway 166, which itself is connected to the PDN gateway 172. The PDN gateway 172 provides UE IP address allocation and other functions. The PDN gateway 172 and BM-SC170 are connected to IP services 176, which may include, for example, the Internet, intranet, IP Multimedia Subsystem (IMS), packet-switched (PS) streaming services, and / or other IP services.

[0034]

[0057] The BM-SC170 can provide functions for provisioning and delivering MBMS user services. The BM-SC170 can function as an entry point for content provider MBMS transmissions and can be used to authorize and initiate MBMS bearer services within a public land mobile network (PLMN), and / or to schedule MBMS transmissions. The MBMS gateway 168 can be used to deliver MBMS traffic to BS102, which belongs to a Multicast Broadcast Single Frequency Network (MBSFN) area broadcasting a specific service, and / or can be involved in session management (start / stop) and collecting eMBMS-related billing information.

[0035]

[0058] The 5GC190 may include various functional components, including an Access and Mobility Management Function (AMF)192, other AMFs193, a Session Management Function (SMF)194, and a User Plane Function (UPF)195. The AMF192 may communicate with Unified Data Management (UDM)196.

[0036]

[0059] AMF192 is a control node that handles signaling between UE104 and 5GC190. AMF192 provides, for example, quality of service (QoS) flow and session management.

[0037]

[0060] Internet Protocol (IP) packets are forwarded through UPF195, which connects to IP service 197 and provides UE IP address allocation and other functions related to 5GC190. IP service 197 may include, for example, the Internet, intranet, IMS, PS streaming service, and / or other IP services.

[0038]

[0061] In various forms, a network entity or network node can be implemented as, to name a few, an aggregated base station, a separate base station, a base station component, an integrated access and backhaul (IAB) node, a relay node, or a sidelink node.

[0039]

[0062] Figure 2 shows an exemplary architecture of a separate base station 200. The architecture of the separate base station 200 may include one or more central units (CUs) 210 that can communicate directly with the core network 220 via a backhaul link, or indirectly with the core network 220 via one or more separate base station units (such as a quasi-real-time (quasi-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). The CUs 210 can communicate with one or more distributed units (DUs) 230 via a corresponding midhaul link, such as an F1 interface. The DUs 230 can communicate with one or more radio units (RUs) 240 via a corresponding fronthaul link. The RUs 240 can communicate with a corresponding UE 104 via one or more radio frequency (RF) access links. In some implementations, the UE104 can be serviced simultaneously by multiple RU240s.

[0040]

[0063] Each of the units, for example, CU210, DU230, RU240, and the quasi-RT RIC225, non-RT RIC215, and SMO framework 205, may include, or be coupled to, one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via a wired or wireless transmission medium. Each of the units, or any associated processor or controller providing instructions to the communication interfaces of those units, may be configured to communicate with one or more other units via a transmission medium. For example, a unit may include a wired interface configured to receive signals from or transmit signals to one or more other units via a wired transmission medium. Furthermore, or alternatively, those units may also include a wireless interface, which may include a receiver, transmitter, or transceiver (such as a radio frequency (RF) transceiver) configured to receive or transmit or receive signals to or from one or more other units via a wireless transmission medium.

[0041]

[0064] In some embodiments, the CU210 can host one or more higher-layer control functions. Such control functions may include radio resource control (RRC), packet data convergence protocol (PDCP), and service data adaptation protocol (SDAP). Each control function can have an interface configured to communicate signals with other control functions hosted by the CU210. The CU210 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 a combination thereof. In some implementations, the CU210 can be logically divided into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP units can communicate bidirectionally with the CU-CP units via an interface such as the E1 interface. The CU210 can be implemented to communicate with the DU230 as needed for network control and signaling.

[0042]

[0065] The DU230 may correspond to a logic unit including one or more base station functions for controlling the operation of one or more RU240s. In some embodiments, the DU230 may host one or more of the following, at least in part, according to a functional decomposition such as that defined by the 3rd Generation Partnership Project (3GPP): a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more upper physical (PHY) layers (such as modules related to forward error correction (FEC) coding and decoding, scrambling, modulation and demodulation). In some embodiments, the DU230 may further host one or more lower PHY layers. Each layer (or module) may have an interface configured to communicate signals with other layers (and modules) hosted by the DU230, or with control functions hosted by the CU210.

[0043]

[0066] Lower-layer functions can be performed by one or more RU240s. In some deployments, RU240s controlled by DU230s may correspond to logical nodes hosting RF processing functions, or lower PHY layer functions (such as performing fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering), or both, at least partially based on functional partitioning such as lower-layer functional partitioning. In such architectures, RU(s)240s can be implemented to handle over-the-air (OTA) communication with one or more UE104s. In some implementations, real-time and non-real-time modes of control and user-plane communication with RU(s)240s can be controlled by the corresponding DU230s. In some scenarios, this configuration can enable the DU(s)230 and CU210 to be implemented in cloud-based RAN architectures, such as vRAN architectures.

[0044]

[0067] The SMO framework 205 can be configured to support RAN deployment and provisioning of non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO framework 205 can be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via operational and maintenance interfaces (such as the O1 interface). For virtualized network elements, the SMO framework 205 can be configured to interact with a cloud computing platform (such as Open Cloud (O-Cloud) 290) via a cloud computing platform interface (such as the O2 interface) to perform network element lifecycle management (such as instantiating virtualized network elements). Examples of such virtualized network elements include, but are not limited to, CU210, DU230, RU240, and quasi-RT RIC225. In some implementations, the SMO framework 205 can communicate with 4G RAN hardware embodiments such as Open eNB (O-eNB) 211 via the O1 interface. Furthermore, in some implementations, the SMO framework 205 can communicate directly with one or more RU240s via the O1 interface. The SMO framework 205 may also include a non-RT RIC215 configured to support the functionality of the SMO framework 205.

[0045]

[0068] Non-RT RIC215 can be configured to include logical functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updating, or policy-based guidance for applications / functions in quasi-RT RIC225. Non-RT RIC215 can be coupled to or communicate with quasi-RT RIC225 (e.g., via the A1 interface). Quasi-RT RIC225 can be configured to include logical functions that enable quasi-real-time control and optimization of RAN elements and resources via data acquisition and actions through an interface connecting to quasi-RT RIC225 (e.g., via the E2 interface), including one or more CU210s, one or more DU230s, or both, and an O-eNB.

[0046]

[0069] In some implementations, the non-RT RIC215 can receive parameter or external enrichment information from an external server to generate AI / ML models that will be deployed in the quasi-RT RIC225. Such information can be utilized by the quasi-RT RIC225 and can be received in the SMO framework 205 or the non-RT RIC215 from non-network data sources or network functions. In some embodiments, the non-RT RIC215 or quasi-RT RIC225 can be configured to adjust the behavior or performance of the RAN. For example, the non-RT RIC215 can monitor long-term trends and patterns in performance and employ AI / ML models to take corrective action through the SMO framework 205 (such as reconfiguration via O1) or through the creation of RAN management policies (such as A1 policies).

[0047]

[0070] Figure 3 shows exemplary embodiments of BS102 and UE104.

[0048]

[0071] Generally, BS102 includes various processors (e.g., 320, 330, 338, and 340), antennas 334a-t (collectively, 334), transceivers 332a-t (collectively, 332) including modulators and demodulators, other embodiments enabling wireless transmission of data (e.g., data source 312), and other embodiments enabling wireless reception of data (e.g., data sink 339). For example, BS102 can send and receive data between BS102 and UE104. BS102 includes a controller / processor 340 which can be configured to perform various functions related to wireless communication as described herein.

[0049]

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

[0050]

[0073] For exemplary downlink transmissions, BS102 includes a transmitting processor 320 that can receive data from data source 312 and control information from controller / processor 340. The control information may relate to a physical broadcast channel (PBCH), a physical control format indicator channel (PCFICH), a physical hybrid automatic repeating request (HARQ) indicator channel (PHICH), a physical downlink control channel (PDCCH), a group common PDCCH (GC PDCCH), and the like. In some embodiments, the data may relate to a physical downlink shared channel (PDSCH).

[0051]

[0074] The transmit processor 320 can process data and control information (e.g., encode and symbol-map) in order to acquire data symbols and control symbols, respectively. The transmit processor 320 can also generate reference symbols for primary synchronization signals (PSS), secondary synchronization signals (SSS), PBCH demodulation reference signals (DMRS), and channel state information reference signals (CSI-RS), etc.

[0052]

[0075] The Transmit (TX) multi-input multiple-output (MIMO) processor 330 can, where applicable, perform spatial processing (e.g., precoding) on ​​data symbols, control symbols, and / or reference symbols, and provide output symbol streams to the modulators (MODs) in transceivers 332a-332t. Each modulator in transceivers 332a-332t can obtain an output sample stream by processing the corresponding output symbol stream. Each modulator can obtain a downlink signal by further processing the output sample stream (e.g., converting to analog, amplifying, filtering, and upconverting). The downlink signals from the modulators in transceivers 332a-332t can be transmitted via antennas 334a-334t, respectively.

[0053]

[0076] To receive downlink transmissions, UE104 includes antennas 352a-352r, which can receive downlink signals from BS102 and provide the received signals to demodulators (DEMODs) in transceivers 354a-354r, respectively. Each demodulator in transceivers 354a-354r can acquire an input sample by adjusting the corresponding received signal (e.g., filtering, amplifying, downconverting, and digitizing). Each demodulator can acquire a received symbol by further processing the input sample.

[0054]

[0077] The RX MIMO detector 356 can acquire received symbols from all demodulators in transceivers 354a to 354r, perform MIMO detection on those received symbols where applicable, and provide the detected symbols. The receiving processor 358 can process the detected symbols (e.g., demodulate, deinterleave, and decode), provide the decoded data for UE104 to the data sink 360, and provide the decoded control information to the controller / processor 380.

[0055]

[0078] For exemplary uplink transmission, UE104 further includes a transmit processor 364 capable of receiving and processing data from data source 362 (e.g., regarding PUSCH) and control information from controller / processor 380 (e.g., regarding the physical uplink control channel, PUCCH). The transmit processor 364 can also generate reference symbols for reference signals (e.g., for the sounding reference signal, SRS). Symbols from the transmit processor 364 can be precoded by the TX MIMO processor 366 where applicable, further processed by modulators in transceivers 354a-354r (e.g., with respect to SC-FDM, etc.) and transmitted to BS102.

[0056]

[0079] In BS102, the uplink signal from UE104 is received by antennas 334a to 334t, processed by demodulators in transceivers 332a to 332t, detected by RX MIMO detector 336 where applicable, and further processed by the receiving processor 338, thereby obtaining the decoded data and control information transmitted by UE104. The receiving processor 338 can provide the decoded data to the data sink 339 and the decoded control information to the controller / processor 340.

[0057]

[0080] Memories 342 and 382 can store data and program code related to BS102 and UE104, respectively.

[0058]

[0081] The scheduler 344 can schedule UEs for data transmission on the downlink and / or uplink.

[0059]

[0082] In various embodiments, BS102 may be described as transmitting and receiving various types of data associated with the methods described herein. In these contexts, “transmitting” may refer to various mechanisms that output data, such as outputting data from data source 312, scheduler 344, memory 342, transmit processor 320, controller / processor 340, TX MIMO processor 330, transceiver 332a-t, antenna 334a-t, and / or other embodiments described herein. Similarly, “receiving” may refer to various mechanisms that retrieve data, such as antenna 334a-t, transceiver 332a-t, RX MIMO detector 336, controller / processor 340, receive processor 338, scheduler 344, memory 342, and / or other embodiments described herein.

[0060]

[0083] In various embodiments, UE104 may also be described as transmitting and receiving various types of data associated with the methods described herein. In these contexts, “transmitting” may refer to various mechanisms for outputting data, such as outputting data from data source 362, memory 382, ​​transmit processor 364, controller / processor 380, TX MIMO processor 366, transceivers 354a-t, antennas 352a-t, and / or other embodiments described herein. Similarly, “receiving” may refer to various mechanisms for acquiring data, such as acquiring data from antennas 352a-t, transceivers 354a-t, RX MIMO detector 356, controller / processor 380, receive processor 358, memory 382, ​​and / or other embodiments described herein.

[0061]

[0084] In some embodiments, the processor may be configured to send (output) data to or receive (acquire) data from another interface configured to send or receive data, respectively, by performing various operations such as those associated with the methods described herein.

[0062]

[0085] Figures 4A, 4B, 4C, and 4D show various forms of data structures related to wireless communication networks, such as the wireless communication network 100 in Figure 1.

[0063]

[0086] In particular, Figure 4A is a figure 400 showing an embodiment of a first subframe within a 5G (e.g., 5G NR) frame structure, Figure 4B is a figure 430 showing an embodiment of a DL channel within a 5G subframe, Figure 4C is a figure 450 showing an embodiment of a second subframe within a 5G frame structure, and Figure 4D is a figure 480 showing an embodiment of a UL channel within a 5G subframe.

[0064]

[0087] Wireless communication systems can utilize orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP) on the uplink and downlink. Such systems can also support half-duplex operation using time division duplexing (TDD). OFDM and single-carrier frequency division multiplexing (SC-FDM) divide the system bandwidth into multiple orthogonal subcarriers (as shown, for example, in Figures 4B and 4D). Each subcarrier can be modulated with data. The modulated symbols can be transmitted using OFDM in the frequency domain and / or using SC-FDM in the time domain.

[0065]

[0088] The wireless communication frame structure can be frequency division duplex (FDD), where, for a given set of subcarriers, the subframes within that set are dedicated to either DL or UL. The wireless communication frame structure can also be time division duplex (TDD), where, for a given set of subcarriers, the subframes within that set are dedicated to both DL and UL.

[0066]

[0089] In Figures 4A and 4C, the wireless communication frame structure is TDD, where D is DL, U is UL, and X is flexible in terms of use between DL and UL. The UE can be configured in slot format via a received slot format indicator (SFI) (dynamically via DL control information (DCI) or semi-statically / statically via Radio Resource Control (RRC) signaling). In the illustrated embodiment, a 10ms frame is divided into 10 equal-sized 1ms subframes. Each subframe may contain one or more time slots. In some embodiments, each slot may contain 7 or 14 symbols, depending on the slot format. Subframes may also contain minislots, which generally have fewer symbols than the entire slot. Other wireless communication technologies may have different frame structures and / or different channels.

[0067]

[0090] In certain embodiments, the number of slots within a subframe depends on the slot configuration and numerology. For example, with slot configuration 0, different numerology (μ) 0-5 allow 1, 2, 4, 8, 16, and 32 slots per subframe, respectively. With slot configuration 1, different numerology 0-2 allow 2, 4, and 8 slots per subframe, respectively. Therefore, with slot configuration 0 and numerology μ, there are 14 symbols / slot and 2 μ slots / subframe. Subcarrier spacing and symbol length / duration are features of the numerology. Subcarrier spacing is 2 μIt may be equal to ×15kHz, where μ is numerology 0 to 5. Therefore, numerology μ=0 has a subcarrier interval of 15kHz, and numerology μ=5 has a subcarrier interval of 480kHz. The symbol length / duration is inversely proportional to the subcarrier interval. Figures 4A, 4B, 4C, and 4D provide an embodiment of slot configuration 0 having 14 symbols per slot, and numerology μ=2 having 4 slots per subframe. The slot duration is 0.25ms, the subcarrier interval is 60kHz, and the symbol duration is approximately 16.67μs.

[0068]

[0091] As shown in Figures 4A, 4B, 4C, and 4D, a resource grid can be used to represent the frame structure. Each time slot contains a resource block (RB) (also called physical RBs, PRBs) that spans, 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.

[0069]

[0092] As shown in Figure 4A, some of the REs carry reference (pilot) signals (RS) related to the UE (e.g., UE104 in Figures 1 and 3). RS may include demodulation RS (DMRS) and / or channel state information reference signals (CSI-RS) for channel estimation in the UE. RS may also include beam measurement RS (BRS), beam refinement RS (BRRS), and / or phase tracking RS (PT-RS).

[0070]

[0093] Figure 4B shows one embodiment of various DL channels within a subframe of a frame. A physical downlink control channel (PDCCH) carries DCI within one or more control channel elements (CCEs), each CCE containing, for example, nine RE groups (REGs), and each REG containing, for example, four consecutive REs within an OFDM symbol.

[0071]

[0094] A primary synchronization signal (PSS) may be present within symbol 2 of a specific subframe of a frame. The PSS is used by the UE (e.g., 104 in Figures 1 and 3) to determine the timing of the subframe / symbol and physical layer identification information.

[0072]

[0095] A secondary synchronization signal (SSS) may be present within symbol 4 of a specific subframe of a frame. The SSS is used by the UE to determine the group number of the physical layer cell identification information and the timing of the radio frame.

[0073]

[0096] Based on the physical layer identification information and the group number of the physical layer cell identification information, the UE can determine the physical cell identifier (PCI). Based on the PCI, the UE can determine the location of the aforementioned DMRS. A physical broadcast channel (PBCH) carrying a 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 number of RBs within the system bandwidth and the system frame number (SFN). The physical downlink shared channel (PDSCH) carries user data, system information for broadcasts not transmitted through the PBCH such as system information blocks (SIBs), and / or paging messages.

[0074]

[0097] As shown in Figure 4C, some of the REs carry DMRS (shown as R for one particular configuration, but other DMRS configurations are also possible) for channel estimation at the base station. The UE can transmit DMRS for PUCCH and DMRS for PUSCH. PUSCH DMRS can be transmitted, for example, within the first one or two symbols of a PUSCH. PUCCH DMRS can be transmitted in different configurations depending on whether a short or long PUCCH is transmitted and depending on the specific PUCCH format used. The UE 104 can transmit a sounding reference signal (SRS). SRS can be transmitted, for example, within the last symbol of a subframe. SRS may have a comb structure, and the UE can transmit SRS in one of those combs. SRS may be used by the base station for channel quality estimation to enable frequency-dependent scheduling on the UL.

[0075]

[0098] Figure 4D shows one embodiment of various UL channels within a subframe of a frame. In one configuration, the PUCCH may be located as shown. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicators (CQI), precoding matrix indicators (PMI), rank indicators (RI), and HARQ ACK / NACK feedback. The PUCCH carries data and may additionally carry buffer status reports (BSR), power headroom reports (PHR), and / or UCI.

[0076] Aspects related to minimizing signaling-based drive tests (MDT)

[0099] Figure 5 shows a call flow diagram illustrating a call flow 500 for performing signaling-based MDT. Figure 5 shows an Operations, Administration, and Maintenance (OAM) 510, which may be a functional component of 5GC 190 in Figure 1. For example, OAM 510 may refer to a network entity configured to manage the wireless communication network. Figure 5 further shows a UDM 508, which may correspond to UDM 196 in Figure 1. For example, UDM 508 may refer to a network entity configured to manage user data. Figure 5 further shows an AMF 506, which may correspond to AMF 192 in Figure 1. Figure 5 further shows a Radio Access Network (RAN) entity 504, which may correspond to a network entity such as BS 102 in Figures 1 and 3, or a separate base station as described in relation to Figure 2. Figure 5 further shows a UE 502, which may correspond to UE 104 in Figures 1 and 3.

[0077]

[0100] As shown, in 512, OAM510 activates the trace session by sending a trace activation message to UDM508. The trace session is a session for configuring UE502 to collect data, such as standardized data as described. In certain embodiments, the trace activation message includes trace control and configuration parameters, such as identifiers of UE502, such as a Subscription Persistent Identifier (SUPI) and / or International Mobile Device Identification Software Version (IMEISV), and instructions for parameters for configuring the UE for data collection. Thus, UDM508 may store the trace control and configuration parameters.

[0078]

[0101] In 514, the AMF506 receives a registration request from the RAN504. In certain embodiments, the UE502 sends a registration request to the RAN504, and the RAN504 sends the registration request to the AMF506. For example, the registration request is a request for the UE502 to register with the wireless communication network.

[0079]

[0102] In 516, the AMF506 receives / retrieves trace control and configuration parameters from the UDM508 by performing subscriber data management (SDM) acquisition procedures with the UDM508, such as in response to a registration request. Therefore, the AMF506 can store the trace control and configuration parameters.

[0080]

[0103] In step 518, the AMF506 initiates a trace session according to the received trace control and configuration parameters, for example, by sending a trace start message to the RAN504 (e.g., via the Ng interface). The trace start message may include trace control and configuration parameters. Therefore, the RAN504 can store the trace control and configuration parameters and initiate a trace session.

[0081]

[0104] In 520, RAN504 transmits the MDT configuration to UE502, instructing UE502 to collect data (e.g., standardized data). For example, the MDT configuration may include at least some trace controls and configuration parameters. Thus, UE502 stores at least some trace controls and configuration parameters and begins collecting data, such as by performing measurements corresponding to the data. For example, UE502 may perform a cell power measurement by measuring one or more signals transmitted from RAN504. Furthermore, UE502 may measure / track the number of call drops in UE502. Furthermore, UE502 may measure / track the average throughput rate of data transmitted and / or received by UE502 with respect to RAN504, etc.

[0082] Aspects related to OAM-based data acquisition configurations using network servers

[0105] Figure 6 shows a call flow diagram illustrating a call flow 600 for performing signaling-based MDT. Figure 6 shows an OAM 610 which may be a functional component of 5GC 190 in Figure 1. Figure 6 further shows a UDM 608 which may correspond to UDM 196 in Figure 1. Figure 6 further shows an AMF 606 which may correspond to AMF 192 in Figure 1. Figure 6 further shows a RAN entity 604 which may correspond to a network entity such as BS 102 in Figures 1 and 3, or a separate base station as described in relation to Figure 2. Figure 6 further shows a UE 602 which may correspond to UE 104 in Figures 1 and 3. Figure 6 further shows a server 609 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 certain embodiments, server 609 is located within the wireless communication network (e.g., wireless communication network 100 in Figure 1) rather than outside the wireless communication network (e.g., hosted within it). For example, server 609 may be part of 5GC 190. In certain embodiments, server 609 is hosted by a UE vendor or a third party within the wireless communication network.

[0083]

[0106] Call flow 600 illustrates an example of how a server in a wireless communications network may provide an OAM in the wireless communications network with a configuration for data collection in order to configure the UE and / or network entities to perform data collection.

[0084]

[0107] In 611, the server 609 transmits to the OAM 610 a configuration for data collection by one or more UEs and information identifying one or more UEs. In a particular embodiment, the information identifying one or more UEs includes one or more identifiers of one or more UEs, including UE 602, from which the server 609 requests data collection. For example, the UE identifier may include one or more of the UE's SUPI, the UE's IMEISV, or another (e.g., persistent) identifier assigned to the UE. The data collection configuration may include information indicating one or more types of data (e.g., unstandardized data) for each of the one or more UEs to be collected, such as UE battery status, UE computation status (e.g., for tagging of measurement samples), Doppler spread measured at the UE, delayed spread measured at the UE, UE resource constraints, other internal UE status, other external conditions of the UE such as the radio environment, and parameters for feature engineering. In certain aspects, the data collected may be based on service level agreements (SLAs) between operators, UE vendors, network vendors, etc.

[0085]

[0108] In some embodiments, in addition to, or as an alternative to, transmitting a configuration for data collection by one or more UEs in 611, server 609 transmits a configuration for data collection by one or more network entities, such as RAN 604, to OAM 610. In certain embodiments, server 609 further transmits information identifying one or more network entities to OAM 610. In certain embodiments, the information identifying one or more network entities includes one or more identifiers of one or more network entities, including RAN 604, from which server 609 requests data collection. In certain embodiments, the information identifying one or more network entities includes information identifying one or more UEs, so that any RAN entity servicing one or more UEs is identified by the information identifying one or more UEs. In certain embodiments, the configuration for data collection by one or more network entities may include information indicating one or more types of data (e.g., non-standardized data) for each of the one or more network entities to be collected, such as data measured by the network, or other data to support the UE, which may be referred to as supporting information such as codebook indexes or antenna patterns. In certain embodiments, the one or more types of data to be collected may be based on SLAs between operators, UE vendors, network vendors, etc.

[0086]

[0109] In certain embodiments, server 609 transmits at least a portion of the information transmitted in 611 to OAM610 as encrypted data (e.g., containerized data), such as an encrypted configuration for data collection. The data can be encrypted and decrypted using any preferred cryptographic technique, such as public-key cryptography, symmetric cryptography, or asymmetric cryptography. The type of key and / or cryptographic technique used may be distributed to the entity at manufacturing time via separate signaling (e.g., wireless updates). Encrypted data is trusted, for example, if server 609 is in a trusted domain of a wireless communication network. For example, a configuration for data collection by one or more UEs and / or a configuration for data collection by one or more network entities may be encrypted. In certain embodiments, information identifying one or more UEs and / or information identifying one or more network entities may not be encrypted. Encrypting the configuration for data collection keeps the type of data being collected confidential, as described above. Not encrypting information that identifies one or more UEs and / or one or more network entities allows the network to identify which UE(s) and / or network entities(s) should receive the configuration for data collection.

[0087]

[0110] In certain embodiments, only one or more entities, such as one or more UEs and / or one or more network entities, that are configured by the corresponding configuration for data collection have the ability to access (e.g., decrypt) the corresponding configuration for data collection in order to keep the information secure (e.g., they have one or more decryption keys).

[0088]

[0111] In certain embodiments, server 609 transmits information sent in 611 to OAM610 unencrypted (e.g., without containerization such as plaintext), for example, if server 609 is not necessarily within a trusted domain of the wireless communication network. Thus, OAM610 can verify / authorize the information (e.g., check whether the configuration for data collection complies with the SLA) before further distribution of the information within the network, which can beneficially provide security against malicious configurations. In certain such embodiments, OAM610 (or another network entity, such as instructed by OAM610) 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 distribution within the network.

[0089]

[0112] In certain embodiments, instead of the server 609 transmitting the information sent in 611 to the OAM 610, the information may be configured or pre-configured in the OAM 610 in several other ways (e.g., during manufacturing, via radio, etc.). In certain such embodiments, the server 609 transmits a trace start instruction to the OAM 610 in order to initiate a trace session based on the information configured or pre-configured in the OAM 610.

[0090]

[0113] In 612, OAM610 sends a trace activation message to UDM608, similar to 512 in Figure 5. Unlike 512, in 612, OAM610 sends the information for 611 (i.e., encrypted configuration for data collection by one or more UEs, information identifying one or more UEs, encrypted / unencrypted configuration for data collection by one or more network entities, and / or information identifying one or more network entities) along with the trace activation message (e.g., separately from or as part of the trace activation message). UDM608 stores the trace control and configuration parameters as well as the information for 611.

[0091]

[0114] In 614, AMF606 receives registration requests from RAN604, similar to those in 514 in Figure 5, such as a request for UE602 to register with the wireless communication network.

[0092]

[0115] In 616, similar to 516 in Figure 5, the AMF606 receives / retrieves trace control and configuration parameters from the UDM608 by performing an SDM acquisition procedure with the UDM608, such as in response to a registration request. Unlike 516, in 616, the AMF606 also receives / retrieves information for 611 from the UDM608, such as part of the SDM acquisition procedure. Therefore, the AMF606 can store trace control and configuration parameters as well as information for 611.

[0093]

[0116] In 618, similar to 518 in Figure 5, AMF606 initiates a trace session according to the received trace control and configuration parameters, for example, by sending a trace start message to RAN604. The trace start message may include trace control and configuration parameters. Unlike 518, in 618, AMF606 may send information for 611 to RAN604 in the trace start message or in a separate message. Thus, RAN504 can store the trace control and configuration parameters as well as the information for 611 and initiate a trace session. In certain embodiments, instead of sending all of the information for 611 to RAN604, AMF606 changes the information identifying one or more UEs from one or more persistent identifiers of one or more UEs (e.g., SUPI, IMEISV, etc.) to one or more temporary identifiers of one or more UEs and instead sends one or more temporary identifiers of one or more UEs. By using one or more temporary identifiers for one or more UEs, more sensitive information, such as one or more persistent identifiers, may be obscured from RAN604.

[0094]

[0117] In certain embodiments, if the information in 611 includes an encrypted / unencrypted configuration for data collection by one or more network entities, RAN604 (for example, after decrypting the configuration for data collection by one or more network entities) will begin measuring data of the type indicated in the configuration for data collection by one or more network entities if it is identified that data collection will be performed by information identifying one or more network entities.

[0095]

[0118] In 620, similar to 520 in Figure 5, RAN604 indicates to UE602 to collect data by transmitting the MDT configuration (and to any other UEs serviced by RAN604, identified in the information of 611, such as information identifying one or more UEs). For example, the MDT configuration may include at least some trace controls and configuration parameters. The MDT configuration may further include an encrypted configuration for data collection by one or more UEs. Thus, UE602 stores at least some trace controls and configuration parameters and / or the configuration for data collection by one or more UEs (for example, after UE602 has decrypted the encrypted configuration for data collection by one or more UEs). Furthermore, UE602 begins collecting data, such as by performing measurements corresponding to the type of data indicated in the configuration for data collection by one or more UEs. UE602 may transmit data further, as will be further described herein with respect to Figures 12-14.

[0096] Aspects related to AMF-based data acquisition configurations using network servers

[0119] Figure 7 shows a call flow diagram illustrating a call flow 700 for performing signaling-based MDT. Figure 7 shows an OAM 710 which may be a functional component of 5GC 190 in Figure 1. Figure 7 further shows a UDM 708 which may correspond to UDM 196 in Figure 1. Figure 7 further shows an AMF 706 which may correspond to AMF 192 in Figure 1. Figure 7 further shows a RAN entity 704 which may correspond to a network entity such as BS 102 in Figures 1 and 3, or a separate base station as described in relation to Figure 2. Figure 7 further shows a UE 702 which may correspond to UE 104 in Figures 1 and 3. Figure 7 further shows a server 709 which may correspond to a UE, DCAF, AF, AS, ASP, and / or any other network entity or server. In certain embodiments, the server 709 is located within the wireless communication network (e.g., the wireless communication network 100 in Figure 1) rather than outside the wireless communication network (e.g., hosted within it). For example, server 709 may be part of 5GC 190. In certain embodiments, server 709 is hosted by a UE vendor or a third party within a wireless communication network.

[0097]

[0120] Call flow 700 illustrates an example of how a server in a wireless communication network may provide a configuration for data collection to an AMF in the wireless communication network in order to configure UEs and / or network entities to perform data collection. Call flow 700 may be similar to call flow 600 in Figure 6, except that encrypted / unencrypted configuration for data collection by one or more UEs, information identifying one or more UEs, encrypted / unencrypted configuration for data collection by one or more network entities, and / or information identifying one or more network entities are sent to AMF706 instead of OAM710, configured in AMF706, or pre-configured in AMF706.

[0098]

[0121] Call flow 700 may be partially similar to call flow 600 in Figure 6 and partially similar to call flow 500 in Figure 5. In particular, 711 may be similar to 611 in Figure 6, except that server 709 transmits the information of 611 (encrypted / unencrypted configuration for data collection by one or more UEs, information identifying one or more UEs, encrypted / unencrypted configuration for data collection by one or more network entities, and / or information identifying one or more network entities) to AMF 706, or the information is configured or preconfigured in AMF 706 instead of OAM 710. Thus, in certain embodiments, AMF 706 may encrypt at least part of the information or have another entity encrypt it, similar to what has been described for OAM 610. In addition, 712, 714, and 716 are similar to 512, 514, and 516 in Figure 5, respectively. Furthermore, 718 is similar to 618 in Figure 6. For example, AMF706 starts a trace session (e.g., corrects) using the information of 711 (similar to the information of 611 as described above). Furthermore, 720 is similar to 620 in Figure 6.

[0099] Aspects related to OAM-based data acquisition configurations using non-network servers

[0122] Figure 8 shows a call flow diagram illustrating a call flow 800 for performing signaling-based MDT. Figure 8 shows an OAM 810 which may be a functional component of 5GC 190 in Figure 1. Figure 8 further shows a UDM 808 which may correspond to UDM 196 in Figure 1. Figure 8 further shows an AMF 806 which may correspond to AMF 192 in Figure 1. Figure 8 further shows a RAN entity 804 which may correspond to a network entity such as BS 102 in Figures 1 and 3, or a separate base station as described in relation to Figure 2. Figure 8 further shows a UE 802 which may correspond to UE 104 in Figures 1 and 3. Figure 8 further shows a server 809 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 certain embodiments, the server 809 is located outside the wireless communication network (e.g., outside the wireless communication network 100 in Figure 1) rather than inside the wireless communication network (e.g., hosted externally). Figure 8 further illustrates a network exposure function (NEF) 807, which may be a functional component of the 5GC 190 in Figure 1. In certain embodiments, the NEF 807 exposes core network capabilities, such as those of the 5GC 190, outside the wireless communication network, for example, to a third party.

[0100]

[0123] Call flow 800 illustrates an example of how a server outside the wireless communication network may provide a configuration for data collection to an OAM within the wireless communication network in order to configure the UE and / or network entities to perform data collection. Call flow 800 may be similar to call flow 600 in Figure 6 in certain ways, as described.

[0101]

[0124] In particular, 811 may be similar to 611 in Figure 6, except that server 809 transmits the information from 611 (e.g., an unencrypted configuration for data collection by one or more UEs, information identifying one or more UEs, an unencrypted configuration for data collection by one or more network entities, and / or information identifying one or more network entities) to NEF 807, or that the information is configured or pre-configured in OAM 810 and server 809 transmits an instruction to start a trace session, which is an example of an instruction to start data collection, to NEF 807. Furthermore, since server 809 is 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. Thus, NEF 807, like OAM 610, may verify / authorize the information and further encrypt at least a portion of the information.

[0102]

[0125] If, in 812, the server 809 receives an unencrypted configuration for data collection by one or more UEs, information identifying one or more UEs, an unencrypted configuration for data collection by one or more network entities, and / or information identifying one or more network entities, the NEF 807 sends an encrypted configuration for data collection by one or more UEs, information identifying one or more UEs, an encrypted configuration for data collection by one or more network entities, and / or information identifying one or more network entities to the OAM 810. If, in 812, the information is configured or pre-configured in the OAM 810 and the server 809 sends an instruction to the NEF 807 to start a trace session, the NEF 807 sends an instruction to the OAM 810 to start a trace session, which is an example of an instruction to start data collection. In 815, NEF807 sends a response to server 809 indicating that it has received an unencrypted configuration for data collection by one or more UEs, information identifying one or more UEs, an unencrypted configuration for data collection by one or more network entities, and / or information identifying one or more network entities. Furthermore, 813, 814, 816, 818, and 820 are the same as 612, 614, 616, 618, and 620 in Figure 6, respectively.

[0103] Aspects related to AMF-based data acquisition configurations using non-network servers

[0126] Figure 9 shows a call flow diagram illustrating a call flow 900 for performing signaling-based MDT. Figure 9 shows an OAM 910 which may be a functional component of 5GC 190 in Figure 1. Figure 9 further shows a UDM 908 which may correspond to UDM 196 in Figure 1. Figure 9 further shows an AMF 906 which may correspond to AMF 192 in Figure 1. Figure 9 further shows a RAN entity 904 which may correspond to a network entity such as BS 102 in Figures 1 and 3, or a separate base station as described in relation to Figure 2. Figure 9 further shows a UE 902 which may correspond to UE 104 in Figures 1 and 3. Figure 9 further shows a server 909 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 certain embodiments, the server 909 is located outside the wireless communication network (e.g., outside the wireless communication network 100 in Figure 1) rather than inside the wireless communication network (e.g., hosted externally). Figure 9 further shows the NEF907, which may be a functional component of the 5GC 190 in Figure 1.

[0104]

[0127] Call flow 900 illustrates an example of how a server outside the wireless communication network may provide a configuration for data collection to the AMF within the wireless communication network in order to configure the UE and / or network entities to perform data collection. Call flow 900 may be similar in certain ways to call flow 800 in Figure 8 and similar in certain ways to call flow 700 in Figure 7, as described.

[0105]

[0128] In particular, 911 may be similar to 811 in Figure 8, except that when configured or preconfigured, the information is configured or preconfigured in AMF906 instead of OAM910.

[0106]

[0129] In 912, if the server 909 receives an unencrypted configuration for data collection by one or more UEs, information identifying one or more UEs, an unencrypted configuration for data collection by one or more network entities, and / or information identifying one or more network entities, the NEF 907 transmits an encrypted configuration for data collection by one or more UEs, information identifying one or more UEs, an encrypted configuration for data collection by one or more network entities, and / or information identifying one or more network entities to the AMF 906. In 912, if the information is configured or pre-configured in the AMF 906 and the server 909 transmits an instruction to the NEF 907 to start a trace session, the NEF 907 transmits an instruction to the AMF 906 to start a trace session. In certain embodiments, in 912, one or more appropriate AMFs, including the AMF 906, are selected to transmit the aforementioned information from the NEF 907 to one or more AMFs. For example, information identifying one or more UEs may be used to determine which AMF(s) will serve one or more UEs, and such AMF(s) may be selected to transmit the aforementioned information from NEF907 to one or more AMFs. In certain embodiments, the selection of AMF(s) and / or communication from NEF90y to AMF(s) may be performed individually or collectively by one or more of NEF907, OAM910, and / or UDM908.

[0107]

[0130] Furthermore, 914 and 915 may be the same as 814 and 815 in Figure 8, respectively. In addition, 918 and 920 may be the same as 718 and 720 in Figure 7.

[0108] Aspects related to the management-based minimization (MDT) of drive tests

[0131] Figure 10 shows a call flow diagram illustrating a call flow 1000 for performing a management-based MDT. Figure 10 shows OAM1010, which may be a functional component of 5GC 190 in Figure 1. Figure 10 further shows AMF1006, which may correspond to AMF192 in Figure 1. Figure 10 further shows RAN entity 1004, which may correspond to a network entity such as BS 102 in Figures 1 and 3, or a separate base station as described in relation to Figure 2. Figure 10 further shows UE1002, which may correspond to UE104 in Figures 1 and 3.

[0109]

[0132] As shown in the figure, in 1012, AMF1006 transmits information identifying one or more UEs to RAN1004. The information identifying one or more UEs may include one or more identifiers of one or more PLMNs, such as one or more PLMNs on which data collection is permitted. Thus, the information identifies one or more UEs operating on / within one or more PLMNs. For example, the information identifying one or more UEs is transmitted in an initial context setup request or a handover request. RAN1004 may store the information identifying one or more UEs, such as storing the information as a UE context on which management-based MDT is permitted.

[0110]

[0133] Furthermore, as shown in 1014, OAM1010 sends an MDT activation command to RAN1004. The MDT activation command includes trace control and configuration parameters, such as instructions for parameters for configuring the UE for data acquisition. The MDT activation command may activate the trace session and configure UE1002 to collect data, such as standardized data as described. RAN1004 may store the trace control and configuration parameters.

[0111]

[0134] In 1016, RAN1004 selects one or more UEs for data collection using information that identifies one or more UEs. For example, RAN1004 may determine which UEs operate on one or more PLMNs identified in the information that identifies one or more UEs. Additionally or alternatively, RAN1004 may identify one or more UEs based on additional information in trace controls and configuration parameters, which may identify specific UE criteria, and therefore select one or more UEs that satisfy such UE criteria and / or are located in one or more PLMNs identified in the information that identifies one or more UEs. In this example, at least UE1002 is selected.

[0112]

[0135] In step 1018, RAN1004 transmits the MDT activation / configuration to UE1002, instructing UE1002 to collect data (e.g., standardized data). For example, the MDT activation may include at least some trace control and configuration parameters. Thus, UE1002 stores at least some of the trace control and configuration parameters and begins collecting data, such as by performing measurements corresponding to the data.

[0113] Aspects related to data collection configurations for management-based MDT

[0136] Figure 11 shows a call flow diagram illustrating a call flow 1100 for performing a management-based MDT. Figure 11 shows an OAM 1110 which may be a functional component of the 5GC 190 in Figure 1. Figure 11 further shows an AMF 1106 which may correspond to the AMF 192 in Figure 1. Figure 11 further shows a RAN entity 1104 which may correspond to a network entity such as the BS 102 in Figures 1 and 3, or a separate base station as described in relation to Figure 2. Figure 11 further shows a UE 1102 which may correspond to the UE 104 in Figures 1 and 3.

[0114]

[0137] Although not shown in Figure 11, before 1111, the call flow 1100 may include taking actions to provide the OAM 1110 and / or AMF 1106 with an encrypted / unencrypted configuration for data collection by one or more UEs, information identifying one or more UEs, an encrypted / unencrypted configuration for data collection by one or more network entities, and / or information identifying one or more network entities, respectively, in accordance with any one of the call flows 600 to 900 in Figures 6 to 9. For example, 611 in Figure 6 may be performed. In another embodiment, 711 in Figure 7 may be performed. In another embodiment, 811 and 812 in Figure 8 may be performed. In another embodiment, 911 and 912 in Figure 9 may be performed. However, in certain embodiments, unlike the call flows 600 to 900 in Figures 6 to 9, the information identifying one or more UEs may instead include one or more identifiers of one or more vendors, such as a UE vendor, instead of an explicit identifier of one or more UEs.

[0115]

[0138] Furthermore, as shown in the figure, in 1111, UE1102 transmits UE vendor information to RAN1104 that may indicate the vendor of the UE. In certain embodiments, UE1102 transmits UE vendor information as part of a connection establishment, connection re-establishment, restart, or reconfiguration procedure (for example, as part of one or more messages).

[0116]

[0139] As shown in the diagram, in 1112, AMF1106 transmits to RAN1104 one or more identifiers of one or more PLMNs, such as one or more PLMNs from which data collection is permitted. For example, one or more identifiers of one or more PLMNs are transmitted in an initial context setup request or a handover request. In certain embodiments, in 1112, AMF1106 transmits to RAN1104 information identifying one or more UEs, such as one or more identifiers of one or more vendors, in the same or different messages. RAN1104 may store one or more identifiers of one or more PLMNs and one or more identifiers of one or more vendors. In certain embodiments, instead of AMF1106 transmitting one or more identifiers of one or more vendors to RAN1104 in 1112, OAM1110 transmits one or more identifiers of one or more vendors to RAN1104 in 1114. In a particular embodiment, in 1112, AMF1106 transmits to RAN1104, or alternatively, in 1114, OAM1110 transmits to RAN1104 an encrypted configuration for data collection by one or more UEs, information identifying one or more UEs, an encrypted configuration for data collection by one or more network entities, and / or information identifying one or more network entities.

[0117]

[0140] As shown in 1114, OAM1110 sends an MDT activation command to RAN1104. The MDT activation command includes trace control and configuration parameters, such as instructions for parameters for configuring the UE for data collection. The MDT activation command may activate a trace session to configure UE1102 to collect data. RAN1104 may store the trace control and configuration parameters. In certain embodiments, as described, the MDT activation command may include an encrypted configuration for data collection by one or more UEs, information identifying one or more UEs, an encrypted configuration for data collection by one or more network entities, and / or information identifying one or more network entities.

[0118]

[0141] In 1116, RAN1104 selects one or more UEs for data collection using information that identifies 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. For example, in 1111, based on UE vendor information received from one or more UEs including UE1102, RAN1104 may select one or more UEs that have UE vendor information matching one or more identifiers of one or more vendors, as in the case of one or more UEs made by or otherwise associated with one or more vendors. In certain embodiments, one or more UEs are further identified as UEs operating on one or more PLMNs. For example, the selected one or more UEs(single or multiple) may be UEs that operate on one or more PLMNs and are associated with one or more vendors. In this example, at least UE1102 is selected.

[0119]

[0142] In certain embodiments, if RAN1104 is provided with an encrypted / unencrypted configuration for data collection by one or more network entities, RAN1104 (for example, after decrypting the configuration for data collection by one or more network entities) will begin performing data measurement of the type indicated in the configuration for data collection by one or more network entities if it is identified to perform data collection by information that identifies one or more network entities, etc.

[0120]

[0143] In 1118, RAN1104 transmits the MDT activation / configuration to UE1102 (and any other UE serviced by RAN1104 selected in 1116) and instructs UE1102 to collect data. For example, the MDT activation may include at least some trace controls and configuration parameters. The MDT activation may further include an encrypted configuration for data collection by one or more UEs. Thus, UE1102 stores at least some trace controls and configuration parameters and / or the configuration for data collection by one or more UEs (for example, after UE1102 decrypts the encrypted configuration for data collection by one or more UEs). Furthermore, UE1102 begins collecting data, such as by performing measurements corresponding to the type of data indicated in the configuration for data collection by one or more UEs.

[0121] Aspects related to reporting collected data

[0144] In certain embodiments, data collected by UEs and / or network entities may be reported to or transmitted back to a server (e.g., servers 609, 709, 809, or 909 in Figures 6-9) based on configurations for data collection by one or more UEs and / or configurations for data collection by one or more network entities, as described. The collected data may be transmitted end-to-end encrypted (e.g., containerized). In certain embodiments, the configurations for data collection by one or more UEs and / or configurations for data collection by one or more network entities may include the address of a server that may be used to report the collected data back to the server. In certain embodiments, the collected data may be encrypted (e.g., by the UEs and / or network entities) and transmitted to the server directly or via one or more additional entities.

[0122]

[0145] In certain embodiments, a UE may transmit data collected by the UE directly to the server, such as when the server is a trace collection entity (TCE) (which could be an entity in a wireless communications network, such as 5GC 190 in Figure 1). In certain embodiments, a network entity may transmit data collected by the network entity directly to the server, such as when the server is a TCE.

[0123]

[0146] In certain embodiments, a UE may transmit data collected by the UE to another entity, such as a TCE. In certain embodiments, a network entity may transmit data collected by the network entity to another entity, such as a TCE. The TCE may transmit data collected by the UE and / or network entities to a server.

[0124]

[0147] In certain embodiments, a network entity may transmit data collected by the network entity to a UE. The UE may transmit the data collected by the UE and the data collected by the network entity to a server, or to another entity, such as a TCE, which transmits the data collected by the UE 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 for data collection by one or more UEs, and after establishing the PDU session, transmit the data collected by the UE and the data collected by the network entity to the server.

[0125]

[0148] Figure 12 shows a call flow diagram illustrating a call flow 1200 for performing a report of the collected data. Figure 12 further shows a RAN entity 1204 which may correspond to a network entity such as BS 102 in Figures 1 and 3, or a separate base station as described in relation to Figure 2. Figure 12 further shows a UE 1202 which may correspond to UE 104 in Figures 1 and 3. Figure 12 further shows a server 1209 which may correspond to any of the servers 609 to 909 in Figures 6 to 9. Figure 12 further shows a TCE 1207.

[0126]

[0149] In 1212, UE1202 transmits the data collected by UE1202 (e.g., encrypted) to RAN1204. In 1214, if RAN1204 has data collected by RAN1204, RAN1204 combines the data collected by UE1202 with the data collected by RAN1204 (e.g., encrypted). In 1216, RAN1204 transmits the data collected by UE1202, and in some cases the data collected by RAN1204, to TCE1207. In some embodiments, TCE1207 corresponds to server1209. In some embodiments, TCE1207 is separate from server1209, and therefore, in 1218, TCE1207 transmits the data collected by UE1202, and in some embodiments the data collected by RAN1204, to server1209.

[0127]

[0150] Figure 13 shows a call flow diagram illustrating a call flow 1300 for performing a report of the collected data. Figure 13 further shows a RAN entity 1304 which may correspond to a network entity such as BS 102 in Figures 1 and 3, or a separate base station as described in relation to Figure 2. Figure 13 further shows a UE 1302 which may correspond to UE 104 in Figures 1 and 3. Figure 13 further shows a server 1309 which may correspond to any of the servers 609 to 909 in Figures 6 to 9. Figure 13 further shows a TCE 1307.

[0128]

[0151] In 1312, RAN1304 transmits the (e.g., encrypted) data collected by RAN1304 to UE1302. In 1314, UE1302 combines the (e.g., encrypted) data collected by UE1302 with the additional data collected by RAN1304. In 1316, UE1302 transmits the data collected by UE1302 and the additional data collected by RAN1304 to TCE1307. In some embodiments, TCE1307 corresponds to server1309. In some embodiments, TCE1307 is separate from server1309, and therefore, in 1318, TCE1307 transmits the data collected by UE1302 and the additional data collected by RAN1304 to server1309.

[0129]

[0152] Figure 14 shows a call flow diagram illustrating a call flow 1400 for performing a report of collected data. Figure 14 further shows a RAN entity 1404 which may correspond to a network entity such as BS 102 in Figures 1 and 3, or a separate base station as described in relation to Figure 2. Figure 14 further shows a UE 1402 which may correspond to UE 104 in Figures 1 and 3. Figure 14 further shows a server 1409 which may correspond to any of the servers 609 to 909 in Figures 6 to 9. Figure 14 further shows a TCE 1407.

[0130]

[0153] In 1412, UE1402 transmits the data collected by UE1402 to TCE1407. In 1416, RAN1404 transmits the data collected by RAN1404 to TCE1407. In some embodiments, TCE1407 corresponds to server1409. In some embodiments, TCE1407 is separate from server1409, and therefore, in 1418, TCE1407 transmits the data collected by UE1402 and the data collected by RAN1404 to server1409.

[0131] Aspects related to data collection by data collection services that include discovery services

[0154] Figure 15 shows a call flow diagram illustrating call flow 1500 for performing data collection by the data collection service.

[0132]

[0155] Figure 15 shows a data collection service 1509, which may be a functional component of the 5GC 190 in Figure 1. The data collection service 1509 may 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 certain embodiments, the data collection service 1509 is configured to implement an SLA between vendors, operators, etc.

[0133]

[0156] Figure 15 further illustrates a discovery service 1507, which may be a functional component of the 5GC 190 in Figure 1. The discovery service 1507 may be a service or process running on one or more servers, configured to provide the UE, etc., with information about the data collection service in order to enable the UE to connect to the data collection service.

[0134]

[0157] Figure 15 further illustrates a RAN entity 1504 that may correspond to a network entity such as BS 102 in Figures 1 and 3, or a separate base station as described in relation to Figure 2. Figure 11 further illustrates a UE 1502 that may correspond to UE 104 in Figures 1 and 3.

[0135]

[0158] Optionally, in 1512, the data collection service 1509 transmits information about the data collection service 1509 to the discovery service 1507, such as routing information for the data collection service 1509, vendor information indicating that a UE from a vendor is collecting data, and instructions for the purpose of data collection (e.g., for self-organizing networks / MDT, for artificial intelligence or machine learning functions, for other artificial intelligence or machine learning functions, for experience quality, etc.). In certain other embodiments, instead of the data collection service 1509 transmitting information about the data collection service 1509 to the discovery service 1507, the information about the data collection service 1509 may be configured or pre-configured in the discovery service 1507 in a different manner.

[0136]

[0159] In 1514, RAN1504 transmits discovery service information relating to discovery service 1507 to UE1502. The discovery service information may include routing information for discovery service 1507. In certain embodiments, the discovery service information is transmitted to UE1502 in a System Information Block (SIB) or dedicated signaling. In certain embodiments, the discovery service information is broadcast by RAN1504. In certain embodiments, the discovery service information is multicast by RAN1504. In certain embodiments, the discovery service information is unicast by RAN1504 (e.g., on demand).

[0137]

[0160] In 1516, UE1502 uses routing information for discovery service 1507 to send a request for information about one or more data collection services to discovery service 1507.

[0138]

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

[0139]

[0162] In 1520, UE1502 sends a connection establishment request to data collection service 1509 in order to establish a connection with data collection service 1509, based on the decision to communicate with data collection service 1509 as described. In certain embodiments, the connection establishment request includes one or more of the following: vendor information indicating the vendor of UE1502, an identifier for UE1502, etc.

[0140]

[0163] In 1522, in response to the connection establishment request, the data acquisition service 1509 transmits a configuration for data acquisition to the UE 1502, indicating one or more types of data that the UE will collect. In a particular embodiment, the one or more types of data that the UE will collect are determined according to the vendor and / or identifier of the UE 1502. In a particular embodiment, the UE 1502 begins collecting data, including performing measurements corresponding to the types of data indicated in the configuration for data acquisition. In a particular embodiment, in 1522, the data acquisition service 1509 further transmits a second configuration for data acquisition to the RAN 1504, indicating one or more types of data that the RAN 1504 will collect.

[0141]

[0164] In 1524, UE1502 transmits data to data collection service 1509 corresponding to one or more types of data indicated in the data collection configuration that shows one or more types of data that the UE collects.

[0142]

[0165] In a particular embodiment, in 1524, RAN 1504 transmits data corresponding to one or more types of data shown in a second configuration for data collection, which shows one or more types of data for RAN 1504 to collect, to the data collection service 1509.

[0143]

[0166] In a particular embodiment, in 1524, RAN 1504 sends data to UE 1502 corresponding to one or more types of data shown in a second configuration for data collection, which indicates one or more types of data for RAN 1504 to collect, and UE 1502 includes such data in the data transmitted to data collection service 1509.

[0144] Aspects related to data collection by data collection services that do not involve discovery services

[0167] Figure 16 shows a call flow diagram illustrating call flow 1600 for performing data collection by the data collection service.

[0145]

[0168] Figure 16 shows a data collection service 1609, which may be a functional component of the 5GC 190 in Figure 1. The data collection service 1609 may 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 certain embodiments, the data collection service 1609 is configured to implement an SLA between vendors, operators, etc.

[0146]

[0169] Figure 16 further illustrates a RAN entity 1604 that may correspond to a network entity such as BS 102 in Figures 1 and 3, or a separate base station as described in relation to Figure 2. Figure 11 further illustrates a UE 1602 that may correspond to UE 104 in Figures 1 and 3.

[0147]

[0170] In 1612, the data collection service 1609 transmits information about the data collection service 1609 to RAN 1604, including one or more of the following: routing information for the data collection service 1609, vendor information indicating that the UE from the vendor will collect data, and instructions for the purpose of collecting the data (e.g., for self-organizing networks / MDT, for artificial intelligence or machine learning functions, for another artificial intelligence or machine learning function, for experience quality, etc.).

[0148]

[0171] In 1614, RAN1604 transmits information about one or more data collection services, including information about data collection service 1609, to UE1602. In certain embodiments, information about one or more data collection services is transmitted to UE1502 in a System Information Block (SIB) or dedicated signaling. In certain embodiments, information about one or more data collection services is broadcast by RAN1504. In certain embodiments, information about one or more data collection services is multicast by RAN1504. In certain embodiments, information about one or more data collection services is unicast by RAN1504 (e.g., on demand).

[0149]

[0172] In certain embodiments, UE1602 determines which of one or more data collection services to communicate with based on information about one or more data collection services. For example, UE1602 may determine whether its vendor is the same as the vendor indicated by vendor information, which is included in the information about the data collection services and indicates that the UE will collect data from the vendor. If UE1602's vendor is the same as the vendor indicated by the vendor information, UE can communicate with the data collection service. If UE1602's vendor is not the same as the vendor indicated by the vendor information, UE cannot communicate with the data collection service.

[0150]

[0173] In 1616, UE1602 sends a connection establishment request to the data collection service 1609 in order to establish a connection with the data collection service 1609, based on the decision to communicate with the data collection service 1609 as described. In certain embodiments, the connection establishment request includes one or more of the following: vendor information indicating the vendor of UE1602, an identifier for UE1602, etc.

[0151]

[0174] In 1618, in response to the connection establishment request, the data acquisition service 1609 transmits a configuration for data acquisition to UE 1602, indicating one or more types of data that the UE will collect. In a particular embodiment, the one or more types of data that the UE will collect are determined according to the vendor and / or identifier of UE 1602. In a particular embodiment, UE 1602 begins collecting data, including performing measurements corresponding to the types of data indicated in the configuration for data acquisition. In a particular embodiment, in 1618, the data acquisition service 1609 further transmits a second configuration for data acquisition to RAN 1604, indicating one or more types of data that RAN 1604 will collect.

[0152]

[0175] In 1620, UE1602 transmits data to data collection service 1609 corresponding to one or more types of data indicated in the data collection configuration that indicates one or more types of data that the UE collects.

[0153]

[0176] In a particular embodiment, in 1620, RAN 1604 transmits data corresponding to one or more types of data shown in a second configuration for data collection, which shows one or more types of data for RAN 1604 to collect, to the data collection service 1609.

[0154]

[0177] In a particular embodiment, in 1620, RAN1604 sends data to UE1602 corresponding to one or more types of data shown in a second configuration for data collection, which indicates one or more types of data for RAN1604 to collect, and UE1602 includes such data in the data sent to data collection service 1609.

[0155] Exemplary behavior

[0178] Figure 17 shows a method 1700 for wireless communication by devices such as UE104 in Figures 1 and 3.

[0156]

[0179] Method 1700 begins in step 1705 by receiving an encrypted configuration for data collection that indicates one or more types of data to be collected by the device.

[0157]

[0180] Method 1700 then proceeds to step 1710, which decrypts the encrypted configuration for data collection.

[0158]

[0181] Method 1700 then proceeds to step 1715, transmitting data corresponding to one or more types of data.

[0159]

[0182] In certain embodiments, one or more types of data may include one or more of the following: the battery status of the device, the computational status of the device, Doppler diffusion, or Doppler delay.

[0160]

[0183] In certain embodiments, step 1715 may include encrypting the data and transmitting the encrypted data.

[0161]

[0184] In certain embodiments, step 1715 may include transmitting data to at least one of the following: a network entity, a trace collection entity, or a device outside the wireless communication network on which the device operates.

[0162]

[0185] In certain embodiments, method 1700 may further include receiving additional data from the network entity corresponding to the data collected by the network entity. Step 1715 may include transmitting the data and additional data.

[0163]

[0186] In certain embodiments, method 1700 may further include transmitting vendor information of the device to a network entity.

[0164]

[0187] In certain embodiments, step 1705 may include receiving an encrypted configuration from a network entity.

[0165]

[0188] In certain embodiments, Method 1700, or any embodiment thereof, may be carried out by a device such as the communication device 2100 of Figure 21, which includes various components that are operable, configured, or adapted to perform Method 1700. The communication device 2100 is described in more detail below.

[0166]

[0189] Please note that Figure 17 is merely one embodiment of the method, and other methods including fewer steps, additional steps, or alternative steps are possible in accordance with the Disclosure, and the above embodiments may be provided in any combination.

[0167]

[0190] Figure 18 shows a method 1800 for wireless communication using one or more devices, such as BS102 in Figures 1 and 3, or a separate base station as described in relation to Figure 2.

[0168]

[0191] Method 1800 begins in step 1805 by receiving information identifying one or more UEs by a first of one or more devices.

[0169]

[0192] Method 1800 then proceeds to step 1810, in which the first device transmits to one or more UEs an encrypted configuration for data collection indicating one or more types of data that each of the one or more UEs should collect.

[0170]

[0193] In certain embodiments, one or more types of data may include one or more of the following: battery state, computation state, Doppler spread, or Doppler delay.

[0171]

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

[0172]

[0195] In certain embodiments, method 1800 may further include transmitting data corresponding to one or more second types of data by the first device to at least one of one or more UEs, a trace collection entity, or a device outside the wireless communication network on which the first device operates.

[0173]

[0196] In certain embodiments, step 1810 may include, by the first device, encrypting data corresponding to one or more data of the second type, and transmitting the encrypted data.

[0174]

[0197] In certain embodiments, one or more devices may comprise a trace collection entity. Method 1800 may further include receiving data corresponding to one or more second types of data by the trace collection entity, and transmitting data corresponding to one or more second types of data to a device by the trace collection entity.

[0175]

[0198] In certain embodiments, method 1800 may further include, by the first device, receiving data corresponding to one or more types of data from one or more UEs.

[0176]

[0199] In certain embodiments, method 1800 may further include the first device transmitting data corresponding to one or more types of data to at least one of the following: a trace collection entity, a device outside the wireless communication network on which the first device operates.

[0177]

[0200] In certain embodiments, one or more devices may comprise a trace collection entity. Method 1800 may further include, by the trace collection entity, receiving data corresponding to one or more types of data, and by the trace collection entity, transmitting data corresponding to one or more types of data to a device.

[0178]

[0201] In certain embodiments, information identifying one or more UEs may include an explicit identifier for each of the one or more UEs.

[0179]

[0202] In certain embodiments, the information identifying one or more UEs may comprise 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, each of the one or more UEs being associated with one of the one or more vendors.

[0180]

[0203] In certain embodiments, method 1800 may further include receiving an encrypted configuration for data collection from a server.

[0181]

[0204] In certain embodiments, method 1800 may further include receiving a configuration for data collection from a server.

[0182]

[0205] In certain embodiments, method 1800 may further include encrypting the configuration for data collection.

[0183]

[0206] In certain embodiments, one or more devices may comprise an OAM, a UDM, and an AMF. The first device may comprise a radio access network entity. The method may further include the OAM transmitting an encrypted configuration for data collection to the UDM, the UDM transmitting an encrypted configuration for data collection to the AMF, and the AMF transmitting an encrypted configuration for data collection to the first device.

[0184]

[0207] In certain embodiments, method 1800 may further include receiving an encrypted configuration for data collection from a server via OAM.

[0185]

[0208] In certain embodiments, method 1800 may further include receiving a configuration for data collection from a server via OAM.

[0186]

[0209] In certain embodiments, method 1800 may further include encrypting the configuration for data collection by OAM.

[0187]

[0210] In certain embodiments, method 1800 may further include receiving one or more identifiers of one or more UEs by the AMF.

[0188]

[0211] In certain embodiments, method 1800 may further include transmitting information identifying one or more UEs to the first device by the AMF. The information identifying one or more UEs may comprise one or more second identifiers of one or more UEs, which are different from one or more identifiers of one or more UEs.

[0189]

[0212] In certain embodiments, one or more devices may include an NEF. Method 1800 may further include receiving a configuration for data collection from a server via the NEF, encrypting the configuration for data collection via the NEF, and transmitting the encrypted configuration for data collection to the OAM via the NEF.

[0190]

[0213] In certain embodiments, one or more devices may include an NEF. Method 1800 may further include receiving an instruction by the NEF to initiate data acquisition, and transmitting an instruction by the NEF to the OAM to initiate data acquisition.

[0191]

[0214] In certain embodiments, one or more devices may include an AMF. The first device may include a radio access network entity. Method 1800 may further include transmitting an encrypted configuration for data collection to the first device via the AMF.

[0192]

[0215] In certain embodiments, method 1800 may further include the AMF receiving an encrypted configuration for data collection from the server.

[0193]

[0216] In certain embodiments, method 1800 may further include the AMF receiving a configuration for data collection from a server.

[0194]

[0217] In certain embodiments, method 1800 may further include encrypting the configuration for data collection by the AMF.

[0195]

[0218] In certain embodiments, one or more devices may include an NEF. Method 1800 may further include receiving a configuration for data collection from a server via the NEF, encrypting the configuration for data collection via the NEF, and transmitting the encrypted configuration for data collection to the AMF via the NEF.

[0196]

[0219] In certain embodiments, one or more devices may include an NEF. Method 1800 may further include receiving an instruction by the NEF to start data acquisition, and transmitting an instruction by the NEF to the AMF to start data acquisition.

[0197]

[0220] In certain embodiments, Method 1800, or any embodiment thereof, may be carried out by a device such as the communication device 2200 in Figure 22, which includes various components that are operable, configured, or adapted to perform Method 1800. The communication device 2200 is described in more detail below.

[0198]

[0221] Figure 18 is merely one embodiment of the method, and other methods including fewer steps, additional steps, or alternative steps are possible in accordance with the Disclosure, and the above embodiments may be provided in any combination.

[0199]

[0222] Figure 19 shows a method 1900 for wireless communication by devices such as UE104 in Figures 1 and 3.

[0200]

[0223] Method 1900 begins in step 1905 by receiving information regarding the data collection service.

[0201]

[0224] Method 1900 then proceeds to step 1910, which receives a configuration for data acquisition from the data acquisition service indicating one or more types of data to be collected by the device.

[0202]

[0225] Method 1900 then proceeds to step 1915, which transmits data corresponding to one or more types of data to the data collection service.

[0203]

[0226] In certain embodiments, information relating to data collection services may include one or more of the following: routing information for one or more data collection services, including data collection services; vendor information indicating that equipment from a vendor collects data; or instructions for the purpose of collecting data.

[0204]

[0227] In certain embodiments, method 1900 may further include receiving signaling that provides routing information for discovery services.

[0205]

[0228] In certain embodiments, method 1900 may further include sending a request for information regarding data collection services to a discovery service. Receiving information regarding data collection services may include receiving information regarding data collection services from a discovery service.

[0206]

[0229] In certain embodiments, step 1905 may include receiving information regarding data collection services in the SIB or dedicated signaling from a first device among one or more devices.

[0207]

[0230] In certain embodiments, method 1900 may further include transmitting to the data collection service one or more of the following: vendor information indicating the vendor of the device, or an identifier for the device.

[0208]

[0231] In certain embodiments, method 1900 may further include receiving additional data from the network entity corresponding to the data collected by the network entity. Step 1915 may include transmitting the data and the additional data.

[0209]

[0232] In certain embodiments, Method 1900, or any embodiment thereof, may be carried out by a device such as the communication device 2300 in Figure 23, which includes various components that are operable, configured, or adapted to perform Method 1900. The communication device 2300 is described in more detail below.

[0210]

[0233] Figure 19 is merely one embodiment of the method, and other methods including fewer steps, additional steps, or alternative steps are possible in accordance with the Disclosure, and the above embodiments may be provided in any combination.

[0211]

[0234] Figure 20 shows a method 2000 for wireless communication using one or more devices, such as BS102 in Figures 1 and 3, or a separate base station as described with respect to Figure 2.

[0212]

[0235] Method 2000 begins in step 2005 by having the data acquisition service transmit to the UE a configuration for data acquisition indicating one or more types of data for the UE to collect, and one or more devices comprise the data acquisition service.

[0213]

[0236] Method 2000 then proceeds to step 2010, in which the data collection service receives data from the UE corresponding to one or more types of data.

[0214]

[0237] In certain embodiments, Method 2000 may further include transmitting to the UE information relating to a data collection service, including one or more of the following: routing information for the data collection service, vendor information indicating that the UE will collect data from a vendor, or instructions for the purpose of collecting data.

[0215]

[0238] In certain embodiments, one or more devices may comprise a discovery service. Method 2000 may further include, by a data collection service, transmitting a signaling having routing information for the discovery service, and by the discovery service receiving a request from the UE for information regarding the data collection service. Transmitting information regarding the data collection service may include transmitting information regarding the data collection service from the discovery service.

[0216]

[0239] In certain embodiments, transmitting information about data collection services may include transmitting information about data collection services from a first device among one or more devices in a SIB or dedicated signaling.

[0217]

[0240] In certain embodiments, method 2000 may further include transmitting information relating to the data collection service from the data collection service to the first device.

[0218]

[0241] In certain embodiments, Method 2000 may further include, by a data collection service, receiving from the UE one or more of the following: vendor information indicating the vendor of the UE, or an identifier of the UE.

[0219]

[0242] In certain embodiments, the method 2000 may further include, by a first device among one or more devices, receiving from a data acquisition service a second configuration for data indicating one or more second types of data to be collected by the first device.

[0220]

[0243] In certain embodiments, Method 2000 may further include transmitting data corresponding to one or more second types of data to at least one of a UE, a data collection service, by the first device.

[0221]

[0244] In certain embodiments, Method 2000, or any embodiment thereof, may be carried out by a device such as the communication device 2400 in Figure 24, which includes various components that are operable, configured, or adapted to perform Method 2000. The communication device 2400 is described in more detail below.

[0222]

[0245] Figure 20 is merely one embodiment of the method, and other methods including fewer steps, additional steps, or alternative steps are possible in accordance with the Disclosure, and the above embodiments may be provided in any combination.

[0223] Exemplary communication devices

[0246] Figure 21 shows an exemplary embodiment of the communication device 2100. In some embodiments, the communication device 2100 is a user device such as the UE104 described in relation to Figures 1 and 3.

[0224]

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

[0225]

[0248] The processing system 2105 includes one or more processors 2110. In various embodiments, one or more processors 2110 may represent one or more of the receiving processor 358, transmitting processor 364, TX MIMO processor 366, and / or controller / processor 380, as described with respect to Figure 3. One or more processors 2110 are coupled to a computer-readable medium / memory 2130 via a bus 2150. In certain embodiments, the computer-readable medium / memory 2130 is configured to store instructions (e.g., computer-executable code) to be executed by one or more processors 2110, enabling them to execute the method 1700 described with respect to Figure 17, or any related embodiments including any additional steps or substeps described with respect to Figure 17, and the method 1900 described with respect to Figure 19, or any related embodiments including any additional steps or substeps described with respect to Figure 19. Please note that references to processors that perform the functions of communication device 2100 may include one or more processors that perform those functions of communication device 2100 in a distributed manner or similar.

[0226]

[0249] In the illustrated example, the computer-readable medium / memory 2130 stores a code 2135 for receiving, a code 2140 for decoding, and a code 2145 for transmitting. The processing of codes 2135-2145 enables and may cause the communication device 2100 to perform the method 1700 described with respect to Figure 17, or any related aspect thereof, and the method 1900 described with respect to Figure 19, or any related aspect thereof.

[0227]

[0250] One or more processors 2110 include circuits configured to implement (e.g., execute) code stored in a computer-readable medium / memory 2130, including a circuit 2115 for receiving, a circuit 2120 for decoding, and a circuit 2125 for transmitting. Processing by circuits 2115-2125 enables and may cause the communication device 2100 to perform method 1700 or any related aspect thereof as described with respect to Figure 17, and method 1900 or any related aspect thereof as described with respect to Figure 19.

[0228]

[0251] More generally, means for communicating, transmitting, sending, or outputting for transmission may include the transceiver 354, antenna(s) 352, transmit processor 364, TX MIMO processor 366, and / or controller / processor 380 of the UE104 shown in Figure 3, the transceiver 2155 and / or antenna 2160 of the communication device 2100 in Figure 21, and / or one or more processors 2110 of the communication device 2100 in Figure 21. Means for communicating, receiving, or acquiring may include the transceiver 354, antenna(s) 352, receive processor 358, and / or controller / processor 380 of the UE104 shown in Figure 3, the transceiver 2155 and / or antenna 2160 of the communication device 2100 in Figure 21, and / or one or more processors 2110 of the communication device 2100 in Figure 21.

[0229]

[0252] Figure 22 shows an exemplary embodiment of the communication device 2200. In some embodiments, the communication device 2200 is a network entity, such as BS102 in Figures 1 and 3, or a separate base station as described with respect to Figure 2.

[0230]

[0253] The 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 the communication device 2200, such as various signals as described herein, via an antenna 2260. The network interface 2265 is configured to acquire and transmit signals for the communication device 2200 via one or more communication links, such as backhaul links, midhaul links, and / or fronthaul links as described herein, as shown in Figure 2. The processing system 2205 may be configured to perform processing functions relating to the communication device 2200, including processing signals received and / or to be transmitted by the communication device 2200.

[0231]

[0254] The processing system 2205 includes one or more processors 2210. In various embodiments, one or more processors 2210 may represent one or more of the receiving processor 338, transmitting processor 320, TX MIMO processor 330, and / or controller / processor 340, as described with respect to Figure 3. One or more processors 2210 are coupled to computer-readable medium / memory 2230 via bus 2250. In certain embodiments, computer-readable medium / memory 2230 is configured to store instructions (e.g., computer-executable code) that enable and cause one or more processors 2210 to perform, when executed by one or more processors 2210, the method 1800 described with respect to Figure 18, or any related embodiments including any additional steps or substeps described with respect to Figure 18, and the method 2000 described with respect to Figure 20, or any related embodiments including any additional steps or substeps described with respect to Figure 20. Please note that references to the processor of the communication device 2200 that performs the function may include one or more processors of the communication device 2200 that perform that function, such as in a distributed scheme.

[0232]

[0255] In the illustrated example, the computer-readable medium / memory 2230 stores a code 2235 for receiving, a code 2240 for transmitting, and a code 2245 for encryption. Processing of codes 2235-2245 enables and may cause the communication device 2200 to perform the method 1800 described with respect to Figure 18, or any related aspect thereof, and the method 2000 described with respect to Figure 20, or any related aspect thereof.

[0233]

[0256] One or more processors 2210 include circuits configured to implement (e.g., execute) code stored in computer-readable media / memory 2230, including a circuit 2215 for receiving, a circuit 2220 for transmitting, and a circuit 2225 for encryption. Processing using circuits 2215-2225 enables and may cause the communication device 2200 to perform the method 1800 described with respect to Figure 18, or any related aspect thereof, and the method 2000 described with respect to Figure 20, or any related aspect thereof.

[0234]

[0257] More generally, means for communicating, transmitting, sending, or outputting for transmission may include the transceiver 332, antenna(s) 334, transmitting processor 320, TX MIMO processor 330, and / or controller / processor 340 of BS 102 shown in Figure 3, the transceiver 2255 and / or antenna 2260 of communication device 2200 in Figure 22, and / or one or more processors 2210 of communication device 2200 in Figure 22. Means for communicating, receiving, or acquiring may include the transceiver 332, antenna(s) 334, receiving processor 338, and / or controller / processor 340 of BS 102 shown in Figure 3, the transceiver 2255 and / or antenna 2260 of communication device 2200 in Figure 22, and / or one or more processors 2210 of communication device 2200 in Figure 22.

[0235]

[0258] Figure 23 shows an exemplary embodiment of the communication device 2300. In some embodiments, the communication device 2300 is a user device such as the UE104 described above with respect to Figures 1 and 3.

[0236]

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

[0237]

[0260] The processing system 2305 includes one or more processors 2310. In various embodiments, one or more processors 2310 may represent one or more of the receiving processor 358, transmitting processor 364, TX MIMO processor 366, and / or controller / processor 380, as described with respect to Figure 3. One or more processors 2310 are coupled to computer-readable medium / memory 2325 via bus 2340. In certain embodiments, computer-readable medium / memory 2325 is configured to store instructions (e.g., computer-executable code) to be executed by one or more processors 2310, enabling them to execute method 1700 as described with respect to Figure 17, or any related embodiments including any additional steps or substeps described with respect to Figure 17, and method 1900 as described with respect to Figure 19, or any related embodiments including any additional steps or substeps described with respect to Figure 19. Please note that references to processors that perform the functions of communication device 2300 may include one or more processors that perform those functions of communication device 2300 in a distributed manner or similar.

[0238]

[0261] In the illustrated example, the computer-readable medium / memory 2325 stores a code 2330 for receiving and a code 2335 for transmitting. Processing of codes 2330 and 2335 enables and may cause the communication device 2300 to perform the method 1700 described with respect to Figure 17, or any related aspect thereof, and the method 1900 described with respect to Figure 19, or any related aspect thereof.

[0239]

[0262] One or more processors 2310 include circuits configured to implement (e.g., execute) code stored in a computer-readable medium / memory 2325, including a circuit 2315 for receiving and a circuit 2320 for transmitting. Processing using circuits 2315 and 2320 enables and may cause the communication device 2300 to perform the method 1700 described with respect to Figure 17, or any related aspect thereof, and the method 1900 described with respect to Figure 19, or any related aspect thereof.

[0240]

[0263] More generally, means for communicating, transmitting, sending, or outputting for transmission may include the transceiver 354, antenna(s) 352, transmit processor 364, TX MIMO processor 366, and / or controller / processor 380 of the UE104 shown in Figure 3, the transceiver 2345 and / or antenna 2350 of the communication device 2300 in Figure 23, and / or one or more processors 2310 of the communication device 2300 in Figure 23. Means for communicating, receiving, or acquiring may include the transceiver 354, antenna(s) 352, receive processor 358, and / or controller / processor 380 of the UE104 shown in Figure 3, the transceiver 2345 and / or antenna 2350 of the communication device 2300 in Figure 23, and / or one or more processors 2310 of the communication device 2300 in Figure 23.

[0241]

[0264] Figure 24 shows an exemplary configuration of the communication device 2400. In some configurations, the communication device 2400 is a network entity, such as BS102 in Figures 1 and 3, or a separate base station as described with respect to Figure 2.

[0242]

[0265] The 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 the communication device 2400, such as various signals as described herein, via an antenna 2450. The network interface 2455 is configured to acquire and transmit signals for the communication device 2400 via one or more communication links, such as backhaul links, midhaul links, and / or fronthaul links as described herein, as shown in Figure 2. The processing system 2405 may be configured to perform processing functions relating to the communication device 2400, including processing signals received and / or to be transmitted by the communication device 2400.

[0243]

[0266] The processing system 2405 includes one or more processors 2410. In various embodiments, one or more processors 2410 may represent one or more of the receiving processor 338, transmitting processor 320, TX MIMO processor 330, and / or controller / processor 340, as described with respect to Figure 3. One or more processors 2410 are coupled to computer-readable medium / memory 2425 via bus 2440. In certain embodiments, computer-readable medium / memory 2425 is configured to store instructions (e.g., computer-executable code) that enable and cause one or more processors 2410 to perform, when executed by one or more processors 2410, the method 1800 described with respect to Figure 18, or any related embodiments including any additional steps or substeps described with respect to Figure 18, and the method 2000 described with respect to Figure 20, or any related embodiments including any additional steps or substeps described with respect to Figure 20. Please note that references to the processor of the communication device 2400 that performs the function may include one or more processors of the communication device 2400 that perform that function, such as in a distributed scheme.

[0244]

[0267] In the illustrated example, the computer-readable medium / memory 2425 stores a code 2430 for transmission and a code 2435 for reception. Processing of codes 2430 and 2435 enables and may cause the communication device 2400 to perform the method 1800 described with respect to Figure 18, or any related aspect thereof, and the method 2000 described with respect to Figure 20, or any related aspect thereof.

[0245]

[0268] One or more processors 2410 include circuits configured to implement (e.g., execute) code stored in a computer-readable medium / memory 2425, including a circuit 2415 for transmitting and a circuit 2420 for receiving. Processing using circuits 2415 and 2420 enables and may cause the communication device 2400 to perform or cause to perform the method 1800 described with respect to Figure 18, or any related aspect thereof, and the method 2000 described with respect to Figure 20, or any related aspect thereof.

[0246]

[0269] More generally, means for communicating, transmitting, sending, or outputting for transmission may include the transceiver 332, antenna(s) 334, transmit processor 320, TX MIMO processor 330, and / or controller / processor 340 of BS 102 shown in Figure 3, the transceiver 2445 and / or antenna 2450 of communication device 2400 in Figure 24, and / or one or more processors 2410 of communication device 2400 in Figure 24. Means for communicating, receiving, or acquiring may include the transceiver 332, antenna(s) 334, receive processor 338, and / or controller / processor 340 of BS 102 shown in Figure 3, the transceiver 2445 and / or antenna 2450 of communication device 2400 in Figure 24, and / or one or more processors 2410 of communication device 2400 in Figure 24.

[0247] Exemplary clause

[0270] The implementation forms are described in the following numbered clauses.

[0248]

[0271] Clause 1: A method for wireless communication by a device, comprising: receiving an encrypted configuration for data collection 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 one or more types of data.

[0249]

[0272] Clause 2: The method according to Clause 1, wherein one or more types of data include one or more of the device's battery status, device's computational status, Doppler diffusion, or Doppler delay.

[0250]

[0273] Clause 3: The method of Clause 1 or 2, which includes transmitting data, encrypting the data, and transmitting encrypted data.

[0251]

[0274] Clause 4: The method described in any one of Clauses 1 to 3, wherein transmitting data includes transmitting data to at least one of the following: a network entity, a trace collection entity, or a device outside the wireless communications network on which the device operates.

[0252]

[0275] Clause 5: Transmitting data, including receiving additional data from the network entity corresponding to data collected by the network entity, as described in any one of Clauses 1 to 4.

[0253]

[0276] Clause 6: The method described in any one of Clauses 1 to 5, further comprising transmitting vendor information of the device to a network entity.

[0254]

[0277] Clause 7: Receiving an encrypted configuration is the method described in any one of Clauses 1 through 6, including receiving an encrypted configuration from a network entity.

[0255]

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

[0256]

[0279] Clause 9: The method described in Clause 8, wherein one or more types of data include one or more of battery status, computation status, Doppler spread, or Doppler delay.

[0257]

[0280] The method according to Clause 10: The first device receiving a second configuration for data indicating one or more second types of data to be collected by the first device, and the first device transmitting data corresponding to one or more second types of data to at least one of one or more UEs, a trace collection entity, or a device outside the wireless communication network on which the first device operates.

[0258]

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

[0259]

[0282] Clause 12: The method according to Clause 10, wherein one or more devices comprises a trace collection entity, and the method further comprises the trace collection entity receiving data corresponding to one or more second types of data, and the trace collection entity transmitting data corresponding to one or more second types of data to the device.

[0260]

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

[0261]

[0284] Clause 14: The method of Clause 13, wherein one or more devices comprises a trace collection entity, and the method further comprises receiving data corresponding to one or more types of data by the trace collection entity, and transmitting data corresponding to one or more types of data to the device by the trace collection entity.

[0262]

[0285] Clause 15: Information identifying one or more UEs is provided as described in any one of Clauses 8 to 14, comprising the explicit identifier of each of the one or more UEs.

[0263]

[0286] Clause 16: The method of any one of Clauses 8 to 15, wherein the information identifying one or more UEs comprises one or more identifiers of one or more vendors, and the method further comprises receiving corresponding vendor information for a UE from each of one or more UEs, and each of one or more UEs is associated with one of the one or more vendors.

[0264]

[0287] Clause 17: The method described in any one of Clauses 8 to 16, further comprising receiving an encrypted configuration for data collection from the server.

[0265]

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

[0266]

[0289] Clause 19: The method according to any one of Clauses 8 to 18, wherein one or more devices comprises an OAM, a UDM, and an AMF, and the first device comprises a radio access network entity, and the method further comprises transmitting an encrypted configuration for data collection to the UDM by the OAM, transmitting an encrypted configuration for data collection to the AMF by the UDM, and transmitting an encrypted configuration for data collection to the first device by the AMF.

[0267]

[0290] Clause 20. The method of Clause 19, further comprising receiving, by OAM, an encrypted configuration for data collection from a server.

[0268]

[0291] Clause 21. The method of Clause 19, further comprising receiving, by OAM, a configuration for data collection from a server; and encrypting, by OAM, the configuration for data collection.

[0269]

[0292] Clause 22. The method of Clause 19, further comprising receiving, by AMF, one or more identifiers of one or more UEs; and transmitting, by AMF, information identifying the one or more UEs to a first apparatus, wherein the information identifying the one or more UEs comprises 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.

[0270]

[0293] Clause 23. The method of Clause 19, wherein the one or more apparatuses comprise a NEF, the method further comprising receiving, by the NEF, a 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 OAM.

[0271]

[0294] Clause 24. The method of Clause 19, wherein the one or more apparatuses comprise a NEF, the method further comprising receiving, by the NEF, an instruction to start data collection; and transmitting, by the NEF, the instruction to start data collection to OAM.

[0272]

[0295] Clause 25. The method of any one of Clauses 8 to 24, wherein the one or more apparatuses comprise an AMF, the first apparatus comprises a radio access network entity, and the method further comprises transmitting, by the AMF, an encrypted configuration for data collection to the first apparatus.

[0273]

[0296] Clause 26: The method of Clause 25, further comprising receiving an encrypted configuration for data collection from the server by the AMF.

[0274]

[0297] The method of Clause 25, further comprising: Clause 27: AMF receiving a configuration for data collection from a server; and AMF encrypting the configuration for data collection.

[0275]

[0298] Clause 28: The method of Clause 25, wherein one or more devices are equipped with an NEF, and the method further comprises: receiving a 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.

[0276]

[0299] Clause 29: The method of Clause 25, wherein one or more devices are equipped with an NEF, and the method further comprises receiving an instruction by the NEF to initiate data collection, and transmitting an instruction by the NEF to the AMF to initiate data collection.

[0277]

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

[0278]

[0301] Clause 31: The method described in Clause 30, wherein information relating to data collection services includes one or more of the following: routing information for one or more data collection services, including data collection services; vendor information indicating that equipment from a vendor collects data; or instructions for the purpose of collecting data.

[0279]

[0302] Clause 32: The method of Clause 30 or 31, further comprising receiving a signaling having routing information for a discovery service, and sending a request to the discovery service for information about a data collection service, wherein receiving information about a data collection service includes receiving information about a data collection service from the discovery service.

[0280]

[0303] Clause 33: The method described in any one of Clauses 30 to 32, wherein receiving information relating to data collection services includes receiving information relating to data collection services in SIB or dedicated signaling from a first of one or more devices.

[0281]

[0304] Clause 34: The method of any one of Clauses 30 to 33, further comprising transmitting to the data collection service one or more of the following: vendor information indicating the vendor of the device, or an identifier of the device.

[0282]

[0305] Clause 35: Transmitting data, which further includes receiving additional data from the network entity corresponding to data collected by the network entity, as described in any one of Clauses 30 to 34, including transmitting data and additional data.

[0283]

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

[0284]

[0307] Clause 37: The method of Clause 36, further comprising transmitting to the UE information relating to the data collection service, which includes one or more of the following: routing information for the data collection service, vendor information from the vendor indicating that the UE will collect data, or instructions for the purpose of collecting data.

[0285]

[0308] Clause 38: The method of Clause 37, wherein one or more devices include a discovery service, and the method further includes, by a data collection service, transmitting a signaling having routing information for the discovery service, and in the discovery service, receiving a request from a UE for information about the data collection service, and transmitting information about the data collection service, and the method of transmitting information about the data collection service from the discovery service.

[0286]

[0309] Clause 39: The method of Clause 37, which includes transmitting information relating to data collection services from a first device of one or more devices in the SIB or dedicated signaling.

[0287]

[0310] Clause 40: The method of Clause 39, further comprising transmitting information relating to the data collection service from the data collection service to the first device.

[0288]

[0311] Clause 41: The method described in any one of Clauses 36 to 40, further comprising receiving from the UE one or more of the following from the UE: vendor information indicating the vendor of the UE, or an identifier of the UE.

[0289]

[0312] The method described in any one of the clauses 36 to 41, further comprising: the first device receiving a second configuration for data indicating one or more second types of data to be collected by the first device; and the first device transmitting data corresponding to one or more second types of data to at least one of the UE, data collection services.

[0290]

[0313] Clause 43: One or more apparatuses, comprising: one or more memories storing executable instructions; and one or more processors configured to execute the executable instructions, wherein the one or more apparatuses execute the executable instructions to cause the method according to any one of Clauses 1 to 42 to be performed.

[0291]

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

[0292]

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

[0293]

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

[0294] Additional Considerations

[0317] The foregoing description is provided to enable any person skilled in the art to practice the various embodiments described herein. The embodiments discussed herein do not limit the scope, applicability, or embodiments set forth in the claims. Various modifications to these embodiments will be readily apparent to a person skilled in the art, and the general principles defined herein may also be applied to other embodiments. For example, changes may be made to the function and configuration of the elements discussed without departing from the scope of this disclosure. Various embodiments may omit, substitute, or add various procedures or components as needed. For example, the methods described may be performed in an order different from the order described, and various actions may be added, omitted, or combined. Also, features described in some embodiments may be combined in some other embodiments. For example, an apparatus may be implemented or a method may be practiced using any number of embodiments described herein. Furthermore, the scope of this disclosure is intended to encompass apparatus or methods that are practiced using other structures, functions, or structures and functions in addition to, or other than, the various embodiments of this disclosure described herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of the claims.

[0295]

[0318] The various exemplary logic blocks, modules, and circuits described in connection with this disclosure may be implemented or run using general-purpose processors, digital signal processors (DSPs), ASICs, field programmable gate arrays (FPGAs), or other programmable logic devices (PLDs), individual gate logic or transistor logic, individual hardware components, or any combination thereof, designed to perform the functions described herein. A general-purpose processor may be a microprocessor; alternatively, a processor may be any commercially available processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors working with a DSP core, a system on a chip (SoC), or any other such configuration.

[0296]

[0319] Where used herein, the phrase “at least one of” the list of items refers to any combination of those items, including a single member. For example, “at least one of a, b, or c” is intended to include a, b, c, ab, ac, bc, and abc, as well as any combination having multiple identical elements (e.g., aa, aaa, aab, aac, abb, acc, bb, bbb, bbc, cc, and ccc, or any other sequence of a, b, and c).

[0297]

[0320] As used herein, the term “determining” encompasses a wide range of actions. For example, “determining” may include calculating, calculating, processing, deriving, investigating, searching (e.g., searching a table, database, or other data structure), and confirming. It may also include receiving (e.g., receiving information), accessing (e.g., accessing data in memory), and resolving, selecting, choosing, and establishing.

[0298]

[0321] As used herein, “to be coupled” and “to be coupled” generally encompass direct coupling and indirect coupling (including, for example, intermediate coupling) unless otherwise specified. For example, stating that a processor is coupled to memory may mean direct coupling or coupling via an intermediate mode such as a bus.

[0299]

[0322] The methods disclosed herein include one or more actions for achieving the method. The actions of those methods can be interchanged with one another without departing from the claims. In other words, unless a particular order of actions is specified, the order and / or use of any particular action can be modified without departing from the claims. Furthermore, the various operations of the methods described above can be performed by any preferred means capable of performing the corresponding function. These means may include, but are not limited to, a variety of hardware components and / or software components, including circuits, application-specific integrated circuits (ASICs), or processors, and / or a variety of hardware modules and / or software modules.

[0300]

[0323] The following claims are not intended to be limited to the embodiments shown herein, and the full scope consistent with the language of the claims should be recognized. References to singular elements should mean "one or more" and not "only one" unless otherwise specified. For example, references to elements (e.g., "processor," "controller," "memory") should be understood to refer to one or more elements (e.g., "one or more processors," "one or more controllers," "one or more memories") unless otherwise specified. The terms "set" and "group" are intended to include one or more elements and may be used interchangeably with "one or more." When one or more elements performing a function (e.g., steps of a method) are referred to, one element may perform all the functions, or two or more elements may collectively perform the functions. When two or more elements collectively perform a function, each function does not have to be performed by each of those elements (for example, different functions may be performed by different elements), and / or each function does not have to be performed entirely by only one element (for example, different elements may perform different sub-functions of a function). Similarly, when one or more elements are referred to that are configured to cause another element (for example, a device) to perform a function, one element may be configured to cause the other elements to perform all the functions, or two or more elements may be collectively configured to cause the other elements to perform the functions. Unless otherwise specified, the term “several” means one or more. All structural and functional equivalents to the various aspects of the elements described throughout this disclosure, which are known to those skilled in the art or will become known later, are intended to be covered by the claims. Furthermore, nothing disclosed herein is intended to be made public, regardless of whether such disclosure is expressly enumerated in the claims.

Claims

1. A device for wireless communication in a network entity, wherein the device includes a memory containing processor-executable instructions, and one or more processors that execute the processor-executable instructions and the device, Receiving an encrypted configuration for data collection indicating one or more types of data collected by the aforementioned device, Decrypting the encrypted configuration for data collection, A device comprising one or more processors configured to transmit data corresponding to one or more of the aforementioned types of data.

2. The aforementioned one or more types of data are The battery status of the aforementioned device, The calculation state of the aforementioned device, Doppler diffusion, The apparatus according to claim 1, comprising one or more of the following: or Doppler delay.

3. In order to transmit the aforementioned data, one or more processors execute the processor-executable instructions and the device, Encrypting the aforementioned data, The apparatus according to claim 1, configured to transmit the encrypted data and to perform the following actions.

4. In order to transmit the aforementioned data, one or more processors execute the processor-executable instructions and the device, The aforementioned data, Network entity, Trace collection entity, The apparatus according to claim 1, configured to transmit to at least one of the following: or a device outside the wireless communication network on which the apparatus operates.

5. The one or more processors execute the processor-executable instructions and the device, It is configured to receive additional data from the network entity corresponding to the data collected by the network entity, In order to transmit the aforementioned data, one or more processors execute the processor-executable instructions and the device, The apparatus according to claim 1, configured to transmit the aforementioned data and the additional data.

6. The one or more processors execute the processor-executable instructions and the device, The apparatus according to claim 1, configured to transmit vendor information of the apparatus to a network entity.

7. In order to receive the encrypted configuration, one or more processors execute the processor executable instructions and the device, The apparatus according to claim 1, configured to receive the encrypted configuration from a network entity.

8. One or more devices configured for wireless communication, wherein the one or more devices include a memory containing processor-executable instructions, and one or more processors that execute the processor-executable instructions and provide the one or more devices with The first of the one or more devices mentioned above receives information identifying one or more user equipment (UEs), One or more devices comprising: one or more processors, the first device configured to transmit to the one or more UEs an encrypted configuration for data collection indicating one or more types of data that each of the one or more UEs should collect;

9. The aforementioned one or more types of data are Battery status, Calculation status, Doppler diffusion, One or more devices according to claim 8, comprising one or more of the following: or Doppler delay.

10. The one or more processors execute the processor-executable instructions and the device, The first device receives a second configuration for data indicating one or more second types of data to be collected by the first device, The first device generates data corresponding to one or more second types of data. At least one of the one or more UEs mentioned above, Trace collection entity, One or more devices according to claim 8, configured to transmit to at least one of the following: or a device outside the wireless communication network on which the first device operates.

11. In order to transmit the aforementioned data, one or more processors execute the processor-executable instructions and transmit them to one or more devices. The first device encrypts the data corresponding to one or more second types of data, One or more devices according to claim 10, configured to transmit the encrypted data.

12. The one or more devices comprises the trace acquisition entity, the one or more processors execute the processor executable instructions, and the one or more devices, The trace collection entity receives the data corresponding to the one or more second types of data, The one or more devices according to claim 10, wherein the trace collection entity is configured to transmit the data corresponding to the one or more second types of data to the device.

13. The one or more processors execute the processor-executable instructions and the device, The first device receives data corresponding to one or more types of data from one or more UEs, The first device processes the data corresponding to one or more types of data. Trace collection entity, One or more devices according to claim 8, configured to transmit to at least one of the following: or a device outside the wireless communication network on which the first device operates.

14. The one or more devices comprises the trace acquisition entity, the one or more processors execute the processor executable instructions, and the one or more devices, The trace collection entity receives the data corresponding to one or more types of data, The one or more devices according to claim 13, wherein the trace collection entity is configured to transmit the data corresponding to the one or more types of data to the device.

15. The one or more devices according to claim 8, wherein the information identifying one or more UEs comprises an explicit identifier for each of the one or more UEs.

16. The information identifying one or more UEs comprises one or more identifiers of one or more vendors, The one or more processors execute the processor-executable instructions and provide the one or more devices The one or more devices according to claim 8, configured to receive corresponding vendor information for each of the one or more UEs, and each of the one or more UEs being associated with one of the one or more vendors.

17. The one or more processors execute the processor-executable instructions and the device, One or more devices according to claim 8, configured to receive an encrypted configuration for data collection from a server.

18. The one or more processors execute the processor-executable instructions and the device, Receiving the aforementioned configuration for data collection from the server, One or more devices according to claim 8, configured to encrypt the aforementioned configuration for data collection.

19. The one or more of the above devices include operation, management, and maintenance (OAM), integrated data management (UDM), and access and mobility functions (AMF), The first device comprises a wireless access network entity, The one or more processors execute the processor-executable instructions and provide the one or more devices The OAM transmits the encrypted configuration for data collection to the UDM, The UDM transmits the encrypted configuration for data collection to the AMF, The one or more devices according to claim 8, wherein the AMF is configured to cause the first device to transmit the encrypted configuration for data collection.

20. The one or more processors execute the processor-executable instructions and the device, The device according to claim 19, wherein the OAM is configured to receive the encrypted configuration for data collection from the server.

21. The one or more processors execute the processor-executable instructions and the device, The aforementioned OAM receives the aforementioned configuration for data collection from the server, The device according to claim 19, wherein the OAM is configured to encrypt the configuration for data collection and to perform the above-mentioned actions.

22. The one or more processors execute the processor-executable instructions and the device, The AMF receives one or more identifiers of the one or more UEs, The one or more devices according to claim 19, wherein the AMF is configured to transmit the information identifying the one or more UEs to the first device, and the information identifying the one or more UEs comprises a second identifier for the one or more UEs that is different from the one or more identifiers of the one or more UEs.

23. The one or more devices are equipped with a network exposure function (NEF), and the one or more processors execute the processor executable instructions and provide the one or more devices with The NEF receives the aforementioned configuration for data collection from the server, The NEF encrypts the aforementioned configuration for data collection, The device according to claim 19, wherein the NEF is configured to transmit the encrypted configuration for data collection to the OAM.

24. The one or more devices are equipped with a network exposure function (NEF), and the one or more processors execute the processor executable instructions and provide the one or more devices with The NEF receives an instruction to start data collection, The device according to claim 19, wherein the NEF is configured to transmit the instruction to the OAM to start data collection, and the device is configured to perform the above.

25. The one or more of the aforementioned devices are equipped with access and mobility functions (AMF), The first device comprises a wireless access network entity, The one or more processors execute the processor-executable instructions and provide the one or more devices The one or more devices according to claim 8, wherein the AMF is configured to cause the first device to transmit the encrypted configuration for data collection.

26. The one or more processors execute the processor-executable instructions and the device, The device according to claim 25, wherein the AMF is configured to receive the encrypted configuration for data collection from the server.

27. The one or more processors execute the processor-executable instructions and the device, The AMF receives the aforementioned configuration for data collection from the server, The device according to claim 25, wherein the AMF is configured to encrypt the configuration for data collection and to perform the following actions.

28. The one or more devices are equipped with a network exposure function (NEF), and the one or more processors execute the processor executable instructions and provide the one or more devices with The NEF receives the aforementioned configuration for data collection from the server, The NEF encrypts the aforementioned configuration for data collection, The device according to claim 25, wherein the NEF is configured to transmit the encrypted configuration for data collection to the AMF.

29. The one or more devices are equipped with a network exposure function (NEF), and the one or more processors execute the processor executable instructions and provide the one or more devices with The NEF receives an instruction to start data collection, The device according to claim 25, wherein the NEF is configured to transmit the instruction to the AMF to start data collection, and one or more devices according to claim 25.

30. A device for wireless communication in a network entity, wherein the device includes a memory containing processor-executable instructions, and one or more processors that execute the processor-executable instructions and the device, Receiving information about data collection services, The device receives a data collection configuration from the data collection service that indicates one or more types of data to be collected by the device. An apparatus comprising one or more processors configured to cause the data collection service to transmit data corresponding to one or more types of data.

31. The information relating to the data collection service is Routing information for one or more data collection services, including the aforementioned data collection service, Vendor information indicating that the device from the vendor collects data. The apparatus according to claim 30, comprising one or more of the following: an instruction for the purpose of data collection.

32. The one or more processors execute the processor-executable instructions and the device, Receiving signaling containing routing information for discovery services, The apparatus according to claim 30, configured to transmit a request to the discovery service for the information relating to the data collection service, wherein one or more processors execute processor-executable instructions and cause the apparatus to receive the information relating to the data collection service from the discovery service in order to receive the information relating to the data collection service.

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

34. The one or more processors execute the processor-executable instructions and the device, The aforementioned data collection service, Vendor information indicating the vendor of the aforementioned device, The apparatus according to claim 30, configured to transmit one or more of the identifiers of the apparatus or the apparatus.

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

36. One or more devices configured for wireless communication, wherein the one or more devices include a memory containing processor-executable instructions, and one or more processors that execute the processor-executable instructions and provide the one or more devices with The data collection service transmits a data collection configuration to a user device (UE) indicating one or more types of data to be collected by the UE, and the one or more devices are equipped with the data collection service and transmit. One or more devices comprising one or more processors configured to cause the data collection service to receive data corresponding to one or more types of data from the UE.

37. The one or more processors execute the processor-executable instructions and provide the one or more devices The aforementioned UE, Routing information for data collection services, Vendor information indicating that the UE will collect data from the vendor, The apparatus according to claim 36, configured to transmit information relating to the data collection service, including one or more of the following: an instruction for the purpose of data collection.

38. The one or more devices provided a discovery service, the one or more processors executing the processor executable instructions, and the one or more devices, The data collection service transmits signaling including routing information for the discovery service, The one or more devices according to claim 37, wherein the one or more processors are configured to receive a request from the UE for information relating to the data collection service in the discovery service, and the one or more processors are configured to execute a processor executable instruction and cause the one or more devices to transmit the information relating to the data collection service from the discovery service.

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

40. The one or more processors execute the processor-executable instructions and provide the one or more devices One or more devices according to claim 39, configured to cause the data collection service to transmit the information relating to the data collection service to the first device.

41. The one or more processors execute the processor-executable instructions and provide the one or more devices The aforementioned data collection service provides the following information from the UE: Vendor information indicating the vendor of the aforementioned UE, One or more devices according to claim 36, configured to receive one or more of the identifiers of the UE.

42. The one or more processors execute the processor-executable instructions and provide the one or more devices The first of the one or more devices receives from the data collection service a second configuration of data indicating one or more second types of data collected by the first device, The first device generates data corresponding to one or more second types of data. The aforementioned UE, One or more devices according to claim 36, configured to transmit to at least one of the following: or a data collection service.

43. A method for wireless communication by a device, wherein the method is Receiving an encrypted configuration for data collection indicating one or more types of data collected by the aforementioned device, Decrypting the encrypted configuration for data collection, A method comprising transmitting data corresponding to one or more of the aforementioned types of data.

44. The aforementioned one or more types of data are The battery status of the aforementioned device, The calculation state of the aforementioned device, Doppler diffusion, The method according to claim 43, comprising one or more of the following: or Doppler delay.

45. Transmitting the aforementioned data Encrypting the aforementioned data, The method according to claim 43, comprising transmitting the encrypted data.

46. Transmitting the aforementioned data The aforementioned data, Network entity, Trace collection entity, The method according to claim 43, comprising transmitting to at least one of the following: or a device outside the wireless communication network on which the device operates.

47. Further including receiving additional data from the network entity corresponding to the data collected by the network entity, and transmitting the data, The method according to claim 43, comprising transmitting the aforementioned data and the additional data.

48. The method according to claim 43, further comprising transmitting vendor information of the device to a network entity.

49. Receiving the encrypted configuration The method according to claim 43, comprising receiving the encrypted configuration from a network entity.

50. A method for wireless communication using one or more devices, The first of the one or more devices mentioned above receives information identifying one or more user equipment (UEs), A method comprising transmitting to one or more UEs an encrypted configuration for data collection indicating one or more types of data to be collected by each of the one or more UEs, using the first device.

51. The aforementioned one or more types of data are Battery status, Calculation status, Doppler diffusion, The method according to claim 50, comprising one or more of the following: or Doppler delay.

52. The first device receives a second configuration for data indicating one or more second types of data to be collected by the first device, The first device generates data corresponding to one or more second types of data. At least one of the one or more UEs mentioned above, Trace collection entity, The method according to claim 50, further comprising transmitting to at least one of the following: or a device outside the wireless communication network on which the first device operates.

53. Transmitting the aforementioned data The first device encrypts the data corresponding to one or more second types of data, The method according to claim 52, comprising transmitting the encrypted data.

54. The one or more devices comprises the trace collection entity, and the method is The trace collection entity receives the data corresponding to the one or more second types of data, The method of claim 52, further comprising transmitting the data corresponding to the one or more second types of data to the device by the trace collection entity.

55. The first device receives data corresponding to one or more types of data from one or more UEs, The first device processes the data corresponding to one or more types of data. Trace collection entity, The method according to claim 50, further comprising transmitting to at least one of the following: or a device outside the wireless communication network on which the first device operates.

56. The one or more devices comprises the trace collection entity, and the method is The trace collection entity receives the data corresponding to one or more types of data, The method of claim 55, further comprising transmitting the data corresponding to the one or more types of data to the device by the trace collection entity.

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

58. The information identifying one or more UEs comprises one or more identifiers of one or more vendors, and the method is The method according to claim 50, further comprising 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.

59. The method according to claim 50, further comprising receiving the encrypted data collection configuration from the server.

60. Receiving the aforementioned configuration for data collection from the server, The method according to claim 50, further comprising encrypting the above configuration for data collection.

61. The one or more devices include Operation, Management, and Maintenance (OAM), Integrated Data Management (UDM), and Access and Mobility Functions (AMF), and the first device includes a wireless access network entity, and the method is The OAM transmits the encrypted configuration for data collection to the UDM, The UDM transmits the encrypted configuration for data collection to the AMF, The method according to claim 50, further comprising transmitting the encrypted configuration for data acquisition to the first device by the AMF.

62. The method according to claim 61, further comprising receiving an encrypted configuration for data collection from the server via the OAM.

63. The aforementioned OAM receives the aforementioned configuration for data collection from the server, The method according to claim 61, further comprising encrypting the configuration for data collection using the OAM.

64. The AMF receives one or more identifiers of the one or more UEs, The method according to claim 61, further comprising 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 comprises 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 one or more of the aforementioned devices are equipped with a network publishing function (NEF), and the method is The NEF receives the aforementioned configuration for data collection from the server, The aforementioned NEF encrypts the aforementioned configuration for data collection, The method according to claim 61, further comprising transmitting the encrypted configuration for data collection to the OAM via the NEF.

66. The one or more of the aforementioned devices are equipped with a network publishing function (NEF), and the method is The NEF receives an instruction to start data collection, The method according to claim 61, further comprising transmitting the instruction to the OAM to start data collection via the NEF.

67. The one or more of the devices are equipped with access and mobility functions (AMF), the first device is equipped with a wireless access network entity, and the method is The method according to claim 50, further comprising transmitting the encrypted configuration for data acquisition to the first device by the AMF.

68. The method according to claim 67, further comprising the AMF receiving the encrypted data collection configuration from the server.

69. The AMF receives the aforementioned configuration for data collection from the server, The method according to claim 67, further comprising encrypting the configuration for data collection using the AMF.

70. The one or more of the aforementioned devices are equipped with a network publishing function (NEF), and the method is The NEF receives the aforementioned configuration for data collection from the server, The aforementioned NEF encrypts the aforementioned configuration for data collection, The method according to claim 67, further comprising transmitting the encrypted configuration for data collection to the AMF via the NEF.

71. The one or more of the aforementioned devices are equipped with a network publishing function (NEF), and the method is The NEF receives an instruction to start data collection, The method according to claim 67, further comprising transmitting the instruction to the AMF to start data collection via the NEF.

72. A method for wireless communication by a device, wherein the method is Receiving information about data collection services, The device receives a data collection configuration from the data collection service that indicates one or more types of data to be collected by the device. A method comprising transmitting data corresponding to one or more types of data to the data collection service.

73. The information relating to the data collection service is Routing information for one or more data collection services, including the aforementioned data collection service, Vendor information indicating that the device from the vendor collects data. The method according to claim 72, comprising one or more of the following: or instructions for the purpose of data collection.

74. Receiving signaling containing routing information for discovery services, The method of claim 72, further comprising transmitting a request to the discovery service for the information relating to the data collection service, wherein receiving the information relating to the data collection service includes receiving the information relating to the data collection service from the discovery service.

75. The method according to claim 72, wherein receiving the information relating to the data collection service includes receiving the information relating to the data collection service from another device in a system information block (SIB) or dedicated signaling.

76. The aforementioned data collection service, Vendor information indicating the vendor of the aforementioned device, The method according to claim 72, further comprising transmitting one or more of the identifiers of the device.

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

78. A method for wireless communication using one or more devices, The data collection service transmits a data collection configuration to a user device (UE) indicating one or more types of data to be collected by the UE, and the one or more devices are equipped with the data collection service and transmit. A method comprising receiving data corresponding to one or more types of data from the UE through the data collection service.

79. The aforementioned UE, Routing information for data collection services, Vendor information indicating that the UE will collect data from the vendor, The method of claim 78, further comprising transmitting information relating to the data collection service, which includes one or more of the following: an instruction for the purpose of data collection.

80. The one or more devices described above provide a discovery service, and the method described above is The aforementioned data collection service transmits signaling including routing information for the discovery service, The method of claim 79, further comprising receiving a request for the information relating to the data collection service from the UE in the discovery service, wherein transmitting the information relating to the data collection service includes transmitting the information relating to the data collection service from the discovery service.

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

82. The method according to claim 81, further comprising transmitting the information relating to the data collection service from the data collection service to the first device.

83. The aforementioned data collection service provides the following information from the UE: Vendor information indicating the vendor of the aforementioned UE, The method according to claim 78, further comprising receiving one or more of the identifiers of the UE.

84. The first of the one or more devices receives from the data collection service a second configuration of data indicating one or more second types of data collected by the first device, The first device generates data corresponding to one or more second types of data. The aforementioned UE, The method of claim 78, further comprising transmitting to at least one of the following: or a data collection service.

Images