Automatic rest position recommendation

Abstract

Aspects presented herein may enable a server to recommend a rest / stop location (or filter out non-recommended rest / stop locations) for an occupant (e.g., a driver and his / her occupant) of a vehicle based on a location in the vehicle where a person with a similar occupant has a rest. In one aspect, a server receives first information from a user equipment (UE), the first information relating to a set of occupants in a vehicle and at least one feature for at least one occupant in the set of occupants. The server calculates a probability that the route of the vehicle includes the target location set based on the first information. The server selects at least one target location based on the first information. The server sends an indication of the selected at least one target location to the UE.

Description

[0001] Cross-references to related applications

[0002] This application claims the benefit of U.S. non-provisional patent application No. 18 / 453,631, filed on August 22, 2023, entitled “AUTOMATED BREAK LOCATION RECOMMENDATION”, the entire contents of which are expressly incorporated herein by reference. Technical Field

[0003] This disclosure relates generally to communication systems, and more specifically to wireless communication relating to navigation. Background Technology

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunications services, such as telephone, video, data, messaging, and broadcasting. 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 telecommunications standards to provide a common protocol that enables different wireless devices to communicate at the city, national, regional, and even global levels. An example telecommunications standard is 5G New Radio (NR). 5G NR is part of the Continuous Evolution of Mobile Broadband (CEM) program issued by the 3rd 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 communications (mMTC), and ultra-reliable low-latency communications (URLLC). Some aspects of 5G NR can be based on the 4G Long Term Evolution (LTE) standard. Further improvements to 5G NR technology are needed. Furthermore, these improvements can also be applied to other multiple access technologies and telecommunications standards that adopt these technologies.

[0006] In some scenarios, drivers may be instructed to take one or more rest stops during long drives. However, the appropriate rest areas may differ when different occupants are involved in the drive (e.g., with children / elderly, driving alone, and / or with pets). While some apps can provide recommended stop areas based on user requests or input (e.g., a user requests stop area recommendations via a travel / navigation app), these apps typically only provide a list of possible stops along the route / trip, which can be difficult for drivers to decide on (especially while driving). The aspects presented in this article can improve road safety for drivers and / or their passengers by providing automatic rest location recommendations. Summary of the Invention

[0007] The following is a simplified summary of one or more aspects to provide a basic understanding of these aspects. This summary is not a comprehensive overview of all conceived aspects. It neither identifies key or essential elements of all aspects nor describes 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 the more detailed descriptions that follow.

[0008] In one aspect of this disclosure, a method, computer-readable medium, and apparatus are provided. The apparatus receives first information from a user equipment (UE) relating to a set of occupants in a vehicle and at least one characteristic for at least one occupant in the set of occupants. The apparatus selects at least one target location based on the first information. The apparatus sends an indication to the UE of the selected at least one target location.

[0009] In one aspect of this disclosure, a method, computer-readable medium, and apparatus are provided. The apparatus sends first information to a server, the first information relating to a set of occupants in a vehicle and at least one characteristic of at least one occupant in the set of occupants. Based on the first information and based on second information from crowdsourcing, the apparatus receives from the server indications of at least one target location in a set of target locations.

[0010] To achieve the foregoing and related objectives, one or more aspects may include the features fully described below and specifically pointed out in the claims. The following description and drawings set forth some exemplary features of one or more aspects in detail. However, these features indicate only a few of the various ways in which the principles of the various aspects may be employed. Attached Figure Description

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

[0012] Figure 2A This is an illustration of an example of the first frame according to various aspects of this disclosure.

[0013] Figure 2B This is a diagram illustrating examples of downlink (DL) channels within a subframe according to various aspects of this disclosure.

[0014] Figure 2C This is an illustration of an example of a second frame according to various aspects of this disclosure.

[0015] Figure 2D This is a diagram illustrating examples of uplink (UL) channels within a subframe according to various aspects of this disclosure.

[0016] Figure 3 This is a diagram illustrating examples of base stations and user equipment (UEs) in an access network.

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

[0018] Figure 5 This is a diagram illustrating an example of sidelink communication between devices.

[0019] Figure 6 These are illustrations illustrating examples of navigation applications according to various aspects of this disclosure.

[0020] Figure 7 This is an illustration of an example of a server collecting information from multiple modes of transportation to provide automatic rest location recommendations, according to various aspects of this disclosure.

[0021] Figure 8 This is an example of a communication flow in which a server recommends one or more stops to a vehicle (e.g., its occupants) according to various aspects of this disclosure.

[0022] Figure 9 This is a diagram illustrating example use cases where a server provides automatic rest location recommendations according to various aspects of this disclosure.

[0023] Figure 10 This is a flowchart of a wireless communication method.

[0024] Figure 11 This is a flowchart of a wireless communication method.

[0025] Figure 12 This is a diagram illustrating an example of a hardware implementation used for an example network entity.

[0026] Figure 13 This is a flowchart of a wireless communication method.

[0027] Figure 14 This is a flowchart of a wireless communication method.

[0028] Figure 15 These are illustrations illustrating specific hardware implementations used for example devices and / or network entities. Detailed Implementation

[0029] The aspects presented in this paper can improve road safety for drivers and / or their passengers by providing automatic rest location recommendations. For example, filters can be added / implemented in in-vehicle navigation systems (e.g., on-board unit (OBU)) or devices running navigation applications (e.g., smartphones) that recommend rest locations to the driver (or filter out unrecommended rest locations) based on locations where similar occupants in the vehicle can rest. The aspects presented in this paper can provide drivers / users with a personalized navigation experience tailored to the specific needs of their vehicle's occupants by sharing the driver's thoughts and decisions. The aspects presented in this paper can also allow users to input their preferences for rest types during navigation (e.g., fastest route, most scenic route, quietest or most secluded route, dog-walking route, etc.) and provide users with / the option to stop and re-record that best suits their needs and expectations.

[0030] This paper presents various aspects of a technique for recommending rest stops along a driving route based on crowdsourced information. The proposed solution may include the following aspects: 1) Crowdsourcing various data, including: the location of the stop, the duration of the stop, the number of passengers, the number of children, pets, etc. 2) Providing rest stop recommendations based on various criteria that may match or correspond to the crowdsourced data: driving route, expected driving time, user profiles and preference options, information about passengers (e.g., the number of adults, the number of pets, the number of children, etc.), and indications of passenger behavior that may require stopping. 3) Refining / adjusting the recommendations based on user feedback and information collected during and after the recommended rest stops.

[0031] The detailed descriptions following, illustrated with reference to the accompanying drawings, describe various configurations and do not represent the only configurations in which the concepts described herein can be practiced. To provide a thorough understanding of the various concepts, the detailed descriptions 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 obscuring these concepts.

[0032] Various apparatuses and methods are presented with reference to several aspects of a telecommunications system. These apparatuses and methods are described in detail below and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively, “elements”). These elements may 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 system as a whole.

[0033] As an example, an element, any part of an element, or any combination of elements may be implemented as a "processing system" including one or more processors. When multiple processors are implemented, the multiple processors may perform functions individually or in combination. 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, system-on-a-chip (SoCs), baseband processors, field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gate logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionalities described throughout this disclosure. One or more processors in the 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 instructions, instruction sets, code, code segments, program code, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, or any combination thereof.

[0034] Therefore, 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 code on a computer-readable medium. Computer-readable media include computer storage media. Storage media may be any available medium accessible to 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 disc storage devices, magnetic disk storage devices, 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 accessible to a computer.

[0035] While aspects, implementations, and / or use cases are described herein by way of example, additional or different aspects, implementations, and / or use cases may arise in many different arrangements and scenarios. The aspects, implementations, and / or use cases described herein can be implemented across many different platform types, devices, systems, shapes, sizes, and package arrangements. For example, aspects, implementations, and / or use cases may arise via integrated chip implementations and other devices based on non-modular components (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchasing devices, medical devices, AI-enabled devices, etc.). While some examples may or may not be specific to a use case or application, the described examples may exhibit broad applicability. Aspects, implementations, and / or use cases can range from chip-level or modular components to non-modular, non-chip-level implementations, and further to aggregated, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more of the technologies described herein. In some practical settings, devices incorporating the described aspects and features 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 involve 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, chip-level components, systems, distributed arrangements, aggregated or decomposed components, end-user equipment, etc., of various sizes, shapes, and configurations.

[0036] Communication systems, such as 5G NR systems, can be deployed in various ways with a variety of components or parts. In a 5G NR system or network, network nodes, network entities, network mobility elements, radio access network (RAN) nodes, core network nodes, network elements or network equipment (such as base stations (BS)), or one or more units (or components) performing base station functions can be implemented in aggregated or decomposed architectures. For example, BSs (such as Node B (NB), evolved NB (eNB), NR BS, 5G NB, access point (AP), transmit / receive point (TRP), or cell, etc.) can be implemented as aggregated base stations (also known as standalone BS or monolithic BS) or decomposed base stations.

[0037] Aggregated base stations can be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node. Decentralized base stations can be configured to utilize a protocol stack that is physically or logically distributed across 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, the CU may be implemented within a RAN node, and one or more DUs may co-located with the CU, or alternatively, may be geographically or virtually distributed across one or more other RAN nodes. DUs may be implemented to communicate with one or more RUs. Each of the CU, DU, and RU may be implemented as a virtual unit, namely a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0038] Base station operation or network design can take into account the aggregation characteristics of base station functionality. For example, decomposed base stations can be utilized in Integrated Access Backhaul (IAB) networks, Open Radio Access Networks (O-RAN (such as network configurations initiated by the O-RAN Alliance)), or Virtualized Radio Access Networks (vRAN, also known as Cloud Radio Access Networks (C-RAN)). Decomposition can include distributing functionality across two or more units in various physical locations, as well as virtually distributing the functionality of at least one unit, which enables flexibility in network design. The various units of a decomposed base station or decomposed RAN architecture can be configured to communicate wirelessly with at least one other unit.

[0039] Figure 1 Figure 100 illustrates an example of a wireless communication system and access network. The illustrated wireless communication system includes a decomposed base station architecture. The decomposed base station architecture may include one or more CUs 110, which may communicate directly with the core network 120 via a backhaul link, or indirectly with the core network 120 via one or more decomposed 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. CUs 110 may communicate with one or more DUs 130 via a corresponding midhaul link (such as an F1 interface). DUs 130 may communicate with one or more RUs 140 via a corresponding fronthaul link. RUs 140 may communicate with a corresponding UE 104 via one or more radio frequency (RF) access links. In some implementations, a UE 104 may be served simultaneously by multiple RUs 140.

[0040] Each of the units (i.e., CU 110, DU 130, RU 140, and near-RT RIC 125, non-RT RIC 115, and SMO frame 105) may include or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via wired or wireless transmission media. Each of the units, or an associated processor or controller providing instructions to the communication interfaces of these units, may be configured to communicate with one or more other units via transmission media. For example, these units may include wired interfaces configured to receive signals or transmit signals to one or more other units via wired transmission media. Additionally, these units may include wireless interfaces that may include receivers, transmitters, or transceivers (such as RF transceivers) configured to receive signals via wireless transmission media and / or transmit signals to one or more other units.

[0041] In some aspects, the CU 110 can host one or more higher-level control functions. Such control functions may include Radio Resource Control (RRC), Packet Data Convergence Protocol (PDCP), Serving Data Adaptation Protocol (SDAP), etc. Each control function can be implemented using an interface configured to signal to other control functions hosted by the CU 110. The CU 110 can 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 implementations, the CU 110 can be logically divided into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP units can communicate bidirectionally with the CU-CP units via an interface such as an E1 interface. The CU 110 can be implemented to communicate with the DU 130 for network control and signaling, as needed.

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

[0043] Lower-layer functionality can be implemented by one or more RU 140s. In some deployments, an RU140 controlled by a DU 130 may correspond to a logical node that at least partially 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.) based on functional decomposition such as lower-layer functional decomposition, or both. In this architecture, the RU 140 can be implemented to handle over-the-air (OTA) communications with one or more UEs 104. In some specific implementations, the 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 allows the DU 130 and CU 110 to be implemented in cloud-based RAN architectures such as vRAN architectures.

[0044] SMO framework 105 can be configured to support RAN deployment and provisioning of both non-virtualized and virtualized network elements. For non-virtualized network elements, SMO framework 105 can be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via operation and maintenance interfaces such as the O1 interface. For virtualized network elements, SMO framework 105 can be configured to interact with a cloud computing platform such as 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 the 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 implementations, SMO framework 105 can communicate with hardware aspects of the 4G RAN, such as Open eNB (O-eNB) 111, via the O1 interface. Additionally, in some implementations, SMO framework 105 can communicate directly with one or more RU 140s via the O1 interface. SMO framework 105 may also include a non-RT RIC 115 configured to support the functionality of SMO framework 105.

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

[0046] In some implementations, to generate AI / ML models 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. This information can be utilized by the near-RT RIC 125 and can be received from non-network data sources or network functions 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 tune RAN behavior or performance. For example, the non-RT RIC 115 may monitor long-term trends and patterns in performance and employ AI / ML models to perform corrective actions via the SMO framework 105 (such as reconfiguration via O1) or by creating RAN management policies (such as A1 policies).

[0047] At least one of CU 110, DU 130, and RU 140 may be referred to as base station 102. Therefore, base station 102 may include one or more of CU 110, DU 130, and RU 140 (each component is indicated by a dashed line to indicate that each component may or may not be included in base station 102). Base station 102 provides UE 104 with an access point to core network 120. Base station 102 may include macro cells (high-power cellular base stations) and / or small cells (low-power cellular base stations). Small cells include femtocells, picocells, and microcells. A network that includes both small cells and macro cells may be referred to as a heterogeneous network. A heterogeneous network may also include an evolved home node B (eNB) (HeNB), which can provide service to a restricted group referred to as a closed subscriber group (CSG). The communication link between RU 140 and UE 104 may include uplink (UL) transmission (also known as reverse link) from UE 104 to RU 140 and / or downlink (DL) transmission (also known as forward link) transmission from RU 140 to UE 104. The communication link may utilize multiple-input multiple-output (MIMO) antenna techniques, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link may use one or more carriers. For each direction, the total number of carriers used for transmission can be up to [number missing]. Yx MHz ( x For each carrier allocated in carrier aggregation (of component carriers), base station 102 / UE 104 can use up to [number] carriers. Y A spectrum with a bandwidth of MHz (e.g., 5MHz, 10MHz, 15MHz, 20MHz, 100MHz, 400MHz, etc.). Carriers may be adjacent to each other or may not be adjacent to each other. Carrier allocation may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated to DL compared to UL). Component carriers may include primary component carriers and one or more secondary component carriers. The primary component carrier may be referred to as the primary cell (PCell) and the secondary component carrier may be referred to as the secondary cell (SCell).

[0048] Some UEs 104 can communicate with each other using device-to-device (D2D) communication link 158. D2D communication link 158 can use DL / UL wireless wide area network (WWAN) spectrum. D2D communication link 158 can use one or more sidelink channels, such as Physical Sidelink Broadcast Channel (PSBCH), Physical Sidelink Discovery Channel (PSDCH), Physical Sidelink Shared Channel (PSSCH), and Physical Sidelink Control Channel (PSCCH). D2D communication can be performed through various wireless D2D communication systems, such as Bluetooth. ™ (Bluetooth is a trademark of the Bluetooth Special Interest Group (SIG), and is based on the IEEE 802.11 standard for Wi-Fi.)™ (Wi-Fi is a trademark of the Wi-Fi Alliance), LTE, or NR.

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

