Context aware navigation

Abstract

Aspects presented herein relate to methods and devices for wireless communication, including apparatuses, such as devices, servers, or network entities. The apparatus may obtain an indication of at least one of device information associated with the device or route information associated with one or more route segments for the device. Additionally, the apparatus may perform a ranging procedure with a second device based on at least one of the device information associated with the device or the route information associated with the one or more route segments, where the ranging procedure is associated with an identification of at least one of the device or a location of the device.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of Greek patent application serial number 20220100572, filed on July 19, 2022, entitled “CONTEXT-AWARE NAVIGATION”, which is expressly incorporated herein by reference in its entirety. Technical Field

[0003] The present disclosure relates generally to communication systems, and more particularly, to positioning measurements in wireless communication systems. Background Art

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

[0005] These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate at city, country, region, and even global levels. An example telecommunication standard is 5G New Radio (NR). 5G NR is part of the continuous mobile broadband evolution promulgated by the Third Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with the Internet of Things (IoT)) and other requirements. 5G NR includes services associated with enhanced mobile broadband (eMBB), massive machine type communication (mMTC), and ultra-reliable low latency communication (URLLC). Certain aspects of 5G NR may be based on 4G Long Term Evolution (LTE) standards. It is necessary to further improve 5G NR technology. In addition, these improvements may also be applicable to other multiple access technologies and telecommunication standards that employ these technologies. Summary of the invention

[0006] The following presents a summary of one or more aspects in order to provide a basic understanding of these aspects. This summary is not a comprehensive review of all contemplated aspects. This summary is neither intended to identify the key or important elements of all aspects, nor to describe the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to a more detailed description presented later.

[0007] In one aspect of the present disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus may be an apparatus for wireless communication at a device or user equipment (UE). The apparatus may obtain an indication of at least one of device information associated with the device or route information associated with one or more route segments for the device. The apparatus may also perform a ranging process with a second device based on at least one of the device information associated with the device or the route information associated with the one or more route segments, wherein the ranging process is associated with an identification of at least one of the device or the location of the device. In addition, the apparatus may perform one or more sensor measurements along the one or more route segments; and send an indication of the one or more sensor measurements to at least one of a server, the second device, or a network entity. The apparatus may also wake up when reaching a drop point among a plurality of points of the one or more route segments; and send a report of a drop event after reaching the drop point, wherein the drop event corresponds to dropping goods on the device at the drop point. The apparatus may also receive an indication of updated device information associated with the device or updated route information associated with the one or more route segments from a server. In addition, the device may obtain density information associated with a set of network entities along the one or more route segments; and determine whether to switch from the first positioning technology to the second positioning technology along the one or more route segments based on the density information associated with the set of network entities. The device may also send an indication of the determination of whether to switch from the first positioning technology to the second positioning technology along the one or more route segments; and receive an indication of the one or more route segments associated with the switch from the first positioning technology to the second positioning technology. The device may also receive an indication of a positioning state of the device from a server, wherein the positioning state is based on the density information associated with the set of network entities along the one or more route segments; and receive an indication of at least one of a sleep schedule for the device or a communication period for the device, wherein the sleep schedule or the communication period is based on the density information or the positioning state.

[0008] In one aspect of the present disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus may be an apparatus for performing device configuration at a server. The apparatus may send a request to a second device for monitoring one or more devices along one or more route segments, wherein the request for monitoring includes at least one of device information associated with the one or more devices or route information associated with the one or more route segments. The apparatus may also receive an indication of a monitoring status of the one or more devices along the one or more route segments from the second device, wherein the indication of the monitoring status indicates that the one or more devices are being monitored by the second device. In addition, the apparatus may receive an indication of one or more sensor measurements along the one or more route segments from at least one of the one or more devices; or receive a report of a delivery event from at least one of the one or more devices, wherein the delivery event corresponds to the delivery of goods from the at least one device at a delivery point among a plurality of points of the one or more route segments. The apparatus may also update the device information based on the one or more devices, or update the route information based on the one or more route segments; and send an indication of the updated device information or the updated route information. The apparatus may also receive from the second device an indication of a lack of coverage for monitoring the one or more devices; and send to at least one other second device a second request for handing over monitoring the one or more devices. In addition, the apparatus may obtain density information associated with a set of network entities along the one or more route segments; and determine whether to switch from the first positioning technology to the second positioning technology along the one or more route segments based on the density information associated with the set of network entities. The apparatus may also send an indication of the determination of whether to switch from the first positioning technology to the second positioning technology along the one or more route segments, wherein the determination of whether to switch from the first positioning technology to the second positioning technology is based on the capabilities of the set of network entities or the reliability of the set of network entities; or identify the one or more route segments for the switch from the first positioning technology to the second positioning technology based on the density information; and send an indication of the one or more route segments associated with the switch from the first positioning technology to the second positioning technology.The device can also obtain density information associated with a set of network entities along the one or more route segments; determine the positioning state of the one or more devices based on the density information associated with the set of network entities, wherein the positioning state of the one or more devices corresponds to rural positioning, suburban positioning, or urban positioning; send an indication of the positioning state of the one or more devices to each of the one or more devices; select at least one of a sleep schedule for the one or more devices or a communication time period for the one or more devices based on the density information or the positioning state of the one or more devices; and send an indication of at least one of the sleep schedule for the one or more devices or the communication time period for the one or more devices.

[0009] In one aspect of the present disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus may be an apparatus for wireless communication at a device. The apparatus may receive a request from a server for monitoring one or more devices along one or more route segments, wherein the request for monitoring includes at least one of device information associated with the one or more devices or route information associated with the one or more route segments. The apparatus may also perform a ranging process with the one or more devices based on at least one of the device information or the route information, wherein the ranging process is associated with an identification of at least one of the one or more devices or the location of the one or more devices. In addition, the apparatus may identify the one or more devices based on at least one of the device information, the route information, or the ranging process, wherein the ranging process is based on at least one of the distance of the communication between the one or more devices and the device, the timing of the communication between the one or more devices and the device, or the signal strength of the communication between the one or more devices and the device; and monitor the one or more devices along the one or more route segments based on identifying the one or more devices, wherein the indication of the monitoring status indicates that the one or more devices are being monitored by the device. The device may also send an indication of a monitoring status of the one or more devices along the one or more route segments, wherein the monitoring status is based on the ranging process with the one or more devices. The device may also receive an indication of one or more sensor measurements along the one or more route segments from at least one of the one or more devices. In addition, the device may receive a report of a drop event from at least one of the one or more devices, wherein the drop event corresponds to the drop of goods from the at least one device at a drop point among a plurality of points in the one or more route segments. The device may also receive an indication of updated device information associated with the one or more devices or updated route information associated with the one or more route segments from the server. The device may also detect a lack of coverage for monitoring the one or more devices; and send an indication of the lack of coverage for monitoring the one or more devices to the server.

[0010] To achieve the aforementioned and related purposes, one or more aspects include the features described in full below and particularly pointed out in the claims. The following description and the accompanying drawings set forth in detail some exemplary features of one or more aspects. However, these features are only indicative of only some of the various ways in which the principles of the various aspects can be employed. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] Figure 1 is a diagram illustrating an example of a wireless communication system and an access network.

[0012] Figure 2Ais a diagram illustrating an example of a first frame according to various aspects of the present disclosure.

[0013] Figure 2B is a diagram illustrating an example of downlink (DL) channels within a subframe according to various aspects of the present disclosure.

[0014] Figure 2C is a diagram illustrating an example of a second frame according to various aspects of the present disclosure.

[0015] Figure 2D is a diagram illustrating an example of uplink (UL) channels within a subframe according to various aspects of the present disclosure.

[0016] Figure 3 is a diagram illustrating an example of a base station and a user equipment (UE) in an access network.

[0017] Figure 4 is a diagram illustrating an example of UE positioning based on reference signal measurement.

[0018] Figure 5 is a diagram illustrating an example of a wireless communication system.

[0019] Figure 6 is a diagram illustrating an example positioning procedure.

[0020] Figure 7 is a diagram illustrating example routes for devices in a wireless communication system.

[0021] Figure 8 is a diagram illustrating example routes for devices in a wireless communication system.

[0022] Fig. 9 is a diagram illustrating example routes for devices in a wireless communication system.

[0023] Fig.10 is a diagram illustrating example routes for devices in a wireless communication system.

[0024] Fig.11 is a communication flow diagram illustrating example communications between a device and a server.

[0025] Fig.12 is a communication flow diagram illustrating example communications between a server and a device.

[0026] Fig.13 is a flow chart of a method of wireless communication.

[0027] Fig.14 is a flow chart of a method of wireless communication.

[0028] Fig.15is a flow chart of a method of wireless communication.

[0029] Fig.16 is a flow chart of a method of wireless communication.

[0030] Fig.17 is a flow chart of a method of wireless communication.

[0031] Fig.18 is a flow chart of a method of wireless communication.

[0032] Fig.19 are diagrams illustrating examples of hardware implementations for example devices and / or network entities.

[0033] Fig. 20 is a diagram illustrating an example of a hardware implementation for an example network entity.

[0034] Fig.21 is a diagram illustrating an example of a hardware implementation for an example network entity. DETAILED DESCRIPTION

[0035] Aspects of the communication or device configuration may utilize several different mapping or navigation processes for a device (e.g., an Internet of Things (IoT) device). For example, a mapping or navigation process may navigate a device along a route or route segment, and determine or update the location of the device along the route or route segment. Therefore, a mapping or navigation process is similar to a position positioning process because the device location can be determined along a route or route segment. However, some types of mapping or navigation processes may not utilize some types of positioning technologies. For example, the operating system of the mapping or navigation process may specify which positioning technologies can be used for a given positioning request (e.g., a positioning request on the device or smartphone side). In addition, a server or network (NW) may specify the periodicity of a specific positioning technology, regardless of the scenario within the mapping or navigation process. That is, a server or network (e.g., a low-level server / network) may select a specific positioning technology for several reasons, such as to reduce power consumption. Additionally, there may be certain geographic areas where positioning technologies produce poor results and cause battery drain (e.g., battery drain at the device). Therefore, this may lead to a false sense of reliability for determining the location of a device using certain types of positioning technologies. In addition, the classification of the mobile mode of the device can be changed based on the context of the route or area that the device is really close to. However, these factors may not take into account how the environment or environmental factors along the route or route segment may affect the device or package being transported along the route or route segment. In some types of environments, some positioning technologies may not perform well compared with other positioning technologies. For example, in some approaches (e.g., commercial approaches), devices (e.g., tracking devices) that do not know the route or route segment can continue to try to perform specific positioning in certain situations (e.g., dense urban environments) where certain positioning technologies (e.g., global navigation satellite systems (GNSS)) may not perform well. In addition, in these situations (e.g., dense urban environments), some positioning technologies may request the device to stay awake for a longer period of time than normal, which may consume battery power at the device. In some scenarios, after calculating the location, the device may spend a lot of time trying to reconnect to the network in the location (e.g., rural environment) with inconsistent network quality or unavailable. Additionally, in some scenarios, it may be necessary to prompt (e.g., prompted by a server) the device to change the quality of service (QoS) or positioning technology, which may also cause an increase in battery consumption at the device. Aspects of the present disclosure may indicate to a device that certain positioning technologies are to be utilized in order to determine the location of the device. For example, a device herein may receive an indication of which positioning technologies are to be utilized in certain scenarios (e.g., certain environments or sections of a route). In some instances, prior to a route or a particular route segment, a device herein may be preconfigured with positioning technologies to be utilized in certain environments (e.g., a dense urban environment or a rural environment) or certain route sections.By doing so, the devices herein can utilize a reduced amount of battery consumption because they may not need to be prompted to change QoS or positioning techniques in certain scenarios. That is, the various aspects presented herein can reduce the power consumption of the devices by indicating a suitable or desired method for determining the location of each device. For example, the devices herein can receive (e.g., from a server) an indication of a suitable or desired methodology for determining the location of the device when the device is located in a particular environment or segment of a route.

[0036] The detailed description set forth below in conjunction with the accompanying drawings is a description of various configurations and does not represent the only configurations in which the concepts described herein can be practiced. In order to provide a thorough understanding of the various concepts, the specific embodiments include specific details. However, these concepts can be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form to avoid blurring these concepts.

[0037] Several aspects of the telecommunication system are also presented with reference to various apparatuses and methods. These apparatuses and methods are described in the following detailed description and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as "elements"). These elements can be implemented using electronic hardware, computer software, or any combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0038] As an example, an element, or any part of an element, or any combination of elements can be implemented as a "processing system", which includes one or more processors. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, systems on chip (SoCs), baseband processors, field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gate logic pieces, discrete hardware circuits, and other suitable hardware configured to perform various functions described throughout the present disclosure. One or more processors in a processing system can execute software. Whether referred to as software, firmware, middleware, microcode, hardware description language, or other terms, software should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, or any combination thereof.

[0039] Thus, in one or more example aspects, specific implementations and / or use cases, the described functionality may be implemented in hardware, software, or any combination thereof. If implemented in software, the functionality may be stored or encoded as one or more instructions or codes on a computer-readable medium. Computer-readable media include computer storage media. Storage media may be any available media that can be accessed by a computer. By way of example, such computer-readable media may include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of these types of computer-readable media, or any other medium that can be used to store computer-executable code in the form of instructions or data structures that can be accessed by a computer.

[0040] Although various aspects, specific implementations and / or use cases are described in this application by the illustration of some examples, additional or different aspects, specific implementations and use cases may be generated in many different arrangements and scenarios. The various aspects, specific implementations and / or use cases described herein can be implemented across many different platform types, devices, systems, shapes, sizes and packaging arrangements. For example, various aspects, specific implementations and / or use cases can be generated via integrated chip specific implementations and other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail / purchase equipment, medical equipment, artificial intelligence (AI) enabled devices, etc.). Although some examples may or may not be specifically for use cases or applications, the described examples may have a wide range of applicability. Various aspects, specific implementations and / or use cases can be in the range from chip-level or modular components to non-modular, non-chip-level specific implementations, and further to the range of aggregated, distributed or original equipment manufacturer (OEM) equipment or systems in conjunction with one or more technologies herein. In some practical environments, the equipment combined with the various aspects and features described may also include additional components and features for implementing and practicing the claimed and described aspects. For example, the transmission and reception of wireless signals necessarily include multiple components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.) The techniques described herein can be practiced in a wide variety of devices of various sizes, shapes, and configurations, chip-level components, systems, distributed arrangements, aggregated or disaggregated components, end-user devices, etc.

[0041] The deployment of a communication system (such as a 5G NR system) can be arranged with various components or constituent parts in a variety of ways. In a 5G NR system or network, a network node, a network entity, a mobility element of a network, a radio access network (RAN) node, a core network node, a network element or a network equipment (such as a base station (BS), or one or more units (or one or more components) that perform base station functionality can be implemented in an aggregated or decomposed architecture. For example, a BS (such as a Node B (NB), an evolved NB (eNB), an NR BS, a 5G NB, an access point (AP), a transmit receive point (TRP) or a cell, etc.) can be implemented as an aggregated base station (also referred to as an independent BS or a monolithic BS) or a decomposed base station.

[0042] A converged base station may be configured to utilize a radio protocol stack physically or logically integrated within a single RAN node. A decomposed base station may be configured to utilize a protocol stack physically or logically distributed between two or more units, such as one or more central or centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs). In some aspects, a CU may be implemented within a RAN node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed in one or more other RAN nodes. A DU may be implemented to communicate with one or more RUs. Each of a CU, a DU, and a RU may be implemented as a virtual unit, i.e., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0043] Base station operation or network design may take into account the aggregated nature of base station functionality. For example, a disaggregated base station may be used in an integrated access backhaul (IAB) network, an open radio access network (O-RAN (network configuration such as that initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Decomposition may include distributing functionality across two or more units at various physical locations, as well as virtually distributing functionality of at least one unit, which may enable flexibility in network design. Individual units of a disaggregated base station or disaggregated RAN architecture may be configured for wired or wireless communication with at least one other unit.

[0044] Figure 11 is a diagram 100 illustrating an example of a wireless communication system and an access network. The illustrated wireless communication system includes a disaggregated base station architecture. The disaggregated base station architecture may include one or more CUs 110 that may communicate directly with a core network 120 via a backhaul link, or indirectly with the core network 120 through one or more disaggregated base station units, such as a near real-time (near RT) RAN intelligent controller (RIC) 125 via an E2 link, or a non-real-time (non-RT) RIC 115 associated with a service management and orchestration (SMO) framework 105, or both. The CU 110 may communicate with one or more DUs 130 via corresponding midhaul links, such as an F1 interface. The DU 130 may communicate with one or more RUs 140 via corresponding fronthaul links. The RU 140 may communicate with corresponding UEs 104 via one or more radio frequency (RF) access links. In some implementations, a UE 104 may be served simultaneously by multiple RUs 140.

[0045] Each of the units (i.e., CU 110, DU 130, RU 140, and near-RT RIC 125, non-RT RIC 115, and SMO framework 105) may include or be coupled to one or more interfaces configured to receive or send signals, data, or information (collectively, signals) via a wired or wireless transmission medium. Each of the units or an associated processor or controller that provides instructions to the communication interfaces of these units may be configured to communicate with one or more of the other units via a transmission medium. For example, these units may include a wired interface configured to receive signals from one or more of the other units or send signals to one or more of the other units on a wired transmission medium. Additionally, these units may include a wireless interface that may include a receiver, transmitter, or transceiver (such as an RF transceiver) configured to receive and / or send signals to one or more of the other units on a wireless transmission medium.

[0046] In some aspects, CU 110 may host one or more higher layer control functions. Such control functions may include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), etc. Each control function may be implemented using an interface configured to communicate signals with other control functions hosted by CU 110. CU110 may be configured to handle user plane functionality (i.e., central unit-user plane (CU-UP)), control plane functionality (i.e., central unit-control plane (CU-CP)), or a combination thereof. In some specific implementations, CU 110 may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). As needed, CU 110 may be implemented to communicate with DU 130 for network control and signaling.

[0047] DU 130 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 140. In some aspects, DU 130 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) coding and decoding, scrambling, modulation, demodulation, etc.) at least in part according to a functional split (such as a functional split defined by 3GPP). In some aspects, DU 130 may further host one or more low PHY layers. Each layer (or module) may be implemented using an interface that is configured to communicate signals with other layers (and modules) hosted by DU 130 or with control functions hosted by CU 110.

[0048] The lower layer functions may be implemented by one or more RUs 140. In some deployments, the RU 140 controlled by the DU 130 may correspond to a logical node that hosts RF processing functions or low PHY layer functions (such as performing fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.), or both, based at least in part on functional splitting such as lower layer functional splitting. In such an architecture, the RU 140 may be implemented to handle over-the-air (OTA) communications with one or more UEs 104. In some specific implementations, real-time and non-real-time aspects of control plane and user plane communications with the RU 140 may be controlled by the corresponding DU 130. In some scenarios, this configuration may enable the DU 130 and CU 110 to be implemented in a cloud-based RAN architecture (such as a vRAN architecture).

[0049] The SMO framework 105 may be configured to support RAN deployment and configuration of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 105 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO framework 105 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) 190) to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements may include, but are not limited to, CU 110, DU 130, RU 140, and near-RT RIC 125. In some specific implementations, the SMO framework 105 may communicate with hardware aspects of the 4G RAN (such as an open eNB (O-eNB) 111) via the O1 interface. Additionally, in some specific implementations, the SMO framework 105 may communicate directly with one or more RUs 140 via the O1 interface. The SMO framework 105 may also include a non-RT RIC 115 configured to support the functionality of the SMO framework 105 .

[0050] The non-RT RIC 115 may be configured to include logic functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence (AI) / machine learning (ML) (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 125. The non-RT RIC 115 may be coupled to or in communication with the near-RT RIC 125 (such as via an A1 interface). The near-RT RIC 125 may be configured to include logic functions that enable near-real-time control and optimization of RAN elements and resources via data collection and actions through an interface (such as via an E2 interface) that connects one or more CUs 110, one or more DUs 130, or both, and O-eNBs with the near-RT RIC 125.

[0051] In some implementations, in order to generate an AI / ML model to be deployed in the near-RT RIC 125, the non-RT RIC 115 may receive parameters or external enrichment information from an external server. Such information may be utilized by the near-RT RIC 125 and may be received from a non-network data source or from a network function at the SMO framework 105 or the non-RT RIC 115. In some examples, the non-RT RIC 115 or the near-RT RIC 125 may be configured to adjust RAN behavior or performance. For example, the non-RT RIC 115 may monitor long-term trends and patterns of performance and employ AI / ML models to perform corrective actions through the SMO framework 105 (such as via reconfiguration of O1) or via the creation of RAN management policies (such as A1 policies).

[0052] At least one of the CU 110, the DU 130, and the RU 140 may be referred to as a base station 102. Therefore, the base station 102 may include one or more of the CU 110, the DU 130, and the RU 140 (each component is indicated by a dotted line to indicate that each component may or may not be included in the base station 102). The base station 102 provides an access point to the core network 120 for the UE 104. The base station 102 may include a macro cell (a high-power cellular base station) and / or a small cell (a low-power cellular base station). Small cells include femto cells, pico cells, and micro cells. A network including both small cells and macro cells may be referred to as a heterogeneous network. A heterogeneous network may also include a home evolved Node B (eNB) (HeNB), which may provide services to a restricted group referred to as a closed subscriber group (CSG). The communication link between RU140 and UE 104 may include uplink (UL) (also known as reverse link) transmission from UE 104 to RU 140 and / or downlink (DL) (also known as forward link) transmission from RU 140 to UE 104. The communication link may use multiple-input multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming and / or transmit diversity. The communication link may pass through one or more carriers. For each carrier allocated in a carrier aggregation of up to YxMHz (x component carriers) for transmission in each direction, the base station 102 / UE 104 may use a spectrum of up to YMHz (e.g., 5MHz, 10MHz, 15MHz, 20MHz, 100MHz, 400MHz, etc.) bandwidth. The carriers may be adjacent to each other or may not be adjacent to each other. The allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated to DL compared to UL). The component carrier may include a primary component carrier and one or more secondary component carriers. The primary component carrier may be referred to as a primary cell (PCell) and the secondary component carrier may be referred to as a secondary cell (SCell).

[0053] Some UEs 104 may communicate with each other using a device-to-device (D2D) communication link 158. The D2D communication link 158 may use DL / UL wireless wide area network (WWAN) spectrum. The D2D communication link 158 may use one or more side link channels, such as a physical side link broadcast channel (PSBCH), a physical side link discovery channel (PSDCH), a physical side link shared channel (PSSCH), and a physical side link control channel (PSCCH). The D2D communication may be through a variety of wireless D2D communication systems, such as, for example, Bluetooth, Wi-Fi based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, LTE, or NR.

[0054] The wireless communication system may also include a Wi-Fi AP 150 that communicates with a UE 104 (also referred to as a Wi-Fi station (STA)) via a communication link 154, for example, in a 5 GHz unlicensed spectrum, etc. When communicating in an unlicensed spectrum, the UE 104 / AP 150 may perform a clear channel assessment (CCA) to determine whether a channel is available prior to communication.

[0055] The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc. based on frequency / wavelength. In 5G NR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz - 7.125 GHz) and FR2 (24.25 GHz - 52.6 GHz). Although a portion of FR1 is greater than 6 GHz, FR1 is often referred to (interchangeably) as the "sub-6 GHz" band in various documents and articles. A similar naming issue sometimes occurs with respect to FR2, which is often (interchangeably) referred to as the "millimeter wave" band in documents and articles, despite being different from the extremely high frequency (EHF) band (30 GHz - 300 GHz) identified as the "millimeter wave" band by the International Telecommunication Union (ITU).

[0056] Frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR research has identified the operating bands for these mid-band frequencies as frequency range designation FR3 (7.125GHz-24.25GHz). The bands falling within FR3 can inherit FR1 characteristics and / or FR2 characteristics, and therefore the features of FR1 and / or FR2 can be effectively extended to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operations to more than 52.6GHz. For example, three higher operating bands have been identified as frequency range designations FR2-2 (52.6GHz-71GHz), FR4 (71GHz-114.25GHz) and FR5 (114.25GHz-300GHz). Each of these higher frequency bands falls within the EHF band.

[0057] In view of the above, unless otherwise specified, if the term "sub-6 GHz" or the like is used herein, it may broadly refer to frequencies that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies. In addition, unless otherwise specified, if the term "millimeter wave" or the like is used herein, it may broadly refer to frequencies that may include mid-band frequencies, may be within FR2, FR4, FR2-2, and / or FR5, or may be within the EHF band.

[0058] The base station 102 and the UE 104 may each include multiple antennas (such as antenna elements, antenna panels, and / or antenna arrays) to facilitate beamforming. The base station 102 may send a beamformed signal 182 to the UE 104 in one or more transmit directions. The UE 104 may receive the beamformed signal from the base station 102 in one or more receive directions. The UE 104 may also send a beamformed signal 184 to the base station 102 in one or more transmit directions. The base station 102 may receive the beamformed signal from the UE 104 in one or more receive directions. The base station 102 / UE 104 may perform beam training to determine the best receive direction and transmit direction for each of the base station 102 / UE 104. The transmit direction and receive direction of the base station 102 may be the same or different. The transmit direction and receive direction of the UE 104 may be the same or different.

[0059] The base station 102 may include and / or be referred to as a gNB, a Node B, an eNB, an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), a transmit receive point (TRP), a network node, a network entity, a network equipment, or some other suitable term. The base station 102 may be implemented as an integrated access and backhaul (IAB) node, a relay node, a sidelink node, a clustered (monolithic) base station with a baseband unit (BBU) (including a CU and a DU) and a RU, or as a decomposed base station including one or more of a CU, a DU, and / or a RU. A set of base stations that may include decomposed base stations and / or clustered base stations may be referred to as a next generation (NG) RAN (NG-RAN).

[0060] The core network 120 may include an access and mobility management function (AMF) 161, a session management function (SMF) 162, a user plane function (UPF) 163, a unified data management (UDM) 164, one or more location servers 168, and other functional entities. AMF 161 is a control node that handles signaling between UE 104 and the core network 120. AMF 161 supports registration management, connection management, mobility management, and other functions. SMF 162 supports session management and other functions. UPF 163 supports packet routing, packet forwarding, and other functions. UDM 164 supports the generation of authentication and key agreement (AKA) credentials, user identity handling, access authorization, and subscription management. One or more location servers 168 are illustrated as including a gateway mobile location center (GMLC) 165 and a location management function (LMF) 166. However, in general, the one or more location servers 168 may include one or more location / positioning servers, which may include one or more of the GMLC 165, the LMF 166, the position determination entity (PDE), the serving mobile location center (SMLC), the mobile positioning center (MPC), etc. The GMLC 165 and the LMF 166 support UE location services. The GMLC 165 provides an interface for clients / applications (e.g., emergency services) to access UE positioning information. The LMF 166 receives measurements and assistance information from the NG-RAN and the UE 104 via the AMF 161 to calculate the location of the UE 104. The NG-RAN may determine the location of the UE 104 using one or more positioning methods. Positioning the UE 104 may involve signal measurements, position estimation, and optional speed calculations based on these measurements. Signal measurements may be performed by the UE 104 and / or the serving base station 102. The measured signal can be based on a satellite positioning system (SPS) 170 (e.g., one or more of a global navigation satellite system (GNSS), a global positioning system (GPS), a non-terrestrial network (NTN), or other satellite positioning / positioning systems), LTE signals, wireless local area network (WLAN) signals, Bluetooth signals, a terrestrial beacon system (TBS), sensor-based information (e.g., an atmospheric pressure sensor, a motion sensor), an NR enhanced cell ID (NR E-CID) method, an NR signal (e.g., multi-round trip time (multi-RTT), DL angle of departure (DL-AoD), DL time difference of arrival (DL-TDOA), UL time difference of arrival (UL-TDOA), and UL angle of arrival (UL-AoA) positioning) and / or one or more of other systems / signals / sensors.

[0061] Examples of UE 104 include cellular phones, smart phones, session initiation protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radios, global positioning systems, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablet computers, smart devices, wearable devices, vehicles, electric meters, gas pumps, large or small kitchen appliances, healthcare equipment, implants, sensors / actuators, displays, or any other similarly functional devices. Some of the UEs in UE 104 may be referred to as IoT devices (e.g., parking meters, gas pumps, toasters, vehicles, heart monitors, etc.). UE 104 may also be referred to as stations, mobile stations, subscriber stations, mobile units, subscriber units, wireless units, remote units, mobile devices, wireless devices, wireless communication devices, remote devices, mobile subscriber stations, access terminals, mobile terminals, wireless terminals, remote terminals, mobile phones, user agents, mobile clients, clients, or some other suitable terminology. In some scenarios, the term UE may also be applied to one or more supporting devices such as in a device constellation arrangement. One or more of these devices may access a network together and / or individually. In some scenarios, the term UE may also be applied to one or more supporting devices such as in a device constellation arrangement. One or more of these devices may access the network jointly and / or individually. The network node may be implemented as a base station (ie, an aggregated base station), a decomposed base station, an integrated access and backhaul (IAB) node, a relay node, a side link node, etc. The network entity may be implemented as a base station (ie, an aggregated base station), or alternatively as a central unit (CU), a distributed unit (DU), a radio unit (RU), a near real-time (near RT) RAN intelligent controller (RIC), or a non-real-time (non-RT) RIC in a decomposed base station architecture.

[0062] Reference again Figure 1In certain aspects, the UE 104 may include a monitoring component 198 that may be configured to obtain an indication of at least one of device information associated with the device or route information associated with one or more route segments for the device. The monitoring component 198 may also be configured to perform a ranging process with a second device based on at least one of the device information associated with the device or the route information associated with the one or more route segments, wherein the ranging process is associated with an identification of at least one of the device or the location of the device. The monitoring component 198 may also be configured to perform one or more sensor measurements along the one or more route segments; and send an indication of the one or more sensor measurements to at least one of a server, a second device, or a network entity. The monitoring component 198 may also be configured to wake up upon reaching a drop point among a plurality of points in the one or more route segments; and send a report of a drop event after reaching the drop point, wherein the drop event corresponds to dropping a cargo on the device at the drop point. The monitoring component 198 may also be configured to receive an indication of updated device information associated with the device or updated route information associated with the one or more route segments from the server. The monitoring component 198 may also be configured to obtain density information associated with a set of network entities along one or more route segments; and determine whether to switch from a first positioning technology to a second positioning technology along the one or more route segments based on the density information associated with the set of network entities. The monitoring component 198 may also be configured to send an indication of a determination of whether to switch from a first positioning technology to a second positioning technology along the one or more route segments; and receive an indication of one or more route segments associated with a switch from the first positioning technology to the second positioning technology. The monitoring component 198 may also be configured to receive an indication of a positioning state of the device from a server, wherein the positioning state is based on the density information associated with the set of network entities along the one or more route segments; and receive an indication of at least one of a sleep schedule for the device or a communication period for the device, wherein the sleep schedule or the communication period is based on the density information or the positioning state.

[0063] Reference again Figure 1In some aspects, the base station 102 may include a monitoring component 199 that may be configured to send a request to a second device for monitoring one or more devices along one or more route segments, wherein the request for monitoring includes at least one of device information associated with the one or more devices or route information associated with the one or more route segments. The monitoring component 199 may also be configured to receive an indication of a monitoring status of one or more devices along the one or more route segments from the second device, wherein the indication of the monitoring status indicates that the one or more devices are being monitored by the second device. The monitoring component 199 may also be configured to receive an indication of one or more sensor measurements along the one or more route segments from at least one of the one or more devices; or to receive a report of a drop event from at least one of the one or more devices, wherein the drop event corresponds to the drop of goods from at least one device at a drop point among a plurality of points of the one or more route segments. The monitoring component 199 may also be configured to update device information based on the one or more devices, or to update route information based on the one or more route segments; and to send an indication of the updated device information or the updated route information. The monitoring component 199 may also be configured to receive an indication of a lack of coverage for monitoring one or more devices from a second device; and send a second request to at least one other second device for handing over monitoring of the one or more devices. The monitoring component 199 may also be configured to obtain density information associated with a set of network entities along one or more route segments; and determine whether to switch from a first positioning technology to a second positioning technology along one or more route segments based on the density information associated with the set of network entities. The monitoring component 199 may also be configured to send an indication of a determination of whether to switch from a first positioning technology to a second positioning technology along one or more route segments, wherein the determination of whether to switch from a first positioning technology to a second positioning technology is based on capabilities of the set of network entities or reliability of the set of network entities; or identify one or more route segments for switching from a first positioning technology to a second positioning technology based on density information; and send an indication of one or more route segments associated with switching from a first positioning technology to a second positioning technology. The monitoring component 199 can also be configured to obtain density information associated with a set of network entities along one or more route segments; determine a positioning state of one or more devices based on the density information associated with the set of network entities, wherein the positioning state of the one or more devices corresponds to rural positioning, suburban positioning, or urban positioning; send an indication of the positioning state of the one or more devices to each of the one or more devices; select at least one of a sleep schedule for the one or more devices or a communication time period for the one or more devices based on the density information or the positioning state of the one or more devices; and send an indication of at least one of a sleep schedule for the one or more devices or a communication time period for the one or more devices.

[0064] Reference again Figure 1 In certain aspects, the LMF 166 may include a monitoring component 199 that may be configured to receive a request from a server for monitoring one or more devices along one or more route segments, wherein the request for monitoring includes at least one of device information associated with the one or more devices or route information associated with the one or more route segments. The monitoring component 199 may also be configured to perform a ranging process with the one or more devices based on at least one of the device information or the route information, wherein the ranging process is associated with an identification of at least one of the one or more devices or the location of the one or more devices. The monitoring component 199 may also be configured to identify the one or more devices based on at least one of the device information, the route information, or the ranging process, wherein the ranging process is based on at least one of a distance of communication between the one or more devices, a timing of communication between the one or more devices, or a signal strength of communication between the one or more devices; and monitor the one or more devices along the one or more route segments based on identifying the one or more devices, wherein an indication of a monitoring status indicates that the one or more devices are being monitored by the device. The monitoring component 199 may also be configured to send an indication of a monitoring status of the one or more devices along the one or more route segments, wherein the monitoring status is based on the ranging process with the one or more devices. The monitoring component 199 may also be configured to receive an indication of one or more sensor measurements along one or more route segments from at least one of the one or more devices. The monitoring component 199 may also be configured to receive a report of a drop event from at least one of the one or more devices, wherein the drop event corresponds to the drop of goods from at least one device at a drop point among a plurality of points in the one or more route segments. The monitoring component 199 may also be configured to receive an indication of updated device information associated with one or more devices or updated route information associated with one or more route segments from a server. The monitoring component 199 may also be configured to detect a lack of coverage for monitoring one or more devices; and send an indication of a lack of coverage for monitoring one or more devices to a server. Although the following description may focus on 5G NR, the concepts described herein may be applicable to other similar fields, such as LTE, LTE-A, CDMA, GSM, and other wireless technologies.

[0065] Figure 2A FIG200 is a diagram illustrating an example of a first subframe within a 5G NR frame structure. Figure 2B FIG230 is a diagram illustrating an example of DL channels within a 5G NR subframe. Figure 2C FIG250 is a diagram illustrating an example of a second subframe within a 5G NR frame structure. Figure 2DFIG280 is a diagram illustrating an example of UL channels within a 5G NR subframe. The 5G NR frame structure may be frequency division duplex (FDD), where for a particular set of subcarriers (carrier system bandwidth), subframes within that subcarrier set are dedicated to either DL or UL, or may be time division duplex (TDD), where for a particular set of subcarriers (carrier system bandwidth), subframes within that subcarrier set are dedicated to both DL and UL. Figure 2A , Figure 2C In the example provided, the 5G NR frame structure is assumed to be TDD, where subframe 4 is configured with slot format 28 (most of which are DL), where D is DL, U is UL, and F is flexible between DL / UL, and subframe 3 is configured with slot format 1 (all of which are UL). Although subframes 3 and 4 are shown as having slot formats 1 and 28, respectively, any particular subframe may be configured with any of the various available slot formats 0-61. Slot formats 0 and 1 are both DL and both UL, respectively. Other slot formats 2-61 include a mix of DL, UL, and flexible symbols. The slot format is configured for the UE via a received slot format indicator (SFI) (dynamically configured via DL control information (DCI) or semi-statically / statically configured via radio resource control (RRC) signaling). Note that the following description also applies to the 5G NR frame structure as TDD.

[0066] FIG. 2A to FIG. 2D The frame structure is illustrated, and various aspects of the present disclosure may be applicable to other wireless communication technologies that may have different frame structures and / or different channels. A frame (10ms) may be divided into 10 subframes (1ms) of the same size. Each subframe may include one or more time slots. A subframe may also include a microslot, which may include 7, 4, or 2 symbols. Each time slot may include 14 or 12 symbols, depending on whether the cyclic prefix (CP) is conventional or extended. For conventional CPs, each time slot may include 14 symbols, and for extended CPs, each time slot may include 12 symbols. The symbols on the DL may be CP orthogonal frequency division multiplexing (OFDM) (CP-OFDM) symbols. The symbols on the UL may be CP-OFDM symbols (for high throughput scenarios) or discrete Fourier transform (DFT) spread OFDM (DFT-s-OFDM) symbols (also known as single carrier frequency division multiple access (SC-FDMA) symbols) (for power-limited scenarios; limited to single stream transmission). The number of slots within a subframe is based on the CP and the parameter set. The parameter set defines the subcarrier spacing (SCS) and effectively defines the symbol length / duration, which is equal to 1 / SCS.

[0067]

[0068] For normal CP (14 symbols / slot), different parameter sets μ 0 to 4 allow 1, 2, 4, 8, and 16 slots per subframe, respectively. For extended CP, parameter set 2 allows 4 slots per subframe. Accordingly, for normal CP and parameter set μ, there are 14 symbols / slot and 2 μ timeslots / subframe. The subcarrier spacing can be equal to 2 μ *15kHz, where μ is parameter set 0 to 4. Therefore, the subcarrier spacing for parameter set μ=0 is 15kHz, and the subcarrier spacing for parameter set μ=4 is 240kHz. The symbol length / duration is inversely related to the subcarrier spacing. FIG. 2A to FIG. 2D An example of a conventional CP is provided, where there are 14 symbols per slot and the parameter set μ=2, where there are 4 slots per subframe. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 μs. Within a frame set, there may be one or more different bandwidth parts (BWPs) that are frequency-division multiplexed (see Figure 2B ). Each BWP can have a specific parameter set and CP (normal or extended).

[0069] A resource grid may be used to represent a frame structure. Each slot includes a resource block (RB) (also referred to as a physical RB (PRB)) extending over 12 consecutive subcarriers. The resource grid is divided into a plurality of resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0070] like Figure 2A As illustrated, some of the REs carry reference (pilot) signals (RS) for the UE. The RS may include a demodulation RS (DM-RS) (indicated as R for a particular configuration, but other DM-RS configurations are possible) and a channel state information reference signal (CSI-RS) for channel estimation at the UE. The RS may also include a beam measurement RS (BRS), a beam refinement RS (BRRS), and a phase tracking RS (PT-RS).

[0071] Figure 2BExamples of various DL channels within a subframe of a frame are illustrated. A physical downlink control channel (PDCCH) carries DCI within one or more control channel elements (CCEs) (e.g., 1, 2, 4, 8, or 16 CCEs), each CCE including six RE groups (REGs), each REG including 12 consecutive REs in an OFDM symbol of an RB. A PDCCH within a BWP may be referred to as a control resource set (CORESET). The UE is configured to monitor PDCCH candidates in a PDCCH search space (e.g., a common search space, a UE-specific search space) during a PDCCH monitoring opportunity on a CORESET, wherein the PDCCH candidates have different DCI formats and different aggregation levels. Additional BWPs may be located at higher and / or lower frequencies on the channel bandwidth. A primary synchronization signal (PSS) may be within symbol 2 of a particular subframe of a frame. The PSS is used by UE 104 to determine subframe / symbol timing and physical layer identification. A secondary synchronization signal (SSS) may be within symbol 4 of a particular subframe of a frame. The SSS is used by the UE to determine the physical layer cell identity group number and the radio frame timing. Based on the physical layer identity and the physical layer cell identity group number, the UE can determine the physical cell identifier (PCI). Based on the PCI, the UE can determine the location of the DM-RS. The physical broadcast channel (PBCH) carrying the master information block (MIB) can be logically grouped with the PSS and SSS to form a synchronization signal (SS) / PBCH block (also referred to as an SS block (SSB)). The MIB provides the system frame number (SFN) and the number of RBs in the system bandwidth. The physical downlink shared channel (PDSCH) carries user data, broadcast system information such as system information blocks (SIBs) that are not sent via the PBCH, and paging messages.

[0072] like Figure 2C As illustrated, some of the REs carry DM-RS (indicated as R for a particular configuration, but other DM-RS configurations are possible) for channel estimation at the base station. The UE may send the DM-RS of the physical uplink control channel (PUCCH) and the DM-RS of the physical uplink shared channel (PUSCH). The PUSCH DM-RS may be sent in the first or first two symbols of the PUSCH. Depending on whether a short PUCCH or a long PUCCH is sent and depending on the specific PUCCH format used, the PUCCH DM-RS may be sent in different configurations. The UE may send a sounding reference signal (SRS). The SRS may be sent in the last symbol of a subframe. The SRS may have a comb structure, and the UE may send the SRS on one of the teeth of the comb. The SRS may be used by the base station for channel quality estimation to achieve frequency-dependent scheduling of the UL.

[0073] Figure 2DExamples of various UL channels within a subframe of a frame are illustrated. The PUCCH may be located at a position as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicators (CQI), precoding matrix indicators (PMI), rank indicators (RI), and hybrid automatic repeat request (HARQ) acknowledgement (ACK) (HARQ-ACK) feedback (i.e., one or more HARQ ACK bits indicating one or more ACKs and / or negative ACKs (NACKs)). The PUSCH carries data and may additionally be used to carry a buffer status report (BSR), a power headroom report (PHR), and / or UCI.

[0074] Figure 3 375. The Controller / Processor 375 is a block diagram of a base station 310 in an access network communicating with a UE 350. In the DL, Internet Protocol (IP) packets may be provided to a controller / processor 375. The controller / processor 375 implements layer 3 and layer 2 functionality. Layer 3 includes a radio resource control (RRC) layer, and layer 2 includes a service data adaptation protocol (SDAP) layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a medium access control (MAC) layer. The controller / processor 375 provides RRC layer functionality associated with broadcasting of system information (e.g., MIB, SIB), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-radio access technology (RAT) mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality associated with header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with delivery of upper layer packet data units (PDUs), error correction through ARQ, concatenation, segmentation and reassembly of RLC service data units (SDUs), re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

[0075] The transmit (TX) processor 316 and receive (RX) processor 370 implement layer 1 functionality associated with various signal processing functions. Layer 1 (which includes the physical (PHY) layer) may include error detection on the transport channel, forward error correction (FEC) coding / decoding of the transport channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. The TX processor 316 processes the mapping to the signal constellation based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-order phase shift keying (M-PSK), M-order quadrature amplitude modulation (M-QAM)). The coded and modulated symbols can then be split into parallel streams. Each stream can then be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., pilot) in the time and / or frequency domain, and then combined using an inverse fast Fourier transform (IFFT) to produce a physical channel carrying a time domain OFDM symbol stream. The OFDM stream is spatially pre-coded to generate multiple spatial streams. Channel estimates from a channel estimator 374 may be used to determine the coding and modulation schemes, as well as for spatial processing. Channel estimates may be derived from reference signals and / or channel condition feedback sent by the UE 350. Each spatial stream may then be provided to a different antenna 320 via a separate transmitter 318Tx. Each transmitter 318Tx may modulate a radio frequency (RF) carrier with a corresponding spatial stream for transmission.