[0050] 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 designated as frequency ranges FR1 (410MHz to 7.125GHz) and FR2 (24.25GHz to 52.6GHz). Although a portion of FR1 is greater than 6GHz, in various documents and articles, FR1 is often (interchangeably) referred to as the "sub-6GHz" band. Similar naming issues sometimes occur with FR2, which is often (interchangeably) referred to as the "millimeter wave" band in documents and articles, although this is distinct from the Extremely High Frequency (EHF) band (30GHz to 300GHz) designated as "millimeter wave" by the International Telecommunication Union (ITU).

[0051] The frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR studies have identified the operating bands used for these mid-band frequencies as the frequency range designation FR3 (7.125 GHz to 24.25 GHz). Bands falling within FR3 can inherit FR1 and / or FR2 characteristics, and thus can effectively extend the features of FR1 and / or FR2 to mid-band frequencies. Furthermore, higher frequency bands are currently being explored to extend 5G NR operation beyond 52.6 GHz. For example, three higher operating bands have been identified as the frequency range designations FR2-2 (52.6 GHz to 71 GHz), FR4 (71 GHz to 114.25 GHz), and FR5 (114.25 GHz to 300 GHz). Each of these higher frequency bands falls within the EHF band.

[0052] In view of the above, unless otherwise specifically stated, the term "below 6 GHz" as used herein can broadly refer to frequencies less than 6 GHz, within FR1, or including intermediate frequency band frequencies. Furthermore, unless otherwise specifically stated, the term "millimeter wave" as used herein can broadly refer to frequencies that can include intermediate frequency band frequencies, within FR2, FR4, FR2-2 and / or FR5, or within the EHF band.

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

[0054] Base station 102 may include and / or be referred to as gNB, Node B, eNB, access point, transceiver base station, radio base station, radio transceiver, transceiver function, basic service set (BSS), extended service set (ESS), TRP, network node, network entity, network equipment, or some other suitable terminology. Base station 102 may be implemented as an integrated access and backhaul (IAB) node, relay node, sidelink node, aggregated (monolithic) base station with baseband units (BBU) (including CU and DU) and RU, or may be implemented as a decomposed base station including one or more of CU, DU, and / or RU. A collection of base stations that may include decomposed base stations and / or aggregated base stations may be referred to as Next Generation (NG) RAN (NG-RAN).

[0055] The core network 120 may include Access and Mobility Management Function (AMF) 161, Session Management Function (SMF) 162, User Plane Function (UPF) 163, Unified Data Management (UDM) 164, one or more location servers 168, and other functional entities. AMF 161 is the 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 authentication and key agreement (AKA) credential generation, user identity processing, access authorization, and subscription management. One or more location servers 168 are exemplified as including a Gateway Mobile Location Center (GMLC) 165 and a Location Management Function (LMF) 166. However, generally, one or more location servers 168 may include one or more location / positioning servers, which may include one or more of GMLC 165, LMF 166, Position Determination Entity (PDE), Serving Mobile Location Center (SMLC), Mobile Location Center (MPC), etc. GMLC 165 and LMF 166 support UE location services. GMLC 165 provides an interface for clients / applications (e.g., emergency services) to access UE location information. LMF 166 receives measurement and auxiliary information from NG-RAN and UE 104 via AMF 161 to calculate the location of UE 104. NG-RAN may use one or more positioning methods to determine the location of UE 104. Positioning UE 104 may involve signal measurement, location estimation, and optional speed calculation based on these measurements. Signal measurement may be performed by UE 104 and / or base station 102 serving UE 104. The measured signals may be based on one or more of the following systems / signals / sensors: Satellite Positioning System (SPS) 170 (e.g., one or more of Global Navigation Satellite System (GNSS), Global Positioning System (GPS), Non-Terrestrial Network (NTN) or other position / location systems), LTE signals, Wireless Local Area Network (WLAN) signals, Bluetooth signals, Terrestrial Beacon System (TBS), sensor-based information (e.g., barometric pressure sensor, motion sensor), NR Enhanced Cell ID (NR E-CID) method, NR signals (e.g., multiple round-trip time (multiple RTT), DL departure angle (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 other systems / signals / sensors.

[0056] Examples of UE 104 include cellular phones, smartphones, Session Initiation Protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radios, GPS devices, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablet devices, smart devices, wearable devices, vehicles, electricity meters, air pumps, large or small kitchen appliances, healthcare devices, implants, sensors / actuators, displays, or any other similarly functional device. Some UEs in UE 104 may be referred to as IoT devices (e.g., parking meters, air pumps, toasters, vehicles, heart monitors, etc.). UE 104 may also be referred to as a station, mobile station, subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, mobile phone, user agent, mobile client, client, or some other suitable terminology. In some scenarios, the term UE may also be applied to one or more companion devices, such as in a device constellation arrangement. One or more of these devices may access the network together and / or individually.

[0057] Refer again Figure 1 In some aspects, UE 104 may have a vehicle sensor component 198 configured to: send first information to a server, the first information relating to a set of occupants in a vehicle and at least one feature for at least one occupant in the set of occupants; and receive from the server, based on the first information and based on second information from crowdsourcing, an indication of at least one target location in a set of target locations. In some aspects, base station 102 or one or more location servers 168 may have a location recommendation component 199 configured to: receive first information from the UE, the first information relating to a set of occupants in a vehicle and at least one feature for at least one occupant in the set of occupants; calculate, based on the first information, the probability that a route of the vehicle includes the set of target locations; select at least one target location based on the first information; and send an indication of the selected at least one target location to the UE.

[0058] Figure 2A Figure 200 illustrates an example of the first subframe within a 5G NR frame structure. Figure 2B Figure 230 illustrates an example of a DL channel within a 5G NR subframe. Figure 2C Figure 250 is an example of a second subframe within a 5G NR frame structure. Figure 2DFigure 280 illustrates an example of a UL channel within a 5G NR subframe. The 5G NR frame structure can be Frequency Division Duplex (FDD) (where subframes within a specific set of subcarriers (carrier system bandwidth) are dedicated to either DL or UL) or Time Division Duplex (TDD) (where subframes within a specific set of subcarriers (carrier system bandwidth) are dedicated to both DL and UL). Figure 2A , Figure 2C In the provided example, 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 can be configured with any of the various available slot formats 0-61. Slot formats 0 and 1 are both DL and UL, respectively. Other slot formats 2-61 include a mixture of DL, UL, and flexible symbols. The slot format is configured for the UE via the 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.

[0059] Figures 2A to 2D The frame structure is illustrated, and aspects of this disclosure are applicable to other wireless communication technologies that may have different frame structures and / or different channels. A frame (10 ms) can be divided into 10 equal-sized subframes (1 ms). Each subframe may include one or more time slots. Subframes may also include micro-time slots, 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 normal or extended. For normal CP, each time slot may include 14 symbols, and for extended CP, each time slot may include 12 symbols. Symbols on the DL may be CP Orthogonal Frequency Division Multiplexing (OFDM) (CP-OFDM) symbols. Symbols on the UL may be CP-OFDM symbols (for high-throughput scenarios) or Discrete Fourier Transform (DFT) Extended OFDM (DFT-s-OFDM) symbols (for power-constrained scenarios; limited to single-stream transmission). The number of time slots within a subframe is based on the CP and a parameter set. The parameter set defines the subcarrier spacing (SCS) (see Table 1). Symbol length / duration can be scaled with 1 / SCS.

[0060]

[0061] Table 1: Parameter Set, SCS, and CP

[0062] For a normal CP (14 symbols / slot), different parameter sets µ 0 through 4 allow 1, 2, 4, 8, and 16 slots per subframe, respectively. For an extended CP, parameter set 2 allows 4 slots per subframe. Therefore, for a normal CP and parameter set µ, there are 14 symbols / slot and 2... µ One time slot / subframe. Subcarrier spacing can be equal to ,in The parameter sets are 0 to 4. Therefore, the subcarrier spacing is 15 kHz for parameter set µ=0 and 240 kHz for parameter set µ=4. The symbol length / duration is negatively correlated with the subcarrier spacing. Figures 2A to 2D Examples of a normal frequency division multiplexing (CP) with 14 symbols per time slot and a parameter set of µ=2 with 4 time slots per subframe are provided. The time slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 μs. Within the frame set, there may be one or more distinct bandwidth portions (BWPs) of frequency division multiplexing (see [link to relevant documentation]). Figure 2B Each BWP can have a specific set of parameters and CP (normal or extended).

[0063] A resource grid can be used to represent the frame structure. Each time slot consists of a resource block (RB) extending for 12 consecutive subcarriers (also known as a physical RB (PRB)). The resource grid is divided into multiple resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

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

[0065] Figure 2BExamples of various DL channels within a subframe of a frame are illustrated. The Physical Downlink Control Channel (PDCCH) carries the DCI within one or more Control Channel Elements (CCEs) (e.g., 1, 2, 4, 8, or 16 CCEs), each CCE comprising six RE Groups (REGs), each REG comprising 12 consecutive REs in the OFDM symbol of the RB. A PDCCH within a BWP can be referred to as a Control Resource Set (CORESET). The UE is configured to monitor PDCCH candidates in the PDCCH search space (e.g., the common search space, the UE-specific search space) during PDCCH monitoring timing on the CORESET, where 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. The Primary Synchronization Signal (PSS) may be located within symbol 2 of a specific subframe of the frame. The PSS is used by the UE 104 to determine subframe / symbol timing and physical layer identification. The Secondary Synchronization Signal (SSS) may be located within symbol 4 of a specific subframe of the frame. The SSS is used by the UE to determine the Physical Layer Cell Identifier Group Number and radio frame timing. Based on the Physical Layer Identifier and the Physical Layer Cell Identifier Group Number, the UE can determine the Physical Cell Identifier (PCI). Based on the PCI, the UE can determine the location of the 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 known as an SS block (SSB)). The MIB provides the System Frame Number (SFN) and the number of Restricted Blocks (RBs) in the system bandwidth. The Physical Downlink Shared Channel (PDSCH) carries user data, broadcast system information not transmitted via the PBCH (such as System Information Blocks (SIBs)), and paging messages.

[0066] like Figure 2C As illustrated, some REs in the REs carry DM-RS (indicated as R for one particular configuration, but other DM-RS configurations are possible) for channel estimation at the base station. The UE can transmit DM-RS for the Physical Uplink Control Channel (PUCCH) and DM-RS for the Physical Uplink Shared Channel (PUSCH). The PUSCH DM-RS can be transmitted in the first or first two symbols of the PUSCH. Depending on whether a short or long PUCCH is transmitted and depending on the specific PUCCH format used, the PUCCH DM-RS can be transmitted in different configurations. The UE can transmit a Sounding Reference Signal (SRS). The SRS can be transmitted in the last symbol of a subframe. The SRS can have a comb structure, and the UE can transmit the SRS on one of the comb teeth. The SRS can be used by the base station for channel quality estimation to enable frequency-dependent scheduling of the UL.

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

[0068] Figure 3 This is a block diagram illustrating communication between base station 310 and UE 350 in the access network. In the DL, Internet Protocol (IP) packets can be provided to controller / processor 375. Controller / processor 375 implements Layer 3 and Layer 2 functionality. Layer 3 includes the Radio Resource Control (RRC) layer, and Layer 2 includes the Service Data Adaptation Protocol (SDAP) layer, Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, and Media Access Control (MAC) layer. The controller / processor 375 provides RRC layer functionality associated with broadcasting 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 the delivery of upper-layer packet data units (PDUs), error correction via ARQ, concatenation, segmentation, and reassembly of RLC service data units (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 transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction via HARQ, priority handling, and logical channel priority ordering.

[0069] 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) decoding / decoding of the transport channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. 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 decoded and modulated symbols can then be split into parallel streams. Each stream can then be mapped to OFDM subcarriers, multiplexed with a reference signal (e.g., a pilot) in the time and / or frequency domains, and subsequently combined using inverse fast Fourier transform (IFFT) to produce a physical channel carrying a stream of time-domain OFDM symbols. The OFDM stream is spatially pre-decoded to generate multiple spatial streams. Channel estimates from channel estimator 374 can be used to determine the decoding and modulation scheme, as well as for spatial processing. Channel estimates can be derived from reference signals transmitted by UE 350 and / or channel condition feedback. Each spatial stream can then be provided to different antennas 320 via a separate transmitter 318Tx. Each transmitter 318Tx can use the corresponding spatial stream to modulate a radio frequency (RF) carrier for transmission.

[0070] At UE 350, each receiver 354Rx receives signals via its corresponding antenna 352. Each receiver 354Rx recovers the information modulated onto the RF carrier and provides that information to the receive (RX) processor 356. The TX processor 368 and 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 UE 350. If multiple spatial streams are destined for UE 350, the RX processor 356 can combine them into a single OFDM symbol stream. The RX processor 356 then uses a Fast Fourier Transform (FFT) to transform the OFDM symbol stream from the time domain to the frequency domain. The frequency domain signal consists of a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, along with the reference signal, are recovered and demodulated by determining the most probable signal constellation point transmitted by base station 310. These soft decisions can be based on a channel estimate calculated by channel estimator 358. Subsequently, the soft decision is decoded and deinterleaved to recover the data and control signals originally transmitted by base station 310 on the physical channel. The data and control signals are then provided to controller / processor 359, which implements layer 3 and layer 2 functionality.

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

[0072] Similar to the functionality described in conjunction with DL transmission performed by base station 310, controller / processor 359 provides RRC layer functionality associated with system information (e.g., MIB, SIB) acquisition, RRC connectivity, and measurement reporting; PDCP layer functionality associated with header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functionality associated with upper-layer PDU delivery, error correction via 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 via HARQ, priority handling, and logical channel priority ordering.

[0073] The TX processor 368 can use the channel estimate derived from the reference signal or feedback transmitted by the channel estimator 358 from the base station 310 to select an appropriate decoding and modulation scheme and facilitate spatial processing. The spatial stream generated by the TX processor 368 can be provided to different antennas 352 via individual transmitters 354Tx. Each transmitter 354Tx can use the corresponding spatial stream to modulate an RF carrier for transmission.

[0074] UL transmission is processed at base station 310 in a manner similar to that described in conjunction with the receiver function at UE 350. Each receiver 318Rx receives signals via its corresponding antenna 320. Each receiver 318Rx recovers the information modulated onto the RF carrier and provides that information to RX processor 370.

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

[0076] At least one of the TX processor 368, RX processor 356, and controller / processor 359 can be configured to perform and Figure 1 The vehicle sensor assembly 198 integrates various aspects.

[0077] At least one of the TX processor 316, RX processor 370, and controller / processor 375 can be configured to perform and Figure 1 The recommended location component 199 combines various aspects.

[0078] Figure 4 Figure 400 illustrates an example of UE positioning based on reference signal measurements (which may also be referred to as "network-based positioning") according to various aspects of this disclosure. UE 404 can [operate at time T]. SRS_TX Send UL-SRS 412 and at time T PRS_RX Receives the DL positioning reference signal (PRS) (DL-PRS) 410. TRP 406 can be used at time T. SRS_RX Receive UL-SRS 412 and at time T PRS_TX Send DL-PRS 410. UE 404 may receive DL-PRS 410 before sending UL-SRS 412, or may send UL-SRS 412 before receiving DL-PRS 410. In both cases, the location server (e.g., location server 168) or UE 404 may base its response on ||T SRS_RX – T PRS_TX | – |T SRS_TX – T PRS_RX || to determine RTT 414. Therefore, multi-RTT positioning can utilize the UE Rx-Tx time difference measurement (i.e., |T) of downlink signals received from multiple TRPs 402, 406 and measured by UE 404. 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 (i.e., |T) of the uplink signal transmitted from UE404 at multiple TRPs 402, 406. SRS_RX – T PRS_TX|) and UL SRS-RSRP. UE 404 uses auxiliary data received from the positioning server to measure the UE Rx-Tx time difference (and / or the DL-PRS-RSRP of the received signal), and TRPs 402, 406 use auxiliary data received from the positioning server to measure the gNB Rx-Tx time difference (and / or the UL-SRS-RSRP of the received signal). These measurements can be used at the positioning server or at UE 404 to determine the RTT, which is used to estimate the location of UE 404. Other methods for determining the RTT are possible, such as, for example, using DL-TDOA and / or UL-TDOA measurements.

[0079] PRS can be defined for network-based positioning (e.g., NR positioning) to enable the UE to detect and measure more neighboring transmit and receive points (TRPs), supporting various configurations for diverse deployments (e.g., indoor, outdoor, sub-6, mmW, etc.). Beam scanning can also be configured for PRS to support PRS beam operation. The UL positioning reference signal can be based on an enhanced / adjusted probe reference signal (SRS) for positioning purposes. In some examples, the UL-PRS may be referred to as "SRS for Positioning," and new information elements (IEs) can be configured for the SRS for positioning in RRC signaling.

[0080] DL PRS-RSRP can be defined as the linear average of the power contribution (in [W]) of a resource element carrying a DL PRS reference signal configured for RSRP measurement at an antenna port within the considered measurement frequency bandwidth. In some examples, for FR1, the reference point for DL ​​PRS-RSRP can be the UE's antenna connector. For FR2, DL PRS-RSRP can be measured based on a combined signal from an antenna element corresponding to a given receiver branch. For FR1 and FR2, if the UE uses receiver diversity, the reported DL PRS-RSRP value can be no less than the corresponding DL PRS-RSRP of any individual receiver branch within the individual receiver branch. Similarly, UL SRS-RSRP can be defined as the linear average of the power contribution (in [W]) of a resource element carrying a probe reference signal (SRS). UL SRS-RSRP can be measured by a configured resource element within the considered measurement frequency bandwidth at a configured measurement time. In some examples, for FR1, the reference point for UL SRS-RSRP can be the antenna connector of a base station (e.g., gNB). For FR2, the UL SRS-RSRP can be measured based on the combined signal from the antenna element corresponding to a given receiver branch. For FR1 and FR2, if the base station uses receiver diversity, the reported UL SRS-RSRP value may not be lower than the corresponding UL SRS-RSRP of any individual receiver branch within the individual receiver branch.

[0081] PRS-Path RSRP (PRS-RSRPP) can be defined as the power of the linear average of the channel response at the i-th path delay carrying the resource element configured for measurement of the DL PRS signal, where the DL PRS-RSRPP at the first path delay is the power contribution corresponding to the first detected path in time. In some examples, the PRS path phase measurement may refer to the phase associated with the i-th path of the channel derived using the PRS resource.

[0082] DL-AoD positioning utilizes the measured DL-PRS-RSRP of downlink signals received at UE 404 from multiple TRPs 402, 406. UE 404 uses auxiliary data received from the positioning server to measure the DL-PRS-RSRP of the received signals, and the resulting measurement, along with the azimuth departure (A-AoD), zenith departure (Z-AoD), and other configuration information, is used to position UE 404 relative to adjacent TRPs 402, 406.

[0083] DL-TDOA positioning utilizes the DL Reference Signal Time Difference (RSTD) (and / or DL-PRS-RSRP) of downlink signals received at UE 404 from multiple TRPs 402, 406. UE 404 uses auxiliary data received from the positioning server to measure the DL RSTD (and / or DL-PRS-RSRP) of the received signals, and the resulting measurement, along with other configuration information, is used to position UE 404 relative to adjacent TRPs 402, 406.

[0084] UL-TDOA positioning utilizes the UL relative time of arrival (RTOA) (and / or UL-SRS-RSRP) of the uplink signal transmitted from UE 404 at multiple TRPs 402, 406. TRPs 402, 406 use auxiliary data received from the positioning server to measure the UL-RTOA (and / or UL-SRS-RSRP) of the received signal, and the resulting measurements, along with other configuration information, are used to estimate the location of UE 404.

[0085] UL-AoA positioning utilizes the azimuth angle (A-AoA) and zenith angle (Z-AoA) of the uplink signal transmitted from UE 404 at multiple TRPs 402, 406. TRPs 402, 406 use auxiliary data received from a positioning server to measure the A-AoA and Z-AoA of the received signal, and the resulting measurements, along with other configuration information, are used to estimate the position of UE 404. For the purposes of this disclosure, a positioning operation in which the UE provides measurements to a base station / positioning entity / server for calculating the UE's position can be described as "UE-assisted," "UE-assisted positioning," and / or "UE-assisted position calculation," while a positioning operation in which the UE measures and calculates its own position can be described as "UE-based," "UE-based positioning," and / or "UE-based position calculation."

[0086] Additional positioning methods can be used to estimate the location of UE 404, such as, for example, UE-side UL-AoD and / or DL-AoA. It should be noted that data / measurements from various technologies can be combined in various ways to increase accuracy, determine and / or enhance certainty, supplement / improve measurements, and / or replace / provide missing information.

[0087] It should be noted that the terms "location reference signal" and "PRS" generally refer to specific reference signals used for positioning in NR and LTE systems. However, as used herein, the terms "location reference signal" and "PRS" can 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. Furthermore, the terms "location reference signal" and "PRS" can refer to downlink or uplink positioning reference signals, unless otherwise indicated by the context. To further distinguish the types of PRS, downlink positioning reference signals may be referred to as "DL PRS," and uplink positioning reference signals (e.g., SRS, PTRS used for positioning) may be referred to as "UL-PRS." Additionally, for signals that can be transmitted in both uplink and downlink (e.g., DMRS, PTRS), these signals may be prefixed with "UL" or "DL" to distinguish direction. For example, "UL-DMRS" can be distinguished from "DL-DMRS." Furthermore, the terms “location” and “positioning” are used interchangeably throughout the specification, and the term can refer to a specific geographical location or a relative location.

[0088] Figure 5 Example 500 illustrates sidelink communication between devices. This communication can be based on and combined with Figures 2A to 2DThe time slot structures described are similar in all aspects. For example, UE 502 may transmit sidelink transmission 514 (e.g., including a control channel (e.g., PSCCH) and / or a corresponding data channel (e.g., PSSCH)), which may be received by UEs 504, 506, and 508. The control channel may include information for decoding the data channel (e.g., sidelink control information (SCI)), which includes reservation information, such as information about time and / or frequency resources reserved for data channel transmission. For example, the SCI may indicate the number of TTIs and RBs that can be occupied by data transmission. The SCI may be used by the receiving device to avoid interference by suppressing transmissions on reserved resources. UEs 502, 504, 506, and 508 are each capable of performing sidelink transmissions in addition to sidelink reception. Therefore, UEs 504, 506, and 508 are exemplified as transmitting sidelink transmissions 513, 515, 516, and 520. Sidelink transmissions 513, 514, 515, 516, and 520 can be unicast, broadcast, or multicast to nearby devices. For example, UE 504 can transmit sidelink transmissions 513 and 515 intended to be received by other UEs within range 501 of UE 504, and UE 506 can transmit sidelink transmission 516. Additionally or alternatively, RSU 507 can receive communications from and / or transmit communications to UEs 502, 504, 506, and 508, 518. One or more of UEs 502, 504, 506, 508, or RSU 507 may include, as in combination Figure 1 The vehicle sensor assembly 198 and / or location recommendation assembly 199 are described.

[0089] Sidelink communication can be based on one or more transmission modes. In one transmission mode for a first radio access technology (RAT) (which may be referred to herein as “Mode 4” of the first RAT), the wireless device can autonomously select resources for transmission. A network entity can allocate one or more sub-channels to the wireless device to transmit one or more transport blocks (TBs) using one or more channels. The wireless device can randomly reserve allocated resources for one-shot transmission. The wireless device can use a sense-based semi-persistent transmission scheme or a semi-persistent scheduling (SPS) mode to select reserved resources for transmission. For example, before selecting resources for data transmission, the wireless device can first determine whether the resources have already been reserved by another wireless device. Semi-persistent transmission allows the wireless device to utilize semi-periodic traffic arrivals by using historical interference patterns to predict future interference patterns. The wireless device can sense at least one of priority information, energy sensing information, or PSCCH decoding information to optimize resource selection. In one aspect, the wireless device can avoid selecting resources scheduled for higher-priority packet transmission for transmission. In another aspect, the wireless device can rank resources based on the amount of energy received and select the resource with the lowest energy. On the other hand, wireless devices can avoid having their control decoded or their received energy exceeding a threshold of resources.

[0090] Network entities can configure the periodicity of reserved subchannels using DCI transmitted via PDCCH. The period of semi-persistent transmission resources can be, for example, 20, 50, 100, 200, 300, 400, 500, 600, 700, 800, 900, or 1000 milliseconds (ms). This periodicity can be referred to as the Resource Reservation Period (RSVP). In an alternative implementation, the periodicity can be referred to as the Resource Reservation Interval (RRI). Network entities can limit the possible values ​​of the periodicity of transmission resources. Radio devices such as UEs can select transmission resources based on the periodicity of arriving packets. A counter can be used to trigger periodicity reselection. For example, a radio device can randomly select a counter between 5 and 15 and can reserve resources based on this counter (e.g., 10). The counter represents the resource reservation period (the number of MAC Protocol Data Units (PDUs) transmitted equals the counter value). After each transmission, or after the reservation period has elapsed, the counter can be decremented until it reaches zero. For example, with a reservation period of 100ms and a counter of 10, the counter can be decremented every 100ms until one second has elapsed, at which point the wireless device can reselect sidelink resources. In one aspect, the wireless device can reselect sidelink resources based on a reselection probability value. For example, in response to the counter decrementing to zero, the wireless device can reselect sidelink resources within x% of that time, and may not reselect sidelink resources within (1-x)% of that time, where x < 1. The wireless device can then reset the counter and repeat the process when the counter decrements to zero again. The wireless device can measure the Received Signal Strength Indicator (RSSI) measurement for each 100ms time slot, and then use this as the average of 10 RSSI measurements taken within a one-second period to calculate the RSSI of the band resources. The wireless device can select a suitable frequency band resource from the last 20% of the resources calculated in the wireless device's RSSI ranking. In some respects, the counter can be decremented after each MAC PDU is sent. The wireless device can be configured to reselect a sidelink resource after the counter expires (i.e., reaches zero) and a MAC PDU is received.

[0091] Sidelink communication in other RATs can be based on different types or modes of resource allocation mechanisms. In another resource allocation mode of the second RAT (which may be referred to herein as "Mode 1" of the second RAT), the network entity can provide centralized resource allocation. For example, the network entity can determine the resources used for sidelink communication and allocate the resources to different radio devices for sidelink transmission. In this first mode, the radio device can receive the allocation of sidelink resources from the base station. In the second resource allocation mode (which may be referred to herein as "Mode 2"), distributed resource allocation can be provided. In Mode 2, each radio device can autonomously determine the resources to be used for sidelink transmission. To coordinate the selection of sidelink resources by the various radio devices, each radio device can use sensing technology to monitor the resource reservations of other sidelink radio devices and can select resources for sidelink transmission from unreserved resources. Devices communicating based on sidelinks can determine one or more radio resources used by other devices in the time and frequency domains in order to select transmission resources that avoid conflict with other devices.

[0092] Sidelink transmission and / or resource reservation can be periodic or aperiodic, whereby the wireless device can reserve resources for transmission in the current time slot and up to two future time slots (discussed below).

[0093] Therefore, in this second mode (e.g., mode 2), each wireless device can autonomously select resources for sidelink transmissions, for example, without requiring a central entity (such as a base station) to instruct the devices on the resources to use. The first wireless device can reserve the selected resources to notify other wireless devices about the resources that the first wireless device intends to use for sidelink transmissions.

[0094] In some examples, resource selection for sidelink communication can be based on sensing mechanisms. For instance, before selecting resources for data transmission, the wireless device can determine in advance whether the resources have been reserved by other wireless devices.

[0095] For example, as part of the sensing mechanism for resource allocation mode 2 for the second RAT, the wireless device can determine (e.g., sense) whether the selected sidelink resource has been reserved by another wireless device before selecting a sidelink resource for data transmission. If the wireless device determines that the sidelink resource has not been reserved by another wireless device, the wireless device can use the selected sidelink resource to transmit data, for example, in PSSCH transmission. The wireless device can estimate or determine which radio resources (e.g., sidelink resources) may be in use and / or reserved by other wireless devices by detecting and decoding sidelink control information (SCI) transmitted by other wireless devices. The wireless device can use a sensing-based resource selection algorithm to estimate or determine which radio resources are in use and / or reserved by other wireless devices. The wireless device can receive an SCI from another wireless device, which may include reservation information based on a resource reservation field in the SCI. The wireless device can continuously monitor (e.g., sense) and decode SCIs from peer wireless devices. The SCI may include reservation information, such as indicating the time slots and RBs that a particular wireless device has selected for future transmissions. A wireless device can exclude resources used and / or reserved by other wireless devices from a candidate resource set used by the wireless device for sidelink transmission, and the wireless device can select / reserve resources for sidelink transmission from unused resources that thus form the candidate resource set. The wireless device can continuously sense SCIs with resource reservations to maintain a candidate resource set from which the wireless device can select one or more resources for sidelink transmission. Once the wireless device selects a candidate resource, it can transmit an SCI indicating its own reservation of resources for sidelink transmission. The amount of resources reserved by the wireless device (e.g., sub-channels per subframe) can depend on the size of the data to be transmitted by the wireless device. Although this example is described with respect to a wireless device receiving reservation information from another wireless device, reservation information can be received from an RSU or other devices communicating via the sidelink.

[0096] In some examples, software or applications that accept positioning-related measurements from Global Navigation Satellite System (GNSS) / Global Positioning System (GPS) chipsets and / or sensors to estimate a device's position, velocity, and / or altitude can be referred to as a Positioning Engine (PE). Furthermore, a positioning engine capable of achieving a specific high level of accuracy (e.g., centimeter / decimeter level accuracy) and / or latency can be referred to as a Precise Positioning Engine (PPE). On the other hand, navigation applications can refer to applications in user equipment (e.g., smartphones, in-vehicle navigation systems, GPS devices, etc.) that provide real-time navigation guidance. In recent years, users have become increasingly reliant on navigation applications due to the various benefits they offer. For example, navigation applications can facilitate users by enabling them to find their way to their destination and also allow users to contribute information and mark important locations, thereby generating the most accurate description of the location. In some examples, navigation applications can also provide users with expert guidance, guiding them to their destination via the best, most direct, or most time-saving route. For example, a navigation app can obtain the current traffic status and then locate the shortest and fastest route for the user to reach their destination, and also provide approximate travel time. Therefore, navigation apps can use an internet connection and a GPS / GNSS navigation system to provide turn-by-turn directions on how to reach a given destination.