[0076] At the UE 350, each receiver 354Rx receives a signal through its corresponding antenna 352. Each receiver 354Rx recovers the information modulated onto the RF carrier and provides the information to a receive (RX) processor 356. The TX processor 368 and the RX processor 356 implement layer 1 functionality associated with various signal processing functions. The RX processor 356 can perform spatial processing on the information to recover any spatial stream destined for the UE 350. If multiple spatial streams are destined for the UE 350, they can be combined into a single OFDM symbol stream by the RX processor 356. The RX processor 356 then converts the OFDM symbol stream from the time domain to the frequency domain using a fast Fourier transform (FFT). The frequency domain signal includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbol on each subcarrier and the reference signal are recovered and demodulated by determining the signal constellation point most likely to be sent by the base station 310. These soft decisions can be based on the channel estimate calculated by the channel estimator 358. The soft decisions are then decoded and deinterleaved to recover the data and control signals originally sent on the physical channel by the base station 310. The data and control signals are then provided to the controller / processor 359, which implements layer 3 and layer 2 functionality.

[0077] The controller / processor 359 may be associated with a memory 360 that stores program codes and data. The memory 360 may be referred to as a computer readable medium. In the UL, the controller / processor 359 provides demultiplexing between transport channels and logical channels, packet reassembly, decryption, header decompression, and control signal processing to recover IP packets. The controller / processor 359 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operations.

[0078] Similar to the functions described in conjunction with DL transmission performed by the base station 310, the controller / processor 359 provides RRC layer functionality associated with system information (e.g., MIB, SIB) acquisition, RRC connection, and measurement reporting; PDCP layer functionality associated with header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functionality associated with transmission of upper layer PDUs, error correction through ARQ, concatenation, segmentation and reassembly of RLC SDUs, resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

[0079] The TX processor 368 may use channel estimates derived by the channel estimator 358 from a reference signal or feedback sent by the base station 310 to select appropriate coding and modulation schemes and to facilitate spatial processing. The spatial streams generated by the TX processor 368 may be provided to different antennas 352 via corresponding transmitters 354Tx. Each transmitter 354Tx may modulate an RF carrier with a corresponding spatial stream for transmission.

[0080] UL transmissions are processed at the base station 310 in a manner similar to that described in conjunction with the receiver functionality at the UE 350. Each receiver 318Rx receives a signal through its corresponding antenna 320. Each receiver 318Rx recovers information modulated onto an RF carrier and provides the information to the RX processor 370.

[0081] The controller / processor 375 may be associated with a memory 376 that stores program codes and data. The memory 376 may be referred to as a computer readable medium. In the UL, the controller / processor 375 provides demultiplexing between transport channels and logical channels, packet reassembly, decryption, header decompression, control signal processing to recover IP packets. The controller / processor 375 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operations.

[0082] At least one of the TX processor 368, the RX processor 356, and the controller / processor 359 may be configured to perform a combined Figure 1 198. At least one of the TX processor 316, the RX processor 370, and the controller / processor 375 may be configured to perform a combined Figure 1 Various aspects of monitoring component 199.

[0083] Figure 4 4 is a diagram illustrating an example of UE positioning based on reference signal measurement. UE 404 may be at time T SRS_TX UL-SRS 412 is sent and at time T PRS_RX A DL positioning reference signal (PRS) (DL-PRS) 410 is received. TRP 406 may be at time T SRS_RX Receive UL-SRS 412 and at time T PRS_TX 410. UE 404 may receive DL-PRS 410 before transmitting UL-SRS 412, or may transmit UL-SRS 412 before receiving DL-PRS 410. In both cases, a positioning server (e.g., location server 168) or UE 404 may determine the UL-SRS 412 based on ||T SRS_RX -T PRS_TX |-|T SRS_TX -T PRS_RX || to determine RTT 414. Thus, multi-RTT positioning may utilize UE ERx-Tx time difference measurements (i.e., |T SRS_TX -T PRS_RX |) and DL-PRS reference signal received power (RSRP) (DL-PRS-RSRP), and the measured TRP Rx-Tx time difference measurement (ie, |T SRS_RX -T PRS_TX |) and UL-SRS-RSRP. The UE 404 measures the UE Rx-Tx time difference measurement (and optionally the DL-PRS-RSRP of the received signal) using the assistance data received from the positioning server, and the TRP 402, 406 measures the gNB Rx-Tx time difference measurement (and optionally the UL-SRS-RSRP of the received signal) using the assistance data received from the positioning server. These measurements may be used at the positioning server or the UE 404 to determine the RTT, which is used to estimate the position of the UE 404. Other methods for determining the RTT are possible, such as, for example, using DL-TDOA and / or UL-TDOA measurements.

[0084] DL-AoD positioning may utilize measured DL-PRS-RSRP of downlink signals received at a UE 404 from multiple TRPs 402, 406. The UE 404 measures the DL-PRS-RSRP of the received signals using assistance data received from a positioning server, and the resulting measurements are used along with the departure azimuth angle (A-AoD), departure zenith angle (Z-AoD), and other configuration information to position the UE 404 relative to neighboring TRPs 402, 406. DL-TDOA positioning may utilize DL reference signal time difference (RSTD) (and optionally DL-PRS-RSRP) of downlink signals received at a UE 404 from multiple TRPs 402, 406. The UE 404 measures the DL RSTD (and optionally DL-PRS-RSRP) of the received signals using assistance data received from a positioning server, and the resulting measurements are used along with other configuration information to position the UE 404 relative to neighboring TRPs 402, 406.

[0085] UL-TDOA positioning may utilize the UL relative time of arrival (RTOA) (and optionally UL-SRS-RSRP) of uplink signals sent from the UE 404 at multiple TRPs 402, 406. The TRPs 402, 406 measure the UL-RTOA (and optionally UL-SRS-RSRP) of the received signals using assistance data received from the positioning server, and the resulting measurements are used along with other configuration information to estimate the position of the UE 404. UL-AoA positioning may utilize the measured azimuth angle of arrival (A-AoA) and zenith angle of arrival (Z-AoA) of uplink signals sent from the UE 404 at multiple TRPs 402, 406. The TRPs 402, 406 measure the A-AoA and Z-AoA of the received signals using assistance data received from the positioning server, and the resulting measurements are used along with other configuration information to estimate the position of the UE 404.

[0086] Additional positioning methods may be used to estimate the position of the UE 404, such as, for example, UE-side UL-AoD and / or DL-AoA. Note that data / measurements from various techniques may be combined in various ways to increase accuracy, determine and / or enhance certainty, supplement / complete measurements, and / or replace / provide missing information.

[0087] Figure 5500 is a diagram illustrating an example of estimating a UE's position based on multi-RTT measurements from multiple TRPs in accordance with various aspects of the present disclosure. The UE 502 may be configured by a serving base station to decode DL-PRS resources 512 corresponding to and transmitted from a first TRP 504 (TRP-1), a second TRP 506 (TRP-2), a third TRP 508 (TRP-3), and a fourth TRP 510 (TRP-4). The UE 502 may also be configured to transmit a UL-SRS on a UL-SRS resource set, which may include a first SRS resource 514, a second SRS resource 516, a third SRS resource 518, and a fourth SRS resource 520, so that a serving cell (e.g., a first TRP 504, a second TRP 506, a third TRP 508, and a fourth TRP 510) and other neighboring cells may be able to measure the UL-SRS resource set transmitted from the UE 502. For multi-RTT measurements based on DL-PRS and UL-SRS, since there may be a correlation between the UE's measurement of the DL-PRS and the TRP's measurement of the UL-SRS, the smaller the gap between the UE's DL-PRS measurement and the UE's UL-SRS transmission, the better the accuracy of estimating the UE's position and / or the UE's distance for each TRP may be.

[0088] In some aspects of wireless communications, the terms "positioning reference signal" and "PRS" may generally refer to specific reference signals used for positioning in NR and LTE systems. However, as used herein, the terms "positioning reference signal" and "PRS" may also refer to any type of reference signal that can be used for positioning, such as, but not limited to: PRS, TRS, PTRS, CRS, CSI-RS, DMRS, PSS, SSS, SSB, SRS, UL-PRS, etc. as defined in LTE and NR. In addition, the terms "positioning reference signal" and "PRS" may refer to downlink or uplink positioning reference signals, unless otherwise indicated by the context. In some aspects, a downlink positioning reference signal may be referred to as a "DL-PRS", while an uplink positioning reference signal (e.g., positioning SRS, PTRS) may be referred to as a "UL-PRS". In addition, for signals (e.g., DMRS, PTRS) that may be sent in both uplink and downlink, these signals may be prepended with "UL" or "DL" to distinguish the direction. For example, "UL-DMRS" may be distinguished from "DL-DMRS".

[0089] Figure 66 is a communication flow 600 illustrating an example multi-RTT positioning procedure in accordance with various aspects of the present disclosure. The numbers associated with the communication flow 600 do not specify a particular time sequence and are merely used as a reference for the communication flow 600. In addition, DL-only and / or UL-only positioning may use one or more subsets of the multi-RTT positioning procedure.

[0090] At 610, the LMF 606 may request one or more positioning capabilities from the UE 602 (e.g., from a target device). In some examples, the request for one or more positioning capabilities from the UE 602 may be associated with the LTE Positioning Protocol (LPP). For example, the LMF 606 may request the positioning capabilities of the UE 602 using the LPP capability transmission procedure. At 612, the LMF 606 may request UL SRS configuration information for the UE 602. The LMF 606 may also provide assistance data (e.g., path loss reference, spatial relationship and / or SSB configuration, etc.) specified by the serving base station 604. For example, the LMF 606 may transmit an NR Positioning Protocol A (NRPPa) positioning information request message to the serving base station 604 to request UL information for the UE 602.

[0091] At 614, the serving base station 604 may determine resources available for UL SRS, and at 616, the serving base station 604 may configure one or more UL SRS resource sets for the UE 602 based on the available resources. At 618, the serving base station 604 may provide UL SRS configuration information to the LMF 606, such as via an NRPPa Positioning Information Response message. At 620, the LMF 606 may select one or more candidate neighboring BS / TRPs 608, and the LMF 606 may provide the UL SRS configuration to the one or more candidate neighboring BS / TRPs 608 and / or the serving base station 604, such as via an NRPPa Measurement Request message. The message may include information for enabling the one or more candidate neighboring BS / TRPs 608 and / or the serving base station to perform UL measurements.

[0092] At 622, the LMF 606 may transmit an LPP Provide Assistance Data message to the UE 602. The message may include specified assistance data for the UE 602 to perform DL measurements. At 624, the LMF 606 may transmit an LPP Request Location Information message to the UE 602 to request multi-RTT measurements. At 626, for semi-persistent or aperiodic UL SRS, the LMF 606 may request the serving base station 604 to activate / trigger the UL SRS in the UE 602. For example, the LMF 606 may request activation of UE SRS transmission by transmitting an NRPPa Positioning Activation Request message to the serving base station 604.

[0093] At 628, the serving base station 604 may activate UE SRS transmission and transmit an NRPPa positioning activation response message. In response, the UE 602 may start UL-SRS transmission according to the time domain behavior of the UL SRS resource configuration. At 630, the UE 602 may perform DL measurements from one or more candidate neighboring BS / TRPs 608 and / or serving base stations 604 provided in the auxiliary data. At 632, each of the configured one or more candidate neighboring BS / TRPs 608 and / or serving base stations 604 may perform UL measurements. At 634, the UE 602 may report the DL measurements to the LMF 606, such as via an LPP provide location information message. At 636, each of the one or more candidate neighboring BS / TRPs 608 and / or serving base stations 604 may report the UL measurements to the LMF 606, such as via an NRPPa measurement response message. At 638, the LMF 606 may determine the RTT from the UE 602 and the BS / TRP Rx-Tx time difference measurements for each of the one or more candidate neighboring BS / TRPs 608 and / or serving base stations 604 for which corresponding UL and DL measurements were provided at 634 and 636, and the LMF 606 may calculate the positioning of the UE 602.

[0094] Various aspects of the communication or device configuration may utilize several different mapping or navigation processes for a device (e.g., an Internet of Things (IoT) device). For example, a mapping or navigation process may navigate a device along a route or route segment, and determine or update the position of the device along the route or route segment. Therefore, a mapping or navigation process is similar to a position positioning process because the device location can be determined along a route or route segment. However, some types of mapping or navigation processes may not utilize some types of positioning technologies. For example, the operating system of the mapping or navigation process may specify which positioning technologies can be used for a given positioning request (e.g., a positioning request on the device or smartphone side). In addition, a server or network (NW) may specify the periodicity of a specific positioning technology, regardless of the scenario within the mapping or navigation process. That is, a server or network (e.g., a low-level server / network) may select a specific positioning technology for several reasons, such as to reduce power consumption. In fact, the server / network may opportunistically select a specific technology for positioning a device in order to reduce power consumption at the device in a reactive manner.

[0095] Additionally, there may be certain geographic areas where positioning technologies produce poor results and cause battery drain (e.g., battery drain at the device). For example, certain areas or geo-fences (i.e., virtual perimeters around real-world geographic areas) can cause certain positioning technologies to perform poorly, and cause the device to lose excessive battery power within the area. As a result, this may lead to a false sense of the reliability of the location of the device determined using certain types of positioning technologies. In addition, the classification of the device's movement pattern may change based on the context of the route or area to which the device is indeed close. Furthermore, in some instances, the device's destination route selection may be performed based on several factors, such as traffic conditions, positioning reliability, etc. However, these factors may not take into account how the environment or environmental factors along the route or route segment may affect the device or package being transported along the route or route segment.

[0096] In some types of environments, some positioning technologies may not perform well compared to other positioning technologies. For example, in some approaches (e.g., commercial approaches), a device (e.g., a tracking device) that does not know a route or route segment may continue to try to perform a specific positioning in certain situations (e.g., dense urban environments) where some positioning technologies (e.g., global navigation satellite systems (GNSS)) may not perform well. In addition, in these situations (e.g., dense urban environments), some positioning technologies may request the device to remain awake for a longer period of time than normal, which may consume battery power at the device. In some scenarios, after calculating the location, the device may spend a lot of time trying to reconnect to a network in a location (e.g., a rural environment) where the network quality is inconsistent or unavailable. Additionally, in some scenarios, it may be necessary to prompt (e.g., by a server) the device to change the quality of service (QoS) or positioning technology, which may also result in increased battery consumption at the device. Based on the above, it may be advantageous for the device to understand the positioning technology used to determine its location. For example, it may be advantageous for the device to know the positioning technology to be used for certain environments or route segments.

[0097] Various aspects of the present disclosure can indicate to the device that certain positioning technologies will be utilized in order to determine the device location. For example, the device herein can receive instructions for which positioning technologies are utilized in certain scenarios (e.g., certain environments or sections of a route). In some instances, before a route or a specific route segment, the device herein may be preconfigured with positioning technologies to be utilized in certain environments (e.g., dense urban environments or rural environments) or certain route sections. By doing so, the device herein can utilize reduced battery consumption because it may not be necessary to prompt them to change QoS or positioning technologies in certain scenarios. That is, the various aspects presented herein can reduce the power consumption of the device by indicating a suitable or desired method for determining the location of each device. For example, the device herein can receive (e.g., from a server) instructions for a suitable or desired methodology for determining the location of the device when the device is located in a specific environment or section of the route.

[0098] In some aspects, the device herein may receive an indication of a route or route segment (i.e., one or more segments or sections of a route or path). Route segments may be grouped together to form an entire route, or each route segment may be a separate route so that all route segments correspond to multiple routes. For example, a server (e.g., a cloud server) or a network may send an indication of a route or route segment to a device before the device embarks on a route or route segment. The indication of a route / route segment may indicate an expected route or expected point along the route / route segment for the device. In addition, a route or route segment may indicate a sequence in which expected points will appear along the route or route segment, as well as a sequence of overall expected routes or route segments. For example, a route or route segment may indicate the following sequence: (i) a left turn or left motion mode at a first point (point 1), (ii) a right turn or right motion mode at a second point (point 2), (iii) a right turn or right motion mode at a third point (point 3), (iv) a left turn or left motion mode at a fourth point (point 4), and (v) a pothole or pothole motion mode at a fifth point (point 5). For example, this motion sequence may correspond to the following Figure 7 The movement sequence indicated in .

[0099] In some aspects, a server or network may obtain a route or several points (e.g., a starting point and a destination point) associated with at least one device. The server or network may also receive several route segments (i.e., one or more segments of a route) for the device. For example, the server may obtain one or more routes or route segments from the starting point to the destination point. Additionally, the server may determine several device parameters for one or more route segments (e.g., road segments) associated with the route. That is, after obtaining the route or route segment, the server or network may select a set of device parameters (e.g., one or more device parameters) for one or more route segments. In some instances, the set of device parameters for the route segment may include an indication of the operation of the device along each route segment. In addition, at least one of these device parameters may be based on the proximity (e.g., threshold distance) of the device to the corresponding route segment. The route or route segment may be indicated based on a certain area or perimeter near the route. For example, a route segment (e.g., road segment) may be indicated based on a geofence (i.e., a virtual perimeter around a real-world geographic area) such as an absolute geofence or a relative geofence. The route segment may also be indicated based on several timers, time periods, and / or distances. At certain points along the route (or route segment), the device (e.g., a tracking device) may wake up and perform a search for a certain positioning technology or radio access technology (RAT) such as WiFi, WiFi received signal strength indicator (RSSI), WiFi fine time measurement (FTM), ultra-wideband (UWB), Bluetooth low energy (BLE), 5G new radio (NR), or 4G long term evolution (LTE). The device may also identify nearby access points (APs) (e.g., WiFi APs), base stations (BSs) (e.g., gNBs), or transmit receive points (TRPs) (e.g., 5GTRPs) for communication with the positioning technology or RAT. For example, the device may use the identified WiFi APs or 5G TRPs to identify the relative distance to a nearby geo-fence, and select a particular sleep duration based on the expected time to the geo-fence.

[0100] In some aspects, a server or network may send an indication of a set of parameters (e.g., device parameters) to a device. For example, a server or network may provide device parameters to a device (e.g., a tracking device) for use along a route or route segment. The device may then set or apply the device parameters for use along a route or route segment. In one aspect, these device parameters may be loaded to the device before initiating a trip along a route (or route segment). In addition, the device parameters may be loaded after the device has started on the route. The device parameters may also be dynamically updated along a route or route segment. The indicated parameters (e.g., device parameters, route parameters, or device route parameters) may indicate several different factors or parameters to be utilized along a route or route segment. For example, the device parameters may include at least one of the following items or any combination thereof: auxiliary data (e.g., auxiliary data download parameters), positioning technology (e.g., positioning technology parameters), motion parameters, sensor parameters, connectivity parameters, sleep parameters. The auxiliary data download parameters may include route-specific data, one or more alternative routes, global navigation satellite system (GNSS) auxiliary data, or a combination thereof. For example, the assistance data download parameters may include route specific data for certain positioning (e.g., WiFi AP positioning, wireless / cellular base station / TRP positioning, BLE positioning, UWB positioning (such as alternative routes or route deviation paths)). The assistance data download parameters may also include additional GNSS assistance data (e.g., precise point positioning (PPP) data, real-time kinematic (RTK) data, ephemeris data, almanac data, etc.). In addition, the assistance data download parameters may include opportunities for additional downloads of data, which may be tied to specific geo-fences, time-based data, etc. Additional downloads of data may be performed at device configuration time, before the device departs along a route, or at some point during a route or a specific route segment.

[0101] As indicated above, the device parameters may also include several positioning technology parameters or positioning method parameters. The positioning technology / method parameters may indicate which positioning technologies or methods are used for each route segment (e.g., a road segment) or during a route. For example, the positioning technology / method parameters may specifically include a downlink (DL) time difference of arrival (TDOA) (DL-TDOA) for a specific positioning technology (e.g., DL-TDOA for 5G or DL-TDOA for UWB). The positioning technology / method parameters may also include the expected accuracy or expected latency of a specific positioning technology or method. In addition, the positioning technology / method parameters may include which specific parameters (e.g., frequency band, maximum power, etc.) are used in certain environments. In addition, the positioning technology / method parameters may include a weighting scheme (e.g., the power of the device), several fallback options, etc. In some instances, the positioning technology / method parameters may include an indication of when (or under what circumstances) waveform samples (e.g., samples from the environment surrounding the device, samples from the environment along a route or route segment, etc.) are included. The positioning technology / method parameters may also include the amount of positioning to be batched or stored before reporting associated with the device.

[0102] Additionally, the device parameters may include several motion parameters or sensor parameters. Motion / sensor parameters may indicate several motion modes that can trigger the device to perform a certain action. For example, the motion / sensor parameters may indicate a motion mode that triggers the device to perform at least one of the following actions or any combination thereof: wake up, sleep, report (e.g., report back to the network / server certain information), determine the specific location of the device along the route. The motion / sensor parameters may also indicate sensor threshold parameters corresponding to sensor detection of a certain device function. For example, the motion / sensor parameters may indicate when the device should report (e.g., report back to the network / server certain information), whether the device may need to record certain information and opportunistically report the information, or whether the information may need to be reported immediately. In addition, the device parameters may include several connectivity parameters or connection-related parameters. Connectivity parameters may indicate when the device should be connected to a certain network (e.g., time threshold, indication of a specific road segment, minimum payload size, or maximum payload size). For example, connectivity parameters may indicate a specific time or location that triggers the device to connect to the network. Connectivity parameters may also indicate whether to use a specific feature (e.g., a small data transmission (SDT) feature) when in a specific mode (e.g., a radio resource control (RRC) inactive mode). In addition, connectivity parameters may indicate how to compress information to fit a specific payload (e.g., an SDT payload). Connectivity parameters may also include several network synchronization parameters related to synchronization with a certain network (e.g., opportunities for synchronization between a device and a network, several synchronization thresholds for triggering synchronization between a device and a network, etc.). In addition, device parameters may include several sleep parameters for the device. Sleep parameters may directly indicate a specific time when the device should sleep. Sleep parameters may also indicate a certain point, location, or distance at which the device should sleep. In addition, sleep parameters may indicate a triggering event that triggers a certain device action, such as a triggering event for sleep and / or a triggering event for wakeup.