[0097] Figure 6 Figure 600 illustrates examples of navigation applications according to various aspects of this disclosure. As shown at 602, a navigation application that can run on a UE such as a vehicle (e.g., a vehicle's built-in GPS / GNSS system) or a smartphone can provide a user with turn-by-turn guidance to a destination and an estimated time of arrival based on real-time information (e.g., via a display or interface). For example, the navigation application may receive / download real-time traffic information, road condition information, local traffic rules (e.g., speed limits), and / or map information / data from a server. The navigation application can then calculate a route to the destination based at least on the map information and other available information. The map information may include a map of the area in which the user is traveling, such as the area's streets, buildings, and / or terrain, or a map compatible with the navigation application and the GPS / GNSS system. In some examples, the route calculated by the navigation application may be the shortest or fastest route. For the purposes of this disclosure, the information associated with the calculated route may be referred to as navigation route information. For example, navigation route information may include the user's predicted / estimated location, speed, acceleration, direction, and / or altitude at different points in time.

[0098] For example, as shown at 604, based on map information, speed limits, and real-time road condition information, a navigation application can generate navigation route information 606 to guide user 608 to their destination. In some examples, the navigation route information 606 may include the user's location and the user's speed relative to / with respect to time, which may be represented as follows: and For example, a navigation application can estimate that at a first time point (T1), a user can reach a first point / location at a specific speed (e.g., at the intersection of 59th Street and Vista Drive at 35 mph), and at a second time point (T2), a user can reach a second point / location at a specific speed (e.g., at the intersection of 60th Street and Vista Drive at 15 mph), and so on up to the Nth time point (TN), and so on.

[0099] During long-distance driving (e.g., extended driving distances, driving beyond a predefined range, etc.), regular breaks can be important for drivers to ensure the safety of themselves and their passengers and minimize fatigue. The frequency of driver breaks may depend on several factors, such as driving conditions, personal comfort, and / or legal requirements. These breaks typically last from 15 to 30 minutes, allowing drivers to rest, stretch their legs, use the restroom, and recharge. Prolonged, uninterrupted driving can lead to driver fatigue, which can impair judgment, reaction time, and overall driving ability. Therefore, regular breaks help prevent fatigue and also provide drivers with the opportunity to remain alert and focused on the road, thus reducing the risk of accidents. However, in some scenarios, taking breaks may be difficult or challenging when drivers are driving in unfamiliar areas (during long-distance driving). For example, a driver may not realize the need for a break until late at night, and the nearest rest area may be far away. In another example, a driver may not know where to stop and / or whether the upcoming stop / rest area is suitable for certain purposes (e.g., whether there is a good place for a walk, a playground for children, and / or a grassy area for pets, etc.).

[0100] While rest stops may be necessary during long drives, the appropriate rest areas can vary depending on the number of passengers involved (e.g., children / elderly, driving alone, and / or pets). Although some apps can provide recommended stop areas based on user requests or input (e.g., a user requests stop area recommendations via a travel / navigation app), these apps typically only provide a list of possible stops along the route / trip, which can be difficult for drivers to decide on (especially while they are driving).

[0101] The aspects presented in this article can improve road safety for drivers and / or their passengers by providing automatic rest location recommendations. For example, filters can be added / implemented in in-vehicle navigation systems or devices running navigation applications (e.g., smartphones) that recommend rest locations to the driver based on locations where similar passengers in the driver's vehicle would take a break (or filter out unrecommended rest locations). The aspects presented in this article can provide drivers / users with a personalized navigation experience tailored to the specific needs of their vehicle's occupants by sharing the driver's thoughts and decisions. The aspects presented in this article can also allow users to input their preferences for rest types during navigation (e.g., fastest route, most scenic route, quietest or most secluded route, dog-walking route, etc.) and provide users with / the option to stop and re-record that best suits their needs and expectations.

[0102] Figure 7 Figure 700 illustrates an example of a server collecting information from multiple vehicles to provide automatic rest location recommendations according to various aspects of this disclosure. In one aspect of this disclosure, server 702 (e.g., location server, cloud server, cloud storage device, etc.) may be configured to perform crowdsourcing of data / information related to vehicles and their stopping locations (which may be referred to as "crowdsourced data / information" or "mass-outsourced data / information"), such as by collecting crowdsourced data / information 706 from a set of vehicles 704 that have never moved (e.g., vehicles shifted into park, vehicles that have not moved for a duration exceeding a threshold, etc.).

[0103] For the purposes of this disclosure, crowdsourcing can refer to a mechanism for collecting information (e.g., “crowdsourced data / information”) from a group of entities (e.g., UEs, vehicles, devices, etc.) typically via an online server. For example, crowdsourcing may involve obtaining data from a group of UEs / vehicles, which may submit the data to a crowdsourcing server or internet platform (e.g., social media, mobile applications, etc.). Based on the data collected from the group of UEs / vehicles, the crowdsourcing server may aggregate the data, analyze the data, and determine which sets of data may be useful or have good credibility to other devices. For example, a crowdsourcing server may collect weather conditions reported in real time by a group of UEs / vehicles within a region. Based on the weather conditions received from the group of UEs / vehicles, the crowdsourcing server may be able to determine the current weather conditions in the region, and the crowdsourcing server may share such information (e.g., the determined current weather conditions) with other UEs / vehicles (e.g., UEs / vehicles approaching or moving toward the region). In some examples, “crowdsourcing” may be used interchangeably with “mass outsourcing”.

[0104] In one example, as shown at 708, crowdsourced data / information 706 may include identifiers of occupants in the vehicle and at least one characteristic associated with at least one occupant. Occupant identifiers may refer to identifying whether the occupant in the vehicle is a human, animal, or object (e.g., luggage, bag, etc.) and / or the number of occupants in the vehicle. At least one characteristic may refer to at least one property of the occupant, such as the occupant's age (e.g., newborns / infants aged 0 to 12 months, toddlers aged 1 to 5 years, children aged 5 to 13 years, teenagers aged 13 to 18 years, adults aged 18 years and older, etc.), the occupant's gender (e.g., male, female, etc.), the occupant's species (e.g., breed of dog / cat, etc.), the occupant's type (e.g., human, animal, inanimate object, etc.), the occupant's size (e.g., small, medium, large, 30kg to 40kg, 50kg to 70kg, etc.), the occupant's posture (e.g., frequently looking out the window), the occupant's pattern (e.g., stopping once every X hours) and / or the occupant's behavior (e.g., frequently changing position, frequently massaging his / her body, showing signs of fatigue, unfastening the seat belt, etc.).

[0105] In one aspect, occupant identification and / or identification of at least one characteristic associated with at least one occupant can be performed by an in-cabin monitoring system (ICMS) associated with the vehicle. For example, the ICMS can be configured to determine the number of people in the vehicle, the number of adults in the vehicle, the number and age of children in the vehicle, the number of pets in the vehicle, their approximate size and species, etc. In some scenarios, the ICMS can also be configured to detect occupant postures, patterns, and / or behaviors (e.g., occupants noticing traffic signs or making gestures that suggest they want to stop, etc.). In some configurations, the ICMS can also be configured to monitor occupant conversations and detect whether certain defined keywords (e.g., restroom, stop, rest, etc.) have appeared in the conversation. These postures, patterns, behaviors, and / or keywords can be used by server 702 to determine whether at least one occupant is looking for a stop. For example, if 50% of the vehicles in the vehicle set 704 stop within 15 minutes of detecting the word "toilet," then server 702 can recommend to the occupants of the vehicles a stop within 15 minutes of the vehicle's travel time when the word "toilet" is detected. For the purposes of this disclosure, ICMS can refer to a technology used in vehicles (such as automobiles) for monitoring the interior of the vehicle's cabin. ICMS can improve vehicle safety by monitoring the health of both the driver and passengers. ICMS can typically employ various sensors, radars, and / or cameras (which may include infrared cameras) placed within the vehicle's cabin to monitor different aspects of the vehicle's internal environment. In some examples, ICMS can be configured (e.g., via at least one camera) to monitor the eyes of the driver and / or occupants, and ICMS can determine which direction the driver and / or occupants are looking. Thus, ICMS can determine whether the driver is focused on driving (e.g., looking directly at the road instead of looking down at a mobile phone), or whether the driver or occupant is looking for a rest area (e.g., the driver or occupant's eyes (frequently) turn towards a rest area sign whenever it is present), etc.

[0106] In another example, as shown at 710, crowdsourced data / information 706 may include vehicle status (e.g., parked, reversed, in neutral, driving, etc.) or information that may be associated with that vehicle status. For example, a vehicle may be configured to upload its crowdsourced data / information when it is parked, or when it is traveling at a speed below a speed threshold or stopped for a limited duration (e.g., traveling at 5 km / h for 10 minutes, stopped for 5 minutes, etc.). This information (e.g., vehicle status) allows server 702 to determine whether the vehicle might have stopped due to a rest / interval, or simply because of a traffic light, etc.

[0107] In another example, as shown at 712, crowdsourced data / information 706 may include the time of day (e.g., when the vehicle starts moving, when the vehicle stops, etc.) and / or the duration of each stop / stay. For example, a vehicle may be configured to include the time it starts moving, the time it stops (e.g., the time the vehicle switches to a parked state), and the duration the vehicle stays (e.g., the duration the vehicle is parked) in the crowdsourced data / information 706. This information allows server 702 to identify the likelihood / frequency that a group of occupants (or combinations of occupants) would seek a rest area if they left at a particular time, and / or whether the location where the vehicle stops is suitable for a long or short rest, etc. For example, this information may allow the server to determine that a vehicle that starts driving between 7:00 and 8:00 AM might seek a rest area between approximately 11:00 AM and 12:00 PM, a vehicle with children might stay for a longer duration in an area with a playground, a vehicle with pets might stay for a longer duration in a park, etc. In another example, a short-duration stop by a driver with a pet / child might suggest that these stops are not desirable (e.g., these stops may not be suitable for pets / children). In some implementations, the vehicle may also send an instruction to server 702 only when it arrives at or leaves an area, and the server may determine the time and duration of the vehicle's stay (e.g., based on the time the instruction is received by the server or sent by the vehicle).

[0108] In another example, as shown at 714, crowdsourced data / information 706 may include an Operational Design Domain (ODD) description of the vehicle. The ODD may describe the constraints and operating conditions upon which the autonomous driving system is designed, and the server 702 may use such information to determine / recommend stopping areas for vehicles with similar ODD descriptions.

[0109] In another example, as shown at 716, crowdsourced data / information 706 may include the location of a vehicle, such as the location where the vehicle has been stopped for a specified duration (e.g., at least 10 minutes). For example, the vehicle's onboard unit (OBU) or onboard GPS / GNSS system or a smartphone used for navigation in the vehicle may determine the vehicle's location when it detects that the vehicle has stopped (e.g., based on a GPS / GNSS system and / or as in combination). Figure 4The described web-based location information can be included in crowdsourced data / information 706. Server 702 can then recommend the location to other drivers (e.g., the location may be unpopular or unknown to navigation applications / databases). In some implementations, server 702 may also obtain additional information associated with the location from other sources. For example, by obtaining the location where the vehicle stopped (e.g., a set of coordinates, the name of the location, etc.), server 702 can obtain additional information about the location (e.g., from other sources), such as the type of location (e.g., gas station, rest area, shopping mall, picnic area, etc.), weather conditions at the location, opening hours of the location (if any), and / or rules and conditions applied to the location (e.g., adults only, maximum number of occupants, road closures every Sunday). This allows server 702 to recommend more suitable stopping areas for the occupant group.

[0110] In another example, as shown at 718, the crowdsourced data / information 706 may include surrounding information related to the location where the vehicle is parked, where such surrounding information may be based on sensor data obtained by the vehicle, such as images captured by the vehicle's cameras. Sensor data may include any data obtained using at least one sensor of the vehicle. For example, when the vehicle is parked in an area, the vehicle may use one or more external cameras of the vehicle to capture images of its surrounding environment (e.g., the surrounding environment of the area). The vehicle may then include the captured images in its crowdsourced data / information 706. Based on this information, the server 702 may be able to identify specific details about the area, such as whether the area includes grass or paved roads, the number of visitors (e.g., based on the number of parked cars and people captured in the images), hazards associated with the area (e.g., near / below a cliff), etc. This information may also enable the server 702 to identify / mark routes or areas, such as determining whether a route is a scenic route, a remote route, etc. In another example, sensor data may include weather conditions detected using weather / environment sensors or cameras, and / or the duration of occupants leaving and returning to the vehicle detected by cameras. This information allows server 702 to determine whether a location is suitable for a long / short rest for a specified set of occupants and / or whether it is suitable for certain weather conditions (e.g., rainy days, snowy days, etc.). For example, based on sensor data collected from the set of vehicles 704, server 702 may determine that location Y is suitable for children on rainy days because on rainy days, vehicles carrying at least one child typically remain at location Y for at least 20 minutes before moving again (e.g., the duration of children leaving and returning to the vehicle is detected to be at least 20 minutes).

[0111] In another example, as shown at 720, crowdsourced data / information 706 may include navigation information associated with vehicles, such as the vehicle's origin, destination (e.g., input by the user), and / or routes planned by a navigation system. Server 702 may use the route / navigation information collected from the vehicle set 704 to learn the stopping areas of people traveling from location A to location B (e.g., with different passenger combinations), people heading to location B, and / or people taking specific routes (e.g., specific highways / expressways, scenic routes, etc.).

[0112] Based on the crowdsourced data / information 706 collected from the vehicle set 704, server 702 can aggregate and analyze the data, and create a set of mappings that map different target locations (e.g., recommended stops / rest areas) to different occupant combinations, different locations, different times of day, etc., within the vehicles. Server 702 can then use the aggregated and analyzed data to provide stop / rest area recommendations to drivers / vehicles with similar setups (discussed in detail below). It should be noted that vehicles can send the crowdsourced data / information 706 to server 702 periodically or non-periodically via a single message or multi-level messages. For example, a vehicle can be configured to periodically send its location (e.g., as described in conjunction 716) and time of day (e.g., as described in conjunction 712), and send occupant information (e.g., as described in conjunction 708) only at the start of a trip (e.g., when the destination is entered into the navigation system, when the vehicle's engine is started / ignited, etc.).

[0113] Figure 8 This is an example of a communication flow 800 illustrating a server recommending one or more stops for a vehicle (e.g., its occupants) according to various aspects of this disclosure. The numbers associated with communication flow 800 do not specify a particular time order and are used only as references to communication flow 800. The aspects presented herein enable a server (e.g., server 702) to recommend one or more stops (which may be referred to as target locations for the purposes of this disclosure) for a vehicle, at least based on information associated with the occupants of the vehicle. For the purposes of this disclosure, a stop may be broadly defined as a location where a vehicle may remain for at least a short period of time. For example, a stop may be a rest area beside a highway, a national park, a place with public restrooms, a park with a playground, etc.

[0114] At 820, UE 804 (e.g., an in-vehicle navigation system, an on-board unit (OBU), a smartphone running a navigation application, etc.) can be configured to detect / identify information 806 related to one or more occupants 808 (e.g., a driver, one or more passengers, one or more animals, one or more objects, etc.) in vehicle 810, such as the number of occupants in vehicle 810, and at least one characteristic associated with at least one of the one or more occupants 808. (As in combination) Figure 7 As described in 708, at least one characteristic may include the occupant's age, occupant's sex, occupant's species, occupant's type, occupant's size, occupant's posture, occupant's pattern, and / or occupant's behavior, etc.

[0115] In some examples, UE 804 may use an ICMS or at least one sensor (e.g., a camera) to detect or identify information 806 related to one or more occupants 808 in vehicle 810. For example, as shown at 822, the ICMS or camera in vehicle 810 may detect that there are four occupants in vehicle 810, including two adult women, an infant (e.g., three to twelve months old), and a dog weighing approximately 12 pounds. Furthermore, the ICMS / sensor may also be configured to detect occupant postures, patterns, drowsiness, and / or behaviors, such as whether the occupants are exhibiting signs of fatigue, for example, the first adult woman frequently unfastening / adjusting her seatbelt, the second adult woman searching for a stop area, the first adult woman massaging her neck / legs, the infant crying, and / or the two adult women speaking certain keywords (e.g., rest, urinate, tired, etc.).

[0116] At 824, UE 804 may send detected information 806 (e.g., information related to occupant 808) to server 702. In some examples, information 806 may also include additional information that may not be related to one or more occupants 808, but allows server 702 to make more accurate / appropriate recommendations for the stopping point. For example, additional information may include the speed of the vehicle (e.g., for server 702 to determine whether vehicle 810 is on a highway and / or the distance that vehicle 810 can travel within a limited time period), the travel time of vehicle 810 (e.g., for server 702 to estimate when to recommend a stop), the input destination and / or the estimated route of the vehicle (e.g., for server 702 to select a stop along the route to the destination), the previous stopping position of the vehicle (e.g., for server 702 to determine the time and location of the next stopping position), the current location of vehicle 810, feedback or recommendations from passengers (e.g., for server 702 to learn passenger preference options), the ODD description / ICMS specification of vehicle 810 and / or the vehicle status of vehicle 810, etc.

[0117] At point 826, based on information 806 provided by UE 804, server 702 can calculate / determine whether any one of one or more occupants 808 is scheduled to rest within a specified timeframe (e.g., during the next 30 minutes, one hour, etc.) or before reaching the destination (e.g., before reaching city D). For example, if server 702 has route planning information from UE 804 (e.g., a route from city S to city D recommended by UE 804), server 702 can determine whether to recommend at least one stop near or along the planned route of vehicle 810 based on the vehicle 810's previous stops (or start time), the vehicle 810's current location, and / or the vehicle 810's travel time. For illustration, server 702 can recommend a stop if vehicle 810 has been on the road for more than two hours and the destination is still three hours away, or if a baby in vehicle 810 has been crying for 20 minutes, etc. On the other hand, if server 702 determines that vehicle 810 will arrive at its destination within a limited time period (e.g., within ten minutes, twenty minutes, etc.), server 702 can be configured not to recommend any stopping point (even if information 806 implies that a stopping point is specified).

[0118] In some examples, the calculation / determination of whether to recommend at least one stop (e.g., at least one target location) to the user may also depend on probability. For example, based on information 806 provided by UE 804, server 702 may calculate the probability that any one of one or more occupants 808 specifies at least one stop within a specified time frame or before reaching the destination, and if the probability exceeds a probability threshold (e.g., >40%, ≥50%, etc.), server 702 may select / recommend at least one stop.

[0119] At 828, server 702 may be based on information 806 and also on crowdsourced data / information 706 (e.g., as combined with...). Figure 7 (As described) Select at least one stop 812 (e.g., select at least one target location from multiple candidate target locations). For example, if server 702 determines that at least one of one or more occupants 808 (e.g., two adult women, an infant, and a dog) requests a rest stop, server 702 may recommend stops suitable for women (e.g., a safe area with a large number of people), stops suitable for changing diapers for infants (such as public and spacious restrooms), and / or stops suitable for walking dogs, wherein these recommended stops may be selected based on crowdsourced data / information 706 (e.g., based on vehicles with similar occupants and / or conditions).

[0120] In another example, instead of selecting at least one stop 812, server 702 may also be configured to filter out unwanted / unsuitable locations from the list of recommended stops. For example, based on crowdsourced data / information 706, server 702 may filter out stops where people with pets / babies are only stopping briefly (e.g., these stops may be unsuitable for pets / babies), sparsely populated stops (e.g., places that may be considered less safe for female travelers), and / or locations unsuitable for babies and pets, etc. In some examples, as described in conjunction with 826, server 702 may select at least one stop 812 based on the probability that at least one occupant in vehicle 810 will specify a rest exceeding a probability threshold.

[0121] At 830, after server 702 selects at least one stop 812, server 702 may transmit an instruction 814 (e.g., message, signaling, etc.) to UE 804 for the selected at least one stop 812, wherein UE 804 may display the selected at least one stop 812 to its users (e.g., one or more occupants 808, driver of vehicle 810, etc.) via a screen.

[0122] In some specific implementations, as shown at 832, UE 804 may enable the user to provide feedback on at least one stop 812 selected by server 702, such as by providing ranking scores (e.g., a stop the user deems suitable / desirable ranked 1 and a stop the user deems unsuitable / undesirable ranked 5, etc.). Then, as shown at 834, based on the feedback (or ranking scores), 702 may update its crowdsourcing database (e.g., by tagging / reordering locations suitable or unsuitable for pets / babies). In other words, server 702 may be configured to adjust recommendations based on driver feedback.

[0123] Figure 9 Figure 900 illustrates an example use case of a server providing automatic rest location recommendations according to various aspects of this disclosure.

[0124] As shown at 902, in order to recommend rest locations for a vehicle (or for at least one occupant within the vehicle), a server (e.g., server 702) may be configured to first collect information associated with the location of the occupants and the vehicle. Such information may be collected via the vehicle's ICMS or sensors. For example, the server may be specified to know (1) who is in the vehicle, (2) where the vehicle is (currently) located, (3) what the occupants' needs are, and (4) where other users with similar needs have stopped in the past, etc.

[0125] As shown at 904, via the ICMS or sensors of the vehicle (and also based on crowdsourced information), the server can determine that: (1) there are two children (approximately 5 and 7 years old), two adults (approximately over 21 years old) and a large dog in the vehicle; (2) the vehicle is currently traveling on a highway at approximately coordinates (X,Y) or heading towards city X; (3) a child is crying and the driver is frequently merging into the right lane to read exit sign information; and (4) there is a rural rest stop within 1 km of the vehicle, which has well-maintained toilets and an open area for the dog to run around.

[0126] As shown at 906, based on such determination, the server can navigate (or recommend to the user) the vehicle to a rural rest stop 1 km away from the vehicle, where the rural rest stop is selected by the server based on the fact that other vehicles with similar occupants have stopped there in the past.

[0127] As shown at 908, in some implementations, the server may also be configured to receive feedback / rankings from users, which may include feedback such as whether the user liked the recommended stop, how long the rest lasted, whether the time spent navigating off the route was worth the benefits of the rest location, and / or how the passenger's mood was after the rest (e.g., if the mood improved, the location might be recommended / suitable for a rest), etc. The server can then update its crowdsourced database based on the feedback (and retrain its AI / ML modules if AI / ML modules are used).

[0128] This paper presents various aspects of a technique for recommending rest stops along a driving route based on crowdsourced information. The proposed solution may include the following aspects: 1) Crowdsourcing various data, including: the location of the stop, the duration of the stop, the number of passengers, the number of children, pets, etc. 2) Providing rest stop recommendations based on various criteria that may match or correspond to the crowdsourced data: driving route, expected driving time, user profiles and preference options, information about passengers (e.g., the number of adults, the number of pets, the number of children, etc.), and indications of passenger behavior that may require stopping. 3) Refining / adjusting the recommendations based on user feedback and information collected during and after the recommended rest stops.

[0129] Figure 10 This is a flowchart 1000 of a wireless communication method. The method can be performed by a server (e.g., one or more location servers 168; base station 102; server 702; network entity 1260). The method enables the server to recommend (or filter out unrecommended rest / stop locations) for the occupants of a vehicle (e.g., the driver and his / her passengers) based on locations where similar occupants take rest.

[0130] At point 1002, the server may receive first information from the UE, which is related to a set of occupants in the vehicle and at least one characteristic for at least one occupant in the set, such as combining... Figure 7 and Figure 8 As described. For example, in Figure 8 At point 824, server 702 can receive information 806 from UE 804, wherein information 806 may be related to one or more occupants 808 in vehicle 810, such as the number of occupants in vehicle 810, and at least one characteristic associated with at least one of the one or more occupants 808. The reception of the first information may be, for example, by... Figure 12 The recommended location for network entity 1260 is to be executed by component 199, network processor 1212 and / or network interface 1280.

[0131] In one example, the crew set may include at least one human, at least one animal, or a combination thereof.

[0132] In another example, at least one feature may include: the age of the occupant, the sex of the occupant, the species of the occupant, the size of the occupant, the posture of the occupant, the pattern of the occupant, the behavior of the occupant, or a combination thereof.

[0133] In another example, in order to receive the first information, the server may receive the first information via an in-cabin monitoring system (ICMS) associated with the vehicle.

[0134] In another example, the UE can be a vehicle, an on-board unit (OBU) in a vehicle, or a mobile device.

[0135] In another example, the server can calculate the probability that the route of the vehicle includes a set of target locations based on the first information, such as combining... Figure 7 and Figure 8 As described. For example, in Figure 8 At point 826, server 702 can calculate, based on information 806, the probability that the route traveled by vehicle 810 specifies at least one stop (e.g., one or more target locations). This probability can be calculated by, for example... Figure 12The location recommendation component 199, network processor 1212, and / or network interface 1280 of network entity 1260 are used to perform this function. In some embodiments, the target location set includes at least one of the following: a set of stops along the route, wherein the set of stops includes a second set of locations where the vehicle has not moved, or a first set of locations where the vehicle's speed is less than a threshold speed. In some embodiments, to calculate the probability that the vehicle's route includes the target location set, the UE may detect that at least one occupant in the occupant set is exhibiting a defined sign or defined pattern associated with searching for the first location set or the set of stops. In some embodiments, the calculation of the probability that the vehicle's route includes the target location set is further based on at least one of the following: time of day, second information from crowdsourcing, or a combination thereof.

[0136] At point 1010, the server can select at least one target location based on the first information, such as combining... Figure 7 and Figure 8 As described. For example, in Figure 8 At point 828, server 702 can select at least one stop point 812 based on information 806 and crowdsourced data / information 706 (also based on a probability exceeding a probability threshold). The selection of at least one target location can be, for example... Figure 12 The recommended location for network entity 1260 is to be executed by component 199, network processor 1212 and / or network interface 1280.

[0137] In one example, in order to select at least one target location, the server may further select at least one target location based on at least one of the following: time of day, a first number of occupants in the occupant set, a second number of occupants whose age is above or below an age threshold, behavioral patterns of the occupant set, one or more keywords detected in the vehicle, travel time of the vehicle, input destination of the vehicle, previous stopping location of the vehicle, feedback or recommendations from the occupant set, or speed of the vehicle.

[0138] At point 1012, the server can send an indication to the UE of at least one selected target location, such as combining... Figure 7 and Figure 8 As described. For example, in Figure 8 At point 830, server 702 may send an indication 814 to UE 804 indicating at least one stop point 812. The transmission of this indication may be, for example, by... Figure 12 The recommended location for network entity 1260 is to be executed by component 199, network processor 1212 and / or network interface 1280.

[0139] In one example, the server may receive from the UE a second indication of at least one of the following: a first number of occupants in the occupant set, a second number of occupants whose age is above or below an age threshold, a behavioral pattern of the occupant set, one or more keywords detected in the vehicle, the speed of the vehicle, the travel time of the vehicle, the input destination of the vehicle, the previous stopping location of the vehicle, feedback or recommendations from the occupant set, or a combination thereof, wherein the selection of at least one target location is further based on the second indication, such as in combination with... Figure 7 and Figure 8 As described. For example, as in combination Figure 8 As discussed in section 824, information 806 may also include additional information that may not be relevant to one or more occupants 808, but which may enable server 702 to make more accurate / appropriate recommendations regarding stopping points. For example, additional information may include the vehicle's speed (e.g., for server 702 to determine whether vehicle 810 is on a highway and / or the distance vehicle 810 can travel within a limited time period), the vehicle 810's travel time (e.g., for server 702 to estimate when to recommend a stopping point), the input destination and / or the estimated route of the vehicle (e.g., for server 702 to select a stopping point along the route to the destination), the vehicle's previous stopping locations (e.g., for server 702 to determine the time and location of the next stopping point), the vehicle 810's current location, feedback or recommendations from occupants (e.g., for server 702 to learn occupant preferences), the vehicle 810's ODD description / ICMS specification, and / or the vehicle status of vehicle 810, etc. The receipt of the second instruction may be by, for example... Figure 12 The recommended location for network entity 1260 is to be executed by component 199, network processor 1212 and / or network interface 1280.

[0140] In another example, the server may obtain second information based on crowdsourcing prior to the selection of at least one target location, wherein, in order to select at least one target location, the server may further select at least one target location based on the second information, such as combining... Figure 7 and Figure 8 As described. For example, as in combination Figure 7 As discussed, server 702 can receive crowdsourced data / information 706 from the collection of vehicles 704. The acquisition of the second information can be, for example... Figure 12The location recommendation component 199, network processor 1212, and / or network interface 1280 of the network entity 1260 are used to perform this. In some specific implementations, in order to obtain second information based on crowdsourcing, the server may collect third information from each UE in the UE set, which is related to a second set of occupants in the second vehicle and at least one second feature for at least one occupant in the second set of occupants.

[0141] Figure 11 This is a flowchart 1100 of a wireless communication method. The method can be performed by a server (e.g., one or more location servers 168; base station 102; server 702; network entity 1260). The method enables the server to recommend (or filter out unrecommended rest / stop locations) for the occupants of the vehicle (e.g., the driver and his / her passengers) based on locations where similar occupants take rest.

[0142] At 1102, the server may receive first information from the UE, which is related to a set of occupants in the vehicle and at least one characteristic for at least one occupant in the set, such as combining... Figure 7 and Figure 8 As described. For example, in Figure 8 At point 824, server 702 can receive information 806 from UE 804, wherein information 806 may be related to one or more occupants 808 in vehicle 810, such as the number of occupants in vehicle 810, and at least one characteristic associated with at least one of the one or more occupants 808. The reception of the first information may be, for example, by... Figure 12 The recommended location for network entity 1260 is to be executed by component 199, network processor 1212 and / or network interface 1280.

[0143] In one example, the crew set may include at least one human, at least one animal, or a combination thereof.

[0144] In another example, at least one feature may include: the age of the occupant, the sex of the occupant, the species of the occupant, the size of the occupant, the posture of the occupant, the pattern of the occupant, the behavior of the occupant, or a combination thereof.

[0145] In another example, in order to receive the first information, the server may receive the first information via ICMS associated with the vehicle.

[0146] In another example, the UE can be a vehicle, an OBU in a vehicle, or a mobile device.

[0147] At point 1106, the server can calculate the probability that the route of the vehicle includes the set of target locations based on the first information, such as combining... Figure 7 and Figure 8 As described. For example, in Figure 8 At point 826, server 702 can calculate, based on information 806, the probability that the route traveled by vehicle 810 specifies at least one stop (e.g., one or more target locations). This probability can be calculated by, for example... Figure 12 The recommended location for network entity 1260 is to be executed by component 199, network processor 1212 and / or network interface 1280.

[0148] In one example, the target location set includes at least one of the following: a set of stops along the route, wherein the set of stops includes a second set of locations where the vehicle has not moved, or a first set of locations where the vehicle's speed is less than a threshold speed. In some specific implementations, in order to calculate the probability that the vehicle's route includes the target location set, the server may detect that at least one occupant in the occupant set is exhibiting a defined flag or defined pattern associated with searching for the first location set or the set of stops.

[0149] In another example, the probability that a vehicle's route includes a set of target locations can be calculated based on at least one of the following: the time of day, second information, or a combination thereof.

[0150] At point 1110, the server can select at least one target location based on the first information, such as combining... Figure 7 and Figure 8 As described. For example, in Figure 8 At point 828, server 702 can select at least one stop point 812 based on information 806 and crowdsourced data / information 706 (also based on a probability exceeding a probability threshold). The selection of at least one target location can be, for example... Figure 12 The recommended location for network entity 1260 is to be executed by component 199, network processor 1212 and / or network interface 1280.

[0151] In one example, in order to select at least one target location, the server may further select at least one target location based on at least one of the following: time of day, a first number of occupants in the occupant set, a second number of occupants whose age is above or below an age threshold, behavioral patterns of the occupant set, one or more keywords detected in the vehicle, travel time of the vehicle, input destination of the vehicle, previous stopping location of the vehicle, feedback or recommendations from the occupant set, or speed of the vehicle.