[0103] In some aspects, a server (e.g., a cloud server) may select or identify a specific route and / or route segment (e.g., road segment) for a device based on several expected route conditions or road conditions. Route segments may also be selected based on the sensitivity of the goods or packages on the device. For example, a server may identify road segments with fewer potholes along the route (compared to other road segments) based on the sensitivity of the goods or packages being transported on the device. In one instance, input to the server may directly include information about the sensitivity of the goods / packages to specific movements or vibrations. This information may be indirectly input to the server based on the type of goods / packages being transported (e.g., fragile items, temperature-sensitive items, medications, etc.). In addition, the server may select or identify a specific route and / or route segment based on the expected environment or environmental conditions (e.g., weather) along the route. For example, these environmental conditions may be related to the sensitivity of the goods / packages being transported on the device. The server may also select or identify a specific route and / or route segment based on the power consumption at the device or the battery condition at the device. For example, if the device is transporting heavy cargo / packages, this may result in high consumption of power / battery at the device, so the server may select a route or route segment based on high consumption of power or battery power. Additionally, the server or network may indicate which device is able to report back on behalf of other nearby devices (e.g., transport devices or pallet devices). For example, the server may send an indication to each nearby device that includes the device's ability to report back for other nearby devices. Based on this indication, each device may report back to the server (or not report back) on behalf of other nearby devices.

[0104] Figure 7 700 is a diagram illustrating an example route or route segment for device 702. In some instances, device 702 may be traveling along a route or route segment from starting point 740 to destination point 742. For example, device 702 may be traveling along one or more route segments (e.g., route segment 760, route segment 761, route segment 762, route segment 763, or route segment 764) from starting point 740 to destination point 742. Device 702 may be on a mobile object (e.g., a vehicle, a car, a ship, an airplane, etc.) or may be a tracking device on a mobile object. Device 702 may carry one or more other devices including device 702A, device 702B, device 702C, and device 702D. For example, devices 702A, 702B, 702C, and 702D may be cargo, packages, or items on device 702. Device 702 may be configured or pre-configured with a route or route segment associated with a particular motion pattern or set of motion events (e.g., device 702 may be configured with a route or route segment before device 702 leaves starting point 740). Figure 7As depicted in , a motion pattern may include several route segments or expected event sequences that may be determined by a server (e.g., server 704 as a management device 702) as expected to occur when device 702 travels from starting point 740 to destination point 742. Server 704 may be several different servers, such as a cloud server. For example, a route segment or event sequence may include motion events associated with certain types of movement of device 702 (e.g., straight-line movement, left turn movement, or right turn movement). The event sequence may include changes in elevation of device 702 relative to a horizontal plane (e.g., sea level), such as ascent or descent. Figure 7 As shown, the route segment or motion pattern may include one or more events at different locations (e.g., moving straight at point 750, turning left at point 751, turning right at point 752, turning right at point 753, turning left at point 754, and moving straight after point 754). The route segment or event sequence in the motion pattern may correspond to the absolute positioning of the device 702. As used herein, the term "absolute positioning" may refer to positioning relative to the earth (e.g., in terms of longitude, latitude, or altitude). In some aspects, different events at different positioning locations may correspond to one or more relative positions of the device 702 (e.g., the relative position of the device 702 may correspond to the device 702A, the device 702B, the device 702C, or the device 702D). In addition, the device 702 may be configured with certain information at the beginning of the route or route segment (e.g., from the starting point 740 to the destination point 742) or during the route or route segment (by the server or network). For example, a server or network may send information (e.g., small data transmission (SDT) information) to configure device 702 based on certain route conditions (e.g., traffic conditions, road conditions, weather conditions, etc.) that may affect which route or route segment device 702 takes. Device 702 may be configured by several different servers, such as servers associated with the network or servers not associated with the network. For example, the server may be a cloud server or a third-party server. In addition, the server may be an edge server or edge service associated with a software application, such as a software application running on hardware associated with a network entity (e.g., RU, DU, and / or CU). The hardware associated with the network entity may be network-agnostic hardware or network-specific hardware, as well as a mixture of different hardware that is network-agnostic hardware and / or network-specific hardware.

[0105] Additionally, device 702 may be configured with information about a set of access points, base stations, or TRPs along a route or route segment. For example, device 702 may be configured with information about TRP 706A, TRP 706B, TRP 706C, TRP 706D, and TRP 706E along a route or route segment. In some aspects, the information about a set of access points, base stations, or TRPs along a route may be associated with a number of route segments (e.g., route segments 760, 761, 762, 763, and 764) or a set of expected motion events. For example, device 702 may be configured with information that device 702 may (i) wake up and search for TRP 706B or TRP 706C between point 752 and point 753 or (ii) wake up and search for TRP 706D or TRP 706E between point 754 and destination point 742 at 734. Figure 7 As further depicted in , device 702 may be configured to connect to a network or server and report certain information (e.g., absolute or relative positioning) or other motion data at one or more time instances (based on a duty cycle). For example, at 736 (approaching point 754), device 702 may connect to a network or server (e.g., server 704) and report certain positioning information or motion information.

[0106] like Figure 7 As depicted in , device 702 can obtain an indication of one or more route segments (e.g., route segments 760, 761, 762, 763, and 764) before initiating movement along the route segment. For example, device 702 can receive indications of different route segments from server 704, which can indicate the location of each route segment relative to other points / locations (e.g., route segment 760 is between starting point 740 and point 751, route segment 761 is between point 751 and point 752, route segment 762 is between point 752 and point 753, route segment 763 is between point 753 and point 754, and route segment 764 is between point 754 and destination point 742). The route segments can be indicated to device 702 based on a number of factors (such as points / locations), at least one geo-fence (e.g., absolute or relative geo-fence), one or more timers, etc. In addition, server 704 can send a set of device parameters (e.g., device parameters 780) to device 702. Device 702 may obtain device parameters 780 before starting a trip along a route segment and during the trip along the route segment. Device parameters 780 may also be dynamically updated during the trip along the route segment. Device parameters 780 may include at least one of the following: assistance data download parameters, positioning parameters, motion parameters, sensor parameters, connectivity parameters, or sleep parameters.

[0107] like Figure 7As further depicted in FIG. 7 , device 702 may include several sensors (e.g., sensor 712). Device 702 may configure sensor 712 based on device parameter set 780 for route segment. Device 702 may also send sensor-related information associated with sensor 712 to server 704 or network. Device 702 may also obtain indications of different route conditions (e.g., route condition 771 on route segment 762 and / or route condition 772 on route segment 764). For example, these route conditions may be related to environmental conditions of the route (e.g., water, puddles, snow, ice, etc.) or physical conditions of the route (e.g., potholes or cracks in the road). Based on the route conditions, device 702 may update sensing data or device parameters for the route segment. Device 702 may also send indications of updated sensing data or updated device parameters to server 704. Device 702 may also report information about route conditions to server 704. In addition, device 702 may receive indications from server 704, including reporting capabilities of device 702 for reporting back on behalf of other nearby devices. In addition, the device 702 can wake up and search for an access point (AP), a base station, or a TRP (e.g., at 734, the device 702 can wake up and search for TRP 706B or TRP 706C between point 752 and point 753). The device 702 can use the identified AP or TRP to identify the relative distance to a nearby geofence (e.g., area 782) and select a specific sleep duration based on the expected time to the geofence (e.g., area 782). In addition, if the device location is greater than a threshold distance from the target location (e.g., geofence or area 782), the device 702 can receive a warning indication from the server 704.

[0108] In some aspects, a server (e.g., a cloud server) may request a network (e.g., a network entity, a base station, and / or a network TRP) or multiple networks to monitor or track a specific device along a route or route segment. For example, a server may send a request to a network entity or TRP for monitoring one or more devices (e.g., tracking devices) along one or more route segments. The request for monitoring the device may indicate to the network that a specific transport vehicle along a specific route or route segment is to be monitored / tracked via sensing. The transport vehicle may be several devices, such as mobile devices (e.g., vehicles, cars, ships, airplanes, etc.), tracking devices, and / or goods / packages on a specific device. In addition, the server may provide information associated with a route or route segment (i.e., route information) and device information associated with the device to the network. In some instances, the request for monitoring may include device information associated with the device and / or route information associated with the route or route segment. The device information may include a device identifier (ID) for each device, and the route information may include the configuration of the route segment or one or more conditions of the route segment. In addition, the server may indicate (e.g., in a request for monitoring) several different factors regarding network operation during monitoring of the device. For example, the request for monitoring may indicate a time period (i.e., monitoring period) for monitoring the device, a periodicity for monitoring the device, a distance for monitoring the device, and / or a level of accuracy for monitoring the device. In some instances, if a particular network operator does not have coverage to monitor the device, the server may contact another network operator to transfer the monitoring operation (e.g., sensing tracking operation) from the initial network operator to another network operator. For example, the server may re-contact another network operator in a manner similar to the initial network operator, such as by sending a request for monitoring the device. In addition, the server may provide the precise location of the device and identify the device (e.g., a transportation vehicle) or a specific feature that distinguishes the device from other nearby devices or vehicles.

[0109] In response to receiving a request for monitoring a device, the network (e.g., a network entity or a TRP) may identify one or more devices (e.g., via a device ID) and perform ranging (i.e., ranging process) with the device until the network identifies the transport device / vehicle. The ranging process may be associated with the identification of the device or the identification of the location / positioning of the device. The ranging process may be based on the distance of the communication between the device and the network (i.e., ranging communication), the timing of the communication between the device and the network, and / or the signal strength of the communication between the device and the network. The ranging process may be associated with information about the ranging communication between the device and the network (i.e., ranging information). In some instances, the ranging process may be associated with determining the location of the device, which may be performed using different detection / ranging methods (e.g., light detection and ranging (LiDAR) or radio detection and ranging (RADAR)). In addition, the network may identify the transport device / vehicle via sensing or a sensing process. The network may also identify the transport device / vehicle based on ranging information from the ranging process. The network may then send to the server (and the server may receive from the network) an indication of the monitoring status of the relevant device. For example, the server may receive an indication from the network (e.g., a network TRP) when the device has been detected and is being tracked (e.g., a transport vehicle). The server may also update the device information and / or route information associated with the route segment. For example, the server may notify the device on the transport vehicle of the updated device information or the updated route information. The updated device information may include an updated reporting schedule and / or an updated sleep schedule for the device, and the updated route information may include one or more triggering events along the route segment for the device. For example, a device may be triggered by an event (e.g., a device in flight may be triggered by landing) to report information in order to determine positioning. In some instances, the device may wait for a certain period / distance (e.g., until the device has stopped moving) to report information.

[0110] After performing the ranging process and sending an indication of the monitoring status of the relevant equipment, the network can monitor or track the equipment / vehicle along the route or route segment. For example, each network entity (e.g., TRP / AP / base station) in the network along the route (e.g., within a certain proximity or distance of the route) can continue to monitor or track the vehicle as it moves along the route or route segment. The network entity (e.g., TRP / AP / base station) that detects and tracks the vehicle can notify the nearby network entity to hand over the tracking of the vehicle. In some entities, the blind area along the route (i.e., the area where the network entity does not have any coverage to track the vehicle) can correspond to the area where the tracking device performs its own positioning (i.e., the blind area can be "filled" by the device that performs positioning). The route or route segment can also include several delivery points or delivery events (i.e., the event of delivering goods / packages on the device at a specific point ("delivery point")). At each delivery point along the route, some equipment (e.g., tracking equipment) can include a corresponding movement equivalent to leaving the transport device (i.e., being delivered from the transport device). The transport device (or the device being dropped) may wake up and report the drop event (if configured to do so). Additionally, the device (e.g., a tracking device) may batch or store sensor measurements or other relevant information about the location / movement of the device along the route or route segment. This may occur even though at least some of the location / movement tracking may be offloaded to the network.

[0111] Figure 8 800 is a diagram illustrating an example route or route segment for device 802. In some instances, device 802 may be traveling along a route or route segment from starting point 840 to destination point 842. For example, device 802 may be traveling along one or more route segments (e.g., route segment 860, route segment 861, route segment 862, route segment 863, and route segment 864) from starting point 840 to destination point 842. Device 802 may be on a moving object (e.g., a vehicle, a car, a ship, an airplane, etc.) or may be a tracking device on a moving object. Device 802 may carry one or more other devices including device 802A, device 802B, device 802C, and device 802D. For example, devices 802A, 802B, 802C, and 802D may be cargo, packages, or items on device 802. Similar to Figure 7 In the device 702 of FIG. 8 , the device 802 may be configured or pre-configured with a route or route segment associated with a particular motion mode or set of motion events (e.g., the device 802 may be configured with a route or route segment before the device 802 leaves the starting point 840). Figure 8As depicted in , the motion pattern may include a number of route segments or expected event sequences that may be determined by a server (e.g., server 804 managing device 802) as expected to occur when device 802 travels from starting point 840 to destination point 842. Server 804 may be a number of different servers, such as a cloud server. Figure 8 As shown, a route segment or a motion pattern may include one or more events at different locations (e.g., moving in a straight line at point 850, turning left at point 851, turning right at point 852, turning right at point 853, turning left at point 854, and moving in a straight line after point 854). Additionally, device 802 may be configured with information about a set of access points, base stations, or TRPs along a route or route segment. For example, device 802 may be configured with information about TRPs 806A, 806B, 806C, 806D, and 806E along a route or route segment. In some aspects, information about a set of access points, base stations, or TRPs along a route may be associated with several route segments (e.g., route segments 860, 861, 862, 863, and 864) or a set of expected motion events. For example, device 802 may be configured with information that device 802 may (i) wake up and search for TRP 806B or TRP 806C between point 852 and point 853 at 834, or (ii) wake up and search for TRP 806D or TRP 806E between point 854 and destination point 842. Figure 8As further depicted in , device 802 may be configured to be connected to a network or server and report certain information or other motion data at one or more time instances. For example, at 836 (near point 854), device 802 may be connected to a network or server (e.g., server 804) and report certain positioning / motion information. Device 802 may also include several sensors (e.g., sensor 812), and device 802 may send sensor-related information associated with sensor 812 to server 804 or the network. In addition, device 802 may be configured with certain information at the beginning of a route or route segment (e.g., from starting point 840 to destination point 842) or during a route or route segment (by a server or network). For example, a server or network may send information (e.g., small data transmission (SDT) information) to configure device 802 based on certain route conditions (e.g., traffic conditions, road conditions, weather conditions, etc.) that may affect which route or route segment device 802 takes. Device 802 may be configured by several different servers such as a server associated with a network or a server not associated with a network. For example, the server may be a cloud server or a third-party server. In addition, the server may be an edge server or edge service associated with a software application, such as a software application running on hardware associated with a network entity (e.g., RU, DU, and / or CU). The hardware associated with the network entity may be network-agnostic hardware or network-specific hardware, as well as a mixture of different hardware that is network-agnostic hardware and / or network-specific hardware.

[0112] like Figure 8802 , server 804 may send a monitoring request 880 to network entities (e.g., TRP 806A, TRP 806B, TRP 806C, TRP 806D, and TRP 806E) along a route of device 802. Monitoring request 880 may be a request for monitoring device 802 along one or more route segments (e.g., route segments 860, 861, 862, 863, and 864). In response to receiving monitoring request 880, the network (e.g., TRP 806A or TRP 806B) may verify an identifier (e.g., device ID) for device 802 and perform ranging 882 (i.e., ranging process) with device 802 until the network identifies device 802. As indicated above, ranging 882 may be associated with identification of device 802 or location / positioning of device 802. The ranging 882 may be based on the distance of the communication between the device 802 and the TRP 806A, the timing of the communication between the device 802 and the TRP 806A, or the signal strength of the communication between the device 802 and the TRP 806A. After ranging 882, the network (e.g., TRP 806A or TRP 806B) may send a monitoring indication 884 (an indication of the monitoring status of the device 802) to the server 804. For example, the server 804 may receive a monitoring indication 884 regarding when the TRP 806A or TRP 806B has detected the device 802 and is tracking the device 802. Each TRP in the network (TRP 806A, TRP 806B, TRP 806C, TRP 806D, and TRP 806E) may continue to monitor (via monitoring 886) the device 802 along the route or route segment. Furthermore, as device 802 moves along a route or route segment, each TRP in the network (TRP 806A, TRP 806B, TRP 806C, TRP 806D, and TRP 806E) may hand over monitoring (via handover 888) to another TRP along the route. Additionally, route segment 863 may include a drop point 871 where a device / cargo / package on device 802 (e.g., device 802D) is dropped at a particular point (e.g., drop point 871). After drop point 871, device 802 and / or device 802D may wake up and report a drop event. Figure 8 As shown, after drop point 871, devices 802 may no longer include device 802D (because it was previously dropped).

[0113] In some aspects, in order to determine whether to use a certain positioning technology along a specific route segment, the server and / or device can use the density of network entities (e.g., AP / BS / TRP). For example, the server and / or device can use density information related to certain devices (e.g., WiFi AP, cellular / wireless base station, BLE network entity, UWB network entity) to determine whether to use the corresponding positioning technology along a portion of the route. In addition, the server / device can determine to stop using a certain technology (e.g., GNSS) and switch to a different positioning technology, such as by using density information of different positioning technologies. The server / device can explicitly determine which part of the route or route segment to use different positioning technologies. In some instances, the server / device can use the capabilities (e.g., capability type) of base stations (e.g., cellular base stations), TRPs or APs (e.g., WiFi APs) in a certain area to determine whether to use the corresponding technology instead of the initial technology or methodology (e.g., GNSS). The server / device can also indicate whether to use a specific technology of a specific type (e.g., GNSS of GPS only, etc.). In some instances, a certain technology may include capabilities for different positioning types or frequency types. For example, WiFi capabilities may include certain positioning types (e.g., WiFi received signal strength indicator (RSSI) or WiFi fine time measurement (FTM)) and / or certain frequency types (e.g., 2.4GHz, 5GHz, 6GHz, 60GHz, etc.). Capabilities for different positioning technologies may also include whether the technology is open and available, or whether the technology requires an authentication process (e.g., whether WiFi is open and available or whether WiFi requires authentication). The server / device may also indicate whether to use a certain technology based on the reliability of the corresponding network entity (e.g., AP / BS / TRP) in the area (e.g., the number of times the network entity has been crowdsourced, one or more recent measurement results, etc.).

[0114] Additionally, the server and / or device may utilize sensor information during a location positioning process along a route or route segment. For example, the server and / or device may obtain sensor information (e.g., sensor drift information) to determine the exact location of the device. Such sensor information may also be combined with other signals / communications and / or database information (e.g., a database of potential locations, location ranges, etc.). For example, a server may have a database of location information for the device (e.g., WiFi location data), and sensor information from the device may be used to adjust / shift the location information. In addition, the server may receive sensor information from the device and compare this information with other information (e.g., database information). The server may also instruct the device to adjust the use of sensor information along the route or route segment.

[0115] Fig. 9900 is a diagram illustrating an example route or route segment for device 902. In some instances, device 902 may be traveling along a route or route segment from starting point 940 to destination point 942. For example, device 902 may be traveling along one or more route segments (e.g., route segment 960, route segment 961, route segment 962, route segment 963, and route segment 964) from starting point 940 to destination point 942. Device 902 may be on a moving object (e.g., a vehicle, a car, a ship, an airplane, etc.) or may be a tracking device on a moving object. Device 902 may carry one or more other devices including device 902A, device 902B, device 902C, and device 902D. For example, devices 902A, 902B, 902C, and 902D may be cargo, packages, or items on device 902. Similar to Figure 7 Device 702 and Figure 8 In the device 802 of FIG. 1 , the device 902 may be configured or preconfigured with a route or route segment associated with a particular motion mode or set of motion events (e.g., the device 902 may be configured with a route or route segment before the device 902 leaves the starting point 940). Fig. 9 As depicted in , a motion pattern may include several route segments or expected event sequences that may be determined by a server (e.g., server 904 managing device 902) as expected to occur when device 902 travels from starting point 940 to destination point 942. Server 904 may be several different servers, such as a cloud server. Fig. 9 As shown, a route segment or motion pattern may include one or more events at different locations (e.g., moving in a straight line at point 950, turning left at point 951, turning right at point 952, turning right at point 953, turning left at point 954, and moving in a straight line after point 954). Additionally, device 902 may be configured with information about a set of access points, base stations, or TRPs along a route or route segment. For example, device 902 may be configured with information about TRPs 906A, 906B, 906C, 906D, and 906E along a route or route segment. In some aspects, information about a set of access points, base stations, or TRPs along a route may be associated with several route segments (e.g., route segments 960, 961, 962, 963, and 964) or a set of expected motion events. For example, device 902 may be configured with information that device 902 may (i) wake up and search for TRP 906B or TRP 906C between point 952 and point 953, or (ii) wake up and search for TRP 906D or TRP 906E between point 954 and destination point 942 at 934. Fig. 9As further depicted in , device 902 may be configured to be connected to a network or server and report certain information or other motion data at one or more time instances. For example, at 936 (near point 954), device 902 may be connected to a network or server (e.g., server 904) and report certain positioning / motion information. Device 902 may also include several sensors (e.g., sensor 912), and device 902 may send sensor-related information associated with sensor 912 to server 904 or the network. In addition, device 902 may be configured with certain information at the beginning of a route or route segment (e.g., from starting point 940 to destination point 942) or during a route or route segment (by a server or network). For example, a server or network may send information (e.g., small data transmission (SDT) information) that configures device 902 based on certain route conditions (e.g., traffic conditions, road conditions, weather conditions, etc.) that may affect which route or route segment device 902 takes. Device 902 may be configured by several different servers such as a server associated with a network or a server not associated with a network. For example, the server may be a cloud server or a third-party server. In addition, the server may be an edge server or edge service associated with a software application, such as a software application running on hardware associated with a network entity (e.g., RU, DU, and / or CU). The hardware associated with the network entity may be network-agnostic hardware or network-specific hardware, as well as a mixture of different hardware that is network-agnostic hardware and / or network-specific hardware.

[0116] like Fig. 9As depicted in , device 902 may obtain density information 980 from TRP 906A (or any other TRP). Additionally, server 904 may obtain density information 980 from TRP 906B (or any other TRP). Density information 980 may be associated with a set of network entities (e.g., TRP 906A, TRP 906B, TRP 906C, TRP 906D, and TRP 906E) along a route or route segment (e.g., route segments 960, 961, 962, 963, and 964). Device 902 and / or server 904 may determine whether to switch from a first positioning technology (e.g., GNSS) to a second positioning technology (e.g., WiFi) along a route or route segment (e.g., route segments 960, 961, 962, 963, and 964) based on the density information associated with the set of network entities. The determination of whether to switch from the first positioning technology to the second positioning technology may be based on the capabilities of each network entity or the reliability of each network entity. After this determination, device 902 and / or server 904 may send a switching indication 982 (i.e., an indication of a determination of whether to switch from a first positioning technology to a second positioning technology along one or more route segments) to TRP 906A or TRP 906B (or any other TRP). In some instances, the first positioning technology may be a global navigation satellite system (GNSS) and the second positioning technology may be WiFi, WiFi received signal strength indicator (RSSI), WiFi fine time measurement (FTM), ultra-wideband (UWB), Bluetooth low energy (BLE), 5G new radio (NR), or 4G long term evolution (LTE). Fig. 9 As shown, the device 902 may also send sensor information 984 (i.e., sensor-related information associated with the sensor 912) to the server 904. In addition, the server 904 may send a route segment indication 986 associated with the switch in positioning technology to the device 902. Likewise, the device 902 may receive the route segment indication 986 from the server 904. For example, the route segment indication 986 may be an indication of a route segment associated with the switch from the first positioning technology to the second positioning technology.

[0117] In some aspects, the server may determine whether the device is located in a certain type of positioning (e.g., rural positioning, suburban positioning, or urban positioning). This positioning determination may be based on the density of network entities in the area (e.g., the density of WiFi APs or cellular / wireless BS / TRPs). The server may also determine a sleep schedule for the device and / or a communication period for the device based on an identification of the sparsity of network connectivity (e.g., rural / urban environment determination). The identification of the sparsity of network connectivity may include a fallback indication on whether to fall back to a certain connectivity (e.g., satellite-based connectivity). In addition, the server may determine or predict a fallback to a certain connectivity (e.g., satellite-based connectivity). In addition, the server may determine a sleep schedule for the device and / or a communication period for the device based on the density of network entities in the area (e.g., the density of WiFi APs or cellular / wireless BS / TRPs). For example, the server may send a positioning status indication (i.e., an indication of the positioning status of the device) to the device. After this, the server may select / determine a sleep schedule for the device or a communication period for the device based on the density information or the positioning status of the device. The server may then send an indication of a sleep schedule for the device or a communication period for the device to the device. In some examples, different sections of a route segment may correspond to different environments that may be determined based on density information. For example, a first route segment may correspond to a first environment (e.g., a rural environment or a suburban environment), a second route segment may correspond to a second environment (e.g., a dense urban environment), and a third route segment may correspond to a third environment (e.g., a rural environment or a suburban environment).

[0118] Fig.10 1000 is a diagram illustrating an example route or route segment for device 1002. In some instances, device 1002 may be traveling along a route or route segment from starting point 1040 to destination point 1042. For example, device 1002 may be traveling along one or more route segments (e.g., route segment 1060, route segment 1061, route segment 1062, route segment 1063, and route segment 1064) from starting point 1040 to destination point 1042. Device 1002 may be on a moving object (e.g., a vehicle, a car, a boat, an airplane, etc.) or may be a tracking device on a moving object. Device 1002 may carry one or more other devices including device 1002A, device 1002B, device 1002C, and device 1002D. For example, devices 1002A, 1002B, 1002C, and 1002D may be cargo, packages, or items on device 1002. Similar to Figure 7 Device 702 in Figure 8 Device 802 and Fig. 9In the device 902 of FIG. 1 , the device 1002 may be configured or pre-configured with a route or route segment associated with a particular motion mode or set of motion events (e.g., the device 1002 may be configured with a route or route segment before the device 1002 leaves the starting point 1040). Fig.10 As depicted in , the motion pattern may include a number of route segments or expected event sequences that may be determined by a server (e.g., server 1004 managing device 1002) as expected to occur when device 1002 travels from starting point 1040 to destination point 1042. Server 1004 may be a number of different servers, such as a cloud server. Fig.10 As shown, a route segment or motion pattern may include one or more events at different locations (e.g., moving in a straight line at point 1050, turning left at point 1051, turning right at point 1052, turning right at point 1053, turning left at point 1054, and moving in a straight line after point 1054). Additionally, device 1002 may be configured with information about a set of access points, base stations, or TRPs along a route or route segment. For example, device 1002 may be configured with information about TRPs 1006A, 1006B, 1006C, 1006D, and 1006E along a route or route segment. In some aspects, information about a set of access points, base stations, or TRPs along a route may be associated with several route segments (e.g., route segments 1060, 1061, 1062, 1063, and 1064) or a set of expected motion events. For example, device 1002 may be configured with information that device 1002 may (i) wake up and search for TRP 1006B or TRP 1006C between point 1052 and point 1053 at 1034 or (ii) wake up and search for TRP 1006D or TRP 1006E between point 1054 and destination point 1042. Fig.10As further depicted in , device 1002 may be configured to connect to a network or server and report certain information or other motion data at one or more time instances. For example, at 1036 near point 1054, device 1002 may connect to a network or server (e.g., server 1004) and report certain positioning / motion information. Device 1002 may also include several sensors (e.g., sensor 1012), and device 1002 may send sensor-related information associated with sensor 1012 to server 1004 or the network. In addition, device 1002 may be configured with certain information at the beginning of a route or route segment (e.g., from starting point 1040 to destination point 1042) or during a route or route segment (by a server or network). For example, a server or network may send information (e.g., small data transmission (SDT) information) to configure device 1002 based on certain route conditions (e.g., traffic conditions, road conditions, weather conditions, etc.) that may affect which route or route segment device 1002 takes. The device 1002 may be configured by several different servers, such as servers associated with a network or servers not associated with a network. For example, the server may be a cloud server or a third-party server. In addition, the server may be an edge server or edge service associated with a software application, such as a software application running on hardware associated with a network entity (e.g., RU, DU, and / or CU). The hardware associated with the network entity may be network-agnostic hardware or network-specific hardware, as well as a mixture of different hardware that is network-agnostic hardware and / or network-specific hardware.

[0119] like Fig.10, server 1004 may receive / obtain density information 1080 from network entities (e.g., TRP 1006A, TRP 1006B, TRP 1006C, TRP 1006D, and TRP 1006E). The density information may be associated with a set of network entities (e.g., TRPs) along route segments (e.g., route segments 1060, 1061, 1062, 1063, and 1064). Server 1004 may then determine a positioning state of device 1002 based on density information 1080. The positioning state of device 1002 may correspond to a certain type of positioning (e.g., rural positioning, suburban positioning, or urban positioning). Server 1004 may then send a positioning state indication 1082 (i.e., an indication of the positioning state of device 1002) to device 1002. Similarly, device 1002 may receive positioning state indication 1082 from server 1004. Thereafter, the server 1004 may select / determine a sleep schedule for the device 1002 or a communication period for the device 1002 based on the density information 1080 or the positioning state of the device 1002. The server 1004 may then send an indication 1084 of the sleep schedule for the device 1002 or the communication period for the device 1002 to the device 1002. Likewise, the device 1002 may receive the indication 1084. Fig.10 As further shown, different sections of route segments (e.g., route segments 1060, 1061, 1062, 1063, and 1064) may correspond to different environments that may be determined based on density information 1080. For example, route segment 1060 may correspond to environment 1090 (e.g., a suburban environment), route segments 1061, 1062, and 1063 may correspond to environment 1092 (e.g., an urban environment), and route segment 1064 may correspond to environment 1094 (e.g., a suburban environment).

[0120] Various aspects of the present disclosure may include multiple benefits or advantages. For example, the various aspects presented herein can improve the power consumption of devices in a navigation system or a position positioning system. That is, the various aspects presented herein can reduce the power consumption of devices by indicating a suitable or desired method for determining the location of each device. For example, the device herein can receive an indication of a suitable or desired method for determining the location of each device when the device is in a specific route segment (e.g., a road segment). Additionally, before a route or a specific route segment, the device herein can be preconfigured with a positioning technology to be utilized in certain environments (e.g., a dense urban environment or a rural environment) or certain route sections. By doing so, the device herein can utilize a reduced amount of battery / power consumption because it may not be necessary to prompt them to change QoS or positioning technology in certain scenarios.

[0121] Fig.11FIG. 1 is a communication flow diagram 1100 for wireless communication according to one or more techniques of this disclosure. Fig.11 As shown, diagram 1100 includes example communications between a device 1102 (e.g., a wireless device or UE) and a server 1104 (e.g., a cloud server, a third-party server, an edge server, a network, or a network entity) according to one or more techniques of this disclosure. In some aspects, device 1102 may be a first wireless device (e.g., a UE, a base station, a TRP, a server, or a network entity), and server 1104 may be a second wireless device (e.g., a UE, a base station, a TRP, a server, or a network entity).

[0122] At 1110 , device 1102 may obtain an indication of at least one of device information associated with the device or route information associated with one or more route segments for the device.

[0123] At 1112, device 1102 may perform a ranging process with a second device based on at least one of device information associated with the device or route information associated with one or more route segments, wherein the ranging process is associated with identification of at least one of the device or the location of the device. The device information may include a device identifier (ID) of the device, and the route information may include a configuration of one or more route segments or one or more conditions of one or more route segments. The ranging process may be based on at least one of a distance of communication between the device and the second device, a timing of communication between the device and the second device, or a signal strength of communication between the device and the second device, wherein an indication of at least one of the device information or the route information may be obtained from a server, and wherein the device may be monitored by the second device along the one or more route segments.

[0124] At 1120, the server 1104 may send a request to the second device for monitoring one or more devices along one or more route segments, wherein the request for monitoring includes at least one of device information associated with the one or more devices or route information associated with the one or more route segments. The device information may include a device identifier (ID) of each of the one or more devices, and the route information may include a configuration of the one or more route segments or one or more conditions of the one or more route segments. The request for monitoring may indicate at least one of the following: a monitoring period for monitoring the one or more devices, a periodicity for monitoring the one or more devices, a distance for monitoring the one or more devices, an accuracy level for monitoring the one or more devices, or a combination thereof.

[0125] At 1122 , the server 1104 may receive, from the second device, an indication of a monitoring status of one or more devices along the one or more route segments, wherein the indication of the monitoring status indicates that the one or more devices are being monitored by the second device.

[0126] At 1130, device 1102 can perform one or more sensor measurements along the one or more route segments. Additionally, at 1130, device 1102 can send an indication of the one or more sensor measurements (eg, indication 1134) to at least one of a server, a second device, or a network entity.

[0127] At 1132, server 1104 may receive an indication of one or more sensor measurements along one or more route segments from at least one of the one or more devices (e.g., indication 1134). Additionally, at 1132, server 1104 may receive a report of a drop event from at least one of the one or more devices (e.g., report 1144), wherein the drop event corresponds to dropping a shipment from at least one device at a drop point among a plurality of points in the one or more route segments.

[0128] At 1140, the device 1102 may wake up upon reaching a drop point among the plurality of points of the one or more route segments. Additionally, at 1140, the device 1102 may send a report of a drop event (e.g., report 1144) after reaching the drop point, wherein the drop event corresponds to dropping the cargo on the device at the drop point.

[0129] At 1150, the server 1104 may update device information based on the one or more devices, or update route information based on the one or more route segments. Additionally, at 1150, the server 1104 may send an indication of the updated device information or the updated route information (e.g., indication 1154). The updated device information may include an updated reporting schedule or an updated sleep schedule for the one or more devices, and the updated route information may include one or more triggering events along the one or more route segments for the one or more devices.

[0130] At 1152, device 1102 may receive an indication of updated device information associated with the device or updated route information associated with one or more route segments from the server (e.g., indication 1154). The updated device information may include an updated reporting schedule or an updated sleep schedule for the device, and the updated route information may include one or more triggering events for the device.

[0131] At 1160, the server 1104 may receive an indication of a lack of coverage for monitoring the one or more devices from the second device. Additionally, at 1160, the server 1104 may send a second request to at least one other second device to hand over monitoring the one or more devices.

[0132] At 1170, the device 1102 may obtain density information associated with a set of network entities along one or more route segments. Additionally, at 1170, the device 1102 may determine whether to switch from a first positioning technology to a second positioning technology along the one or more route segments based on the density information associated with the set of network entities. The first positioning technology may be a global navigation satellite system (GNSS), and the second positioning technology may be WiFi, WiFi received signal strength indicator (RSSI), WiFi fine time measurement (FTM), ultra-wideband (UWB), Bluetooth low energy (BLE), 5G new radio (NR), or 4G long term evolution (LTE). The determination of whether to switch from the first positioning technology to the second positioning technology may be based on the capabilities of each network entity in the set of network entities or the reliability of each network entity in the set of network entities.

[0133] At 1172, the server 1104 may obtain density information associated with a set of network entities along the one or more route segments. Additionally, at 1172, the server 1104 may determine whether to switch from a first positioning technology to a second positioning technology along the one or more route segments based on the density information associated with the set of network entities. The first positioning technology may be a global navigation satellite system (GNSS), and the second positioning technology may be WiFi, WiFi received signal strength indicator (RSSI), WiFi fine time measurement (FTM), ultra-wideband (UWB), Bluetooth low energy (BLE), 5G new radio (NR), or 4G long term evolution (LTE).

[0134] At 1180, the server 1104 may send an indication of a determination of whether to switch from the first positioning technology to the second positioning technology along one or more route segments (e.g., indication 1184), wherein the determination of whether to switch from the first positioning technology to the second positioning technology is based on the capabilities of the set of network entities or the reliability of the set of network entities. Additionally, at 1180, the server 1104 may identify one or more route segments for switching from the first positioning technology to the second positioning technology based on the density information. Additionally, at 1180, the server 1104 may send an indication of one or more route segments associated with the switch from the first positioning technology to the second positioning technology.

[0135] At 1182, device 1102 may send an indication of a determination of whether to switch from the first positioning technology to the second positioning technology along one or more route segments. Additionally, at 1182, device 1102 may receive an indication of one or more route segments associated with the switch from the first positioning technology to the second positioning technology (e.g., indication 1184).

[0136] At 1190, the server 1104 may obtain density information associated with a set of network entities along one or more route segments. Additionally, at 1190, the server 1104 may determine a location state of one or more devices based on the density information associated with the set of network entities, wherein the location state of the one or more devices corresponds to a rural location, a suburban location, or an urban location. Additionally, at 1190, the server 1104 may send an indication of the location state of the one or more devices to each of the one or more devices (e.g., indication 1194). Additionally, at 1190, the server 1104 may select at least one of a sleep schedule for the one or more devices or a communication period for the one or more devices based on the density information or the location state of the one or more devices. Additionally, at 1190, the server 1104 may send an indication of at least one of a sleep schedule for the one or more devices or a communication period for the one or more devices (e.g., indication 1194).

[0137] At 1192, the device 1102 may receive an indication of a positioning state of the device from the server (e.g., indication 1194), wherein the positioning state is based on density information associated with a set of network entities along one or more route segments. Additionally, at 1192, the device 1102 may receive an indication of at least one of a sleep schedule for the device or a communication period for the device (e.g., indication 1194), wherein the sleep schedule or the communication period is based on the density information or the positioning state. The positioning state of the device may correspond to a rural positioning, a suburban positioning, or an urban positioning.

[0138] Fig.12 1200 is a communication flow diagram of wireless communication according to one or more techniques of this disclosure. Fig.12 As shown, diagram 1200 includes example communications between a server 1204 (e.g., a cloud server, a third-party server, an edge server, a network, or a network entity) and a device 1206 (e.g., a wireless device, a UE, a network entity, a TRP, a base station, a LMF, etc.) according to one or more techniques of this disclosure. In some aspects, server 1204 may be a first wireless device (e.g., a UE, a base station, a TRP, a server, or a network entity), and device 1206 may be a second wireless device (e.g., a UE, a base station, a TRP, a server, or a network entity).

[0139] At 1210, server 1204 may send a request (e.g., request 1214) to a second device for monitoring one or more devices along one or more route segments, wherein the request for monitoring includes at least one of device information associated with the one or more devices or route information associated with the one or more route segments. The device information may include a device identifier (ID) for each of the one or more devices, and the route information may include a configuration of the one or more route segments or one or more conditions of the one or more route segments. The request for monitoring may indicate at least one of: a monitoring period for monitoring the one or more devices, a periodicity for monitoring the one or more devices, a distance for monitoring the one or more devices, an accuracy level for monitoring the one or more devices, or a combination thereof.

[0140] At 1212, device 1206 may receive a request (e.g., request 1214) from a server for monitoring one or more devices along one or more route segments, wherein the request for monitoring includes at least one of device information associated with the one or more devices or route information associated with the one or more route segments. The device information may include a device identifier (ID) for each of the one or more devices, and the route information may include a configuration of the one or more route segments or one or more conditions of the one or more route segments. The request for monitoring may indicate at least one of: a monitoring period for monitoring the one or more devices, a periodicity for monitoring the one or more devices, a distance for monitoring the one or more devices, an accuracy level for monitoring the one or more devices, or a combination thereof.

[0141] At 1220 , the device 1206 may perform a ranging process with the one or more devices based on at least one of the device information or the route information, wherein the ranging process is associated with identification of at least one of the one or more devices or locations of the one or more devices.

[0142] At 1222, the device 1206 may identify the one or more devices based on at least one of the device information, the route information, or a ranging process, wherein the ranging process is based on at least one of a distance of communication between the one or more devices, a timing of communication between the one or more devices, or a signal strength of communication between the one or more devices. Additionally, at 1222, the device 1206 may monitor the one or more devices along the one or more route segments based on identifying the one or more devices, wherein an indication of a monitoring status indicates that the one or more devices are being monitored by the device.

[0143] At 1230 , device 1206 can send an indication (eg, indication 1234 ) of a monitoring status of one or more devices along one or more route segments, wherein the monitoring status is based on a ranging process with the one or more devices.

[0144] At 1232, server 1204 may receive an indication of a monitoring status of one or more devices along one or more route segments (eg, indication 1234) from the second device, wherein the indication of the monitoring status indicates that the one or more devices are being monitored by the second device.

[0145] At 1240, the server 1204 may receive an indication of one or more sensor measurements along the one or more route segments from at least one of the one or more devices. Additionally, at 1240, the server 1204 may receive a report of a drop event from at least one of the one or more devices, wherein the drop event corresponds to a drop of a shipment from the at least one device at a drop point among a plurality of points in the one or more route segments.

[0146] At 1242 , device 1206 can receive, from at least one of the one or more devices, an indication of one or more sensor measurements along one or more route segments.

[0147] At 1244, device 1206 may receive a report of a drop event from at least one of the one or more devices, where the drop event corresponds to dropping a cargo from the at least one device at a drop point among a plurality of points in the one or more route segments.

[0148] At 1250, the server 1204 may update device information based on the one or more devices, or update route information based on the one or more route segments. Additionally, at 1250, the server 1204 may send an indication of the updated device information or the updated route information (e.g., indication 1254). The updated device information may include an updated reporting schedule or an updated sleep schedule for the one or more devices, and the updated route information may include one or more triggering events along the one or more route segments for the one or more devices.

[0149] At 1252, device 1206 may receive an indication of updated device information associated with one or more devices or updated route information associated with one or more route segments from the server (e.g., indication 1254). The updated device information may include an updated reporting schedule or an updated sleep schedule for the one or more devices, and the updated route information may include one or more triggering events for the one or more devices.

[0150] At 1260, device 1206 can detect a lack of coverage for monitoring one or more devices. Additionally, at 1260, device 1206 can send an indication (eg, indication 1264) of a lack of coverage for monitoring one or more devices to a server.

[0151] At 1262, the server 1204 may receive an indication of lack of coverage for monitoring one or more devices from the second device (eg, indication 1264). Additionally, at 1262, the server 1204 may send a second request to at least one other second device to hand over monitoring of the one or more devices.

[0152] At 1270, the server 1204 may obtain density information associated with the set of network entities along the one or more route segments. Additionally, at 1270, the server 1204 may determine whether to switch from a first positioning technology to a second positioning technology along the one or more route segments based on the density information associated with the set of network entities. The first positioning technology may be a global navigation satellite system (GNSS), and the second positioning technology may be WiFi, WiFi received signal strength indicator (RSSI), WiFi fine time measurement (FTM), ultra-wideband (UWB), Bluetooth low energy (BLE), 5G new radio (NR), or 4G long term evolution (LTE).

[0153] At 1280, the server 1204 may send an indication of a determination of whether to switch from the first positioning technology to the second positioning technology along the one or more route segments, wherein the determination of whether to switch from the first positioning technology to the second positioning technology is based on the capabilities of the set of network entities or the reliability of the set of network entities. Additionally, at 1280, the server 1204 may identify one or more route segments for switching from the first positioning technology to the second positioning technology based on the density information. Additionally, at 1280, the server 1204 may send an indication of one or more route segments associated with the switch from the first positioning technology to the second positioning technology.