[0152] At 1112, the server can send an indication to the UE of at least one selected target location, such as combining... Figure 7 and Figure 8 As described. For example, in Figure 8 At point 830, server 702 may send an indication 814 to UE 804 indicating at least one stop point 812. The transmission of this indication may be, for example, by... Figure 12 The recommended location for network entity 1260 is to be executed by component 199, network processor 1212 and / or network interface 1280.

[0153] In one example, as shown at 1104, the server may receive from the UE a second indication of at least one of the following: a first number of occupants in the occupant set, a second number of occupants whose age is above or below an age threshold, a behavioral pattern of the occupant set, one or more keywords detected in the vehicle, the speed of the vehicle, the travel time of the vehicle, the input destination of the vehicle, the previous stopping location of the vehicle, feedback or recommendations from the occupant set, or a combination thereof, wherein the selection of at least one target location is further based on the second indication, such as in combination with Figure 7 and Figure 8 As described. For example, as in combination Figure 8 As discussed in section 824, information 806 may also include additional information that may not be relevant to one or more occupants 808, but which may enable server 702 to make more accurate / appropriate recommendations regarding stopping points. For example, additional information may include the vehicle's speed (e.g., for server 702 to determine whether vehicle 810 is on a highway and / or the distance vehicle 810 can travel within a limited time period), the vehicle 810's travel time (e.g., for server 702 to estimate when to recommend a stopping point), the input destination and / or the estimated route of the vehicle (e.g., for server 702 to select a stopping point along the route to the destination), the vehicle's previous stopping locations (e.g., for server 702 to determine the time and location of the next stopping point), the vehicle 810's current location, feedback or recommendations from occupants (e.g., for server 702 to learn occupant preferences), the vehicle 810's ODD description / ICMS specification, and / or the vehicle status of vehicle 810, etc. The receipt of the second instruction may be by, for example... Figure 12 The recommended location for network entity 1260 is to be executed by component 199, network processor 1212 and / or network interface 1280.

[0154] In another example, as shown at 1108, the server may obtain second information based on crowdsourcing prior to the selection of at least one target location, wherein, in order to select at least one target location, the server may further select at least one target location based on the second information, such as combining... Figure 7 and Figure 8 As described. For example, as in combination Figure 7As discussed, server 702 can receive crowdsourced data / information 706 from the collection of vehicles 704. The acquisition of the second information can be, for example... Figure 12 The location recommendation component 199, network processor 1212, and / or network interface 1280 of the network entity 1260 are used to perform this. In some specific implementations, in order to obtain second information based on crowdsourcing, the server may collect third information from each UE in the UE set, which is related to a second set of occupants in the second vehicle and at least one second feature for at least one occupant in the second set of occupants.

[0155] Figure 12 Figure 1200 illustrates an example of a hardware implementation for network entity 1260. In one example, network entity 1260 may be within core network 120. Network entity 1260 may include at least one network processor 1212. Network processor 1212 may include on-chip memory 1212'. In some aspects, network entity 1260 may also include additional memory module 1214. Network entity 1260 communicates with CU 1202 directly (e.g., via a backhaul link) or indirectly (e.g., via RIC) through network interface 1280. On-chip memory 1212' and additional memory module 1214 may each be considered as computer-readable media / memory. Each computer-readable media / memory may be non-transitory. Network processor 1212 is responsible for general processing, including executing software stored on the computer-readable media / memory. When executed by a corresponding processor, the software causes that processor to perform the various functions described above. The computer-readable media / memory may also be used to store data manipulated by the processor while executing the software.

[0156] As discussed above, location recommendation component 199 may be configured to receive first information from the UE, the first information relating to a set of occupants in a vehicle and at least one characteristic for at least one occupant in the set of occupants. Location recommendation component 199 may also be configured to select at least one target location based on the first information. Location recommendation component 199 may also be configured to send an indication to the UE of the selected at least one target location. Location recommendation component 199 may be located within network processor 1212. Location recommendation component 199 may be one or more hardware components specifically configured to implement the stated process / algorithm, implemented by one or more processors configured to execute the stated process / algorithm, stored in a computer-readable medium for implementation by one or more processors, or some combination thereof. When multiple processors are implemented, the multiple processors may execute the stated process / algorithm individually or in combination. Network entity 1260 may include a variety of components configured for various functions. In one configuration, network entity 1260 may include components for receiving first information from a UE, the first information relating to a set of occupants in a vehicle and at least one characteristic for at least one occupant in the set of occupants. Network entity 1260 may also include components for selecting at least one target location based on the first information. Network entity 1260 may further include components for sending an indication to the UE of the selected at least one target location.

[0157] In one configuration, the crew set may include at least one human, at least one animal, or a combination thereof.

[0158] In another configuration, network entity 1260 may also include a component for calculating the probability that the route of a vehicle includes a set of target locations based on the first information.

[0159] In another configuration, at least one feature may include: the age of the occupant, the sex of the occupant, the species of the occupant, the size of the occupant, the posture of the occupant, the pattern of the occupant, the behavior of the occupant, or a combination thereof.

[0160] In another configuration, the component for receiving the first information may include configuring the network entity 1260 to receive the first information via an ICMS associated with the vehicle.

[0161] In another configuration, the UE can be a vehicle, an on-board unit (OBU) in a vehicle, or a mobile device.

[0162] In another configuration, the target location set includes at least one of the following: a set of stops along the route, wherein the set of stops includes a second set of locations where the vehicle has not moved, or a first set of locations where the vehicle's speed is less than a threshold speed. In some specific implementations, components for calculating the probability that the vehicle's route includes the target location set may include configuring network entity 1260 to detect that at least one occupant in the occupant set is exhibiting a defined flag or defined pattern associated with searching for the first location set or the stop set.

[0163] In another configuration, the probability calculation of the route of a vehicle to the target location set may be further based on at least one of the following: the time of day, second information, or a combination thereof.

[0164] In another configuration, the component for selecting at least one target location may include configuring network entity 1260 to further select at least one target location based on at least one of the following: time of day, a first number of occupants in the occupant set, a second number of occupants whose age is above or below an age threshold, behavioral patterns of the occupant set, one or more keywords detected in the vehicle, travel time of the vehicle, input destination of the vehicle, previous stopping location of the vehicle, feedback or recommendations from the occupant set, or speed of the vehicle.

[0165] In another configuration, network entity 1260 may further include a component for receiving from the UE a second indication of at least one of the following: a first number of occupants in the occupant set, a second number of occupants whose age is above or below an age threshold, a behavioral pattern of the occupant set, one or more keywords detected in the vehicle, the speed of the vehicle, the travel time of the vehicle, the input destination of the vehicle, the previous stopping position of the vehicle, feedback or recommendations from the occupant set, or a combination thereof, wherein the selection of at least one target location is further based on the second indication.

[0166] In another configuration, network entity 1260 may further include components for obtaining second information based on crowdsourcing prior to the selection of at least one target location, wherein the components for selecting at least one target location may include configuring network entity 1260 to further select at least one target location based on the second information. In some specific implementations, the components for obtaining the second information based on crowdsourcing may include configuring network entity 1260 to collect third information from each UE in the UE set, the third information relating to a second set of occupants in the second vehicle and at least one second characteristic for at least one occupant in the second set of occupants.

[0167] The component can be a location recommendation component 199 of network entity 1260 configured to perform the functions described by the component.

[0168] Figure 13 This is a flowchart 1300 of a wireless communication method. The method can be performed by a UE (e.g., UE 104, 404, 502, 504, 506, 508, 804; device 1504). The method enables the UE to provide information related to a set of occupants in a vehicle and, based on that information, receive a set of recommended stopping points (e.g., target areas).

[0169] At 1304, the UE may send first information to the server, which is related to a set of occupants in the vehicle and at least one feature for at least one occupant in that set, such as combining... Figure 7 and Figure 8 As described. For example, in Figure 8 At point 824, UE 804 may send information 806 to server 702, wherein information 806 may be related to one or more occupants 808 in vehicle 810, such as the number of occupants in vehicle 810, and at least one characteristic associated with at least one of the one or more occupants 808. The transmission of the first information may be by, for example... Figure 15 The device 1504 uses the vehicle sensor assembly 198, transceiver 1522, cellular baseband processor 1524, and / or application processor 1506 to perform the operation.

[0170] In one example, the crew set may include at least one human, at least one animal, or a combination thereof.

[0171] In another example, at least one feature may include: the age of the occupant, the sex of the occupant, the species of the occupant, the size of the occupant, the posture of the occupant, the pattern of the occupant, the behavior of the occupant, or a combination thereof.

[0172] In another example, the UE can be a vehicle, an OBU in a vehicle, or a mobile device.

[0173] At 1308, the UE may receive from the server an indication of at least one target location in the target location set based on the first information and the second information from the crowdsourcing, such as combining... Figure 7 and Figure 8 As described. For example, in Figure 8 At point 830, UE 804 may receive an instruction 814 indicating at least one stop 812, wherein the at least one stop 812 is selected based on information 806 and crowdsourced data / information 706. Reception of this instruction may be achieved by, for example... Figure 15The device 1504 uses the vehicle sensor assembly 198, transceiver 1522, cellular baseband processor 1524, and / or application processor 1506 to perform the operation.

[0174] In one example, the target location set may include at least one of the following: a set of stops along the route, wherein the set of stops includes a second set of locations where the vehicle has not moved, or a first set of locations where the vehicle's speed is less than a threshold speed.

[0175] In another example, the UE can detect the first information via ICMS before transmitting the first information, such as by combining... Figure 7 and Figure 8 As described. For example, in Figure 8 At point 820, UE 804 (e.g., an in-vehicle navigation system, a smartphone running a navigation application, etc.) may be configured to detect / identify information 806 related to one or more occupants 808 (e.g., a driver, one or more passengers, one or more animals, one or more objects, etc.) in vehicle 810, such as the number of occupants in vehicle 810, and at least one feature associated with at least one of the one or more occupants 808. In some examples, UE 804 may use an ICMS or at least one sensor (e.g., a camera) to detect or identify information 806 related to one or more occupants 808 in vehicle 810. Detection of the first information may be achieved by, for example... Figure 15 The device 1504 uses the vehicle sensor assembly 198, ICMS 1540, sensor 1518, camera 1532, transceiver 1522, cellular baseband processor 1524 and / or application processor 1506 to perform the operation.

[0176] In another example, the UE may send a second indication to the server for at least one of the following: a first number of occupants in the occupant set, a second number of occupants whose age is above or below an age threshold, behavioral patterns of the occupant set, one or more keywords detected in the vehicle, the speed of the vehicle, the travel time of the vehicle, the input destination of the vehicle, the previous stopping position of the vehicle, feedback or recommendations from the occupant set, or a combination thereof, wherein at least one target location in the target location set is further based on the second indication, such as in combination with... Figure 7 and Figure 8 As described. For example, as in combination Figure 8As discussed in section 824, information 806 may also include additional information that may not be relevant to one or more occupants 808, but which may enable server 702 to make more accurate / appropriate recommendations regarding stopping points. For example, additional information may include the vehicle's speed (e.g., for server 702 to determine whether vehicle 810 is on a highway and / or the distance vehicle 810 can travel within a limited time period), the vehicle's travel time (e.g., for server 702 to estimate when to recommend a stopping point), the input destination and / or the estimated route of the vehicle (e.g., for server 702 to select a stopping point along the route to the destination), the vehicle's previous stopping locations (e.g., for server 702 to determine the time and location of the next stopping point), the vehicle's current location, feedback or recommendations from occupants (e.g., for server 702 to learn occupant preferences), the vehicle's ODD description / ICMS specification, and / or the vehicle's status, etc. The transmission of the second instruction may be by, for example... Figure 15 The device 1504 uses the vehicle sensor assembly 198, ICMS 1540, sensor 1518, camera 1532, transceiver 1522, cellular baseband processor 1524 and / or application processor 1506 to perform the operation.

[0177] In another example, the UE can detect that the vehicle is in a park position or that the vehicle's stopping time exceeds a time threshold; and based on this detection, it sends first information and third information associated with the vehicle's location to the server, such as combining... Figure 7 and Figure 8 As described. For example, as in combination Figure 7 As discussed in 710 and 716, vehicles in the vehicle set 704 can send crowdsourced data / information 706 including vehicle status (e.g., parked, reversing, neutral, driving, etc.). In another example, the crowdsourced data / information 706 may include the location of the vehicle, such as the location where the vehicle has been stopped for a limited duration (e.g., at least 10 minutes). Detection and / or sending can be performed by, for example... Figure 15 The device 1504 uses the vehicle sensor assembly 198, ICMS 1540, sensor 1518, camera 1532, transceiver 1522, cellular baseband processor 1524 and / or application processor 1506 to perform the operation.

[0178] In another example, the UE can record a set of behavioral patterns for at least one occupant in the occupant set while the vehicle is moving; and based on detecting that the vehicle is in a park position or that the vehicle's stopping time exceeds a time threshold, send the set of behavioral patterns to the server, such as combining... Figure 7 and Figure 8As described. For example, as in combination Figure 7 As discussed in section 708, vehicles in the vehicle set 704 can send crowdsourced data / information 706 including the identification of occupants in the vehicle and at least one characteristic associated with at least one occupant. At least one characteristic may refer to at least one property of the occupant, such as the occupant's age (e.g., newborns / infants aged 0 to 12 months, toddlers aged 1 to 5 years, children aged 5 to 13 years, teenagers aged 13 to 18 years, adults aged 18 years and older, etc.), the occupant's gender (e.g., male, female, etc.), the occupant's species (e.g., breed of dog / cat, etc.), the occupant's type (e.g., human, animal, inanimate object, etc.), the occupant's size (e.g., small, medium, large, 30kg to 40kg, 50kg to 70kg, etc.), the occupant's posture (e.g., frequently looking out the window), the occupant's pattern (e.g., stopping every X hours), and / or the occupant's behavior (e.g., frequently changing position, frequently massaging his / her body, showing signs of fatigue, unfastening the seatbelt, etc.). The recording and sending of a set of actions can be achieved by, for example... Figure 15 The device 1504 uses the vehicle sensor assembly 198, ICMS 1540, sensor 1518, camera 1532, transceiver 1522, cellular baseband processor 1524 and / or application processor 1506 to perform the operation.

[0179] In another example, the UE can calculate the duration for which a vehicle is stopped at a certain location, and the UE can send the calculated duration for which the vehicle is stopped at that location to the server.

[0180] Figure 14 This is a flowchart 1400 of a wireless communication method. The method can be performed by a UE (e.g., UE 104, 404, 502, 504, 506, 508, 804; device 1504). The method enables the UE to provide information related to a set of occupants in a vehicle and, based on that information, receive a set of recommended stopping points (e.g., target areas).

[0181] At 1404, the UE may send first information to the server, which is related to a set of occupants in the vehicle and at least one feature for at least one occupant in that set, such as combining... Figure 7 and Figure 8 As described. For example, in Figure 8 At point 824, UE 804 may send information 806 to server 702, wherein information 806 may be related to one or more occupants 808 in vehicle 810, such as the number of occupants in vehicle 810, and at least one characteristic associated with at least one of the one or more occupants 808. The transmission of the first information may be by, for example... Figure 15The device 1504 uses the vehicle sensor assembly 198, transceiver 1522, cellular baseband processor 1524, and / or application processor 1506 to perform the operation.

[0182] In one example, the crew set may include at least one human, at least one animal, or a combination thereof.

[0183] In another example, at least one feature may include: the age of the occupant, the sex of the occupant, the species of the occupant, the size of the occupant, the posture of the occupant, the pattern of the occupant, the behavior of the occupant, or a combination thereof.

[0184] In another example, the UE can be a vehicle, an OBU in a vehicle, or a mobile device.