[0154] At 1290, the server 1204 may obtain density information associated with a set of network entities along one or more route segments. Additionally, at 1290, the server 1204 may determine a location state of one or more devices based on the density information associated with the set of network entities, wherein the location state of the one or more devices corresponds to a rural location, a suburban location, or an urban location. Additionally, at 1290, the server 1204 may send an indication of the location state of the one or more devices to each of the one or more devices. Additionally, at 1290, the server 1204 may select at least one of a sleep schedule for the one or more devices or a communication period for the one or more devices based on the density information or the location state of the one or more devices. Additionally, at 1290, the server 1204 may send an indication of at least one of a sleep schedule for the one or more devices or a communication period for the one or more devices.

[0155] Fig.13 1300 is a flow chart of a method of wireless communication. The method may be performed by a device or UE (e.g., UE 104, device 702, device 802, device 902, device 1002, device 1102; apparatus 1904). The methods described herein may provide several benefits, such as improved resource utilization and / or power conservation.

[0156] At 1302, the device may obtain an indication of at least one of device information associated with the device or route information associated with one or more route segments for the device, such as information about a route segment. Figures 4 to 12 For example, Fig.11 As described in 1110 of , the device 1102 can obtain an indication of at least one of device information associated with the device or route information associated with one or more route segments for the device. In addition, step 1302 can be performed by the monitoring component 198.

[0157] At 1304, the device may perform a ranging process with a second device based on at least one of device information associated with the device or route information associated with one or more route segments, wherein the ranging process is associated with an identification of at least one of the device or the location of the device, such as with respect to Figures 4 to 12 For example, Fig.11As described in 1112 of , device 1102 may perform a ranging process with a second device based on at least one of device information associated with the device or route information associated with one or more route segments, wherein the ranging process is associated with an identification of at least one of the device or the location of the device. In addition, step 1304 may be performed by monitoring component 198. The device information may include a device identifier (ID) of the device, and the route information may include a configuration of one or more route segments or one or more conditions of one or more route segments. The ranging process may be based on at least one of a distance of communication between the device and the second device, a timing of communication between the device and the second device, or a signal strength of communication between the device and the second device, wherein an indication of at least one of the device information or the route information may be obtained from a server (e.g., a cloud server, a third-party server, an edge server, a network, or a network entity), and wherein the device may be monitored by the second device along one or more route segments.

[0158] Fig.14 1400 is a flow chart of a method of wireless communication. The method may be performed by a device or UE (e.g., UE 104, device 702, device 802, device 902, device 1002, device 1102; apparatus 1904). The methods described herein may provide several benefits, such as improved resource utilization and / or power conservation.

[0159] At 1402, the device may obtain an indication of at least one of device information associated with the device or route information associated with one or more route segments for the device, such as information about a route segment. Figures 4 to 12 For example, Fig.11 As described in 1110 of , the device 1102 can obtain an indication of at least one of device information associated with the device or route information associated with one or more route segments for the device. In addition, step 1402 can be performed by the monitoring component 198.

[0160] At 1404, the device may perform a ranging process with a second device based on at least one of device information associated with the device or route information associated with one or more route segments, wherein the ranging process is associated with an identification of at least one of the device or the location of the device, such as with respect to Figures 4 to 12 For example, Fig.11As described in 1112 of , device 1102 may perform a ranging process with a second device based on at least one of device information associated with the device or route information associated with one or more route segments, wherein the ranging process is associated with an identification of at least one of the device or the location of the device. In addition, step 1404 may be performed by monitoring component 198. The device information may include a device identifier (ID) of the device, and the route information may include a configuration of one or more route segments or one or more conditions of one or more route segments. The ranging process may be based on at least one of a distance of communication between the device and the second device, a timing of communication between the device and the second device, or a signal strength of communication between the device and the second device, wherein an indication of at least one of the device information or the route information may be obtained from a server, and wherein the device may be monitored by the second device along the one or more route segments.

[0161] At 1406, the device may perform one or more sensor measurements along one or more route segments, such as with respect to Figures 4 to 12 For example, Fig.11 As described in 1130 of , device 1102 can perform one or more sensor measurements along one or more route segments. In addition, step 1406 can be performed by monitoring component 198. In addition, at 1406, the device can send an indication of the one or more sensor measurements to at least one of a server, a second device, or a network entity, such as regarding Figures 4 to 12 For example, Fig.11 As described in 1130 of , the device 1102 can send an indication of one or more sensor measurements to at least one of a server, a second device, or a network entity. In addition, step 1406 can be performed by the monitoring component 198.

[0162] At 1408, the device may wake up upon reaching a drop point in a plurality of points in one or more route segments, such as with respect to Figures 4 to 12 For example, Fig.11 As described in 1140 of the embodiment, the device 1102 can wake up when it reaches a drop point among a plurality of points of one or more route segments. In addition, step 1408 can be performed by the monitoring component 198. In addition, at 1408, the device can send a report of a drop event after reaching the drop point, wherein the drop event corresponds to dropping the goods on the device at the drop point, such as with respect to Figures 4 to 12 For example, Fig.11 As described in step 1140 of the embodiment, the device 1102 may send a report of a delivery event after arriving at the delivery point, wherein the delivery event corresponds to the delivery of goods on the device at the delivery point. In addition, step 1408 may be performed by the monitoring component 198.

[0163] At 1410, the device may receive an indication of updated device information associated with the device or updated route information associated with one or more route segments from a server (e.g., a cloud server, a third-party server, an edge server, a network, or a network entity), such as an indication of updated device information associated with the device or updated route information associated with one or more route segments. Figures 4 to 12 For example, Fig.11 As described in 1152 of , the device 1102 can receive from the server an indication of updated device information associated with the device or updated route information associated with one or more route segments. In addition, step 1410 can be performed by the monitoring component 198. The updated device information can include an updated reporting schedule or an updated sleep schedule for the device, and the updated route information can include one or more triggering events for the device.

[0164] At 1412, the device may obtain density information associated with a set of network entities along one or more route segments, such as Figures 4 to 12 For example, Fig.11 As described in 1170 of , the device 1102 can obtain density information associated with the set of network entities along the one or more route segments. In addition, step 1412 can be performed by the monitoring component 198. In addition, at 1412, the device can determine whether to switch from the first positioning technology to the second positioning technology along the one or more route segments based on the density information associated with the set of network entities, such as with respect to Figures 4 to 12 For example, Fig.11 As described in 1170 of , the device 1102 can determine whether to switch from the first positioning technology to the second positioning technology along one or more route segments based on density information associated with the set of network entities. In addition, step 1412 can be performed by the monitoring component 198. The first positioning technology can be a global navigation satellite system (GNSS), and the second positioning technology can be WiFi, WiFi received signal strength indicator (RSSI), WiFi fine time measurement (FTM), ultra-wideband (UWB), Bluetooth low energy (BLE), 5G new radio (NR), or 4G long-term evolution (LTE). The determination of whether to switch from the first positioning technology to the second positioning technology can be based on the capabilities of each network entity in the set of network entities or the reliability of each network entity in the set of network entities.

[0165] At 1414, the device may send an indication of a determination of whether to switch from a first positioning technology to a second positioning technology along one or more route segments, such as with respect to Figures 4 to 12 For example, Fig.11As described in 1182 of the present invention, the device 1102 can send an indication of a determination of whether to switch from the first positioning technology to the second positioning technology along one or more route segments. In addition, step 1414 can be performed by the monitoring component 198. In addition, at 1414, the device can receive an indication of one or more route segments associated with the switch from the first positioning technology to the second positioning technology, such as the indication of the determination of whether to switch from the first positioning technology to the second positioning technology along the one or more route segments. Figures 4 to 12 For example, Fig.11 As described in 1182 , the device 1102 can receive an indication of one or more route segments associated with a switch from a first positioning technology to a second positioning technology. Additionally, step 1414 can be performed by the monitoring component 198 .

[0166] At 1416, the device may receive an indication of a location status of the device from the server, wherein the location status is based on density information associated with a set of network entities along one or more route segments, such as information about Figures 4 to 12 For example, Fig.11 As described in 1192 of , the device 1102 can receive from the server an indication of a location status of the device, wherein the location status is based on density information associated with a set of network entities along one or more route segments. In addition, step 1416 can be performed by the monitoring component 198. In addition, at 1416, the device can receive an indication of at least one of a sleep schedule for the device or a communication period for the device, wherein the sleep schedule or the communication period is based on the density information or the location status, such as about Figures 4 to 12 For example, Fig.11 As described in 1192 of , the device 1102 can receive an indication of at least one of a sleep schedule for the device or a communication period for the device, wherein the sleep schedule or the communication period is based on density information or a positioning state. In addition, step 1416 can be performed by the monitoring component 198. The positioning state of the device can correspond to a rural positioning, a suburban positioning, or an urban positioning.

[0167] Fig.15 1500 is a flow chart of a method of wireless communication. The method may be performed by a server (e.g., server 704, server 804, server 904, server 1004, server 1104, server 1204, cloud server, third-party server, edge server, etc.) or a base station (e.g., base station 102; network entity 2002). The methods described herein may provide several benefits, such as improved resource utilization and / or power savings.

[0168] At 1502, the server may send a request to a second device for monitoring one or more devices along one or more route segments, wherein the request for monitoring includes at least one of device information associated with the one or more devices or route information associated with the one or more route segments, such as information about Figures 4 to 12 For example, Fig.11 As described in 1120 of , the server 1104 may send a request to the second device for monitoring one or more devices along one or more route segments, wherein the request for monitoring includes at least one of device information associated with the one or more devices or route information associated with the one or more route segments. In addition, step 1502 may be performed by the monitoring component 199. The device information may include a device identifier (ID) of each device in the one or more devices, and the route information may include a configuration of the one or more route segments or one or more conditions of the one or more route segments. The request for monitoring may indicate at least one of the following: a monitoring period for monitoring one or more devices, a periodicity for monitoring one or more devices, a distance for monitoring one or more devices, an accuracy level for monitoring one or more devices, or a combination thereof.

[0169] At 1504, the server may receive from the second device an indication of a monitoring status of one or more devices along the one or more route segments, wherein the indication of the monitoring status indicates that the one or more devices are being monitored by the second device, such as with respect to Figures 4 to 12 For example, Fig.11 As described in 1122 of , the server 1104 can receive an indication of a monitoring status of one or more devices along one or more route segments from the second device, wherein the indication of the monitoring status indicates that the one or more devices are being monitored by the second device. In addition, step 1504 can be performed by the monitoring component 199.

[0170] Fig.16 1600 is a flow chart of a method of wireless communication. The method may be performed by a server (e.g., server 704, server 804, server 904, server 1004, server 1104, server 1204, cloud server, third-party server, edge server, etc.) or a base station (e.g., base station 102; network entity 2002). The methods described herein may provide several benefits, such as improved resource utilization and / or power savings.

[0171] At 1602, the server may send a request to a second device for monitoring one or more devices along one or more route segments, wherein the request for monitoring includes at least one of device information associated with the one or more devices or route information associated with the one or more route segments, such as information about Figures 4 to 12For example, Fig.11 As described in 1120 of , the server 1104 may send a request to the second device for monitoring one or more devices along one or more route segments, wherein the request for monitoring includes at least one of device information associated with the one or more devices or route information associated with the one or more route segments. In addition, step 1602 may be performed by the monitoring component 199. The device information may include a device identifier (ID) of each device in the one or more devices, and the route information may include a configuration of the one or more route segments or one or more conditions of the one or more route segments. The request for monitoring may indicate at least one of the following: a monitoring period for monitoring one or more devices, a periodicity for monitoring one or more devices, a distance for monitoring one or more devices, an accuracy level for monitoring one or more devices, or a combination thereof.

[0172] At 1604, the server may receive from the second device an indication of a monitoring status of one or more devices along the one or more route segments, wherein the indication of the monitoring status indicates that the one or more devices are being monitored by the second device, such as with respect to Figures 4 to 12 For example, Fig.11 As described in 1122 of , the server 1104 can receive from the second device an indication of a monitoring status of one or more devices along one or more route segments, wherein the indication of the monitoring status indicates that the one or more devices are being monitored by the second device. In addition, step 1604 can be performed by the monitoring component 199.

[0173] At 1606, the server may receive, from at least one of the one or more devices, an indication of one or more sensor measurements along one or more route segments, such as with respect to Figures 4 to 12 For example, Fig.11 As described in 1132 of , the server 1104 can receive an indication of one or more sensor measurements along one or more route segments from at least one of the one or more devices. In addition, step 1606 can be performed by the monitoring component 199. In addition, at 1606, the server can receive a report of a drop event from at least one of the one or more devices, wherein the drop event corresponds to dropping a shipment from at least one device at a drop point among a plurality of points in the one or more route segments, such as with respect to Figures 4 to 12 For example, Fig.11 As described in 1132 of , the server 1104 can receive a report of a delivery event from at least one of the one or more devices, wherein the delivery event corresponds to delivering goods from at least one device at a delivery point in a plurality of points of one or more route segments. In addition, step 1606 can be performed by the monitoring component 199.

[0174] At 1608, the server may update device information based on one or more devices, or update route information based on one or more route segments, such as regarding Figures 4 to 12 For example, Fig.11 As described in 1150 of , the server 1104 can update the device information based on one or more devices, or update the route information based on one or more route segments. In addition, step 1608 can be performed by the monitoring component 199. In addition, at 1608, the server can send an indication of the updated device information or the updated route information, such as the indication of the updated device information or the updated route information. Figures 4 to 12 For example, Fig.11 As described in 1150 of , the server 1104 can send an indication of the updated device information or the updated route information. In addition, step 1608 can be performed by the monitoring component 199. The updated device information may include an updated reporting schedule or an updated sleep schedule for one or more devices, and the updated route information may include one or more triggering events along one or more route segments for one or more devices.

[0175] At 1610, the server may receive from a second device an indication of a lack of coverage for monitoring one or more devices, such as regarding Figures 4 to 12 For example, Fig.11 As described in 1160 of , the server 1104 may receive an indication of a lack of coverage for monitoring one or more devices from the second device. In addition, at 1610, the server may send a second request to at least one other second device for handing over monitoring of the one or more devices, as described in 11610 of . Figures 4 to 12 For example, Fig.11 As described in step 1160 , the server 1104 may send a second request for handing over monitoring of one or more devices to at least one other second device. In addition, step 1610 may be performed by the monitoring component 199 .

[0176] At 1612, the server may obtain density information associated with a set of network entities along one or more route segments, such as Figures 4 to 12 For example, Fig.11 As described in 1172 of , the server 1104 can obtain density information associated with the set of network entities along the one or more route segments. In addition, step 1612 can be performed by the monitoring component 199. In addition, at 1612, the server can determine whether to switch from the first positioning technology to the second positioning technology along the one or more route segments based on the density information associated with the set of network entities, such as with respect to Figures 4 to 12 For example, Fig.11 As described in 1172 of , the server 1104 can determine whether to switch from the first positioning technology to the second positioning technology along one or more route segments based on density information associated with the set of network entities. In addition, step 1612 can be performed by the monitoring component 199. The first positioning technology can be a global navigation satellite system (GNSS), and the second positioning technology can be WiFi, WiFi received signal strength indicator (RSSI), WiFi fine time measurement (FTM), ultra-wideband (UWB), Bluetooth low energy (BLE), 5G new radio (NR) or 4G long-term evolution (LTE).

[0177] At 1614, the server may send an indication of a determination of whether to switch from a first positioning technology to a second positioning technology along one or more route segments, wherein the determination of whether to switch from a first positioning technology to a second positioning technology is based on capabilities of a set of network entities or reliability of a set of network entities, such as with respect to Figures 4 to 12 For example, Fig.11 As described in 1180 of , the server 1104 may send an indication of a determination of whether to switch from the first positioning technology to the second positioning technology along one or more route segments, wherein the determination of whether to switch from the first positioning technology to the second positioning technology is based on the capabilities of the set of network entities or the reliability of the set of network entities. In addition, at 1614, the server may identify one or more route segments for switching from the first positioning technology to the second positioning technology based on the density information, such as the one or more route segments for switching from the first positioning technology to the second positioning technology. Figures 4 to 12 For example, Fig.11 As described in 1180 of , the server 1104 may identify one or more route segments for switching from the first positioning technology to the second positioning technology based on the density information. In addition, at 1614, the server may send an indication of one or more route segments associated with the switch from the first positioning technology to the second positioning technology, such as the one or more route segments associated with the switch from the first positioning technology to the second positioning technology. Figures 4 to 12 For example, Fig.11 As described in 1180 , the server 1104 can send an indication of one or more route segments associated with a switch from a first positioning technology to a second positioning technology. Additionally, step 1614 can be performed by the monitoring component 199 .

[0178] At 1616, the server may obtain density information associated with a set of network entities along one or more route segments, such as Figures 4 to 12 For example, Fig.11As described in 1190 of , the server 1104 may obtain density information associated with a set of network entities along one or more route segments. Additionally, at 1616, the server may determine a location state of one or more devices based on the density information associated with the set of network entities, wherein the location state of the one or more devices corresponds to a rural location, a suburban location, or an urban location, as described with respect to Figures 4 to 12 For example, Fig.11 As described in 1190 of , the server 1104 can determine the location status of the one or more devices based on the density information associated with the set of network entities, wherein the location status of the one or more devices corresponds to rural location, suburban location, or urban location. In addition, at 1616, the server can send an indication of the location status of the one or more devices to each of the one or more devices, such as the location status of the one or more devices. Figures 4 to 12 For example, Fig.11 As described in 1190 of , the server 1104 may send an indication of the location status of the one or more devices to each of the one or more devices. In addition, at 1616, the server may select at least one of a sleep schedule for the one or more devices or a communication period for the one or more devices based on the density information or the location status of the one or more devices, as described with respect to Figures 4 to 12 For example, Fig.11 As described in 1190 of FIG. 11, the server 1104 may select at least one of a sleep schedule for one or more devices or a communication period for one or more devices based on the density information or the positioning state of the one or more devices. In addition, at 1616, the server may send an indication of at least one of a sleep schedule for one or more devices or a communication period for one or more devices, such as regarding Figures 4 to 12 For example, Fig.11 As described in 1190 of , the server 1104 can send an indication of at least one of a sleep schedule for one or more devices or a communication period for one or more devices. In addition, step 1616 can be performed by the monitoring component 199.

[0179] Fig.17 1700 is a flow chart of a method of wireless communication. The method may be performed by a device or UE (e.g., UE 104, device 702, device 802, device 902, device 1002, device 1102; apparatus 1904) or a network entity (e.g., LMF 166; TRP 706A-706E, TRP 806A-806E, TRP 906A-906E, TRP 1006A-1006E; network entity 2160). The methods described herein may provide several benefits, such as improved resource utilization and / or power savings.

[0180] At 1702, a device may receive a request from a server to monitor one or more devices along one or more route segments, wherein the request to monitor includes at least one of device information associated with the one or more devices or route information associated with the one or more route segments, such as information about Figures 4 to 12 For example, Fig.12 As described in 1212 of , device 1206 may receive a request for monitoring one or more devices along one or more route segments from a server (e.g., a cloud server, a third-party server, an edge server, etc.), wherein the request for monitoring includes at least one of device information associated with the one or more devices or route information associated with the one or more route segments. In addition, step 1702 may be performed by monitoring component 199. The device information may include a device identifier (ID) of each of the one or more devices, and the route information may include a configuration of one or more route segments or one or more conditions of one or more route segments. The request for monitoring may indicate at least one of the following: a monitoring period for monitoring one or more devices, a periodicity for monitoring one or more devices, a distance for monitoring one or more devices, an accuracy level for monitoring one or more devices, or a combination thereof.

[0181] At 1704, the device may perform a ranging process with one or more devices based on at least one of the device information or the route information, wherein the ranging process is associated with at least one of identification of the one or more devices or the location of the one or more devices, such as with respect to Figures 4 to 12 For example, Fig.12 As described in 1220 of , the device 1206 can perform a ranging process with one or more devices based on at least one of the device information or the route information, wherein the ranging process is associated with at least one of the identification of the one or more devices or the location of the one or more devices. In addition, step 1704 can be performed by the monitoring component 199.

[0182] At 1708, the device may send an indication of a monitoring status of one or more devices along one or more route segments, wherein the monitoring status is based on a ranging process with the one or more devices, such as with respect to Figures 4 to 12 For example, Fig.12 As described in 1230 , the device 1206 can send an indication of a monitoring status of one or more devices along one or more route segments, wherein the monitoring status is based on a ranging process with the one or more devices. In addition, step 1708 can be performed by the monitoring component 199 .

[0183] Fig.181800 is a flow chart of a method of wireless communication. The method may be performed by a device or UE (e.g., UE 104, device 702, device 802, device 902, device 1002, device 1102; apparatus 1904) or a network entity (e.g., LMF 166; TRP 706A-706E, TRP 806A-806E, TRP 906A-906E, TRP 1006A-1006E; network entity 2160). The methods described herein may provide several benefits, such as improved resource utilization and / or power savings.

[0184] At 1802, a device may receive a request from a server (e.g., a cloud server, a third-party server, an edge server, etc.) for monitoring one or more devices along one or more route segments, wherein the request for monitoring includes at least one of device information associated with the one or more devices or route information associated with the one or more route segments, such as information about Figures 4 to 12 For example, Fig.12 As described in 1212 of , device 1206 may receive a request from a server for monitoring one or more devices along one or more route segments, wherein the request for monitoring includes at least one of device information associated with the one or more devices or route information associated with the one or more route segments. In addition, step 1802 may be performed by monitoring component 199. The device information may include a device identifier (ID) of each of the one or more devices, and the route information may include a configuration of one or more route segments or one or more conditions of one or more route segments. The request for monitoring may indicate at least one of the following: a monitoring period for monitoring one or more devices, a periodicity for monitoring one or more devices, a distance for monitoring one or more devices, an accuracy level for monitoring one or more devices, or a combination thereof.

[0185] At 1804, the device may perform a ranging process with one or more devices based on at least one of the device information or the route information, wherein the ranging process is associated with an identification of at least one of the one or more devices or the location of the one or more devices, such as with respect to Figures 4 to 12 For example, Fig.12 As described in 1220 of , the device 1206 can perform a ranging process with one or more devices based on at least one of the device information or the route information, wherein the ranging process is associated with an identification of at least one of the one or more devices or the location of the one or more devices. In addition, step 1804 can be performed by the monitoring component 199.