[0185] At 1408, the UE may receive from the server an indication of at least one target location in the target location set based on the first information and the second information from the crowdsourcing, such as combining... Figure 7 and Figure 8 As described. For example, in Figure 8 At point 830, UE 804 may receive an instruction 814 indicating at least one stop 812, wherein the at least one stop 812 is selected based on information 806 and crowdsourced data / information 706. Reception of this instruction may be achieved by, for example... Figure 15 The device 1504 uses the vehicle sensor assembly 198, transceiver 1522, cellular baseband processor 1524, and / or application processor 1506 to perform the operation.

[0186] In one example, the target location set may include at least one of the following: a set of stops along the route, wherein the set of stops includes a second set of locations where the vehicle has not moved, or a first set of locations where the vehicle's speed is less than a threshold speed.

[0187] In another example, as shown at 1402, the UE can detect the first information via ICMS before transmitting the first information, such as in conjunction with... Figure 7 and Figure 8 As described. For example, in Figure 8At point 820, UE 804 (e.g., an in-vehicle navigation system, a smartphone running a navigation application, etc.) may be configured to detect / identify information 806 related to one or more occupants 808 (e.g., a driver, one or more passengers, one or more animals, one or more objects, etc.) in vehicle 810, such as the number of occupants in vehicle 810, and at least one feature associated with at least one of the one or more occupants 808. In some examples, UE 804 may use an ICMS or at least one sensor (e.g., a camera) to detect or identify information 806 related to one or more occupants 808 in vehicle 810. Detection of the first information may be achieved by, for example... Figure 15 The device 1504 uses the vehicle sensor assembly 198, ICMS 1540, sensor 1518, camera 1532, transceiver 1522, cellular baseband processor 1524 and / or application processor 1506 to perform the operation.

[0188] In another example, as shown at 1406, the UE may send a second indication to the server for at least one of the following: a first number of occupants in the occupant set, a second number of occupants whose age is above or below an age threshold, a behavioral pattern of the occupant set, one or more keywords detected in the vehicle, the speed of the vehicle, the travel time of the vehicle, the input destination of the vehicle, the previous stopping position of the vehicle, feedback or recommendations from the occupant set, or a combination thereof, wherein at least one target location in the target location set is further based on the second indication, such as in combination with... Figure 7 and Figure 8 As described. For example, as in combination Figure 8 As discussed in section 824, information 806 may also include additional information that may not be relevant to one or more occupants 808, but which may enable server 702 to make more accurate / appropriate recommendations regarding stopping points. For example, additional information may include the vehicle's speed (e.g., for server 702 to determine whether vehicle 810 is on a highway and / or the distance vehicle 810 can travel within a limited time period), the vehicle's travel time (e.g., for server 702 to estimate when to recommend a stopping point), the input destination and / or the estimated route of the vehicle (e.g., for server 702 to select a stopping point along the route to the destination), the vehicle's previous stopping locations (e.g., for server 702 to determine the time and location of the next stopping point), the vehicle's current location, feedback or recommendations from occupants (e.g., for server 702 to learn occupant preferences), the vehicle's ODD description / ICMS specification, and / or the vehicle's status, etc. The transmission of the second instruction may be by, for example... Figure 15The device 1504 uses the vehicle sensor assembly 198, ICMS 1540, sensor 1518, camera 1532, transceiver 1522, cellular baseband processor 1524 and / or application processor 1506 to perform the operation.

[0189] In another example, as shown at 1410, the UE can detect that the vehicle is in a park position or that the vehicle's stopping time exceeds a time threshold; and based on this detection, it sends first information and third information associated with the vehicle's location to the server, such as combining... Figure 7 and Figure 8 As described. For example, as in combination Figure 7 As discussed in 710 and 716, vehicles in the vehicle set 704 can send crowdsourced data / information 706 including vehicle status (e.g., parked, reversing, neutral, driving, etc.). In another example, the crowdsourced data / information 706 may include the location of the vehicle, such as the location where the vehicle has been stopped for a limited duration (e.g., at least 10 minutes). Detection and / or sending can be performed by, for example... Figure 15 The device 1504 uses the vehicle sensor assembly 198, ICMS 1540, sensor 1518, camera 1532, transceiver 1522, cellular baseband processor 1524 and / or application processor 1506 to perform the operation.

[0190] In another example, as shown at 1412, the UE can record a set of behavioral patterns for at least one occupant in the occupant set while the vehicle is moving; and based on detecting that the vehicle is in a park position or that the vehicle's stopping time exceeds a time threshold, the UE sends this set of behavioral patterns to the server, such as in combination with... Figure 7 and Figure 8 As described. For example, as in combination Figure 7As discussed in section 708, vehicles in the vehicle set 704 can send crowdsourced data / information 706 including the identification of occupants in the vehicle and at least one characteristic associated with at least one occupant. At least one characteristic may refer to at least one property of the occupant, such as the occupant's age (e.g., newborns / infants aged 0 to 12 months, toddlers aged 1 to 5 years, children aged 5 to 13 years, teenagers aged 13 to 18 years, adults aged 18 years and older, etc.), the occupant's gender (e.g., male, female, etc.), the occupant's species (e.g., breed of dog / cat, etc.), the occupant's type (e.g., human, animal, inanimate object, etc.), the occupant's size (e.g., small, medium, large, 30kg to 40kg, 50kg to 70kg, etc.), the occupant's posture (e.g., frequently looking out the window), the occupant's pattern (e.g., stopping every X hours), and / or the occupant's behavior (e.g., frequently changing position, frequently massaging his / her body, showing signs of fatigue, unfastening the seatbelt, etc.). The recording and sending of a set of actions can be achieved by, for example... Figure 15 The device 1504 uses the vehicle sensor assembly 198, ICMS 1540, sensor 1518, camera 1532, transceiver 1522, cellular baseband processor 1524 and / or application processor 1506 to perform the operation.

[0191] In another example, the UE can calculate the duration for which a vehicle is stopped at a certain location, and the UE can send the calculated duration for which the vehicle is stopped at that location to the server.

[0192] Figure 15Figure 1500 illustrates an example of a hardware implementation for device 1504. Device 1504 may be a UE, a component of a UE, or implement UE functionality. In some aspects, device 1504 may include at least one cellular baseband processor 1524 (also referred to as a modem) coupled to one or more transceivers 1522 (e.g., cellular RF transceivers). Cellular baseband processor 1524 may include at least one on-chip memory 1524'. In some aspects, device 1504 may also include one or more Subscriber Identity Module (SIM) cards 1520 and at least one application processor 1506 coupled to a Secure Digital Card (SD) card 1508 and a screen 1510. Application processor 1506 may include on-chip memory 1506'. In some aspects, device 1504 may also include a Bluetooth module 1512, a WLAN module 1514, an ultra-wideband (UWB) module 1538, an ICMS 1540, an SPS module 1516 (e.g., a GNSS module), one or more sensors 1518 (e.g., an atmospheric pressure sensor / altimeter; motion sensors such as an inertial measurement unit (IMU), a gyroscope, and / or an accelerometer; light detection and ranging (LIDAR), radio-assisted detection and ranging (RADAR), sound navigation and ranging (SONAR), a magnetometer, audio, and / or other technologies for positioning), an additional memory module 1526, a power source 1530, and / or a camera 1532. Bluetooth module 1512, UWB module 1538, ICMS 1540, WLAN module 1514, and SPS module 1516 may include on-chip transceivers (TRX) (or in some cases, only receivers (RX)). Bluetooth module 1512, WLAN module 1514, and SPS module 1516 may include their own dedicated antennas and / or communicate using antenna 1580. Cellular baseband processor 1524 communicates with UE 104 and / or with RUs associated with network entity 1502 via transceiver 1522 through one or more antennas 1580. Cellular baseband processor 1524 and application processor 1506 may each include computer-readable media / memory 1524', 1506'. Additional memory module 1526 may also be considered computer-readable media / memory. Each computer-readable media / memory 1524', 1506', 1526 may be non-transitory. Cellular baseband processor 1524 and application processor 1506 are each responsible for general processing, including the execution of software stored on the computer-readable media / memory. When executed by cellular baseband processor 1524 / application processor 1506, the software causes cellular baseband processor 1524 / application processor 1506 to perform the various functions described above. Cellular baseband processor 1524 and application processor 1506 are configured to perform the various functions described above, at least in part, based on information stored in memory.That is, the cellular baseband processor 1524 and application processor 1506 can be configured to perform a first subset of the various functions described above without information stored in memory, and can be configured to perform a second subset of the various functions described above based on information stored in memory. The computer-readable medium / memory can also be used to store data manipulated by the cellular baseband processor 1524 / application processor 1506 during software execution. The cellular baseband processor 1524 / application processor 1506 can be a component of the UE 350 and can include at least one of a memory 360 and / or at least one of a TX processor 368, an RX processor 356, and a controller / processor 359. In one configuration, the device 1504 can be at least one processor chip (modem and / or application) and includes only the cellular baseband processor 1524 and / or application processor 1506, while in another configuration, the device 1504 can be the entire UE (e.g., see below). Figure 3 The UE 350 includes an additional module of the device 1504.

[0193] As discussed above, the vehicle sensor component 198 may be configured to send first information to a server, the first information relating to a set of occupants in the vehicle and at least one characteristic for at least one occupant in the set of occupants. The vehicle sensor component 198 may also be configured to receive from the server, based on the first information and based on second information from crowdsourcing, indications of at least one target location in a set of target locations. The vehicle sensor component 198 may be located within the cellular baseband processor 1524, the application processor 1506, or both the cellular baseband processor 1524 and the application processor 1506. The vehicle sensor component 198 may be one or more hardware components specifically configured to execute the stated process / algorithm, implemented by one or more processors configured to execute the stated process / algorithm, stored in a computer-readable medium for implementation by one or more processors, or some combination thereof. When multiple processors are implemented, the multiple processors may execute the stated process / algorithm individually or in combination. As shown, the device 1504 may include a variety of components configured for various functions. In one configuration, device 1504, and specifically cellular baseband processor 1524 and / or application processor 1506, may include components for sending first information to a server, the first information relating to a set of occupants in a vehicle and at least one characteristic for at least one occupant in the set of occupants. Device 1504 may also include components for receiving from the server, based on the first information and based on second information from crowdsourcing, an indication of at least one target location in a set of target locations.

[0194] In one configuration, the crew set may include at least one human, at least one animal, or a combination thereof.

[0195] In another configuration, at least one feature may include: the age of the occupant, the sex of the occupant, the species of the occupant, the size of the occupant, the posture of the occupant, the pattern of the occupant, the behavior of the occupant, or a combination thereof.

[0196] In another configuration, device 1504 may be a vehicle, an OBU in a vehicle, or a mobile device.

[0197] In another configuration, the target location set may include at least one of the following: a set of stops along the route, wherein the set of stops includes a second set of locations where the vehicle has not moved, or a first set of locations where the vehicle's speed is less than a threshold speed.

[0198] In another configuration, the device 1504 may also include components for detecting the first information via ICMS prior to the transmission of the first information.

[0199] In another configuration, the device 1504 may further include components for sending a second instruction to a server for at least one of: a first number of occupants in the occupant set, a second number of occupants whose age is above or below an age threshold, a behavioral pattern of the occupant set, one or more keywords detected in the vehicle, the speed of the vehicle, the travel time of the vehicle, the input destination of the vehicle, the previous stopping position of the vehicle, feedback or recommendations from the occupant set, or a combination thereof, wherein at least one target location in the target location set is further based on the second instruction.

[0200] In another configuration, the device 1504 may further include components for detecting that the vehicle is in a parking position or that the vehicle has been stopped for a period of time exceeding a time threshold; and components for sending first information and third information associated with the location of the vehicle to a server based on the detection.

[0201] In another configuration, the device 1504 may further include components for recording a set of behavioral patterns for at least one occupant in the occupant set while the vehicle is in motion; and components for sending the set of behavioral patterns to a server based on the detection that the vehicle is in a parking gear or that the vehicle has been stopped for a period of time exceeding a time threshold.

[0202] In another configuration, the device 1504 may further include components for calculating the duration of a vehicle's stop at a location, and components for sending the calculated duration of the vehicle's stop at that location to a server.

[0203] The component may be a vehicle sensor assembly 198 of device 1504 configured to perform the functions described therein. As described above, device 1504 may include a TX processor 368, an RX processor 356, and a controller / processor 359. Thus, in one configuration, these components may be the TX processor 368, the RX processor 356, and / or the controller / processor 359 configured to perform the functions described therein.

[0204] It should be understood that the specific order or hierarchy of the boxes in the disclosed process / flowcharts is merely an example of the exemplary method. It should be understood that the specific order or hierarchy of the boxes in the process / flowcharts may be rearranged based on design preferences. Furthermore, some boxes may be combined or omitted. The appended method claims present the elements of various boxes in a sample order, but are not limited to the given specific order or hierarchy.

[0205] 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 may be applied to other aspects. Therefore, the claims are not limited to the aspects described herein but should be given the full scope consistent with the language of the claims. Unless specifically stated otherwise, references to elements in the singular form do not mean “one and only one” but rather “one or more.” Terms such as “if,” “when,” and “simultaneously” do not imply a direct temporal relationship or reaction. That is, these phrases, such as “when…”, do not imply an immediate action in response to the occurrence of an action or during the occurrence of an action, but simply suggest that if a condition is met, then the action will occur, without requiring a specific or immediate time limit for the occurrence of the action. The word “exemplary” is used herein to mean “serving as an example, instance, or illustration.” Any aspect described herein as “exemplary” is not necessarily to be construed as preferred or superior to other aspects. Unless specifically stated otherwise, 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" can 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 collection of elements with a number of one or more elements. Therefore, for a set of X, X will include one or more elements. When at least one processor is configured to execute a set of functions, the at least one processor is configured to execute the set of functions individually or in any combination. Therefore, each of the at least one processor can be configured to perform a specific subset of the set of functions, wherein the subset is the complete set, a suitable subset of the set, or an empty subset of the set. If the first device receives data from or sends data to the second device, data can be received / sent directly between the first and second devices, or indirectly between the first and second devices via a set of devices. A device configured to “output” data (such as transmission, signaling, or a message) can, for example, transmit the data using a transceiver, or can transmit the data to the device that sent the data. A device configured to “receive” data (such as transmission, signaling, or a message) can, for example, receive the data using a transceiver, or can obtain the data from the device that received the data.Information stored in memory includes instructions and / or data. All structural and functional equivalents of the elements throughout the various aspects described herein that are known to or will later be known to a person skilled in the art are expressly incorporated herein by reference and are covered by the claims. Furthermore, nothing disclosed herein is intended to be offered to the public, whether or not such disclosure is expressly recited in the claims. The terms “module,” “mechanism,” “element,” “device,” etc., cannot replace the word “component.” Therefore, no claim element will be construed as a functional component unless the element is expressly recited using the phrase “component for…”.

[0206] As used in this article, 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, conditions, factors, etc.) should be interpreted as “based on at least A”, unless specifically stated differently.

[0207] The following aspects are merely illustrative and may be combined with other aspects or teachings described herein without limitation.

[0208] Aspect 1 is a method for wireless communication at a server, the method comprising: receiving first information from a user equipment (UE), the first information being associated with a set of occupants in a vehicle and at least one feature for at least one occupant in the set of occupants; calculating, based on the first information, a probability that a route of the vehicle includes a set of target locations; selecting at least one target location based on the first information; and sending an indication to the UE of the selected at least one target location.

[0209] Aspect 2 is the method according to aspect 1, wherein the crew includes at least one human, at least one animal, or a combination thereof.

[0210] Aspect 3 is the method according to aspect 1 or aspect 2, wherein the at least one feature includes: the age of the occupant, the sex of the occupant, the species of the occupant, the size of the occupant, the posture of the occupant, the pattern of the occupant, the behavior of the occupant, or a combination thereof.

[0211] Aspect 4 is the method according to any one of Aspects 1 to 3, wherein receiving the first information includes receiving the first information via an in-cabin monitoring system (ICMS) associated with the vehicle.

[0212] Aspect 5 is a method according to any one of Aspects 1 to 4, the method further comprising: receiving from the UE a second indication of at least one of: a first number of occupants in the occupant set, a second number of occupants whose age is higher or lower than an age threshold, a behavioral pattern of the occupant set, one or more keywords detected in the vehicle, the speed of the vehicle, the travel time of the vehicle, the input destination of the vehicle, the previous stopping position of the vehicle, feedback or recommendations from the occupant set, or a combination thereof; and wherein the selection of the at least one target location is further based on the second indication.

[0213] Aspect 6 is the method according to any one of Aspects 1 to 5, wherein selecting the at least one target location includes further selecting the at least one target location based on at least one of the following: time of day, a first number of occupants in the occupant set, a second number of occupants whose age is above or below an age threshold, the behavioral pattern of the occupant set, one or more keywords detected in the vehicle, the travel time of the vehicle, the input destination of the vehicle, the previous stopping location of the vehicle, feedback or recommendations from the occupant set, or the speed of the vehicle.

[0214] Aspect 7 is the method according to any one of Aspects 1 to 6, wherein the UE is the vehicle, the on-board unit (OBU) in the vehicle, or the mobile device.

[0215] Aspect 8 is the method according to any one of aspects 1 to 7, the method further comprising: obtaining second information based on crowdsourcing prior to the selection of the at least one target location, wherein selecting the at least one target location includes further selecting the at least one target location based on the second information.

[0216] Aspect 9 is the method according to any one of Aspects 1 to 8, wherein obtaining the second information based on the crowdsourcing includes: collecting third information from each UE in the UE set, the third information being related to a second set of occupants in the second vehicle and at least one second feature for at least one occupant in the second set of occupants.

[0217] Aspect 10 is a method according to any one of aspects 1 to 9, the method further comprising: calculating a probability that the route of the vehicle includes a set of target locations based on the first information, wherein selecting the at least one target location based on the first information includes selecting the at least one target location in the set of target locations based on the first information based on a probability greater than a threshold probability.

[0218] Aspect 11 is a method according to any one of aspects 1 to 10, wherein the target location set includes at least one of: a set of stops along the route, wherein the set of stops includes a second set of locations where the vehicle has not moved, or a first set of locations where the vehicle's speed is less than a threshold speed.

[0219] Aspect 12 is a method according to any one of aspects 1 to 11, wherein calculating the probability that the route of the vehicle includes the set of target locations includes detecting that at least one occupant in the set of occupants is exhibiting a defined sign or defined pattern associated with finding the first set of locations or the set of stops.

[0220] Aspect 13 is the method according to any one of Aspects 1 to 12, wherein the calculation of the probability that the route of the vehicle includes the set of target locations is further based on at least one of the following: time of day, second information from crowdsourcing, or a combination thereof.

[0221] Aspect 14 is an apparatus for wireless communication at a server, the apparatus comprising: at least one memory; and at least one processor coupled to the at least one memory and based at least in part on information stored in the at least one memory, the at least one processor being configured individually or in any combination to implement any one of aspects 1 to 13.

[0222] Aspect 15 is the apparatus according to aspect 14, the apparatus further comprising at least one of a transceiver or an antenna coupled to the at least one processor.

[0223] Aspect 16 is an apparatus for wireless communication, the apparatus comprising: components for implementing any one of aspects 1 to 13.

[0224] Aspect 17 is a computer-readable medium (e.g., a non-transitory computer-readable medium) storing computer-executable code, wherein the code, when executed by a processor, causes the processor to implement any one of aspects 1 to 13.

[0225] Aspect 18 is a method for wireless communication at a user equipment (UE), the method comprising: sending first information to a server, the first information relating to a set of occupants in a vehicle and at least one characteristic for at least one occupant in the set of occupants; and receiving from the server, based on the first information and based on second information from crowdsourcing, an indication of at least one target location in a set of target locations.

[0226] Aspect 19 is the method according to aspect 18, wherein the target location set includes at least one of: a set of stops along the route, wherein the set of stops includes a second set of locations where the vehicle has not moved, or a first set of locations where the vehicle's speed is less than a threshold speed.

[0227] Aspect 20 is the method according to aspect 18 or aspect 19, wherein the crew group includes at least one human, at least one animal, or a combination thereof.

[0228] Aspect 21 is the method according to any one of aspects 18 to 20, wherein the at least one feature includes: the age of the occupant, the sex of the occupant, the species of the occupant, the size of the occupant, the posture of the occupant, the pattern of the occupant, the behavior of the occupant, or a combination thereof.

[0229] Aspect 22 is the method according to any one of aspects 18 to 21, the method further comprising: detecting the first information via an in-cabin monitoring system (ICMS) prior to the transmission of the first information.

[0230] Aspect 23 is a method according to any one of aspects 18 to 22, the method further comprising: sending to the server a second indication of at least one of: a first number of occupants in the occupant set, a second number of occupants whose age is above or below an age threshold, a behavioral pattern of the occupant set, one or more keywords detected in the vehicle, the speed of the vehicle, the travel time of the vehicle, the input destination of the vehicle, the previous stopping position of the vehicle, feedback or recommendations from the occupant set, or a combination thereof; and wherein the at least one target location in the target location set is further based on the second indication.

[0231] Aspect 24 is the method according to any one of aspects 18 to 23, wherein the UE is the vehicle, the on-board unit (OBU) in the vehicle, or the mobile device.

[0232] Aspect 25 is a method according to any one of aspects 18 to 24, the method further comprising: detecting that the vehicle is in a parking gear or that the stopping time of the vehicle exceeds a time threshold; and sending the first information and third information associated with the location of the vehicle to the server based on the detection.

[0233] Aspect 26 is a method according to any one of aspects 18 to 25, the method further comprising: recording a set of behavioral patterns of at least one occupant in the occupant set while the vehicle is moving; and sending the set of behavioral patterns to the server based on detecting that the vehicle is in a parking gear or that the stopping time of the vehicle exceeds a time threshold.

[0234] Aspect 27 is the method according to any one of aspects 18 to 26, the method further comprising: calculating the duration of the vehicle being stopped at a location; and sending the calculated duration of the vehicle being stopped at the location to the server.

[0235] Aspect 28 is an apparatus for wireless communication at a user equipment (UE), the apparatus comprising: at least one memory; and at least one processor coupled to the at least one memory and based at least in part on information stored in the at least one memory, the at least one processor being configured individually or in any combination to implement any one of aspects 18 to 27.

[0236] Aspect 29 is the apparatus according to aspect 28, the apparatus further comprising at least one of a transceiver or an antenna coupled to the at least one processor.

[0237] Aspect 30 is a device for wireless communication, the device comprising: components for implementing any one of aspects 18 to 27.

[0238] Aspect 31 is a computer-readable medium (e.g., a non-transitory computer-readable medium) storing computer-executable code, wherein the code, when executed by a processor, causes the processor to implement any one of aspects 18 to 27.

Claims

1. An apparatus for wireless communication at a server, the apparatus comprising: at least one memory; at least one transceiver; and at least one processor coupled to the at least one memory and the at least one transceiver, the at least one processor, individually or in any combination, configured to: receive, via the at least one transceiver, first information from a user equipment (UE), the first information related to a set of occupants in a vehicle and at least one characteristic for at least one occupant of the set of occupants; select at least one target location based on the first information; and transmit, to the UE, an indication of the selected at least one target location.

2. The apparatus of claim 1, wherein the set of occupants comprises at least one human, at least one animal, or a combination thereof.

3. The apparatus of claim 1, wherein the at least one characteristic comprises: an age of an occupant, a gender of the occupant, a species of the occupant, a size of the occupant, a posture of the occupant, a mode of the occupant, a behavior of the occupant, or a combination thereof.

4. The apparatus of claim 1, wherein to receive the first information, the at least one processor, individually or in any combination, is configured to: receive the first information via an in-cabin monitoring system (ICMS) associated with the vehicle.

5. The apparatus of claim 1, wherein the at least one processor, individually or in any combination, is further configured to: receive, from the UE, a second indication of at least one of: a first number of occupants in the set of occupants, a second number of occupants having an age above or below an age threshold, a behavior pattern of the set of occupants, one or more keywords detected in the vehicle, a speed of the vehicle, a travel time of the vehicle, an input destination of the vehicle, a previous stop location of the vehicle, feedback or recommendations from the set of occupants, or a combination thereof; and wherein the selection of the at least one target location is further based on the second indication.

6. The apparatus of claim 1, wherein to select the at least one target location, the at least one processor, individually or in any combination, is configured to: select the at least one target location further based on at least one of: a time of day, a first number of occupants in the set of occupants, a second number of occupants having an age above or below an age threshold, a behavior pattern of the set of occupants, one or more keywords detected in the vehicle, a travel time of the vehicle, an input destination of the vehicle, a previous stop location of the vehicle, feedback or recommendations from the set of occupants, or a speed of the vehicle.

7. The apparatus of claim 1, wherein the UE is the vehicle, an on-board unit (OBU) in the vehicle, or a mobile device.

8. The apparatus of claim 1, wherein the at least one processor, individually or in any combination, is further configured to: ​ obtaining second information based on crowd-sourcing prior to the selection of the at least one target location, wherein to select the at least one target location, the at least one processor, singly or in any combination, is configured to further select the at least one target location based on the second information.

9. The apparatus of claim 8, wherein to obtain the second information based on the crowd-sourcing, the at least one processor, singly or in any combination, is configured to: collect third information from each UE in a set of UEs, the third information relating to a set of second occupants in a second vehicle and at least one second characteristic for at least one occupant in the set of second occupants.

10. The apparatus of claim 1, wherein the at least one processor, singly or in any combination, is further configured to compute a probability that a route of the vehicle includes a set of target locations based on the first information, wherein to select the at least one target location based on the first information, the at least one processor, singly or in any combination, is configured to select the at least one target location in the set of target locations based on the first information based on the probability being greater than a threshold probability.

11. The apparatus of claim 10, wherein the set of target locations includes at least one of: a set of stops along the route, wherein the set of stops includes a set of second locations where the vehicle is not moving, or a set of first locations where a speed of the vehicle is less than a threshold speed.

12. The apparatus of claim 11, wherein to compute the probability that the route of the vehicle includes the set of target locations, the at least one processor, singly or in any combination, is configured to: detect that at least one occupant in the set of occupants is exhibiting a defined sign or a defined pattern associated with looking for the set of first locations or the set of stops.

13. The apparatus of claim 10, wherein the computation of the probability that the route of the vehicle includes the set of target locations is further based on at least one of: a time of day, second information from crowd-sourcing, or a combination thereof.

14. A method of wireless communication at a server, comprising: receiving first information from a user equipment (UE), the first information relating to a set of occupants in a vehicle and at least one characteristic for at least one occupant in the set of occupants; selecting at least one target location based on the first information; and transmitting an indication of the selected at least one target location to the UE.

15. The method of claim 14, further comprising: receiving, from the UE, a second indication of at least one of: a first number of occupants in the set of occupants, a second number of occupants having an age above or below an age threshold, a behavioral pattern of the set of occupants, one or more keywords detected in the vehicle, a speed of the vehicle, a travel time of the vehicle, an input destination of the vehicle, a previous stop location of the vehicle, ​ feedback or recommendations from the set of occupants, or a combination thereof; and wherein the selection of the at least one target location is further based on the second indication.

16. The method of claim 14, wherein selecting the at least one target location comprises selecting the at least one target location further based on at least one of: a time of day, a first number of occupants in the set of occupants, a second number of occupants older or younger than an age threshold, a behavior pattern of the set of occupants, one or more keywords detected in the vehicle, a travel time of the vehicle, an input destination of the vehicle, a previous stop location of the vehicle, feedback or recommendations from the set of occupants, or a speed of the vehicle.

17. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: at least one memory; and at least one processor coupled to the at least one memory, the at least one processor, individually or in any combination, configured to: send, to a server, first information related to a set of occupants in a vehicle and at least one characteristic for at least one occupant in the set of occupants; and receive, from the server, an indication of at least one target location in a set of target locations based on the first information and based on second information from a crowdsource.

18. The apparatus of claim 17, wherein the set of target locations comprises at least one of: a set of stops along a route, wherein the set of stops comprises a set of second locations where the vehicle did not move, or a first set of locations where a speed of the vehicle is less than a threshold speed.

19. The apparatus of claim 17, wherein the set of occupants comprises at least one human, at least one animal, or a combination thereof.

20. The apparatus of claim 17, wherein the at least one characteristic comprises: an age of an occupant, a gender of the occupant, a species of the occupant, a size of the occupant, a posture of the occupant, a pattern of the occupant, a behavior of the occupant, or a combination thereof.

21. The apparatus of claim 17, wherein the at least one processor, individually or in any combination, is further configured to: detect the first information via an in-cabin monitoring system (ICMS) prior to the sending of the first information.

22. The apparatus of claim 17, wherein the at least one processor, individually or in any combination, is further configured to: send, to the server, a second indication of at least one of: a first number of occupants in the set of occupants, a second number of occupants older or younger than an age threshold, a behavior pattern of the set of occupants, one or more keywords detected in the vehicle, a speed of the vehicle, a travel time of the vehicle, an input destination of the vehicle, a previous stop location of the vehicle, feedback or recommendations from the set of occupants, or a combination thereof; and wherein the selection of the at least one target location is further based on the second indication. wherein the at least one target location of the set of target locations is further based on the second indication.

23. The apparatus of claim 17, wherein the UE is the vehicle, an on-board unit (OBU) in the vehicle, or a mobile device.

24. The apparatus of claim 17, wherein the at least one processor is further configured to, individually or in any combination: detect that the vehicle is in a parked gear or a stop time of the vehicle exceeds a time threshold; and send, to the server, the first information and third information associated with a location of the vehicle based on the detection.

25. The apparatus of claim 17, wherein the at least one processor is further configured to, individually or in any combination: record a set of behavior patterns of at least one occupant of the set of occupants while the vehicle is moving; and send, to the server, the set of behavior patterns based on detecting that the vehicle is in a parked gear or a stop time of the vehicle exceeds a time threshold.

26. The apparatus of claim 17, wherein the at least one processor is further configured to, individually or in any combination: calculate a duration of time that the vehicle stops at a location; and send, to the server, the calculated duration of time that the vehicle stops at the location.

27. The apparatus of claim 17, further comprising at least one of a transceiver or an antenna coupled to the at least one processor, wherein to receive the indication of the at least one target location, the at least one processor is configured to, individually or in any combination, receive the indication of the at least one target location from the server via at least one of the transceiver or the antenna.

28. A method of wireless communication at a user equipment (UE), the method comprising: sending, to a server, first information related to a set of occupants in a vehicle and at least one characteristic for at least one occupant of the set of occupants; and receiving, from the server, an indication of at least one target location of a set of target locations based on the first information and based on second information from a crowd-sourcing.

29. The method of claim 28, the method further comprising: sending, to the server, a second indication of at least one of: a first number of occupants of the set of occupants, a second number of occupants with an age above or below an age threshold, a behavior pattern of the set of occupants, one or more keywords detected in the vehicle, a speed of the vehicle, a travel time of the vehicle, an input destination of the vehicle, a previous stop location of the vehicle, feedback or recommendations from the set of occupants, or a combination thereof; and wherein the at least one target location of the set of target locations is further based on the second indication.

30. The method of claim 28, the method further comprising: detecting that the vehicle is in a parking gear or that a stop time of the vehicle exceeds a time threshold; and sending, based on the detection, the first information and third information associated with a location of the vehicle to the server.

Images