[0186] At 1806, the device may identify the one or more devices based on at least one of device information, route information, or a ranging process based on at least one of a distance of communication between the one or more devices, a timing of communication between the one or more devices, or a signal strength of communication between the one or more devices, such as with respect to Figures 4 to 12 For example, Fig.12 As described in 1222 of the present invention, the device 1206 can identify the one or more devices based on at least one of device information, route information, or a ranging process, wherein the ranging process is based on at least one of a distance of communication between the one or more devices, a timing of communication between the one or more devices, or a signal strength of communication between the one or more devices. In addition, step 1806 can be performed by the monitoring component 199. In addition, at 1806, the device can monitor the one or more devices along the one or more route segments based on identifying the one or more devices, wherein the indication of the monitoring status indicates that the one or more devices are being monitored by the device, such as with respect to Figures 4 to 12 For example, Fig.12 As described in 1222 of , the device 1206 can monitor one or more devices along one or more route segments based on identifying one or more devices, wherein the indication of the monitoring status indicates that the one or more devices are being monitored by the device. In addition, step 1806 can be performed by the monitoring component 199.

[0187] At 1808, the device may send an indication of a monitoring status of one or more devices along one or more route segments, wherein the monitoring status is based on a ranging process with the one or more devices, such as with respect to Figures 4 to 12 For example, Fig.12 As described in 1230 , the device 1206 can send an indication of a monitoring status of one or more devices along one or more route segments, wherein the monitoring status is based on a ranging process with the one or more devices. In addition, step 1808 can be performed by the monitoring component 199 .

[0188] At 1810, the device may receive, from at least one of the one or more devices, an indication of one or more sensor measurements along one or more route segments, such as with respect to Figures 4 to 12 For example, Fig.12 As described in 1242 of , the device 1206 can receive an indication of one or more sensor measurements along one or more route segments from at least one of the one or more devices. In addition, step 1810 can be performed by the monitoring component 199.

[0189] At 1812, the device may receive a report of a drop event from at least one of the one or more devices, wherein the drop event corresponds to dropping a cargo from the at least one device at a drop point in a plurality of points in the one or more route segments, such as with respect to Figures 4 to 12 For example, Fig.12 As described in 1244 of , the device 1206 can receive a report of a delivery event from at least one of the one or more devices, wherein the delivery event corresponds to delivering goods from at least one device at a delivery point in a plurality of points of the one or more route segments. In addition, step 1812 can be performed by the monitoring component 199.

[0190] At 1814, the device may receive from the server an indication of updated device information associated with one or more devices or updated route information associated with one or more route segments, such as with respect to Figures 4 to 12 For example, Fig.12 As described in 1252 of , device 1206 can receive from the server an indication of updated device information associated with one or more devices or updated route information associated with one or more route segments. In addition, step 1814 can be performed by monitoring component 199. The updated device information can include an updated reporting schedule or an updated sleep schedule for one or more devices, and the updated route information can include one or more triggering events for one or more devices.

[0191] At 1816, the device may detect a lack of coverage for monitoring one or more devices, such as Figures 4 to 12 For example, Fig.12 As described in 1260 of , device 1206 can detect a lack of coverage for monitoring one or more devices. In addition, step 1816 can be performed by monitoring component 199. In addition, at 1816, the device can send an indication of a lack of coverage for monitoring one or more devices to the server, such as regarding Figures 4 to 12 For example, Fig.12 As described in 1260 of , the device 1206 can send an indication of lack of coverage for monitoring one or more devices to the server. In addition, step 1816 can be performed by the monitoring component 199.

[0192] Fig.191900 is a diagram illustrating an example of a hardware implementation for an apparatus 1904. The apparatus 1904 may be a device, a wireless device, a UE, a component of a UE, or may implement UE functionality. In some aspects, the apparatus 1904 may include a cellular baseband processor 1924 (also referred to as a modem) coupled to one or more transceivers 1922 (e.g., a cellular RF transceiver). The cellular baseband processor 1924 may include on-chip memory 1924'. In some aspects, the apparatus 1904 may also include one or more subscriber identity module (SIM) cards 1920 and an application processor 1906 coupled to a secure digital (SD) card 1908 and a screen 1910. The application processor 1906 may include on-chip memory 1906'. In some aspects, the device 1904 may also include a Bluetooth module 1912, a WLAN module 1914, an SPS module 1916 (e.g., a GNSS module), one or more sensor modules 1918 (e.g., an atmospheric pressure sensor / altimeter; a motion sensor such as an inertial management unit (IMU), a gyroscope, and / or an accelerometer; light detection and ranging (LIDAR), radio-aided detection and ranging (RADAR), sound navigation and ranging (SONAR), a magnetometer, audio for positioning, and / or other technologies), an additional memory module 1926, a power source 1930, and / or a camera 1932. The Bluetooth module 1912, the WLAN module 1914, and the SPS module 1916 may include an on-chip transceiver (TRX) (or in some cases, only a receiver (RX)). The Bluetooth module 1912, the WLAN module 1914, and the SPS module 1916 may include their own dedicated antennas and / or communicate using an antenna 1980. The cellular baseband processor 1924 communicates with the UE 104 and / or with the RU associated with the network entity 1902 through the transceiver 1922 via one or more antennas 1980. The cellular baseband processor 1924 and the application processor 1906 may each include a computer-readable medium / memory 1924', 1906', respectively. The additional memory module 1926 may also be considered as a computer-readable medium / memory. Each computer-readable medium / memory 1924', 1906', 1926 may be non-transitory. The cellular baseband processor 1924 and the application processor 1906 are each responsible for general processing, including the execution of software stored on the computer-readable medium / memory. The software, when executed by the cellular baseband processor 1924 / application processor 1906, enables the cellular baseband processor 1924 / application processor 1906 to perform the various functions described above. The computer-readable medium / memory can also be used to store data manipulated by the cellular baseband processor 1924 / application processor 1906 when executing the software.The cellular baseband processor 1924 / application processor 1906 may be a component of the UE 350 and may include the memory 360 and / or at least one of the TX processor 368, the RX processor 356, and the controller / processor 359. In one configuration, the device 1904 may be a processor chip (modem and / or application) and include only the cellular baseband processor 1924 and / or the application processor 1906, while in another configuration, the device 1904 may be the entire UE (e.g., see. Figure 3 350) and includes additional modules of device 1904.

[0193] As discussed above, the monitoring component 198 may be configured to obtain an indication of at least one of device information associated with the device or route information associated with one or more route segments for the device. The monitoring component 198 may also be configured to perform a ranging process with the second device based on at least one of the device information associated with the device or the route information associated with one or more route segments, wherein the ranging process is associated with an identification of at least one of the device or the location of the device. The monitoring component 198 may also be configured to receive an indication of updated device information associated with the device or updated route information associated with one or more route segments from the server. The monitoring component 198 may also be configured to perform one or more sensor measurements along the one or more route segments; and send an indication of the one or more sensor measurements to at least one of the server, the second device, or the network entity. The monitoring component 198 may also be configured to wake up when reaching a drop point among a plurality of points in the one or more route segments; and send a report of a drop event after reaching the drop point, wherein the drop event corresponds to dropping goods on the device at the drop point. The monitoring component 198 may also be configured to obtain density information associated with a set of network entities along one or more route segments; and determine whether to switch from a first positioning technology to a second positioning technology along the one or more route segments based on the density information associated with the set of network entities. The monitoring component 198 may also be configured to send an indication of a determination of whether to switch from a first positioning technology to a second positioning technology along the one or more route segments; and receive an indication of one or more route segments associated with a switch from the first positioning technology to the second positioning technology. The monitoring component 198 may also be configured to receive an indication of a positioning state of the device from a server, wherein the positioning state is based on the density information associated with the set of network entities along the one or more route segments; and receive an indication of at least one of a sleep schedule for the device or a communication period for the device, wherein the sleep schedule or the communication period is based on the density information or the positioning state.

[0194] The monitoring component 198 may be within the cellular baseband processor 1924, the application processor 1906, or both the cellular baseband processor 1924 and the application processor 1906. The monitoring component 198 may be one or more hardware components specifically configured to perform the stated process / algorithm, implemented by one or more processors configured to perform the stated process / algorithm, stored in a computer-readable medium for implementation by one or more processors, or some combination of the above. As shown, the device 1904 may include a variety of components configured for various functions. In one configuration, the device 1904 (and in particular the cellular baseband processor 1924 and / or the application processor 1906) includes a component for obtaining an indication of at least one of device information associated with the device or route information associated with one or more route segments for the device. The device 1904 may also include a component for performing a ranging process with a second device based on at least one of the device information associated with the device or the route information associated with one or more route segments, wherein the ranging process is associated with an identification of at least one of the device or the location of the device. The device 1904 may also include a component for receiving an indication of updated device information associated with the device or updated route information associated with one or more route segments from the server. The device 1904 may also include a component for performing one or more sensor measurements along the one or more route segments; and a component for sending an indication of the one or more sensor measurements to at least one of the server, the second device, or the network entity. The device 1904 may also include a component for waking up when reaching a drop point among a plurality of points of the one or more route segments; and a component for sending a report of a drop event after reaching the drop point, wherein the drop event corresponds to dropping goods on the device at the drop point. The device 1904 may also include a component for obtaining density information associated with a set of network entities along the one or more route segments; and a component for determining whether to switch from the first positioning technology to the second positioning technology along the one or more route segments based on the density information associated with the set of network entities. The device 1904 may also include a component for sending an indication of a determination of whether to switch from the first positioning technology to the second positioning technology along the one or more route segments; and a component for receiving an indication of one or more route segments associated with the switch from the first positioning technology to the second positioning technology. The apparatus 1904 may also include means for receiving an indication of a location status of the device from a server, wherein the location status is based on density information associated with a set of network entities along one or more route segments; and means for receiving an indication of at least one of a sleep schedule for the device or a communication period for the device, wherein the sleep schedule or the communication period is based on the density information or the location status. The means may be a monitoring component 198 of the apparatus 1904 configured to perform the functions recited by the means.As described above, the device 1904 may include the TX processor 368, the RX processor 356, and the controller / processor 359. Thus, in one configuration, the components may be the TX processor 368, the RX processor 356, and / or the controller / processor 359 configured to perform the functions recited by the components.

[0195] Fig. 20 2000 is a diagram illustrating an example of a hardware implementation for a network entity 2002. The network entity 2002 may be a server (e.g., a cloud server, a third-party server, an edge server, etc.), a BS, a component of a BS, or may implement BS functionality. The network entity 2002 may include at least one of a CU 2010, a DU 2030, or a RU 2040. For example, depending on the layer functionality handled by the monitoring component 199, the network entity 2002 may include a CU 2010; both a CU 2010 and a DU 2030; each of the CU 2010, the DU 2030, and the RU 2040; the DU 2030; both a DU 2030 and a RU 2040; or a RU 2040. The CU 2010 may include a CU processor 2012. The CU processor 2012 may include an on-chip memory 2012′. In some aspects, the CU 2010 may also include an additional memory module 2014 and a communication interface 2018. The CU 2010 communicates with the DU 2030 via a midhaul link, such as an F1 interface. The DU 2030 may include a DU processor 2032. The DU processor 2032 may include an on-chip memory 2032'. In some aspects, the DU 2030 may also include an additional memory module 2034 and a communication interface 2038. The DU 2030 communicates with the RU 2040 via a fronthaul link. The RU 2040 may include a RU processor 2042. The RU processor 2042 may include an on-chip memory 2042'. In some aspects, the RU 2040 may also include an additional memory module 2044, one or more transceivers 2046, an antenna 2080, and a communication interface 2048. The RU 2040 communicates with the UE 104. The on-chip memory 2012', 2032', 2042' and the additional memory modules 2014, 2034, 2044 can each be considered as a computer-readable medium / memory. Each computer-readable medium / memory can be non-transitory. Each of the processors 2012, 2032, 2042 is responsible for general processing, including executing software stored on the computer-readable medium / memory. The software, when executed by the corresponding processor, causes the processor to perform the various functions described above. The computer-readable medium / memory can also be used to store data manipulated by the processor when executing the software.

[0196] As discussed above, the monitoring component 199 may be configured to send a request to a second device for monitoring one or more devices along one or more route segments, wherein the request for monitoring includes at least one of device information associated with the one or more devices or route information associated with the one or more route segments. The monitoring component 199 may also be configured to receive an indication of a monitoring status of one or more devices along the one or more route segments from the second device, wherein the indication of the monitoring status indicates that the one or more devices are being monitored by the second device. The monitoring component 199 may also be configured to update device information based on one or more devices, or update route information based on one or more route segments; and send an indication of the updated device information or the updated route information. The monitoring component 199 may also be configured to receive an indication of a lack of coverage for monitoring one or more devices from a second device; and send a second request to at least one other second device for handing over monitoring of the one or more devices. The monitoring component 199 may also be configured to receive a report of a drop event from at least one of the one or more devices, wherein the drop event corresponds to the drop of cargo from at least one device at a drop point among a plurality of points of the one or more route segments; and receive an indication of one or more sensor measurements along the one or more route segments from at least one of the one or more devices. The monitoring component 199 may also be configured to obtain density information associated with a set of network entities along the one or more route segments; and determine whether to switch from a first positioning technology to a second positioning technology along the one or more route segments based on the density information associated with the set of network entities; and send an indication of the determination of whether to switch from the first positioning technology to the second positioning technology along the one or more route segments, wherein the determination of whether to switch from the first positioning technology to the second positioning technology is based on the capabilities of the set of network entities or the reliability of the set of network entities. The monitoring component 199 may also be configured to identify one or more route segments for switching from the first positioning technology to the second positioning technology based on the density information; and send an indication of the one or more route segments associated with the switch from the first positioning technology to the second positioning technology. The monitoring component 199 can also be configured to obtain density information associated with a set of network entities along one or more route segments; determine the positioning state of the one or more devices based on the density information associated with the set of network entities, wherein the positioning state of the one or more devices corresponds to rural positioning, suburban positioning, or urban positioning; send an indication of the positioning state of the one or more devices to each of the one or more devices; select at least one of a sleep schedule for the one or more devices or a communication time period for the one or more devices based on the density information or the positioning state of the one or more devices; and send an indication of at least one of the sleep schedule for the one or more devices or the communication time period for the one or more devices.

[0197] The monitoring component 199 may be within one or more processors of one or more of the CU 2010, the DU 2030, and the RU 2040. The monitoring component 199 may be one or more hardware components that are specifically configured to perform the stated process / algorithm, implemented by one or more processors configured to perform the stated process / algorithm, stored in a computer-readable medium so as to be implemented by one or more processors, or some combination of the above. The network entity 2002 may include a variety of components configured for various functions. In one configuration, the network entity 2002 may include a component for sending a request for monitoring one or more devices along one or more route segments to a second device, wherein the request for monitoring includes at least one of device information associated with the one or more devices or route information associated with the one or more route segments. The network entity 2002 may also include a component for receiving an indication of a monitoring status of one or more devices along the one or more route segments from the second device, wherein the indication of the monitoring status indicates that the one or more devices are being monitored by the second device. The network entity 2002 may also include a component for updating device information based on one or more devices, or updating route information based on one or more route segments; and a component for sending an indication of the updated device information or the updated route information. The network entity 2002 may also include a component for receiving an indication of a lack of coverage for monitoring one or more devices from a second device; and a component for sending a second request to at least one other second device for handing over monitoring of the one or more devices. The network entity 2002 may also include a component for receiving a report of a drop event from at least one of the one or more devices, wherein the drop event corresponds to dropping cargo from at least one device at a drop point among a plurality of points in one or more route segments; and a component for receiving an indication of one or more sensor measurements along one or more route segments from at least one of the one or more devices. The network entity 2002 may also include a component for obtaining density information associated with the set of network entities along one or more route segments; and a component for determining whether to switch from a first positioning technology to a second positioning technology along the one or more route segments based on the density information associated with the set of network entities; and a component for sending an indication of the determination of whether to switch from the first positioning technology to the second positioning technology along the one or more route segments, wherein the determination of whether to switch from the first positioning technology to the second positioning technology is based on the capabilities of the set of network entities or the reliability of the set of network entities. The network entity 2002 may also include a component for identifying one or more route segments for switching from the first positioning technology to the second positioning technology based on the density information; and a component for sending an indication of the one or more route segments associated with the switching from the first positioning technology to the second positioning technology.The network entity 2002 may also include a component for obtaining density information associated with a set of network entities along one or more route segments; a component for determining a location state of one or more devices based on the density information associated with the set of network entities, wherein the location state of the one or more devices corresponds to a rural location, a suburban location, or an urban location; a component for sending an indication of the location state of the one or more devices to each of the one or more devices; a component for selecting at least one of a sleep schedule for the one or more devices or a communication period for the one or more devices based on the density information or the location state of the one or more devices; and sending an indication of at least one of a sleep schedule for the one or more devices or a communication period for the one or more devices. The component may be a monitoring component 199 of the network entity 2002 configured to perform the functions recited by the component. As described above, the network entity 2002 may include a TX processor 316, an RX processor 370, and a controller / processor 375. Thus, in one configuration, the component may be a TX processor 316, an RX processor 370, and / or a controller / processor 375 configured to perform the functions recited by the component.

[0198] Fig.21 2100 is an example of a hardware implementation for a network entity 2160. In one example, the network entity 2160 may be within the core network 120. The network entity 2160 may include a network processor 2112. The network processor 2112 may include an on-chip memory 2112'. In some aspects, the network entity 2160 may also include an additional memory module 2114. The network entity 2160 communicates with the CU 2102 directly (e.g., backhaul link) or indirectly (e.g., through the RIC) via the network interface 2180. The on-chip memory 2112' and the additional memory module 2114 may each be considered as a computer-readable medium / memory. Each computer-readable medium / memory may be non-transitory. The processor 2112 is responsible for general processing, including executing software stored on a computer-readable medium / memory. The software, when executed by the corresponding processor, enables the processor to perform the various functions described above. The computer-readable medium / memory may also be used to store data manipulated by the processor when executing the software.

[0199] As discussed above, the monitoring component 199 may be configured to receive a request from a server for monitoring one or more devices along one or more route segments, wherein the request for monitoring includes at least one of device information associated with the one or more devices or route information associated with the one or more route segments. The monitoring component 199 may also be configured to perform a ranging process with the one or more devices based on at least one of the device information or the route information, wherein the ranging process is associated with an identification of at least one of the one or more devices or the location of the one or more devices. The monitoring component 199 may also be configured to send an indication of a monitoring status of one or more devices along the one or more route segments, wherein the monitoring status is based on the ranging process with the one or more devices. The monitoring component 199 may also be configured to receive an indication of updated device information associated with the one or more devices or updated route information associated with the one or more route segments from the server. The monitoring component 199 may also be configured to identify one or more devices based on at least one of device information, route information, or a ranging process, wherein the ranging process is based on at least one of a distance of communication between one or more devices, a timing of communication between one or more devices, or a signal strength of communication between one or more devices; and monitor one or more devices along one or more route segments based on identifying the one or more devices, wherein an indication of a monitoring status indicates that the one or more devices are being monitored by the device. The monitoring component 199 may also be configured to detect a lack of coverage for monitoring one or more devices; and send an indication of a lack of coverage for monitoring one or more devices to a server. The monitoring component 199 may also be configured to receive a report of a drop event from at least one of the one or more devices, wherein the drop event corresponds to a drop of goods from at least one device at a drop point among a plurality of points in the one or more route segments. The monitoring component 199 may also be configured to receive an indication of one or more sensor measurements along one or more route segments from at least one of the one or more devices.

[0200] The monitoring component 199 may be within the processor 2112. The monitoring component 199 may be one or more hardware components specifically configured to perform the stated process / algorithm, implemented by one or more processors configured to perform the stated process / algorithm, stored in a computer-readable medium for implementation by one or more processors, or some combination of the above. The network entity 2160 may include a variety of components configured for various functions. In one configuration, the network entity 2160 may include a component for receiving a request from a server for monitoring one or more devices along one or more route segments, wherein the request for monitoring includes at least one of device information associated with the one or more devices or route information associated with the one or more route segments. The network entity 2160 may also include a component for performing a ranging process with one or more devices based on at least one of the device information or the route information, wherein the ranging process is associated with an identification of at least one of the one or more devices or the location of the one or more devices. The network entity 2160 may also include a component for sending an indication of a monitoring status of one or more devices along one or more route segments, wherein the monitoring status is based on a ranging process with one or more devices. The network entity 2160 may also include a component for receiving an indication of updated device information associated with one or more devices or updated route information associated with one or more route segments from a server. The network entity 2160 may also include a component for identifying one or more devices based on at least one of device information, route information, or a ranging process, wherein the ranging process is based on at least one of the distance of communication between one or more devices, the timing of communication between one or more devices, or the signal strength of communication between one or more devices; and a component for monitoring one or more devices along one or more route segments based on identifying one or more devices, wherein the indication of the monitoring status indicates that one or more devices are being monitored by the device. The network entity 2160 may also include a component for detecting a lack of coverage for monitoring one or more devices; and a component for sending an indication of a lack of coverage for monitoring one or more devices to a server. The network entity 2160 may also include a component for receiving a report of a delivery event from at least one of the one or more devices, wherein the delivery event corresponds to the delivery of goods from at least one device at a delivery point among multiple points of one or more route segments. The network entity 2160 may also include means for receiving, from at least one of the one or more devices, an indication of one or more sensor measurements along one or more route segments.The means may be a monitoring component 199 of the network entity 2160 configured to perform the functions recited by the means.

[0201] It should be understood that the specific order or hierarchy of the blocks in the disclosed process / flowchart is only an illustration of the exemplary method. It should be understood that the specific order or hierarchy of the blocks in the process / flowchart can be rearranged based on design preferences. Further, some blocks can be combined or omitted. The attached method claims provide the elements of each block in a sample order, but are not limited to the specific order or hierarchy provided.

[0202] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein can be applied to other aspects. Therefore, the claims are not limited to the various aspects described herein, but should be given the full scope consistent with the language claims. Unless otherwise specified, reference to an element in the singular form does not mean "one and only one", but "one or more". Terms such as "if", "when" and "while" do not mean a direct temporal relationship or reaction. That is, these phrases, such as "when ......", do not mean an immediate action in response to the occurrence of an action or during the occurrence of an action, but simply imply that if the conditions are met, the action will occur, but no specific or immediate time limit for the occurrence of the action is required. The word "exemplary" is used herein to mean "used as an example, instance, or illustration". Any aspect described as "exemplary" herein is not necessarily interpreted as being preferred or having advantages over other aspects. Unless otherwise specified, the term "some" refers to one or more. Combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B and C", "one or more of A, B, and C", and "A, B, C, or any combination thereof" include any combination of A, B, and / or C, and may include multiple A, multiple B, or multiple C. Specifically, combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B, and C", "one or more of A, B, and C", and "A, B, C, or any combination thereof" may be only A, only B, only C, A and B, A and C, B and C, or A and B and C, where any such combination may contain one or more members of A, B, or C. A set should be interpreted as a set of elements, where the number of elements is one or more. Thus, for a set of X, X will include one or more elements. If the first device receives data from the second device or sends data to the second device, data can be directly received / sent between the first device and the second device, or data can be indirectly received / sent between the first device and the second device through a set of devices. All structural and functional equivalents of the elements throughout the various aspects described in this disclosure that are known or will be known later to those of ordinary skill in the art are expressly incorporated herein by reference and are covered by the claims. In addition, nothing disclosed herein is intended to be dedicated to the public, regardless of whether such disclosure is explicitly stated in the claims. Words such as "module", "mechanism", "element", "device" cannot replace the word "component". Therefore, no claim element will be understood as a component plus function unless the element is explicitly stated using the phrase "component for...".

[0203] As used herein, the phrase "based on" should not be interpreted as referring to a closed set of information, one or more conditions, one or more factors, etc. In other words, the phrase "based on A" (where "A" can be information, a condition, a factor, etc.) should be interpreted as "based at least on A" unless specifically stated differently.

[0204] The following aspects are merely illustrative and may be combined with other aspects or teachings described herein, but are not limiting.

[0205] Aspect 1 is an apparatus for performing wireless communication at a device, the apparatus comprising: a memory; and at least one processor, the at least one processor being coupled to the memory and being configured, at least in part based on information stored in the memory, to: obtain an indication of at least one of device information associated with the device or route information associated with one or more route segments for the device; and perform a ranging process with a second device based on at least one of the device information associated with the device or the route information associated with the one or more route segments, wherein the ranging process is associated with an identification of at least one of the device or the location of the device.

[0206] Aspect 2 is an apparatus according to aspect 1, wherein the at least one processor is further configured to: receive an indication of updated device information associated with the device or updated route information associated with the one or more route segments from a server.

[0207] Aspect 3 is an apparatus according to any one of Aspects 1 and 2, wherein the updated device information includes an updated reporting schedule or an updated sleep schedule for the device, and wherein the updated route information includes one or more triggering events for the device.

[0208] Aspect 4 is an apparatus according to any one of Aspects 1 to 3, wherein the device information includes a device identifier (ID) of the device, and wherein the route information includes a configuration of the one or more route segments or one or more conditions of the one or more route segments.

[0209] Aspect 5 is an apparatus according to any one of Aspects 1 to 4, wherein the at least one processor is further configured to: perform one or more sensor measurements along the one or more route segments; and send an indication of the one or more sensor measurements to at least one of a server, the second device, or a network entity.

[0210] Aspect 6 is an apparatus according to any one of Aspects 1 to 5, wherein the at least one processor is further configured to: wake up upon reaching a delivery point among multiple points of the one or more route segments; and send a report of a delivery event after reaching the delivery point, wherein the delivery event corresponds to the delivery of goods on the device at the delivery point.

[0211] Aspect 7 is an apparatus according to any one of Aspects 1 to 6, wherein the ranging process is based on at least one of the distance of communication between the device and the second device, the timing of the communication between the device and the second device, or the signal strength of the communication between the device and the second device, wherein the indication of at least one of the device information or the route information is obtained from a server, and wherein the device is monitored by the second device along the one or more route segments.

[0212] Aspect 8 is an apparatus according to any one of Aspects 1 to 7, wherein the at least one processor is further configured to: obtain density information associated with a set of network entities along the one or more route segments; and determine whether to switch from a first positioning technology to a second positioning technology along the one or more route segments based on the density information associated with the set of network entities.

[0213] Aspect 9 is an apparatus according to any one of aspects 1 to 8, wherein the at least one processor is further configured to: send an indication of the determination whether to switch from the first positioning technology to the second positioning technology along the one or more route segments.

[0214] Aspect 10 is an apparatus according to any one of Aspects 1 to 9, wherein the first positioning technology is a global navigation satellite system (GNSS), and wherein the second positioning technology is WiFi, WiFi received signal strength indicator (RSSI), WiFi fine time measurement (FTM), ultra-wideband (UWB), Bluetooth low energy (BLE), 5G new radio (NR) or 4G long term evolution (LTE).

[0215] Aspect 11 is an apparatus according to any one of Aspects 1 to 10, wherein the determination of whether to switch from the first positioning technology to the second positioning technology is based on the capability of each network entity in the set of network entities or the reliability of each network entity in the set of network entities.

[0216] Aspect 12 is an apparatus according to any one of aspects 1 to 11, wherein the at least one processor is further configured to: receive an indication of the one or more route segments associated with the switch from the first positioning technology to the second positioning technology.

[0217] Aspect 13 is an apparatus according to any one of Aspects 1 to 12, wherein the at least one processor is further configured to: receive an indication of a positioning status of the device from a server, wherein the positioning status is based on density information associated with a set of network entities along the one or more route segments.

[0218] Aspect 14 is an apparatus according to any one of aspects 1 to 13, wherein the location status of the device corresponds to a rural location, a suburban location, or an urban location.

[0219] Aspect 15 is an apparatus according to any one of Aspects 1 to 14, wherein the at least one processor is further configured to: receive an indication of at least one of a sleep schedule for the device or a communication period for the device, wherein the sleep schedule or the communication period is based on the density information or the positioning state.

[0220] Aspect 16 is an apparatus for performing device configuration at a server (e.g., a cloud server, a third-party server, an edge server, a network, or a network entity), the apparatus comprising: a memory; and at least one processor, the at least one processor being coupled to the memory and, based at least in part on information stored in the memory, the at least one processor being configured to: send a request to a second device for monitoring one or more devices along one or more route segments, wherein the request for monitoring includes at least one of device information associated with the one or more devices or route information associated with the one or more route segments; and receive from the second device an indication of a monitoring status of the one or more devices along the one or more route segments, wherein the indication of the monitoring status indicates that the one or more devices are being monitored by the second device.

[0221] Aspect 17 is an apparatus according to Aspect 16, wherein the at least one processor is further configured to: update the device information based on the one or more devices, or update the route information based on the one or more route segments; and send an indication of the updated device information or the updated route information.

[0222] Aspect 18 is an apparatus according to any one of Aspects 16 to 17, wherein the updated device information includes an updated reporting schedule or an updated sleep schedule for the one or more devices, and wherein the updated route information includes one or more trigger events along the one or more route segments for the one or more devices.

[0223] Aspect 19 is an apparatus according to any one of Aspects 16 to 18, wherein the device information includes a device identifier (ID) of each of the one or more devices, and wherein the route information includes a configuration of the one or more route segments or one or more conditions of the one or more route segments; and wherein the request for monitoring indicates at least one of the following: a monitoring period for monitoring the one or more devices, a periodicity for monitoring the one or more devices, a distance for monitoring the one or more devices, an accuracy level for monitoring the one or more devices, or a combination thereof.

[0224] Aspect 20 is an apparatus according to any one of Aspects 16 to 19, wherein the at least one processor is further configured to: receive an indication of a lack of coverage for monitoring the one or more devices from the second device; and send a second request to at least one other second device for handing over monitoring of the one or more devices.

[0225] Aspect 21 is an apparatus according to any one of Aspects 16 to 20, wherein the at least one processor is further configured to: receive a report of a delivery event from at least one of the one or more devices, wherein the delivery event corresponds to the delivery of goods from the at least one device at a delivery point among multiple points of the one or more route segments.

[0226] Aspect 22 is an apparatus according to any one of aspects 16 to 21, wherein the at least one processor is further configured to: receive an indication of one or more sensor measurements along the one or more route segments from at least one device of the one or more devices.

[0227] Aspect 23 is an apparatus according to any one of Aspects 16 to 22, wherein the at least one processor is further configured to: obtain density information associated with a set of network entities along the one or more route segments; and determine whether to switch from a first positioning technology to a second positioning technology along the one or more route segments based on the density information associated with the set of network entities.

[0228] Aspect 24 is an apparatus according to any one of Aspects 16 to 23, wherein the at least one processor is further configured to: send an indication of the determination of whether to switch from the first positioning technology to the second positioning technology along the one or more route segments, wherein the determination of whether to switch from the first positioning technology to the second positioning technology is based on the capabilities of the set of network entities or the reliability of the set of network entities.

[0229] Aspect 25 is an apparatus according to any one of Aspects 16 to 24, wherein the first positioning technology is a global navigation satellite system (GNSS), and wherein the second positioning technology is WiFi, WiFi received signal strength indicator (RSSI), WiFi fine time measurement (FTM), ultra-wideband (UWB), Bluetooth low energy (BLE), 5G new radio (NR) or 4G long term evolution (LTE).

[0230] Aspect 26 is an apparatus according to any one of Aspects 16 to 25, wherein the at least one processor is further configured to: identify the one or more route segments used for the switch from the first positioning technology to the second positioning technology based on the density information; and send an indication of the one or more route segments associated with the switch from the first positioning technology to the second positioning technology.

[0231] Aspect 27 is an apparatus according to any one of Aspects 16 to 26, wherein the at least one processor is further configured to: obtain density information associated with a set of network entities along the one or more route segments; determine the positioning status of the one or more devices based on the density information associated with the set of network entities, wherein the positioning status of the one or more devices corresponds to rural positioning, suburban positioning, or urban positioning; and send an indication of the positioning status of the one or more devices to each of the one or more devices.

[0232] Aspect 28 is an apparatus according to any one of Aspects 16 to 27, wherein the at least one processor is further configured to: select at least one of a sleep schedule for the one or more devices or a communication time period for the one or more devices based on the density information or the positioning status of the one or more devices; and send an indication of at least one of the sleep schedule for the one or more devices or the communication time period for the one or more devices.

[0233] Aspect 29 is an apparatus for wireless communication at a device or a network entity, the apparatus comprising: a memory; and at least one processor, the at least one processor being coupled to the memory and, based at least in part on information stored in the memory, the at least one processor being configured to: receive a request from a server for monitoring one or more devices along one or more route segments, wherein the request for monitoring comprises at least one of device information associated with the one or more devices or route information associated with the one or more route segments; perform a ranging process with the one or more devices based on the device information or at least one of the route information, wherein the ranging process is associated with an identification of the one or more devices or at least one of the locations of the one or more devices; and send an indication of a monitoring status of the one or more devices along the one or more route segments, wherein the monitoring status is based on the ranging process with the one or more devices.

[0234] Aspect 30 is an apparatus according to aspect 29, wherein the at least one processor is further configured to: receive an indication of updated device information associated with the one or more devices or updated route information associated with the one or more route segments from the server.

[0235] Aspect 31 is an apparatus according to any one of Aspects 29 and 30, wherein the updated device information includes an updated reporting schedule or an updated sleep schedule for the one or more devices, and wherein the updated route information includes one or more trigger events for the one or more devices.

[0236] Aspect 32 is an apparatus according to any one of Aspects 29 to 31, wherein the device information includes a device identifier (ID) of each of the one or more devices, and wherein the route information includes a configuration of the one or more route segments or one or more conditions of the one or more route segments.

[0237] Aspect 33 is an apparatus according to any one of Aspects 29 to 32, wherein the request for monitoring indicates at least one of: a monitoring period for monitoring the one or more devices, a periodicity for monitoring the one or more devices, a distance for monitoring the one or more devices, an accuracy level for monitoring the one or more devices, or a combination thereof.

[0238] Aspect 34 is an apparatus according to any one of Aspects 29 to 33, wherein the at least one processor is further configured to: identify the one or more devices based on at least one of the device information, the route information, or the ranging process, wherein the ranging process is based on at least one of the distance of communication between the one or more devices and the device, the timing of the communication between the one or more devices and the device, or the signal strength of the communication between the one or more devices and the device; and monitor the one or more devices along the one or more route segments based on identifying the one or more devices, wherein the indication of the monitoring status indicates that the one or more devices are being monitored by the device.

[0239] Aspect 35 is an apparatus according to any one of Aspects 29 to 34, wherein the at least one processor is further configured to: detect a lack of coverage for monitoring the one or more devices; and send an indication of the lack of coverage for monitoring the one or more devices to the server.

[0240] Aspect 36 is an apparatus according to any one of Aspects 29 to 35, wherein the at least one processor is further configured to: receive a report of a delivery event from at least one of the one or more devices, wherein the delivery event corresponds to the delivery of goods from the at least one device at a delivery point among multiple points of the one or more route segments.

[0241] Aspect 37 is an apparatus according to any one of aspects 29 to 36, wherein the at least one processor is further configured to: receive an indication of one or more sensor measurements along the one or more route segments from at least one device of the one or more devices.

[0242] Aspect 38 is an apparatus according to any one of aspects 1 to 37, wherein the apparatus is a wireless communication device, the apparatus further comprising at least one of an antenna or a transceiver coupled to the at least one processor.

[0243] Aspect 39 is a method for wireless communication implementing any one of aspects 1 to 38.

[0244] Aspect 40 is an apparatus for wireless communication, the apparatus comprising means for implementing any one of aspects 1 to 38.

[0245] Aspect 41 is a computer-readable medium (eg, non-transitory computer-readable medium) storing computer-executable code, which, when executed by at least one processor, causes the at least one processor to implement any one of aspects 1 to 38.

Claims

1. An apparatus for wireless communication at a device, the apparatus comprising: Memory; as well as at least one processor coupled to the memory and based at least in part on first information stored in the memory, the at least one processor configured to: obtaining an indication of at least one of device information associated with the device or route information associated with one or more route segments for the device; and A ranging process is performed with a second device based on at least one of the device information associated with the device or the route information associated with the one or more route segments, wherein the ranging process is associated with identification of at least one of the device or the location of the device.

2. The apparatus of claim 1 , wherein the at least one processor is further configured to: An indication of updated device information associated with the device or updated route information associated with the one or more route segments is received from a server.

3. The apparatus of claim 2, wherein the updated device information comprises an updated reporting schedule or an updated sleep schedule for the device, and wherein the updated route information comprises one or more triggering events for the device.

4. The apparatus of claim 1, wherein the device information comprises a device identifier (ID) of the device, and wherein the route information comprises a configuration of the one or more route segments or one or more conditions of the one or more route segments.

5. The apparatus of claim 1 , wherein the at least one processor is further configured to: performing one or more sensor measurements along the one or more route segments; and sending an indication of the one or more sensor measurements to at least one of a server, the second device, or a network entity.

6. The apparatus of claim 1, wherein the at least one processor is further configured to: waking up upon reaching a drop-off point among a plurality of points of the one or more route segments; and A report of a drop event is sent after reaching the drop point, wherein the drop event corresponds to dropping the cargo on the device at the drop point.

7. An apparatus according to claim 1, wherein the ranging process is based on at least one of a distance of communication between the device and the second device, a timing of the communication between the device and the second device, or a signal strength of the communication between the device and the second device, wherein the indication of at least one of the device information or the route information is obtained from a server, and wherein the device is monitored by the second device along the one or more route segments.

8. The apparatus of claim 1, wherein the at least one processor is further configured to: obtaining density information associated with a set of network entities along the one or more route segments; and A determination is made based on the density information associated with the set of network entities whether to switch from a first positioning technology to a second positioning technology along the one or more route segments.

9. The apparatus of claim 8, wherein the at least one processor is further configured to: An indication of the determination of whether to switch from the first positioning technology to the second positioning technology along the one or more route segments is transmitted.

10. The apparatus of claim 8, wherein the first positioning technology is a global navigation satellite system (GNSS), and wherein the second positioning technology is WiFi, WiFi received signal strength indicator (RSSI), WiFi fine time measurement (FTM), ultra-wideband (UWB), Bluetooth low energy (BLE), 5G new radio (NR), or 4G long term evolution (LTE).

11. The apparatus of claim 8, wherein the determination of whether to switch from the first positioning technology to the second positioning technology is based on a capability of each network entity in the set of network entities or a reliability of each network entity in the set of network entities.

12. The apparatus of claim 8, wherein the at least one processor is further configured to: An indication of the one or more route segments associated with the switch from the first positioning technology to the second positioning technology is received.

13. The apparatus of claim 1, wherein the at least one processor is further configured to: An indication of a location status of the device is received from a server, wherein the location status is based on density information associated with a set of network entities along the one or more route segments.

14. The apparatus of claim 13, wherein the location status of the device corresponds to a rural location, a suburban location, or an urban location.

15. The apparatus of claim 13, wherein the at least one processor is further configured to: An indication of at least one of a sleep schedule for the device or a communication period for the device is received, wherein the sleep schedule or the communication period is based on the density information or the positioning status.

16. An apparatus for performing device configuration at a server, the apparatus comprising: Memory; as well as at least one processor coupled to the memory and based at least in part on first information stored in the memory, the at least one processor configured to: sending a request to a second device to monitor one or more devices along one or more route segments, wherein the request to monitor includes at least one of device information associated with the one or more devices or route information associated with the one or more route segments; as well as An indication of a monitoring status of the one or more devices along the one or more route segments is received from the second device, wherein the indication of the monitoring status indicates that the one or more devices are being monitored by the second device.

17. The apparatus of claim 16, wherein the at least one processor is further configured to: updating the device information based on the one or more devices, or updating the route information based on the one or more route segments; and An indication of the updated device information or the updated route information is sent.

18. An apparatus according to claim 17, wherein the updated device information includes an updated reporting schedule or an updated sleep schedule for the one or more devices, and wherein the updated route information includes one or more triggering events along the one or more route segments for the one or more devices.

19. The apparatus of claim 16, wherein the device information comprises a device identifier (ID) of each of the one or more devices, and wherein the route information comprises a configuration of the one or more route segments or one or more conditions of the one or more route segments; and The request for monitoring indicates at least one of: a monitoring period for monitoring the one or more devices, a periodicity for monitoring the one or more devices, a distance for monitoring the one or more devices, an accuracy level for monitoring the one or more devices, or a combination thereof.

20. The apparatus of claim 16, wherein the at least one processor is further configured to: receiving, from the second device, an indication of a lack of coverage for monitoring the one or more devices; and A second request for handing over monitoring of the one or more devices is sent to at least one other second device.

21. The apparatus of claim 16, wherein the at least one processor is further configured to: A report of a drop event is received from at least one of the one or more devices, wherein the drop event corresponds to a drop of cargo from the at least one device at a drop point among a plurality of points in the one or more route segments.

22. The apparatus of claim 16, wherein the at least one processor is further configured to: An indication of one or more sensor measurements along the one or more route segments is received from at least one of the one or more devices.

23. The apparatus of claim 16, wherein the at least one processor is further configured to: obtaining density information associated with a set of network entities along the one or more route segments; and A determination is made based on the density information associated with the set of network entities whether to switch from a first positioning technology to a second positioning technology along the one or more route segments.

24. The apparatus of claim 23, wherein the at least one processor is further configured to: An indication of the determination of whether to switch from the first positioning technology to the second positioning technology along the one or more route segments is sent, wherein the determination of whether to switch from the first positioning technology to the second positioning technology is based on capabilities of the set of network entities or reliability of the set of network entities.

25. The apparatus of claim 23, wherein the first positioning technology is a global navigation satellite system (GNSS), and wherein the second positioning technology is WiFi, WiFi received signal strength indicator (RSSI), WiFi fine time measurement (FTM), ultra-wideband (UWB), Bluetooth low energy (BLE), 5G new radio (NR), or 4G long term evolution (LTE).

26. The apparatus of claim 23, wherein the at least one processor is further configured to: identifying the one or more route segments for the switch from the first positioning technology to the second positioning technology based on the density information; and An indication of the one or more route segments associated with the switch from the first positioning technology to the second positioning technology is sent.

27. The apparatus of claim 16, wherein the at least one processor is further configured to: obtaining density information associated with a set of network entities along the one or more route segments; determining a location status of the one or more devices based on the density information associated with the set of network entities, wherein the location status of the one or more devices corresponds to a rural location, a suburban location, or an urban location; and An indication of the positioning status of the one or more devices is sent to each of the one or more devices.

28. The apparatus of claim 27, wherein the at least one processor is further configured to: selecting at least one of a sleep schedule for the one or more devices or a communication period for the one or more devices based on the density information or the positioning status of the one or more devices; and An indication of at least one of the sleep schedule for the one or more devices or the communication period for the one or more devices is sent.

29. A method of wireless communication at a device, the method comprising: obtaining an indication of at least one of device information associated with the device or route information associated with one or more route segments for the device; as well as A ranging process is performed with a second device based on at least one of the device information associated with the device or the route information associated with the one or more route segments, wherein the ranging process is associated with identification of at least one of the device or the location of the device.

30. A method for performing device configuration at a server, the method comprising: sending a request to a second device to monitor one or more devices along one or more route segments, wherein the request to monitor includes at least one of device information associated with the one or more devices or route information associated with the one or more route segments; as well as An indication of a monitoring status of the one or more devices along the one or more route segments is received from the second device, wherein the indication of the monitoring status indicates that the one or more devices are being monitored by the second device.

Images