Reporting framework for machine learning based positioning measurements
By using the channel characteristics derived by machine learning models in wireless communication systems, the problem of insufficient positioning accuracy and efficiency in 5G networks is solved, precise position measurement in higher frequency bands and high-density deployment environments is achieved, and the 5G network is enhanced Positioning ability.
Patent Information
- Application Number
- CN202380035646.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2022-04-29
- Filing Date
- 2023-04-26
- Publication Date
- 2024-12-03
AI Technical Summary
Existing wireless communication systems have shortcomings in positioning accuracy and efficiency, especially in 5G networks, especially in high-frequency band and high-density deployment environments, which are difficult to achieve highly accurate position measurement.
By deducing wireless channel features using machine learning models between network nodes and entities, more precise location information transmission is achieved, and a mechanism of requesting and providing location information messages is adopted to use the channel features derived from machine learning models for positioning measurement.
It improves the positioning accuracy and efficiency of wireless communication systems, adapts to the position measurement needs in high-frequency band and high-density deployment environments, and enhances the positioning capabilities of 5G networks.
Smart Images

Figure CN119072939A_ABST
Abstract
Description
[0001] CROSS-REFERENCE TO RELATED APPLICATIONS
[0002] This patent application claims priority to Greek patent application No. 20220100355, filed on April 29, 2022, entitled "REPORTING FRAMEWORK FOR MACHINE LEARNING-BASED MEASUREMENT FOR POSITIONING", which has been assigned to the assignee of this application and is expressly incorporated herein by reference in its entirety. Background Art Technical Field
[0003] Aspects of the present disclosure relate generally to wireless communications.
[0004] 2. Description of related technologies
[0005] Wireless communication systems have evolved over several generations, including first generation analog wireless telephone service (1G), second generation (2G) digital wireless telephone service (including transitional 2.5G and 2.75G networks), third generation (3G) high speed data, wireless service with Internet capabilities, and fourth generation (4G) service (e.g., Long Term Evolution (LTE) or WiMax). There are many different types of wireless communication systems in use today, including cellular systems and personal communications service (PCS) systems. Examples of known cellular systems include the cellular analog Advanced Mobile Phone System (AMPS), and digital cellular systems based on code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), Global System for Mobile Communications (GSM), and the like.
[0006] The fifth generation (5G) wireless standard, known as New Radio (NR), enables higher data transfer speeds, a greater number of connections, and better coverage, among other improvements. According to the Next Generation Mobile Networks Alliance, the 5G standard is designed to provide higher data rates, more accurate positioning (e.g., based on reference signals for positioning (RS-P), such as downlink, uplink, or sidelink positioning reference signals (PRS)), and other technical enhancements compared to previous standards. These enhancements, along with the use of higher frequency bands, advances in PRS procedures and technologies, and high-density deployments of 5G, enable highly accurate 5G-based positioning. Summary of the invention
[0007] The following presents a simplified summary of the invention related to one or more aspects disclosed herein. Thus, the following summary of the invention should neither be considered as an exhaustive overview related to all conceived aspects, nor should it be considered to identify key or decisive elements related to all conceived aspects or to delineate the scope associated with any particular aspect. Therefore, the sole purpose of the following summary of the invention is to present certain concepts related to one or more aspects related to the mechanisms disclosed herein in a brief form before the detailed embodiments presented below.
[0008] On the one hand, a method of wireless communication performed by a first network node includes: receiving one or more request location information messages from a network entity, wherein the one or more request location information messages configure the first network node to use machine learning to derive one or more characteristics of a wireless channel between the first network node and a second network node; and sending one or more provide location information messages to the network entity, wherein the one or more provide location information messages include the one or more characteristics of the wireless channel, and wherein the one or more characteristics of the wireless channel are derived based on a machine learning model.
[0009] On the one hand, a communication method performed by a network entity includes: sending one or more request location information messages to a first network node, wherein the one or more request location information messages configure the first network node to use machine learning to derive one or more characteristics of a wireless channel between the first network node and a second network node; and receiving one or more provide location information messages from the first network node, wherein the one or more provide location information messages include the one or more characteristics of the wireless channel, and wherein the one or more characteristics of the wireless channel are derived based on a machine learning model.
[0010] In one aspect, a first network node comprises: a memory; at least one transceiver; and at least one processor, the at least one processor communicatively coupling the memory and the at least one transceiver, the at least one processor being configured to: receive one or more request location information messages from a network entity via the at least one transceiver, wherein the one or more request location information messages configure the first network node to use machine learning to derive one or more characteristics of a wireless channel between the first network node and a second network node; and send one or more provide location information messages to the network entity via the at least one transceiver, wherein the one or more provide location information messages include the one or more characteristics of the wireless channel, and wherein the one or more characteristics of the wireless channel are derived based on a machine learning model.
[0011] In one aspect, a network entity includes: a memory; at least one transceiver; and at least one processor, the at least one processor communicatively coupling the memory and the at least one transceiver, the at least one processor being configured to: send one or more request location information messages to a first network node via the at least one transceiver, wherein the one or more request location information messages configure the first network node to use machine learning to derive one or more characteristics of a wireless channel between the first network node and a second network node; and receive one or more provide location information messages from the first network node via the at least one transceiver, wherein the one or more provide location information messages include the one or more characteristics of the wireless channel, and wherein the one or more characteristics of the wireless channel are derived based on a machine learning model.
[0012] In one aspect, a first network node comprises: a component for receiving one or more request location information messages from a network entity, wherein the one or more request location information messages configure the first network node to use machine learning to derive one or more characteristics of a wireless channel between the first network node and a second network node; and a component for sending one or more provide location information messages to the network entity, wherein the one or more provide location information messages include the one or more characteristics of the wireless channel, and wherein the one or more characteristics of the wireless channel are derived based on a machine learning model.
[0013] In one aspect, a network entity includes: a component for sending one or more request location information messages to a first network node, wherein the one or more request location information messages configure the first network node to use machine learning to derive one or more characteristics of a wireless channel between the first network node and a second network node; and a component for receiving one or more provide location information messages from the first network node, wherein the one or more provide location information messages include the one or more characteristics of the wireless channel, and wherein the one or more characteristics of the wireless channel are derived based on a machine learning model.
[0014] In one aspect, a non-transitory computer-readable medium stores computer-executable instructions that, when executed by a first network node, cause the first network node to: receive one or more request location information messages from a network entity, wherein the one or more request location information messages configure the first network node to use machine learning to derive one or more characteristics of a wireless channel between the first network node and a second network node; and send one or more provide location information messages to the network entity, wherein the one or more provide location information messages include the one or more characteristics of the wireless channel, and wherein the one or more characteristics of the wireless channel are derived based on a machine learning model.
[0015] In one aspect, a non-transitory computer-readable medium stores computer-executable instructions that, when executed by a network entity, cause the network entity to: send one or more request location information messages to a first network node, wherein the one or more request location information messages configure the first network node to use machine learning to derive one or more characteristics of a wireless channel between the first network node and a second network node; and receive one or more provide location information messages from the first network node, wherein the one or more provide location information messages include the one or more characteristics of the wireless channel, and wherein the one or more characteristics of the wireless channel are derived based on a machine learning model.
[0016] Other objects and advantages associated with the various aspects disclosed herein will be apparent to those skilled in the art based on the drawings and detailed description. BRIEF DESCRIPTION OF THE DRAWINGS
[0017] The accompanying drawings are presented to aid in describing various aspects of the present disclosure and are provided solely for illustration and not limitation of the various aspects.
[0018] Figure 1 An example wireless communication system in accordance with aspects of the present disclosure is illustrated.
[0019] Figure 2A , Figure 2B and Figure 2C Example wireless network structures according to aspects of the present disclosure are illustrated.
[0020] Figure 3A , Figure 3B and Figure 3C is a simplified block diagram of several sample aspects of components that may be employed in a user equipment (UE), a base station, and a network entity, respectively, and configured to support communications as taught herein.
[0021] Figure 4 Examples of various positioning methods supported in New Radio (NR) according to aspects of the present disclosure are illustrated.
[0022] Figure 5 Example Long Term Evolution (LTE) Positioning Protocol (LPP) procedures between a UE and a location server for performing positioning operations according to aspects of the present disclosure are illustrated.
[0023] Figure 6 is a diagram illustrating an example frame structure according to aspects of the present disclosure.
[0024] Figure 7 is a diagram representing example radio frequency (RF) channel estimation in accordance with aspects of the present disclosure.
[0025] Figure 8 Example neural networks in accordance with aspects of the present disclosure are illustrated.
[0026] Fig. 9 Machine learning based information elements in a request for a location information message in accordance with aspects of the present disclosure are illustrated.
[0027] Fig.10 Machine learning based parameters that may be added to a request location information message for an existing positioning method are illustrated in accordance with aspects of the present disclosure.
[0028] Fig.11 and Fig.12
[0013] Example methods of wireless communications in accordance with aspects of the present disclosure are illustrated. DETAILED DESCRIPTION
[0029] Various aspects of the present disclosure are provided in the following description and related drawings for various examples provided for illustrative purposes. Alternative aspects may be designed without departing from the scope of the present disclosure. In addition, well-known elements of the present disclosure will not be described in detail or will be omitted to avoid making the relevant details of the present disclosure difficult to understand.
[0030] The words "exemplary" and / or "example" are used herein to mean "serving as an example, instance, or illustration." Any aspect described herein as "exemplary" and / or "example" is not necessarily to be construed as preferred or advantageous over other aspects. Likewise, the term "aspects of the disclosure" does not require that all aspects of the disclosure include the discussed feature, advantage, or mode of operation.
[0031] Those skilled in the art will appreciate that any of a variety of different techniques and methods may be used to represent the information and signals described below. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be mentioned throughout the following description may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or optical particles, or any combination thereof, which depends in part on the specific application, in part on the desired design, in part on the corresponding technology, and so on.
[0032] In addition, many aspects are described in terms of a sequence of actions to be performed by, for example, an element of a computing device. It should be understood that the various actions described herein may be performed by a specific circuit (e.g., an application specific integrated circuit (ASIC)), by program instructions executed by one or more processors, or by a combination of the two. Additionally, the sequence of actions described herein may be considered to be fully embodied in any form of non-transient computer-readable storage medium, in which a corresponding computer instruction set is stored, which, when executed, will cause or command the associated processor of the device to perform the functionality described herein. Therefore, various aspects of the present disclosure may be embodied in a variety of different forms, all of which have been contemplated to be within the scope of the subject matter claimed. In addition, for each of the various aspects described herein, the corresponding form of any such aspect may be described herein as, for example, "logic configured to perform the described actions".
[0033] As used herein, unless otherwise specified, the terms "user equipment" (UE) and "base station" are not intended to be dedicated to or otherwise limited to any specific radio access technology (RAT). In general, a UE may be any wireless communication device (e.g., a mobile phone, a router, a tablet computer, a laptop computer, a consumer asset location device, a wearable device (e.g., a smart watch, glasses, an augmented reality (AR) / virtual reality (VR) head-mounted device, etc.), a vehicle (e.g., a car, a motorcycle, a bicycle, etc.), an Internet of Things (IoT) device, etc.) used by a user to communicate over a wireless communication network. A UE may be mobile or may be stationary (e.g., at certain times) and may communicate with a radio access network (RAN). As used herein, the term "UE" may be interchangeably referred to as an "access terminal" or "AT", "client device", "wireless device", "subscriber device", "subscriber terminal", "subscriber station", "user terminal" or "UT", "mobile device", "mobile terminal", "mobile station" or variations thereof. In general, a UE may communicate with a core network via a RAN, and through the core network, the UE may connect to external networks such as the Internet and to other UEs. Of course, other mechanisms for the UE to connect to the core network and / or the Internet are also possible, such as through a wired access network, a wireless local area network (WLAN) network (e.g., based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 specification, etc.), etc.
[0034] A base station may operate according to one of several RATs to communicate with a UE, depending on the network in which the base station is deployed, and may alternatively be referred to as an access point (AP), a network node, a Node B, an evolved Node B (eNB), a next generation eNB (ng-eNB), a new radio (NR) Node B (also referred to as a gNB or gNodeB), etc. A base station may be primarily used to support wireless access for UEs, including supporting data, voice, and / or signaling connections for supported UEs. In some systems, a base station may only provide edge node signaling functions, while in other systems, it may provide additional control and / or network management functions. The communication link by which a UE may transmit a signal to a base station is referred to as an uplink (UL) channel (e.g., a reverse traffic channel, a reverse control channel, an access channel, etc.). The communication link by which a base station may transmit a signal to a UE is referred to as a downlink (DL) or forward link channel (e.g., a paging channel, a control channel, a broadcast channel, a forward traffic channel, etc.). As used herein, the term "traffic channel (TCH)" may refer to an uplink / reverse traffic channel or a downlink / forward traffic channel.
[0035] The term "base station" may refer to a single physical transmit receive point (TRP) or multiple physical TRPs that may or may not be co-located. For example, where the term "base station" refers to a single physical TRP, the physical TRP may be an antenna of the base station corresponding to a cell (or several cell sectors) of the base station. Where the term "base station" refers to multiple co-located physical TRPs, the physical TRP may be an antenna array of a base station (e.g., as in a multiple-input multiple-output (MIMO) system or where the base station employs beamforming). Where the term "base station" refers to multiple non-co-located physical TRPs, the physical TRP may be a distributed antenna system (DAS) (a network of spatially separated antennas connected to a common source via a transmission medium) or a remote radio head (RRH) (a remote base station connected to a serving base station). Alternatively, the non-co-located physical TRP may be a serving base station that receives measurement reports from the UE and a neighboring base station whose reference radio frequency (RF) signal the UE is measuring. Since, as used herein, a TRP is the point through which a base station transmits and receives wireless signals, references to transmitting from or receiving at a base station should be understood to refer to the specific TRP of a base station.
[0036] In some specific implementations of supporting UE positioning, the base station may not support wireless access for the UE (e.g., may not support data, voice and / or signaling connections for the UE), but may instead send a reference signal to be measured by the UE to the UE and / or may receive and measure a signal sent by the UE. Such a base station may be referred to as a positioning beacon (e.g., in the case of sending a signal to the UE) and / or as a position measurement unit (e.g., in the case of receiving and measuring a signal from the UE).
[0037] An "RF signal" includes an electromagnetic wave of a given frequency that transmits information through the space between a transmitter and a receiver. As used herein, a transmitter may transmit a single "RF signal" or multiple "RF signals" to a receiver. However, due to the propagation characteristics of RF signals through multipath channels, a receiver may receive multiple "RF signals" corresponding to each transmitted RF signal. The same transmitted RF signal on different paths between a transmitter and a receiver may be referred to as a "multipath" RF signal. As used herein, an RF signal may also be referred to as a "wireless signal" or simply a "signal" where it is clear from the context that the term "signal" refers to a wireless signal or an RF signal.
[0038] Figure 1 An example wireless communication system 100 according to various aspects of the present disclosure is illustrated. The wireless communication system 100 (which may also be referred to as a wireless wide area network (WWAN)) may include various base stations 102 (labeled as "BS") and various UEs 104. The base stations 102 may include macro cell base stations (high power cellular base stations) and / or small cell base stations (low power cellular base stations). In one aspect, the macro cell base stations may include eNBs and / or ng-eNBs (where the wireless communication system 100 corresponds to an LTE network), or gNBs (where the wireless communication system 100 corresponds to an NR network), or a combination of the two, and the small cell base stations may include femto cells, pico cells, micro cells, etc.
[0039] The base stations 102 may collectively form a RAN and interface with a core network 170 (e.g., an evolved packet core (EPC) or a 5G core (5GC)) through a backhaul link 122, and interface with one or more location servers 172 (e.g., a location management function (LMF) or a secure user plane location (SUPL) location platform (SLP)) through the core network 170. The location server 172 may be part of the core network 170 or may be external to the core network 170. The location server 172 may be integrated with the base station 102. The UE 104 may communicate with the location server 172 directly or indirectly. For example, the UE 104 may communicate with the location server 172 via the base station 102 currently serving the UE 104. The UE 104 may also communicate with the location server 172 via another path, such as via an application server (not shown), via another network, such as via a wireless local area network (WLAN) access point (AP) (e.g., AP 150 described below), and the like. For signaling purposes, communication between UE 104 and location server 172 may be represented as an indirect connection (e.g., through core network 170, etc.) or a direct connection (e.g., as shown via direct connection 128), with intermediate nodes (if any) omitted from the signaling diagram for clarity.
[0040] Among other functions, the base station 102 may perform functions related to one or more of the following: delivering user data, radio channel encryption and decryption, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection establishment and release, load balancing, distribution of non-access stratum (NAS) messages, NAS node selection, synchronization, RAN sharing, multimedia broadcast multicast service (MBMS), subscriber and equipment tracking, RAN information management (RIM), paging, positioning, and delivery of warning messages. The base stations 102 may communicate with each other directly or indirectly (e.g., through EPC / 5GC) via a backhaul link 134, which may be wired or wireless.
[0041] Base station 102 may communicate wirelessly with UE 104. Each of base stations 102 may provide communication coverage for a corresponding geographic coverage area 110. In one aspect, one or more cells may be supported by base station 102 in each geographic coverage area 110. A "cell" is a logical communication entity used to communicate with a base station (e.g., on a frequency resource, which is referred to as a carrier frequency, component carrier, carrier, frequency band, etc.), and may be associated with an identifier (e.g., a physical cell identifier (PCI), an enhanced cell identifier (ECI), a virtual cell identifier (VCI), a cell global identifier (CGI), etc.) used to distinguish cells operating via the same or different carrier frequencies. In some cases, different cells may be configured according to different protocol types (e.g., machine type communication (MTC), narrowband IoT (NB-IoT), enhanced mobile broadband (eMBB), or other protocol types) that may provide access to different types of UEs. Since a cell is supported by a specific base station, the term "cell" may refer to one or both of the logical communication entity and the base station supporting it, depending on the context. In addition, since the TRP is generally the physical transmission point of the cell, the terms "cell" and "TRP" may be used interchangeably. In some cases, the term "cell" may also refer to a geographic coverage area (e.g., a sector) of a base station, as long as a carrier frequency can be detected and used for communications within a portion of the geographic coverage area 110.
[0042] Although the geographic coverage areas 110 of neighboring macrocell base stations 102 may partially overlap (e.g., in a handover region), some of the geographic coverage areas 110 may substantially overlap with the larger geographic coverage areas 110. For example, a small cell base station 102' (labeled "SC" for "small cell") may have a geographic coverage area 110' that substantially overlaps with the geographic coverage areas 110 of one or more macrocell base stations 102. A network that includes both small cell base stations and macrocell base stations may be referred to as a heterogeneous network. A heterogeneous network may also include a home eNB (HeNB), which may provide services to a restricted group called a closed subscriber group (CSG).
[0043] The communication link 120 between the base station 102 and the UE 104 may include uplink (also referred to as reverse link) transmissions from the UE 104 to the base station 102 and / or downlink (DL) (also referred to as forward link) transmissions from the base station 102 to the UE 104. The communication link 120 may use MIMO antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link 120 may be over one or more carrier frequencies. The allocation of carriers may be asymmetric for the downlink and uplink (e.g., more or fewer carriers may be allocated to the downlink than to the uplink).
[0044] The wireless communication system 100 may also include a WLAN access point (AP) 150 that communicates with a wireless local area network (WLAN) station (STA) 152 in an unlicensed spectrum (e.g., 5 GHz) via a communication link 154. When communicating in the unlicensed spectrum, the WLAN STA 152 and / or the WLAN AP 150 may perform a clear channel assessment (CCA) or listen before talk (LBT) procedure prior to communication to determine whether a channel is available.
[0045] The small cell base station 102' can operate in licensed and / or unlicensed spectrum. When operating in the unlicensed spectrum, the small cell base station 102' can adopt LTE or NR technology and use the same 5GHz unlicensed spectrum used by the WLAN AP 150. The small cell base station 102' using LTE / 5G in the unlicensed spectrum can improve the coverage of the access network and / or increase the capacity of the access network. NR in the unlicensed spectrum can be referred to as NR-U. LTE in the unlicensed spectrum can be referred to as LTE-U, License Assisted Access (LAA) or MulteFire.
[0046] The wireless communication system 100 may also include a millimeter wave (mmW) base station 180, which can operate at mmW frequencies and / or near mmW frequencies to communicate with UE 182. Extremely high frequency (EHF) is a part of RF in the electromagnetic spectrum. EHF has a range of 30GHz to 300GHz, and the wavelength is between 1 mm and 10 mm. The radio waves in this band may be referred to as millimeter waves. Near mmW can be extended downward to a frequency of 3GHz, where the wavelength is 100 mm. The super high frequency (SHF) band extends between 3GHz and 30GHz, which is also referred to as centimeter waves. Communication using mmW / near mmW radio frequency bands has high path loss and relatively short distances. The mmW base station 180 and the UE 182 can compensate for the extremely high path loss and short distance by using beamforming (sending and / or receiving) through the mmW communication link 184. In addition, it should be understood that in an alternative configuration, one or more base stations 102 may also use mmW or near mmW and beamforming for transmission. Therefore, it should be understood that the foregoing illustrations are merely examples and should not be construed as limiting the various aspects disclosed herein.
[0047] Transmit beamforming is a technique for focusing an RF signal in a specific direction. Traditionally, when a network node (e.g., a base station) broadcasts an RF signal, it broadcasts the signal in all directions (omnidirectionally). With transmit beamforming, the network node determines where a given target device (e.g., a UE) is located (relative to the transmitting network node) and projects a stronger downlink RF signal in that specific direction, thereby providing a faster (in terms of data rate) and stronger RF signal to the receiving device. In order to change the directionality of the RF signal when transmitting, the network node can control the phase and relative amplitude of the RF signal at each of the one or more transmitters that broadcast the RF signal. For example, a network node can use an array of antennas (referred to as a "phased array" or "antenna array") that creates RF beams that can be "steered" to point in different directions without actually moving the antenna. Specifically, the RF current from the transmitter is fed to each antenna in the correct phase relationship so that the radio waves from the separate antennas are added together to increase the radiation in the desired direction while canceling to suppress the radiation in the undesired direction.
[0048] The transmit beams can be quasi-co-located, which means that they appear to the receiver (e.g., UE) to have the same parameters, regardless of whether the network node's own transmit antenna is physically co-located. In NR, there are four types of quasi-co-location (QCL) relationships. Specifically, a given type of QCL relationship means that certain parameters about the second reference RF signal on the second beam can be derived based on information about the source reference RF signal on the source beam. Therefore, if the source reference RF signal is QCL type A, the receiver can use the source reference RF signal to estimate the Doppler shift, Doppler spread, average delay and delay spread of the second reference RF signal sent on the same channel. If the source reference RF signal is QCL type B, the receiver can use the source reference RF signal to estimate the Doppler shift and Doppler spread of the second reference RF signal sent on the same channel. If the source reference RF signal is QCL type C, the receiver can use the source reference RF signal to estimate the Doppler shift and average delay of the second reference RF signal sent on the same channel. If the source reference RF signal is QCL type D, the receiver may use the source reference RF signal to estimate spatial reception parameters of a second reference RF signal transmitted on the same channel.
[0049] In receive beamforming, the receiver uses receive beams to amplify RF signals detected on a given channel. For example, the receiver may increase the gain setting of the antenna array in a particular direction and / or adjust the phase setting of the antenna array in a particular direction to amplify the RF signals received from that direction (e.g., increase their gain level). Therefore, when a receiver is said to perform beamforming in a certain direction, it means that the beam gain in that direction is high relative to the beam gain along other directions, or the beam gain in that direction is the highest compared to the beam gain in that direction of all other receive beams available to the receiver. This results in a stronger received signal strength (e.g., reference signal received power (RSRP), reference signal received quality (RSRQ), signal to interference plus noise ratio (SINR), etc.) of the RF signal received from that direction.
[0050] The transmit beam and the receive beam may be spatially correlated. The spatial relationship means that parameters of a second beam (e.g., a transmit beam or a receive beam) for a second reference signal may be derived based on information about a first beam (e.g., a receive beam or a transmit beam) for a first reference signal. For example, a UE may use a specific receive beam to receive a reference downlink reference signal (e.g., a synchronization signal block (SSB)) from a base station. The UE may then form a transmit beam for transmitting an uplink reference signal (e.g., a sounding reference signal (SRS)) to the base station based on the parameters of the receive beam.
[0051] Note that depending on the entity forming the "downlink" beam, the beam can be a transmit beam or a receive beam. For example, if the base station is forming a downlink beam to send a reference signal to the UE, the downlink beam is a transmit beam. However, if the UE is forming a downlink beam, the downlink beam is a receive beam that receives a downlink reference signal. Similarly, depending on the entity forming the "uplink" beam, the beam can be a transmit beam or a receive beam. For example, if the base station is forming an uplink beam, it is an uplink receive beam, while if the UE is forming an uplink beam, it is an uplink transmit beam.
[0052] The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc. based on frequency / wavelength. In 5G NR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz–7.125 GHz) and FR2 (24.25 GHz–52.6 GHz). It should be understood that, although portions of FR1 are greater than 6 GHz, FR1 is often (interchangeably) referred to as the “sub-6 GHz” band in various documents and articles. A similar naming issue sometimes occurs with respect to FR2, which is often (interchangeably) referred to as the “millimeter wave” band in documents and articles, despite being different from the extremely high frequency (EHF) band (30 GHz–300 GHz) identified as the “millimeter wave” band by the International Telecommunication Union (ITU).
[0053] Frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR research has identified the operating bands for these mid-band frequencies as frequency range designation FR3 (7.125GHz–24.25GHz). The bands falling within FR3 can inherit FR1 characteristics and / or FR2 characteristics, and therefore the features of FR1 and / or FR2 can be effectively extended to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operations to more than 52.6GHz. For example, three higher operating bands have been identified as frequency range designations FR4a or FR4-1 (52.6GHz–71GHz), FR4 (52.6GHz–114.25GHz), and FR5 (114.25GHz–300GHz). Each of these higher frequency bands falls within the EHF band.
[0054] In view of the above aspects, unless otherwise specifically stated, it should be understood that if the term "sub-6 GHz" or the like is used herein, it can broadly refer to frequencies that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies. In addition, unless otherwise specifically stated, it should be understood that if the term "millimeter wave" or the like is used herein, it can broadly refer to frequencies that may include mid-band frequencies, may be within FR2, FR4, FR4-a or FR4-1 and / or FR5, or may be within the EHF band.
[0055] In a multi-carrier system (such as 5G), one of the carrier frequencies is referred to as the "primary carrier" or "anchor carrier" or "primary serving cell" or "PCell", and the remaining carrier frequencies are referred to as "secondary carriers" or "secondary serving cells" or "SCells". In carrier aggregation, the anchor carrier is a carrier operating on the primary frequency (e.g., FR1) used by the UE 104 / 182 and the cell in which the UE 104 / 182 performs an initial radio resource control (RRC) connection establishment procedure or initiates an RRC connection re-establishment procedure. The primary carrier carries all common and UE-specific control channels and can be a carrier in a licensed frequency (however, this is not always the case). A secondary carrier is a carrier operating on a second frequency (e.g., FR2) that can be configured and used to provide additional radio resources once an RRC connection is established between the UE 104 and the anchor carrier. In some cases, the secondary carrier can be a carrier in an unlicensed frequency. The secondary carrier may contain only necessary signaling information and signals, for example, since the primary uplink carrier and the primary downlink carrier are usually UE-specific, those UE-specific signaling information and signals may not be present in the secondary carrier. This means that different UEs 104 / 182 in a cell may have different downlink primary carriers. The same is true for the uplink primary carrier. The network is able to change the primary carrier of any UE 104 / 182 at any time. This is done, for example, to balance the load on different carriers. Since a "serving cell" (whether PCell or SCell) corresponds to a carrier frequency / component carrier on which a base station communicates, the terms "cell", "serving cell", "component carrier", "carrier frequency", etc. are used interchangeably.
[0056] For example, still referring to Figure 1, one of the frequencies used by macrocell base station 102 may be an anchor carrier (or "PCell"), and the other frequencies used by macrocell base station 102 and / or mmW base station 180 may be secondary carriers ("SCells"). Simultaneous transmission and / or reception of multiple carriers enables UE 104 / 182 to significantly increase its data transmission and / or reception rate. For example, two 20 MHz aggregated carriers in a multi-carrier system would theoretically result in a doubling of the data rate (i.e., 40 MHz) compared to the data rate obtained with a single 20 MHz carrier.
[0057] The wireless communication system 100 may also include a UE 164, which may communicate with the macrocell base station 102 via a communication link 120 and / or communicate with the mmW base station 180 via a mmW communication link 184. For example, the macrocell base station 102 may support a PCell and one or more SCells for the UE 164, and the mmW base station 180 may support one or more SCells for the UE 164.
[0058] In some cases, UE 164 and UE 182 are capable of sidelink communication. A UE with sidelink capability (SL-UE) can communicate with base station 102 via communication link 120 using a Uu interface (i.e., an air interface between UE and base station). SL-UE (e.g., UE 164, UE 182) can also communicate directly with each other via a wireless sidelink 160 using a PC5 interface (i.e., an air interface between UEs with sidelink capability). A wireless sidelink (or just "sidelink") is an adaptation of a core cellular network (e.g., LTE, NR) standard that allows direct communication between two or more UEs without communicating through a base station. Sidelink communications can be unicast or multicast and can be used for device-to-device (D2D) media sharing, vehicle-to-vehicle (V2V) communications, vehicle-to-vehicle (V2X) communications (e.g., cellular V2X (cV2X) communications, enhanced V2X (eV2X) communications, etc.), emergency rescue applications, etc. One or more SL-UEs in a group of SL-UEs utilizing sidelink communications may be located within the geographic coverage area 110 of the base station 102. Other SL-UEs in such a group may be outside the geographic coverage area 110 of the base station 102, or may be unable to receive transmissions from the base station 102 for other reasons. In some cases, groups of SL-UEs communicating via sidelink communications may utilize a one-to-many (1:M) system, where each SL-UE transmits to each other SL-UE in the group. In some cases, the base station 102 facilitates the scheduling of resources for sidelink communications. In other cases, sidelink communications are performed between the SL-UEs without involving the base station 102.
[0059] In one aspect, the sidelink 160 may operate on a wireless communication medium of interest, which may be shared with other vehicles and / or infrastructure access points and other wireless communications between other RATs. A "medium" may include one or more time, frequency, and / or spatial communication resources associated with wireless communications between one or more transmitter / receiver pairs (e.g., covering one or more channels across one or more carriers). In one aspect, the medium of interest may correspond to at least a portion of an unlicensed band shared between various RATs. Although different licensed bands have been reserved for certain communication systems (e.g., by government entities such as the Federal Communications Commission (FCC) in the United States), these systems (particularly those employing small cell access points) have recently expanded operations into unlicensed bands such as the unlicensed National Information Infrastructure (U-NII) band used by wireless local area network (WLAN) technology (most notably the IEEE 802.11x WLAN technology commonly referred to as "Wi-Fi"). Example systems of this type include different variations of CDMA systems, TDMA systems, FDMA systems, orthogonal FDMA (OFDMA) systems, single carrier FDMA (SC-FDMA) systems, and the like.
[0060] Note that although Figure 1 Only two of these UEs are illustrated as SL-UEs (i.e., UEs 164 and 182), but any of the illustrated UEs may be SL-UEs. In addition, although only UE 182 is described as being capable of beamforming, any of the illustrated UEs (including UE 164) may be capable of beamforming. In the case where SL-UEs are capable of beamforming, they may beamform toward each other (i.e., toward other SL-UEs), toward other UEs (e.g., UE 104), toward base stations (e.g., base stations 102, 180, small cells 102', access point 150), etc. Therefore, in some cases, UE 164 and UE 182 may utilize beamforming via side link 160.
[0061] exist Figure 1 In the example of FIG. 1 , the UE illustrated (for simplicity, in Figure 1Any of the UEs 104 (shown as a single UE 104 in FIG. 1 ) may receive a signal 124 from one or more earth orbiting space vehicles (SVs) 112 (e.g., satellites). In one aspect, the SVs 112 may be part of a satellite positioning system that the UEs 104 may use as an independent source of location information. A satellite positioning system typically includes a transmitter system (e.g., SVs 112) positioned to enable a receiver (e.g., UE 104) to determine its position on or above the earth based at least in part on a positioning signal (e.g., signal 124) received from the transmitter. Such transmitters typically transmit signals marked with a repeating pseudo-random noise (PN) code of a set number of chips. Although typically located in the SVs 112, the transmitters may sometimes be located on ground-based control stations, base stations 102, and / or other UEs 104. The UEs 104 may include one or more dedicated receivers that are specifically designed to receive the signal 124 in order to derive geographic location information from the SVs 112.
[0062] In a satellite positioning system, the use of signal 124 may be enhanced by various satellite-based augmentation systems (SBAS) that may be associated with or otherwise enabled for use with one or more global and / or regional navigation satellite systems. For example, SBAS may include augmentation systems that provide integrity information, differential corrections, etc., such as Wide Area Augmentation System (WAAS), European Geostationary Navigation Overlay Service (EGNOS), Multifunction Satellite Augmentation System (MSAS), Global Positioning System (GPS) Assisted Geographic Augmented Navigation or GPS and Geographic Augmented Navigation System (GAGAN), etc. Thus, as used herein, a satellite positioning system may include any combination of one or more global and / or regional navigation satellites associated with such one or more satellite positioning systems.
[0063] In one aspect, SV 112 may additionally or alternatively be part of one or more non-terrestrial networks (NTNs). In an NTN, SV 112 is connected to an earth station (also referred to as a ground station, NTN gateway, or gateway), which in turn is connected to an element in a 5G network, such as an improved base station 102 (without a ground antenna) or a network node in a 5GC. This element in turn will provide access to other elements in the 5G network, and ultimately provide access to entities outside the 5G network (such as Internet web servers and other user devices). In this way, instead of or in addition to communication signals from a ground base station 102, a UE 104 may receive communication signals (e.g., signal 124) from SV 112.
[0064] The wireless communication system 100 may also include one or more UEs, such as UE 190, which are indirectly connected to one or more communication networks via one or more device-to-device (D2D) peer-to-peer (P2P) links (referred to as “side links”). Figure 1 In the example of FIG. 1 , UE 190 has a D2D P2P link 192 with one of UEs 104 connected to one of base stations 102 (e.g., UE 190 can indirectly obtain cellular connectivity through the link), and has a D2D P2P link 194 with WLAN STA 152 connected to WLAN AP 150 (UE 190 can indirectly obtain WLAN-based Internet connectivity through the link). In one example, D2D P2P links 192 and 194 can be supported by any well-known D2D RAT, such as LTE Direct (LTE-D), WiFi Direct (WiFi-D), etc.
[0065] Figure 2A An example wireless network structure 200 is illustrated. For example, the 5GC 210 (also referred to as the Next Generation Core (NGC)) can be functionally viewed as a control plane (C-plane) function 214 (e.g., UE registration, authentication, network access, gateway selection, etc.) and a user plane (U-plane) function 212 (e.g., UE gateway function, access to data networks, IP routing, etc.), which operate in conjunction to form a core network. The user plane interface (NG-U) 213 and the control plane interface (NG-C) 215 connect the gNB 222 to the 5GC 210, and specifically to the user plane function 212 and the control plane function 214, respectively. In an additional configuration, the ng-eNB 224 can also be connected to the 5GC 210 via the NG-C 215 to the control plane function 214 and the NG-U 213 to the user plane function 212. In addition, the ng-eNB 224 can communicate directly with the gNB 222 via the backhaul connection 223. In some configurations, the next generation RAN (NG-RAN) 220 may have one or more gNBs 222, while other configurations include one or more of ng-eNBs 224 and gNBs 222. Either the gNB 222 or the ng-eNB 224 (or both) may communicate with one or more UEs 204 (e.g., any of the UEs described herein).
[0066] Another optional aspect may include a location server 230 that can communicate with the 5GC 210 to provide location assistance for the UE 204. The location server 230 can be implemented as multiple separate servers (e.g., physically separate servers, different software modules on a single server, different software modules distributed across multiple physical servers, etc.), or alternatively can each correspond to a single server. The location server 230 can be configured to support one or more location services for the UE 204 that can be connected to the location server 230 via the core network, the 5GC 210, and / or via the Internet (not illustrated). In addition, the location server 230 can be integrated into a component of the core network, or alternatively can be external to the core network (e.g., a third-party server, such as an original equipment manufacturer (OEM) server or a service server).
[0067] Figure 2B Another example wireless network structure 240 is illustrated. 5GC 260 (which may correspond to Figure 2AThe 5GC 210 in the 5GC 210 can be functionally considered as a control plane function provided by an access and mobility management function (AMF) 264, and a user plane function provided by a user plane function (UPF) 262, which operate in conjunction to form a core network (i.e., 5GC 260). The functions of the AMF 264 include: registration management, connection management, reachability management, mobility management, lawful interception, transmission of session management (SM) messages between one or more UEs 204 (e.g., any UE described herein) and a session management function (SMF) 266, a transparent proxy service for routing SM messages, access authentication and access authorization, transmission of short message service (SMS) messages between the UE 204 and a short message service function (SMSF) (not shown), and security anchor functionality (SEAF). The AMF 264 also interacts with an authentication server function (AUSF) (not shown) and the UE 204, and receives an intermediate key established as a result of the UE 204 authentication process. In the case of authentication based on the UMTS (Universal Mobile Telecommunications System) Subscriber Identity Module (USIM), the AMF 264 retrieves security material from the AUSF. The functionality of the AMF 264 also includes security context management (SCM). The SCM receives keys from the SEAF, which it uses to derive access network specific keys. The functionality of the AMF 264 also includes location service management for regulatory services, for the transmission of location service messages between the UE 204 and the Location Management Function (LMF) 270 (which acts as a location server 230), for the transmission of location service messages between the NG-RAN 220 and the LMF 270, for the allocation of Evolved Packet System (EPS) bearer identifiers for interoperation with EPS, and UE 204 mobility event notifications. In addition, the AMF 264 also supports functionality for non-3GPP (Third Generation Partnership Project) access networks.
[0068] The functions of UPF 262 include: acting as an anchor point for intra-RAT / inter-RAT mobility (when applicable), acting as an external protocol data unit (PDU) session point for interconnection to a data network (not shown), providing packet routing and forwarding, packet inspection, user plane policy rule enforcement (e.g., gating, redirection, service steering), lawful interception (user plane collection), service usage reporting, user plane quality of service (QoS) handling (e.g., uplink / downlink rate enforcement, reflective QoS marking in downlink), uplink service verification (service data flow (SDF) to QoS flow mapping), transport level packet marking in uplink and downlink, downlink packet buffering and downlink data notification triggering, and transmitting and forwarding one or more "end markers" to the source RAN node. UPF 262 can also support the delivery of location service messages between UE 204 and a location server (such as SLP 272) on the user plane.
[0069] The functions of SMF 266 include session management, UE Internet Protocol (IP) address allocation and management, selection and control of user plane functions, traffic steering configuration at UPF 262 for routing traffic to the correct destination, partial control of policy implementation and QoS, and downlink data notification. The interface through which SMF 266 communicates with AMF 264 is called the N11 interface.
[0070] Another optional aspect may include an LMF 270 that can communicate with the 5GC 260 to provide location assistance for the UE 204. The LMF 270 can be implemented as multiple separate servers (e.g., physically separate servers, different software modules on a single server, different software modules distributed across multiple physical servers, etc.), or alternatively can each correspond to a single server. The LMF 270 can be configured to support one or more location services for the UE 204, which can be connected to the LMF 270 via the core network, the 5GC 260, and / or via the Internet (not illustrated). SLP 272 may support similar functionality as LMF 270, but LMF 270 may communicate with AMF 264, NG-RAN 220, and UE 204 on a control plane (e.g., using interfaces and protocols intended to carry signaling messages rather than voice or data), and SLP 272 may communicate with UE 204 and external clients (e.g., third-party servers 274) on a user plane (e.g., using protocols intended to carry voice and / or data, such as Transmission Control Protocol (TCP) and / or IP).
[0071] Yet another optional aspect may include a third-party server 274 that may communicate with the LMF 270, SLP 272, 5GC 260 (e.g., via AMF 264 and / or UPF 262), NG-RAN 220, and / or UE 204 to obtain location information (e.g., a location estimate) of the UE 204. Thus, in some cases, the third-party server 274 may be referred to as a location service (LCS) client or an external client. The third-party server 274 may be implemented as multiple separate servers (e.g., physically separate servers, different software modules on a single server, different software modules distributed across multiple physical servers, etc.), or alternatively may each correspond to a single server.
[0072] The user plane interface 263 and the control plane interface 265 connect the 5GC 260, and specifically the UPF 262 and the AMF 264, respectively, to one or more gNBs 222 and / or ng-eNBs 224 in the NG-RAN 220. The interface between the gNB 222 and / or ng-eNB 224 and the AMF 264 is referred to as the "N2" interface, and the interface between the gNB 222 and / or ng-eNB 224 and the UPF 262 is referred to as the "N3" interface. The gNBs 222 and / or ng-eNBs 224 of the NG-RAN 220 may communicate directly with each other via a backhaul connection 223 referred to as an "Xn-C" interface. One or more of the gNBs 222 and / or ng-eNBs 224 may communicate with one or more UEs 204 via a wireless interface referred to as a "Uu" interface.
[0073] The functionality of the gNB 222 is divided between a gNB central unit (gNB-CU) 226, one or more gNB distributed units (gNB-DU) 228, and one or more gNB radio units (gNB-RU) 229. The gNB-CU 226 is a logical node that includes base station functions other than those specifically assigned to the gNB-DU 228, including delivery of user data, mobility control, radio access network sharing, positioning, session management, etc. More specifically, the gNB-CU 226 generally hosts the radio resource control (RRC), service data adaptation protocol (SDAP), and packet data convergence protocol (PDCP) protocols of the gNB 222. The gNB-DU 228 is a logical node that generally hosts the radio link control (RLC) and medium access control (MAC) layers of the gNB 222. Its operation is controlled by the gNB-CU 226. One gNB-DU 228 can support one or more cells, and one cell is supported by only one gNB-DU 228. The interface 232 between the gNB-CU 226 and one or more gNB-DUs 228 is referred to as the "F1" interface. The physical (PHY) layer functionality of the gNB 222 is typically hosted by one or more independent gNB-RUs 229, which perform functions such as power amplification and signal transmission / reception. The interface between the gNB-DU 228 and the gNB-RU 229 is referred to as the "Fx" interface. Thus, the UE 204 communicates with the gNB-CU 226 via the RRC layer, the SDAP layer, and the PDCP layer, communicates with the gNB-DU 228 via the RLC layer and the MAC layer, and communicates with the gNB-RU 229 via the PHY layer.
[0074] The deployment of a communication system (such as a 5G NR system) can be arranged with various components or components in a variety of ways. In a 5G NR system or network, a network node, a network entity, a mobility element of a network, a RAN node, a core network node, a network element or a network equipment (such as a base station, or one or more units (or one or more components) that perform base station functionality) can be implemented in an aggregated or decomposed architecture. For example, a base station (such as a Node B (NB), an evolved NB (eNB), an NR base station, a 5G NB, an access point (AP), a transmit receive point (TRP) or a cell, etc.) can be implemented as an aggregated base station (also called a stand-alone base station or a single-chip base station) or a decomposed base station.
[0075] A converged base station may be configured to utilize a radio protocol stack physically or logically integrated within a single RAN node. A decomposed base station may be configured to utilize a protocol stack physically or logically distributed between two or more units, such as one or more central or centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs). In some aspects, a CU may be implemented within a RAN node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed in one or more other RAN nodes. A DU may be implemented to communicate with one or more RUs. Each of a CU, a DU, and a RU may also be implemented as a virtual unit, i.e., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).
[0076] Base station type operations or network designs may take into account the aggregated nature of base station functionality. For example, a disaggregated base station may be used in an integrated access backhaul (IAB) network, an open radio access network (O-RAN (network configurations such as those initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Decomposition may include distributing functionality across two or more units at various physical locations, as well as virtually distributing functionality of at least one unit, which may enable flexibility in network design. Individual units of a disaggregated base station or disaggregated RAN architecture may be configured for wired or wireless communication with at least one other unit.
[0077] Figure 2C An example disaggregated base station architecture 250 is illustrated in accordance with aspects of the present disclosure. The disaggregated base station architecture 250 may include one or more central units (CUs) 280 (e.g., gNB-CUs 226) that may communicate directly with a core network 267 (e.g., 5GC 210, 5GC 260) via a backhaul link, or indirectly with the core network 267 through one or more disaggregated base station units, such as a near real-time (near-RT) RAN intelligent controller (RIC) 259 via an E2 link, or a non-real-time (non-RT) RIC 257 associated with a service management and orchestration (SMO) framework 255, or both. The CU 280 may communicate with one or more distributed units (DUs) 285 (e.g., gNB-DUs 228) via respective midhaul links, such as an F1 interface. The DUs 285 may communicate with one or more radio units (RUs) 287 (e.g., gNB-RUs 229) via respective fronthaul links. The RU 287 can communicate with a corresponding UE 204 via one or more radio frequency (RF) access links. In some implementations, a UE 204 can be served by multiple RUs 287 simultaneously.
[0078] Each of these units (i.e., CU 280, DU 285, RU 287, and near-RT RIC 259, non-RT RIC 257, and SMO framework 255) may include or be coupled to one or more interfaces configured to receive or send signals, data, or information (collectively referred to as signals) via a wired or wireless transmission medium. Each of these units or an associated processor or controller that provides instructions to the communication interface of these units may be configured to communicate with one or more of the other units via a transmission medium. For example, these units may include a wired interface configured to receive or send signals to one or more of the other units via a wired transmission medium. Additionally, these units may include a wireless interface that may include a receiver, a transmitter, or a transceiver (such as a radio frequency (RF) transceiver) that is configured to receive or send signals, or both, to one or more of the other units via a wireless transmission medium.
[0079] In some aspects, CU 280 may host one or more higher layer control functions. Such control functions may include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), etc. Each control function may be implemented using an interface that is configured to communicate signals with other control functions hosted by CU 280. CU 280 may be configured to handle user plane functionality (i.e., central unit-user plane (CU-UP)), control plane functionality (i.e., central unit-control plane (CU-CP)), or a combination thereof. In some specific implementations, CU 280 may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). As needed, CU 280 may be implemented to communicate with DU 285 for network control and signaling.
[0080] DU 285 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 287. In some aspects, DU 285 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.) at least in part according to a functional split such as defined by the Third Generation Partnership Project (3GPP). In some aspects, DU 285 may further host one or more low PHY layers. Each layer (or module) may be implemented using an interface that is configured to communicate signals with other layers (and modules) hosted by DU 285 or with control functions hosted by CU 280.
[0081] The lower layer functionality may be implemented by one or more RUs 287. In some deployments, a RU 287 controlled by a DU 285 may correspond to a logical node that hosts RF processing functions or low PHY layer functions (such as performing Fast Fourier Transform (FFT), Inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.), or both, based at least in part on a functional split (such as a lower layer functional split). In such an architecture, the RU 287 may be implemented to handle over-the-air (OTA) communications with one or more UEs 204. In some implementations, real-time and non-real-time aspects of control plane and user plane communications with the RU 287 may be controlled by the corresponding DU 285. In some scenarios, this configuration may enable the implementation of the DU 285 and the CU 280 in a cloud-based RAN architecture (such as a vRAN architecture).
[0082] The SMO framework 255 may be configured to support RAN deployment and configuration of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 255 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO framework 255 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) 269) to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements may include, but are not limited to, CU 280, DU 285, RU 287, and near-RT RIC 259. In some specific implementations, the SMO framework 255 may communicate with hardware aspects of the 4G RAN (such as an open eNB (O-eNB) 261) via the O1 interface. Additionally, in some specific implementations, the SMO framework 255 may communicate directly with one or more RUs 287 via the O1 interface. The SMO framework 255 may also include a non-RT RIC 257 configured to support the functionality of the SMO framework 255 .
[0083] The non-RT RIC 257 may be configured to include logic functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 259. The non-RT RIC 257 may be coupled to or communicate with the near-RT RIC 259 (such as via an A1 interface). The near-RT RIC 259 may be configured to include logic functions that enable near-real-time control and optimization of RAN elements and resources via data collection and actions through an interface (such as via an E2 interface) that connects one or more CUs 280, one or more DUs 285, or both, and the O-eNB with the near-RT RIC 259.
[0084] In some implementations, in order to generate an AI / ML model to be deployed in the near-RT RIC 259, the non-RT RIC 257 may receive parameters or external enrichment information from an external server. Such information may be utilized by the near-RT RIC 259 and may be received from a non-network data source or from a network function at the SMO framework 255 or the non-RT RIC 257. In some examples, the non-RT RIC 257 or the near-RT RIC 259 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 257 may monitor long-term trends and patterns of performance and employ AI / ML models to perform corrective actions through the SMO framework 255 (such as via reconfiguration of O1) or via the creation of RAN management policies (such as A1 policies).
[0085] Figure 3A , Figure 3B and Figure 3C The example may be combined with UE 302 (which may correspond to any UE described herein), base station 304 (which may correspond to any base station described herein), and network entity 306 (which may correspond to or embody any network function described herein, including location server 230 and LMF 270, or alternatively may be independent of Figure 2A and Figure 2B Several example components (represented by corresponding boxes) in the NG-RAN 220 and / or 5GC 210 / 260 infrastructure depicted in the present invention (such as a dedicated network) are shown to support the operations described herein. It should be understood that these components can be implemented in different types of devices with different specific implementations (for example, in an ASIC, in a system on a chip (SoC), etc.). The illustrated components can also be incorporated into other devices in the communication system. For example, other devices in the system may include components similar to those described as providing similar functionality. Moreover, a given device may include one or more of these components. For example, a device may include multiple transceiver components that enable the device to operate on multiple carriers and / or communicate via different technologies.
[0086] UE 302 and base station 304 each include one or more wireless wide area network (WWAN) transceivers 310 and 350, respectively, which provide means (e.g., means for transmitting, means for receiving, means for measuring, means for tuning, means for preventing transmitting, etc.) for communicating via one or more wireless communication networks (not shown), such as NR networks, LTE networks, GSM networks, etc. WWAN transceivers 310 and 350 may each be connected to one or more antennas 316 and 356, respectively, for communicating with other network nodes (such as other UEs, access points, base stations (e.g., eNBs, gNBs), etc.) via at least one designated RAT (e.g., NR, LTE, GSM, etc.) on a wireless communication medium of interest (e.g., a certain set of time / frequency resources in a specific spectrum). The WWAN transceivers 310 and 350 can be configured in different ways to transmit and encode signals 318 and 358 (e.g., messages, indications, information, etc.) according to the specified RAT, and conversely, receive and decode the signals 318 and 358 (e.g., messages, indications, information, pilots, etc.). Specifically, the WWAN transceivers 310 and 350 include: one or more transmitters 314 and 354 for transmitting and encoding the signals 318 and 358, respectively, and one or more receivers 312 and 352 for receiving and decoding the signals 318 and 358, respectively.
[0087] At least in some cases, the UE 302 and the base station 304 each further include one or more short-range wireless transceivers 320 and 360, respectively. The short-range wireless transceivers 320 and 360 can be connected to one or more antennas 326 and 366, respectively, and provide for communicating over the wireless communication medium of interest via at least one designated RAT (e.g., WiFi, LTE-D, The short-range wireless transceivers 320 and 360 are components (e.g., components for sending, components for receiving, components for measuring, components for tuning, components for preventing sending, etc.) for communicating with other network nodes (such as other UEs, access points, base stations, etc.) using a PC5, dedicated short-range communication (DSRC), wireless access for vehicle environments (WAVE), near field communication (NFC), ultra-wideband (UWB), etc.). The short-range wireless transceivers 320 and 360 can be configured in different ways to send and encode signals 328 and 368 (e.g., messages, indications, information, etc.) according to a specified RAT, and conversely, receive and decode signals 328 and 368 (e.g., messages, indications, information, pilots, etc.). Specifically, the short-range wireless transceivers 320 and 360 include: one or more transmitters 324 and 364 for sending and encoding signals 328 and 368, respectively, and one or more receivers 322 and 362 for receiving and decoding signals 328 and 368, respectively. As a specific example, the short-range wireless transceivers 320 and 360 may be WiFi transceivers, Transceiver, and / or transceiver, NFC transceiver, UWB transceiver or vehicle-to-vehicle (V2V) and / or vehicle-to-everything (V2X) transceiver.
[0088] At least in some cases, the UE 302 and the base station 304 also include satellite signal receivers 330 and 370. The satellite signal receivers 330 and 370 may be connected to one or more antennas 336 and 376, respectively, and may provide means for receiving and / or measuring satellite positioning / communication signals 338 and 378, respectively. In the case where the satellite signal receivers 330 and 370 are satellite positioning system receivers, the satellite positioning / communication signals 338 and 378 may be global positioning system (GPS) signals, global navigation satellite system (GLONASS) signals, Galileo signals, Beidou signals, Indian Regional Navigation Satellite System (NAVIC), Quasi-Zenith Satellite System (QZSS), etc. In the case where the satellite signal receivers 330 and 370 are non-terrestrial network (NTN) receivers, the satellite positioning / communication signals 338 and 378 may be communication signals (e.g., carrying control and / or user data) originating from a 5G network. Satellite signal receivers 330 and 370 may include any suitable hardware and / or software for receiving and processing satellite positioning / communication signals 338 and 378, respectively. Satellite signal receivers 330 and 370 may request appropriate information and operations from other systems and, at least in some cases, perform calculations using measurements obtained by any suitable satellite positioning system algorithm to determine the location of UE 302 and base station 304, respectively.
[0089] The base station 304 and the network entity 306 each include one or more network transceivers 380 and 390, respectively, which provide means (e.g., means for sending, means for receiving, etc.) for communicating with other network entities (e.g., other base stations 304, other network entities 306). For example, the base station 304 may employ one or more network transceivers 380 to communicate with other base stations 304 or network entities 306 via one or more wired or wireless backhaul links. As another example, the network entity 306 may employ one or more network transceivers 390 to communicate with one or more base stations 304 via one or more wired or wireless backhaul links, or communicate with other network entities 306 via one or more wired or wireless core network interfaces.
[0090] The transceiver may be configured to communicate over a wired or wireless link. A transceiver (whether a wired transceiver or a wireless transceiver) includes a transmitter circuit system (e.g., transmitters 314, 324, 354, 364) and a receiver circuit system (e.g., receivers 312, 322, 352, 362). In some implementations, the transceiver may be an integrated device (e.g., implementing the transmitter circuit system and the receiver circuit system in a single device), may include separate transmitter circuit systems and separate receiver circuit systems in some implementations, or may be implemented in other ways in other implementations. The transmitter circuit system and the receiver circuit system of a wired transceiver (e.g., network transceivers 380 and 390 in some implementations) may be coupled to one or more wired network interface ports. The wireless transmitter circuitry (e.g., transmitters 314, 324, 354, 364) may include or be coupled to multiple antennas (e.g., antennas 316, 326, 356, 366), such as antenna arrays, which allow the corresponding device (e.g., UE 302, base station 304) to perform transmit "beamforming", as described herein. Similarly, the wireless receiver circuitry (e.g., receiver 312, 322, 352, 362) may include or be coupled to multiple antennas (e.g., antennas 316, 326, 356, 366), such as antenna arrays, which allow the corresponding device (e.g., UE 302, base station 304) to perform receive beamforming, as described herein. In one aspect, the transmitter circuitry and the receiver circuitry may share the same multiple antennas (e.g., antennas 316, 326, 356, 366) so that the corresponding device can only receive or only transmit at a given time, rather than both receive and transmit at the same time. The wireless transceivers (eg, WWAN transceivers 310 and 350, short-range wireless transceivers 320 and 360) may also include a network listening module (NLM) or the like for performing various measurements.
[0091] As used herein, various wireless transceivers (e.g., transceivers 310, 320, 350, and 360 in some implementations, and network transceivers 380 and 390) and wired transceivers (e.g., network transceivers 380 and 390 in some implementations) may be generally characterized as a "transceiver," "at least one transceiver," or "one or more transceivers." Thus, whether a particular transceiver is a wired transceiver or a wireless transceiver may be inferred based on the type of communication being performed. For example, backhaul communications between network devices or servers typically involve signaling via a wired transceiver, while wireless communications between a UE (e.g., UE 302) and a base station (e.g., base station 304) will typically involve signaling via a wireless transceiver.
[0092] UE 302, base station 304, and network entity 306 also include other components that can be used in conjunction with the operations disclosed herein. UE 302, base station 304, and network entity 306 include one or more processors 332, 384, and 394, respectively, for providing functionality related to, for example, wireless communication, and for providing other processing functionality. Thus, processors 332, 384, and 394 can provide means for processing, such as means for determining, means for calculating, means for receiving, means for sending, means for indicating, etc. In one aspect, processors 332, 384, and 394 can include, for example, one or more general-purpose processors, multi-core processors, central processing units (CPUs), ASICs, digital signal processors (DSPs), field programmable gate arrays (FPGAs), other programmable logic devices or processing circuit systems, or various combinations thereof.
[0093] UE 302, base station 304, and network entity 306 include memory circuitry implementing memory 340, 386, and 396 (e.g., each including a memory device) for maintaining information (e.g., information indicating reserved resources, thresholds, parameters, etc.). Thus, memory 340, 386, and 396 may provide means for storing, means for retrieving, means for maintaining, etc. In some cases, UE 302, base station 304, and network entity 306 may include positioning components 342, 388, and 398, respectively. Positioning components 342, 388, and 398, respectively, may be hardware circuits that are part of or coupled to processors 332, 384, and 394, respectively, which when executed cause UE 302, base station 304, and network entity 306 to perform the functionality described herein. In other aspects, the positioning components 342, 388, and 398 can be external to the processors 332, 384, and 394 (e.g., part of a modem processing system, integrated with another processing system, etc.). Alternatively, the positioning components 342, 388, and 398 can be memory modules stored in the memories 340, 386, and 396, respectively, which when executed by the processors 332, 384, and 394 (or a modem processing system, another processing system, etc.), cause the UE 302, the base station 304, and the network entity 306 to perform the functionality described herein. Figure 3A Possible locations for a location component 342 are illustrated, which may be, for example, part of one or more WWAN transceivers 310, memory 340, one or more processors 332, or any combination thereof, or may be a standalone component. Figure 3B Possible locations for a location component 388 are illustrated, which may be, for example, part of one or more WWAN transceivers 350, memory 386, one or more processors 384, or any combination thereof, or may be a standalone component. Figure 3C Possible locations for a location component 398 are illustrated, which may be, for example, part of one or more network transceivers 390, memory 396, one or more processors 394, or any combination thereof, or may be a stand-alone component.
[0094] UE 302 may include one or more sensors 344 coupled to one or more processors 332 to provide a means for sensing or detecting movement and / or orientation information that is independent of motion data derived from signals received by one or more WWAN transceivers 310, one or more short-range wireless transceivers 320, and / or satellite signal receivers 330. As an example, sensor 344 may include an accelerometer (e.g., a microelectromechanical system (MEMS) device), a gyroscope, a geomagnetic sensor (e.g., a compass), an altimeter (e.g., a barometric altimeter), and / or any other type of motion detection sensor. In addition, sensor 344 may include multiple different types of devices and combine their outputs to provide motion information. For example, sensor 344 may use a combination of a multi-axis accelerometer and an orientation sensor to provide the ability to calculate positioning in a two-dimensional (2D) and / or three-dimensional (3D) coordinate system.
[0095] In addition, the UE 302 includes a user interface 346 that provides means for providing indications to a user (e.g., audible and / or visual indications) and / or for receiving user input (e.g., when a user actuates a sensing device such as a keypad, touch screen, microphone, etc.). Although not shown, the base station 304 and the network entity 306 may also include a user interface.
[0096] Referring to the one or more processors 384 in more detail, in a downlink, IP packets from the network entity 306 may be provided to the processor 384. The one or more processors 384 may implement functionality for an RRC layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a medium access control (MAC) layer. One or more processors 384 may provide: RRC layer functionality associated with broadcasting of system information (e.g., master information block (MIB), system information block (SIB)), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-RAT mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality associated with header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with delivery of upper layer PDUs, error correction through automatic repeat request (ARQ), concatenation, segmentation and reassembly of RLC service data units (SDUs), re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, scheduling information reporting, error correction, priority handling, and logical channel prioritization.
[0097] The transmitter 354 and the receiver 352 may implement layer 1 (L1) functionality associated with various signal processing functions. Layer 1, including the physical (PHY) layer, may include error detection on transport channels, forward error correction (FEC) coding / decoding of transport channels, interleaving, rate matching, mapping to physical channels, modulation / demodulation of physical channels, and MIMO antenna processing. The transmitter 354 handles mapping to signal constellations based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-phase shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The coded and modulated symbols may then be separated into parallel streams. Each stream may then be mapped to an orthogonal frequency division multiplexing (OFDM) subcarrier, multiplexed with a reference signal (e.g., a pilot) in the time and / or frequency domain, and then combined together using an inverse fast Fourier transform (IFFT) to produce a physical channel carrying a time domain OFDM symbol stream. The OFDM symbol stream is spatially pre-decoded to generate multiple spatial streams. Channel estimates from a channel estimator may be used to determine coding and modulation schemes and for spatial processing. Channel estimates may be derived based on a reference signal and / or channel condition feedback sent by the UE 302. Each spatial stream may then be provided to one or more different antennas 356. The transmitter 354 may modulate an RF carrier with a corresponding spatial stream for transmission.
[0098] At the UE 302, the receiver 312 receives the signal through its corresponding antenna 316. The receiver 312 recovers the information modulated onto the RF carrier and provides the information to one or more processors 332. The transmitter 314 and the receiver 312 implement layer 1 functionality associated with various signal processing functions. The receiver 312 can perform spatial processing on the information to recover any spatial streams destined for the UE 302. If multiple spatial streams are destined for the UE 302, they can be combined into a single OFDM symbol stream by the receiver 312. The receiver 312 then converts the OFDM symbol stream from the time domain to the frequency domain using a fast Fourier transform (FFT). The frequency domain signal includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier and the reference signal are recovered and demodulated by determining the signal constellation point that is most likely to be sent by the base station 304. These soft decisions can be based on channel estimates calculated by a channel estimator. The soft decisions are then decoded and deinterleaved to recover the data signals and control signals originally sent by the base station 304 on the physical channel. The data and control signals are then provided to one or more processors 332, which implement layer 3 (L3) and layer 2 (L2) functionality.
[0099] In the uplink, one or more processors 332 provide demultiplexing between transport and logical channels, packet reassembly, decryption, header decompression, and control signal processing to recover IP packets from the core network. One or more processors 332 are also responsible for error detection.
[0100] Similar to the functionality described in conjunction with downlink transmissions performed by the base station 304, the one or more processors 332 provide: RRC layer functionality associated with system information (e.g., MIB, SIB) acquisition, RRC connection, and measurement reporting; PDCP layer functionality associated with header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functionality associated with delivery of upper layer PDUs, error correction through ARQ, concatenation, segmentation and reassembly of RLC SDUs, resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through hybrid automatic repeat request (HARQ), priority handling, and logical channel prioritization.
[0101] Channel estimates derived by the channel estimator from a reference signal or feedback sent by the base station 304 may be used by the transmitter 314 to select appropriate coding and modulation schemes and to facilitate spatial processing. The spatial streams generated by the transmitter 314 may be provided to different antennas 316. The transmitter 314 may modulate an RF carrier with a corresponding spatial stream for transmission.
[0102] The uplink transmissions are processed at the base station 304 in a manner similar to that described in conjunction with the receiver functionality at the UE 302. The receiver 352 receives the signal through its respective antenna 356. The receiver 352 recovers the information modulated onto the RF carrier and provides the information to one or more processors 384.
[0103] In the uplink, one or more processors 384 provide demultiplexing between transport and logical channels, packet reassembly, decryption, header decompression, control signal processing to recover IP packets from UE 302. IP packets from one or more processors 384 may be provided to the core network. One or more processors 384 are also responsible for error detection.
[0104] For convenience, UE 302, base station 304 and / or network entity 306 may Figure 3A , Figure 3B and Figure 3C, is shown as including various components that can be configured according to the various examples described herein. However, it should be understood that the illustrated components may have different functionality in different designs. In particular, FIG. 3A to FIG. 3C The various components in are optional in alternative configurations, and various aspects include configurations that may vary due to design choice, cost, use of the device, or other considerations. For example, in Figure 3A In the case of , a specific implementation of UE 302 may omit WWAN transceiver 310 (e.g., a wearable device or tablet or PC or laptop may have Wi-Fi and / or Bluetooth capabilities but no cellular capabilities), or may omit short-range wireless transceiver 320 (e.g., only cellular, etc.), or may omit satellite signal receiver 330, or may omit sensor 344, etc. In another example, in Figure 3B In the case of a wireless cellular network, a specific implementation of the base station 304 may omit the WWAN transceiver 350 (e.g., a Wi-Fi "hotspot" access point without cellular capabilities), or may omit the short-range wireless transceiver 360 (e.g., cellular only, etc.), or may omit the satellite signal receiver 370, etc. For the sake of brevity, illustrations of various alternative configurations are not provided herein, but will be readily apparent to those skilled in the art.
[0105] Various components of the UE 302, base station 304, and network entity 306 may be communicatively coupled to one another via data buses 334, 382, and 392, respectively. In an aspect, the data buses 334, 382, and 392 may form or be part of communication interfaces for the UE 302, base station 304, and network entity 306, respectively. For example, where different logical entities are embodied in the same device (e.g., gNB and location server functionality incorporated into the same base station 304), the data buses 334, 382, and 392 may provide for communication between the different logical entities.
[0106] Figure 3A , Figure 3B and Figure 3C The components of can be implemented in various ways. In some specific implementations, Figure 3A , Figure 3B and Figure 3CThe components of may be implemented in one or more circuits, such as, for example, one or more processors and / or one or more ASICs (which may include one or more processors). Here, each circuit may use and / or be combined with at least one memory component for storing information or executable code used by the circuit to provide the functionality. For example, some or all of the functionality represented by blocks 310 to 346 may be implemented by a processor and memory component of UE 302 (e.g., by executing appropriate code and / or by appropriate configuration of the processor component). Similarly, some or all of the functionality represented by blocks 350 to 388 may be implemented by a processor and memory component of base station 304 (e.g., by executing appropriate code and / or by appropriate configuration of the processor component). Moreover, some or all of the functionality represented by blocks 390 to 398 may be implemented by a processor and memory component of network entity 306 (e.g., by executing appropriate code and / or by appropriate configuration of the processor component). For simplicity, various operations, actions and / or functions are described herein as being performed by "UE", "by base station", "by network entity", etc. However, it should be understood that such operations, actions and / or functions may actually be performed by specific components or combinations of components of the UE 302, base station 304, network entity 306, etc. (such as processors 332, 384, 394, transceivers 310, 320, 350 and 360, memories 340, 386 and 396, positioning components 342, 388 and 398, etc.).
[0107] In some designs, the network entity 306 may be implemented as a core network component. In other designs, the network entity 306 may be operated separately from a network operator or a cellular network infrastructure (e.g., NG RAN 220 and / or 5GC 210 / 260). For example, the network entity 306 may be a component of a dedicated network that may be configured to communicate with the UE 302 via the base station 304 or independently of the base station 304 (e.g., via a non-cellular communication link such as WiFi).
[0108] NR supports a variety of cellular network-based positioning technologies, including downlink-based positioning methods, uplink-based positioning methods, and downlink and uplink-based positioning methods. Downlink-based positioning methods include: Observed Time Difference of Arrival (OTDOA) in LTE, Downlink Time Difference of Arrival (DL-TDOA) in NR, and Downlink Angle of Departure (DL-AoD) in NR. Figure 4Examples of various positioning methods according to various aspects of the present disclosure are illustrated. In an OTDOA or DL-TDOA positioning procedure, as illustrated in scenario 410, the UE measures the difference between the arrival times (ToA) of reference signals (e.g., positioning reference signals (PRS)) received from paired base stations (referred to as reference signal time difference (RSTD) or arrival time difference (TDOA) measurements), and reports these differences to a positioning entity. More specifically, the UE receives identifiers (IDs) of a reference base station (e.g., a serving base station) and multiple non-reference base stations in auxiliary data. The UE then measures the RSTD between the reference base station and each non-reference base station. Based on the known positions of the base stations involved and the RSTD measurements, a positioning entity (e.g., a UE for UE-based positioning or a location server for UE-assisted positioning) can estimate the position of the UE.
[0109] For DL-AoD positioning, the positioning entity determines the angle between the UE and the transmitting base station using measurement reports from the UE regarding received signal strength measurements of multiple downlink transmit beams, as illustrated in scenario 420. The positioning entity can then estimate the position of the UE based on the determined angle and the known position of the transmitting base station.
[0110] Uplink-based positioning methods include uplink time difference of arrival (UL-TDOA) and uplink angle of arrival (UL-AoA). UL-TDOA is similar to DL-TDOA, but UL-TDOA is based on uplink reference signals (e.g., sounding reference signals (SRS)) sent by the UE to multiple base stations. Specifically, the UE sends one or more uplink reference signals, which are measured by a reference base station and multiple non-reference base stations. Each base station then reports the reception time of the reference signal (referred to as relative time of arrival (RTOA)) to a positioning entity (e.g., a location server) that knows the location and relative timing of the base stations involved. Based on the receive-to-receive (Rx-Rx) time difference between the reported RTOA of the reference base station and the reported RTOA of each non-reference base station, the known location of the base stations, and their known timing offsets, the positioning entity can use TDOA to estimate the position of the UE.
[0111] For UL-AoA positioning, one or more base stations measure the received signal strength of one or more uplink reference signals (e.g., SRS) received from the UE on one or more uplink receive beams. The positioning entity uses the signal strength measurements and the angle of the receive beams to determine the angle between the UE and the base station. Based on the determined angle and the known location of the base station, the positioning entity can then estimate the location of the UE.
[0112] Downlink and uplink based positioning methods include: enhanced cell ID (E-CID) positioning and multiple round trip time (RTT) positioning (also referred to as "multi-cell RTT" and "multi-RTT"). In the RTT procedure, a first entity (e.g., a base station or UE) sends a first RTT-related signal (e.g., a PRS or SRS) to a second entity (e.g., a UE or a base station), and the second entity sends a second RTT-related signal (e.g., an SRS or PRS) back to the first entity. Each entity measures the time difference between the arrival time (ToA) of the received RTT-related signal and the transmission time of the transmitted RTT-related signal. The time difference is called the received to transmitted (Rx-Tx) time difference. The Rx-Tx time difference measurement can be made or adjusted to include only the time difference between the nearest time slot boundary of the received signal and the transmitted signal. The two entities may then transmit their Rx-Tx time difference measurements to a location server (e.g., LMF 270), which calculates the round trip propagation time (i.e., RTT) between the two entities based on the two Rx-Tx time difference measurements (e.g., calculated as the sum of the two Rx-Tx time difference measurements). Alternatively, one entity may transmit its Rx-Tx time difference measurements to another entity, which then calculates the RTT. The distance between the two entities may be determined based on the RTT and a known signal speed (e.g., the speed of light). For multi-RTT positioning, as illustrated in scenario 430, a first entity (e.g., a UE or a base station) performs an RTT positioning procedure with a plurality of second entities (e.g., a plurality of base stations or UEs) to enable the position of the first entity to be determined (e.g., using multilateration) based on the distance to the second entity and the known position of the second entity. RTT and multi-RTT methods may be combined with other positioning techniques (such as UL-AoA and DL-AoD) to improve position accuracy, as illustrated in scenario 440.
[0113] The E-CID positioning method is based on radio resource management (RRM) measurements. In E-CID, the UE reports the serving cell ID, timing advance (TA), and the identifiers, estimated timing and signal strength of the detected neighboring base stations. The UE's position is then estimated based on this information and the known locations of the base stations.
[0114] To assist the positioning operation, the location server (e.g., location server 230, LMF 270, SLP 272) may provide assistance data to the UE. For example, the assistance data may include: an identifier of the base station (or cell / TRP of the base station) from which the reference signal is measured, reference signal configuration parameters (e.g., the number of consecutive time slots including PRS, the periodicity of consecutive time slots including PRS, the silent sequence, the frequency hopping sequence, the reference signal identifier, the reference signal bandwidth, etc.), and / or other parameters applicable to a specific positioning method. Alternatively, the assistance data may originate directly from the base station itself (e.g., in an overhead message broadcast periodically, etc.). In some cases, the UE itself is able to detect neighboring network nodes without the use of assistance data.
[0115] In the case of OTDOA or DL-TDOA positioning procedures, the assistance data may further include an expected RSTD value and associated uncertainty, or a search window around the expected RSTD. In some cases, the value range of the expected RSTD may be + / -500 microseconds (μs). In some cases, when any resource used for positioning measurement is in FR1, the value range of the uncertainty of the expected RSTD may be + / -32μs. In other cases, when all resources used for positioning measurement are in FR2, the value range of the uncertainty of the expected RSTD may be + / -8μs.
[0116] The position estimate may be referred to by other names, such as a position estimate, a position, a fix, a position fix, a fix, etc. The position estimate may be geodetic and include coordinates (e.g., latitude, longitude, and possibly altitude), or may be municipal and include a street address, a postal address, or some other verbal description of the location. The position estimate may be further defined relative to some other known location or in absolute terms (e.g., using latitude, longitude, and possibly altitude). The position estimate may include an expected error or uncertainty (e.g., by including an area or volume within which the location is expected to be contained with some specified or default confidence level).
[0117] Figure 5 An example Long Term Evolution (LTE) Positioning Protocol (LPP) procedure 500 is illustrated for performing positioning operations between a UE 504 and a location server (illustrated as a Location Management Function (LMF) 570). Figure 5As illustrated, positioning of the UE 504 is supported via an exchange of LPP messages between the UE 504 and the LMF 570. The LPP messages may be exchanged between the UE 504 and the LMF 570 via a serving base station of the UE 504 (illustrated as serving gNB 502) and a core network (not shown). The LPP procedure 500 may be used to locate the UE 504 in order to support various location-related services, such as navigation for the UE 504 (or for a user of the UE 504), or for routing, or for providing an accurate location to a public safety answering point (PSAP) in association with an emergency call from the UE 504 to the PSAP, or for some other reason. The LPP procedure 500 may also be referred to as a positioning session, and there may be multiple positioning sessions for different types of positioning methods (e.g., downlink time difference of arrival (DL-TDOA), round trip time (RTT), enhanced cell identification (E-CID), etc.).
[0118] Initially, at stage 510, the UE 504 may receive a request for its positioning capabilities (e.g., an LPP Request Capabilities message) from the LMF 570. At stage 520, the UE 504 provides its positioning capabilities with respect to the LPP protocol to the LMF 570 by transmitting an LPP Provide Capabilities message to the LMF 570 indicating that the UE 504 uses the positioning methods supported by the LPP and the characteristics of these positioning methods. In some aspects, the capabilities indicated in the LPP Provide Capabilities message may indicate the types of positioning supported by the UE 504 (e.g., DL-TDOA, RTT, E-CID, etc.) and may indicate the capabilities of the UE 504 to support those positioning types.
[0119] Upon receiving the LPP Provide Capability message, at stage 520, the LMF 570 determines to use a particular type of positioning method (e.g., DL-TDOA, RTT, E-CID, etc.) based on the indicated positioning type supported by the UE 504, and determines a set of one or more Transmit Reception Points (TRPs) from which the UE 504 will measure downlink positioning reference signals or to which the UE 504 will send uplink positioning reference signals. At stage 530, the LMF 570 transmits an LPP Provide Assistance Data message to the UE 504 identifying the set of TRPs.
[0120] In some implementations, in response to an LPP request assistance data message ( Figure 5 (not shown), the LPP provide assistance data message at stage 530 may be transmitted by the LMF 570 to the UE 504. The LPP request assistance data message may include an identifier of the serving TRP of the UE 504 and a request for positioning reference signal (PRS) configuration of a neighboring TRP.
[0121] At stage 540, the LMF 570 transmits a request for location information to the UE 504. The request may be an LPP Request Location Information message. The message typically includes information elements defining the type of location information, the expected accuracy of the location estimate, and the response time (i.e., the expected latency). Note that a low latency requirement allows for a longer response time, while a high latency requirement requires a shorter response time. However, a long response time is referred to as high latency, and a short response time is referred to as low latency.
[0122] Note that in some implementations, the LPP Provide Assistance Data message transmitted at stage 530 may be transmitted after the LPP Request Location Information message at 540, for example, if the UE 504 transmits a request for assistance data to the LMF 570 after receiving the request for location information at stage 540 (e.g., in the LPP Request Assistance Data message, Figure 5 This is the case (not shown).
[0123] At stage 550, the UE 504 utilizes the assistance information received at stage 530 and any additional data received at stage 540 (e.g., desired position accuracy or maximum response time) to perform positioning operations (e.g., measurement of DL-PRS, transmission of UL-PRS, etc.) for the selected positioning method.
[0124] At stage 560, UE 504 may transmit an LPP Provide Location Information message to LMF 570, which conveys the results of any measurements (e.g., time of arrival (ToA), reference signal time difference (RSTD), received to transmitted (Rx-Tx), etc.) obtained at stage 550 and before or at the expiration of any maximum response time (e.g., the maximum response time provided by LMF 570 at stage 540). The LPP Provide Location Information message at stage 560 may also include one or more times at which the positioning measurements were obtained and an identification of the TRP from which the positioning measurements were obtained. Note that the time between the request for location information at 540 and the response at 560 is the "response time" and indicates the latency of the positioning session.
[0125] LMF 570 uses an appropriate positioning technique (eg, DL-TDOA, RTT, E-CID, etc.) to compute an estimated location of UE 504 based at least in part on the measurements received in the LPP Provide Location Information message at stage 560 .
[0126] Various frame structures may be used to support downlink and uplink transmissions between network nodes (eg, base stations and UEs). Figure 6600 is a diagram illustrating an example frame structure according to aspects of the present disclosure. The frame structure may be a downlink or uplink frame structure. Other wireless communication technologies may have different frame structures and / or different channels.
[0127] LTE (and in some cases NR) utilizes orthogonal frequency division multiplexing (OFDM) on the downlink and single carrier frequency division multiplexing (SC-FDM) on the uplink. However, unlike LTE, NR also has the option of using OFDM on the uplink. OFDM and SC-FDM divide the system bandwidth into multiple (K) orthogonal subcarriers, which are also often called tones, frequency bins, etc. Each subcarrier can be modulated with data. In general, modulation symbols are transmitted in the frequency domain using OFDM and in the time domain using SC-FDM. The spacing between adjacent subcarriers can be fixed, and the total number of subcarriers (K) can depend on the system bandwidth. For example, the spacing of the subcarriers can be 15 kilohertz (kHz), and the minimum resource allocation (resource block) can be 12 subcarriers (or 180kHz). Thus, for a system bandwidth of 1.25 megahertz (MHz), 2.5 MHz, 5 MHz, 10 MHz, or 20 MHz, the nominal fast Fourier transform (FFT) size may be equal to 128, 256, 512, 1024, or 2048, respectively. The system bandwidth may also be partitioned into multiple subbands. For example, a subband may cover 1.08 MHz (i.e., 6 resource blocks), and there may be 1, 2, 4, 8, or 16 subbands for a system bandwidth of 1.25 MHz, 2.5 MHz, 5 MHz, 10 MHz, or 20 MHz, respectively.
[0128] LTE supports a single parameter set (subcarrier spacing (SCS), symbol length, etc.). In contrast, NR may support multiple parameter sets (μ), for example, 15kHz (μ=0), 30kHz (μ=1), 60kHz (μ=2), 120kHz (μ=3), and 240kHz (μ=4) or larger subcarrier spacings may be available. In each subcarrier spacing, there are 14 symbols per slot. For 15kHz SCS (μ=0), there is one slot per subframe, 10 slots per frame, the slot duration is 1 millisecond (ms), the symbol duration is 66.7 microseconds (μs), and the maximum nominal system bandwidth (in MHz) with a 4K FFT size is 50. For 30kHz SCS (μ=1), there are two slots per subframe, 20 slots per frame, the slot duration is 0.5ms, the symbol duration is 33.3μs, and the maximum nominal system bandwidth (in MHz) with a 4K FFT size is 100. For 60kHz SCS (μ=2), there are four slots per subframe, 40 slots per frame, the slot duration is 0.25ms, the symbol duration is 16.7μs, and the maximum nominal system bandwidth (in MHz) with a 4K FFT size is 200. For 120kHz SCS (μ=3), there are eight slots per subframe, 80 slots per frame, the slot duration is 0.125ms, the symbol duration is 8.33μs, and the maximum nominal system bandwidth (in MHz) with a 4K FFT size is 400. For 240kHz SCS (μ=4), there are 16 slots per subframe, 160 slots per frame, the slot duration is 0.0625ms, the symbol duration is 4.17μs, and the maximum nominal system bandwidth (in MHz) is 800 with 4K FFT size.
[0129] exist Figure 6 In the example of , a parameter set of 15 kHz is used. Thus, in the time domain, a 10 ms frame is divided into 10 equally sized subframes, each subframe is 1 ms, and each subframe includes one time slot. Figure 6 , time is represented horizontally (on the X-axis), where time increases from left to right, while frequency is represented vertically (on the Y-axis), where frequency increases (or decreases) from bottom to top.
[0130] A resource grid may be used to represent a time slot, each of which includes one or more time-concurrent resource blocks (RBs) in the frequency domain (also referred to as physical RBs (PRBs)). The resource grid is further divided into a plurality of resource elements (REs). An RE may correspond to one symbol length in the time domain and one subcarrier in the frequency domain. Figure 6In the parameter set of , for a normal cyclic prefix, an RB may contain 12 consecutive subcarriers in the frequency domain and seven consecutive symbols in the time domain, for a total of 84 REs. For an extended cyclic prefix, an RB may contain 12 consecutive subcarriers in the frequency domain and six consecutive symbols in the time domain, for a total of 72 REs. The number of bits carried by each RE depends on the modulation scheme.
[0131] Some REs may carry reference (pilot) signals (RS). These reference signals may include positioning reference signals (PRS), tracking reference signals (TRS), phase tracking reference signals (PTRS), cell-specific reference signals (CRS), channel state information reference signals (CSI-RS), demodulation reference signals (DMRS), primary synchronization signals (PSS), secondary synchronization signals (SSS), synchronization signal blocks (SSB), sounding reference signals (SRS), etc., depending on whether the illustrated frame structure is used for uplink or downlink communication. Figure 6 Example locations of REs carrying reference signals (labeled "R") are illustrated.
[0132] A set of resource elements (REs) used for transmission of a PRS is referred to as a "PRS resource". A set of resource elements may span multiple PRBs in the frequency domain and "N" (such as 1 or more) consecutive symbols within a slot in the time domain. In a given OFDM symbol in the time domain, a PRS resource occupies consecutive PRBs in the frequency domain.
[0133] The transmission of PRS resources within a given PRB has a specific comb size (also referred to as "comb density"). The comb size "N" represents the subcarrier spacing (or frequency / tone spacing) within each symbol of the PRS resource configuration. Specifically, for comb size "N", the PRS is transmitted in every Nth subcarrier of a symbol of the PRB. For example, for comb-4, for each symbol of the PRS resource configuration, the RE corresponding to every fourth subcarrier (such as subcarriers 0, 4, 8) is used to transmit the PRS of the PRS resource. Currently, comb sizes of comb-2, comb-4, comb-6, and comb-12 are supported for DL-PRS. Figure 6 An example PRS resource configuration for comb-4 (which spans four symbols) is illustrated. That is, the positions of shaded REs (labeled as "R") indicate the PRS resource configuration of comb-4.
[0134] Currently, DL-PRS resources can span 2, 4, 6, or 12 consecutive symbols in a timeslot using a full frequency domain staggered pattern. DL-PRS resources can be configured in any downlink or flexible (FL) symbol configured by higher layers in a timeslot. There may be a constant energy per resource element (EPRE) for all REs of a given DL-PRS resource. The following are the symbol-by-symbol frequency offsets for comb sizes 2, 4, 6, and 12 on 2, 4, 6, and 12 symbols. 2-symbol Comb-2: {0,1}; 4-symbol Comb-2: {0,1,0,1}; 6-symbol Comb-2: {0,1,0,1,0,1}; 12-symbol Comb-2: {0,1,0,1,0,1,0,1,0,1,0,1}; 4-symbol Comb-4: {0,2,1,3} (as in Figure 6 ); 12-symbol comb-4: {0,2,1,3,0,2,1,3,0,2,1,3}; 6-symbol comb-6: {0,3,1,4,2,5}; 12-symbol comb-6: {0,3,1,4,2,5,0,3,1,4,2,5}; and 12-symbol comb-12:
[0135] {0,6,3,9,1,7,4,10,2,8,5,11}.
[0136] A "PRS resource set" is a set of PRS resources used to send a PRS signal, where each PRS resource has a PRS resource ID. In addition, the PRS resources in the PRS resource set are associated with the same TRP. A PRS resource set is identified by a PRS resource set ID and is associated with a specific TRP (identified by the TRP ID). In addition, the PRS resources in the PRS resource set have the same periodicity, a common muting pattern configuration, and the same repetition factor (such as "PRS-ResourceRepetitionFactor") across time slots. The periodicity is the time from the first repetition of the first PRS resource of the first PRS instance to the same first repetition of the same first PRS resource of the next PRS instance. The periodicity may have a length selected from the following: 2^μ*{4,5,8,10,16,20,32,40,64,80,160,320,640,1280,2560,5120,10240} time slots, where μ=0,1,2,3. The repetition factor may have a length selected from {1, 2, 4, 6, 8, 16, 32} slots.
[0137] The PRS resource ID in a PRS resource set is associated with a single beam (or beam ID) transmitted from a single TRP (where a TRP may transmit one or more beams). That is, each PRS resource in a PRS resource set may be transmitted on a different beam, and therefore, a "PRS resource" (or simply "resource") may also be referred to as a "beam". Note that this does not have any implication on whether the UE knows the TRP and beam on which the PRS is transmitted.
[0138] A "PRS instance" or "PRS opportunity" is an instance of a periodically repeated time window (such as a group of one or more consecutive time slots) in which a PRS is expected to be sent. A PRS opportunity may also be referred to as a "PRS positioning opportunity", "PRS positioning instance", "positioning opportunity", "positioning instance", "positioning repetition", or simply "opportunity", "instance", or "repetition".
[0139] A "positioning frequency layer" (also referred to simply as a "frequency layer") is a set of one or more PRS resource sets with the same values for certain parameters across one or more TRPs. Specifically, the set of PRS resource sets has the same subcarrier spacing and cyclic prefix (CP) type (meaning that all parameter sets supported for the physical downlink shared channel (PDSCH) are also supported by PRS), the same point A, the same value of the downlink PRS bandwidth, the same starting PRB (and center frequency), and the same comb size. The point A parameter takes the value of the parameter "ARFCN-ValueNR" (where "ARFCN" stands for "absolute radio frequency channel number") and is an identifier / code that specifies a pair of physical radio channels used for transmission and reception. The downlink PRS bandwidth can have a granularity of four PRBs, and the minimum value is 24 PRBs and the maximum value is 272 PRBs. Currently, up to four frequency layers have been defined, and up to two PRS resource sets can be configured per TRP per frequency layer.
[0140] The concept of frequency layer is somewhat similar to the concept of component carrier and bandwidth part (BWP), but the difference is that component carrier and BWP are used by one base station (or macro cell base station and small cell base station) to send data channels, while frequency layer is used by several (usually three or more) base stations to send PRS. The UE can indicate the number of frequency layers that the UE can support when the UE transmits its positioning capabilities to the network (such as during an LTE Positioning Protocol (LPP) session). For example, the UE can indicate whether it can support one or four positioning frequency layers.
[0141] It should be noted that the terms "positioning reference signal" and "PRS" generally refer to specific reference signals used for positioning in NR and LTE systems. However, as used herein, the terms "positioning reference signal" and "PRS" may also refer to any type of reference signal that can be used for positioning, such as but not limited to: PRS, TRS, PTRS, CRS, CSI-RS, DMRS, PSS, SSS, SSB, SRS, UL-PRS, etc. as defined in LTE and NR. In addition, the terms "positioning reference signal" and "PRS" may refer to a downlink positioning reference signal, an uplink positioning reference signal, or a sidelink positioning reference signal, unless otherwise indicated by the context. If it is necessary to further distinguish the type of PRS, the downlink positioning reference signal may be referred to as a "DL-PRS", the uplink positioning reference signal (e.g., SRS, PTRS used for positioning) may be referred to as a "UL-PRS", and the sidelink positioning reference signal may be referred to as a "SL-PRS". In addition, for signals (e.g., DMRS) that can be sent in the downlink, uplink, and / or sidelink, these signals may be prefixed with "DL," "UL," or "SL" to distinguish the direction. For example, "UL-DMRS" may be different from "DL-DMRS."
[0142] Figure 7 700 is a diagram representing an example channel estimate of a multipath channel between a receiving device (e.g., any of the UEs or base stations described herein) and a transmitting device (e.g., any other of the UEs or base stations described herein) according to aspects of the present disclosure. The channel estimate represents the strength of a radio frequency (RF) signal (e.g., a PRS) received through a multipath channel as a function of time delay and may be referred to as a channel energy response, a channel impulse response, or a power delay profile of the channel. Thus, the horizontal axis is in units of time (e.g., milliseconds) and the vertical axis is in units of signal strength (e.g., decibels). Note that a multipath channel is a channel between a transmitter and a receiver over which an RF signal follows multiple paths or multipaths due to the transmission of the RF signal on multiple beams and / or due to propagation characteristics of the RF signal (e.g., reflection, refraction, etc.).
[0143] exist Figure 7 In the example of , the receiver detects / measures multiple (four) clusters of channel taps. Each channel tap represents a multipath that the RF signal follows between the transmitter and the receiver. That is, the channel taps represent the arrival of the RF signal on a multipath. Each cluster of channel taps indicates that the corresponding multipath follows substantially the same path. Different clusters may exist because the RF signal is transmitted on different transmit beams (and therefore at different angles), or because of the propagation characteristics of the RF signal (e.g., may follow different paths due to reflections), or both.
[0144] The cluster of all channel taps for a given RF signal represents the multipath channel (or simply channel) between the transmitter and the receiver. Figure 7 Under the illustrated channel, the receiver receives a first cluster of two RF signals on the channel taps at time T1, a second cluster of five RF signals on the channel taps at time T2, a third cluster of five RF signals on the channel taps at time T3, and a fourth cluster of four RF signals on the channel taps at time T4. Figure 7 In the example of , because the first cluster of RF signals at time T1 arrives first, it is assumed to correspond to RF signals transmitted on a transmit beam aligned with line-of-sight (LOS) or the shortest path. The third cluster at time T3 includes the strongest RF signals and may correspond to, for example, RF signals transmitted on a transmit beam aligned with a non-line-of-sight (NLOS) path. Note that although Figure 7 Clusters of two to five channel taps are illustrated, but it should be understood that a cluster may have more or less channel taps than the illustrated number of channel taps.
[0145] Machine learning can be used to generate models that can be used to facilitate various aspects associated with data processing. One particular application of machine learning involves generating measurement models for processing reference signals (e.g., PRS) used for positioning, such as feature extraction, reporting of reference signal measurement results (e.g., selecting which extracted features to report), etc.
[0146] Machine learning models are generally categorized as supervised or unsupervised. Supervised models can be further subdivided into regression models or classification models. Supervised learning involves learning a function that maps inputs to outputs based on example input-output pairs. For example, given a training data set with two variables, age (input) and height (output), a supervised learning model can be generated that predicts a person's height based on their age. In a regression model, the output is continuous. An example of a regression model is linear regression, which simply tries to find the line that best fits the data. Extensions of linear regression include multiple linear regression (e.g., finding the plane of best fit) and polynomial regression (e.g., finding the curve of best fit).
[0147] Another example of a machine learning model is a decision tree model. In a decision tree model, a tree structure is defined as having multiple nodes. Decisions are used to move from a root node at the top of the decision tree to a leaf node (i.e., a node that does not have additional child nodes) at the bottom of the decision tree. Generally speaking, a higher number of nodes in a decision tree model is associated with a higher decision accuracy.
[0148] Another example of a machine learning model is a decision forest. Random forest is an ensemble learning technique built on top of decision trees. Random forest involves creating multiple decision trees using a bootstrapped dataset of the original data and randomly selecting a subset of variables at each step of the decision tree. The model then selects the mode of all predictions of each decision tree. By relying on a "majority decision" model, the risk of error from a single tree is reduced.
[0149] Another example of a machine learning model is a neural network (NN). A neural network is essentially a network of mathematical equations. A neural network accepts one or more input variables and produces one or more output variables by passing through the network of equations. In other words, a neural network receives a vector of inputs and returns a vector of outputs.
[0150] Figure 8 An example neural network 800 in accordance with aspects of the present disclosure is illustrated. The neural network 800 includes an input layer 'i' that receives 'n' input(s) (illustrated as "input 1", "input 2", and "input n"), one or more hidden layers (illustrated as hidden layers 'h1', 'h2', and 'h3') for processing the inputs from the input layer, and an output layer 'o' that provides 'm' output(s) (labeled as "output 1" and "output m"). The number of inputs 'n', hidden layers 'h', and outputs 'm' may be the same or different. In some designs, the hidden layer 'h' may include a linear function and / or an activation function, with the nodes of each successive hidden layer (illustrated as circles) processing the linear function and / or activation function of the nodes from the previous hidden layer.
[0151] In a classification model, the output is discrete. An example of a classification model is logistic regression. Logistic regression is similar to linear regression, but is used to model the probability of a limited number of results (usually two). In essence, a logistic equation is created in such a way that the output value can only be between '0' and '1'. Another example of a classification model is a support vector machine. For example, for two categories of data, a support vector machine will find a hyperplane or boundary between the two categories of data that maximizes the margin between the two categories. There are many planes that can separate the two categories, but only one plane can maximize the margin or distance between these categories. Another example of a classification model is naive Bayes based on Bayes' theorem. Other examples of classification models include decision trees, random forests, and neural networks, which are similar to the above examples, except that the output is discrete rather than continuous.
[0152] Unlike supervised learning, unsupervised learning is used to draw inferences and find patterns based on input data without reference to labeled results. Two examples of unsupervised learning models include clustering and dimensionality reduction.
[0153] Clustering is an unsupervised technique that involves grouping or clustering of data points. Clustering is often used for customer segmentation, fraud detection, and document classification. Common clustering techniques include k-means clustering, hierarchical clustering, mean shift clustering, and density-based clustering. Dimensionality reduction is the process of reducing the number of random variables under consideration by obtaining a set of principal variables. In simpler terms, dimensionality reduction is the process of reducing the dimensionality of a feature set (or, in simpler terms, reducing the number of features). Most dimensionality reduction techniques can be categorized as feature elimination or feature extraction. An example of dimensionality reduction is called principal component analysis (PCA). In the simplest sense, PCA involves projecting higher dimensional data (e.g., three dimensions) into a smaller space (e.g., two dimensions). This produces data of lower dimensionality (e.g., two dimensions instead of three dimensions) while retaining all the original variables in the model.
[0154] Regardless of which machine learning model is used, at a high level, a machine learning module (e.g., implemented by a processing system such as processor 332, 384, or 394) may be configured to iteratively analyze training input data (e.g., measurements of reference signals to / from various target UEs) and associate the training input data with an output data set (e.g., a set of possible or probable candidate locations for the various target UEs) so that the same output data set can be determined later when provided with similar input data (e.g., from other target UEs at the same or similar locations).
[0155] As used herein, a "feature" is a processed (e.g., compressed, encoded, etc.) representation of raw positioning measurement data (e.g., channel estimates, such as channel energy response (CER), channel impulse response (CIR), channel frequency response (CFR), power delay profile (PDP), etc.). A feature may be a positioning measurement of a measured channel, such as ToA, RSTD, AoD, etc. Alternatively, a feature may be a compressed or encoded vector of data representing a channel, which may be decompressed or decoded to obtain a corresponding positioning measurement of the channel.
[0156] The current measurement report configuration allows the location server to configure the UE to (for example, in the LPP Provide Location Information message, such as Figure 5 The UE may report specific measurement quantities such as RSTD, RSRP, etc. at stage 560 of the feature extraction process. The machine learning based approach will allow for a more flexible feature reporting framework, where the specific measurement quantities to be reported can be determined based on the feature extraction machine learning model. For example, the UE may measure a channel (e.g., DL-PRS from the TRP, SL-PRS from the UE) to obtain a channel estimate for the channel (e.g., Figure 7The channel estimate is then input into a machine learning model to obtain one or more characteristics of the channel. The characteristics of the channel may be positioning measurements such as RSTD measurements, ToA measurements, AoD measurements, RSRP measurements, etc. The UE may then report the characteristics of the channel to the location server.
[0157] However, there is currently no framework within the 5G standard to support machine learning based feature reporting for positioning purposes. To enable such a framework, a reporting configuration will be required to indicate to the UE which machine learning operations the UE will need to perform in order to extract the features to be reported. In addition, the UE will need a reporting format to provide the features extracted by the machine learning model.
[0158] The present disclosure introduces an information element (IE) to allow a location server to configure a UE to report characteristics of a channel derived based on a machine learning method (e.g., DL-PRS). In a first aspect (referred to as "Scenario 1"), a positioning method of a specific machine learning type may be configured, and accordingly, measurement information of a specific machine learning type may be requested from the UE for machine learning-based feature reporting. In a second aspect (referred to as "Scenario 2"), existing positioning methods (e.g., DL-TDOA, DL-AoD, multi-RTT, etc.) may be enhanced to include a mode that enables the UE to use a machine learning-based approach to derive the measurement quantity to be reported.
[0159] Note that in scenario 1, the reported feature does not need to be a physical quantity, such as an RSTD measurement. Instead, it can be an abstract quantity (e.g., a compressed data vector) that can then be mapped by another "decoder" machine learning model to a physical quantity such as an RSTD measurement or the location of the UE.
[0160] Referring to scenario 1 in more detail, the location server may respond to a request for location information (e.g., an LPP request location information message, such as in Figure 5 Additional IEs are included at stage 540 of the UE to provide details about the measurement information requested from the UE. Fig. 9 An example of such an IE is shown as "nr-ML-based-RequestLocationInformation" in the LPP "RequestLocationInformation" IE 900. Fig. 9As shown, the machine learning-based location information request IE is listed with other NR-based positioning methods, and will therefore define the quantities to be reported for the positioning method and the reporting method. For example, the machine learning-based location information request IE may provide information about the machine learning model to be used to extract (derive) the features to be reported, such as a machine learning model identifier (e.g., to identify the structure of the model, such as the number and size of layers) and a parameter set identifier (e.g., to identify the value of the machine learning model weights). The UE may then obtain the machine learning model from a location server or a model repository server based on these identifiers. Optionally, multiple model and parameter identifiers may be provided in the machine learning-based location information request IE. In this case, the UE may be configured with one or more rules to select one or more machine learning models from the provided list to derive these features.
[0161] Alternatively or additionally, the machine learning based location information request IE may indicate the machine learning model (e.g., model structure identifier, parameter identifier) to be used to decode the reported features. Using this information, the UE may select any machine learning model for feature extraction that is compatible with the machine learning model that the location server will use to decode the reported features.
[0162] Accordingly, an additional IE may be defined for the UE to provide the requested machine learning-based feature report. The machine learning-based feature report IE may be included in ( Figure 5 Similar to the manner in which a machine learning-based location information request IE may be added to an LPP request location information message) in the LPP provide location information message sent at stage 560 of the . The machine learning-based feature report IE may include: (1) machine learning-based features extracted (derived) using the configured machine learning model, (2) a machine learning model identifier and parameter set identifier for the "encoder" machine learning model used to derive the features, (3) information for identifying the PRS resources used as input to the machine learning model to derive the features, and / or (4) a machine learning model identifier and parameter set identifier for the "decoder" machine learning model that should be used to process the reported features.
[0163] Referring now to scenario 2 in more detail, existing positioning methods (eg, DL-TDOA, multi-RTT, etc.) may be enhanced with additional information elements to indicate a machine learning based operating mode. Fig.10 1 illustrates example parameters or IEs that may be added to a request location information message for an existing positioning method according to aspects of the present disclosure. Fig.10As shown, three machine learning based IEs have been added to the NR-DL-TDOA-RequestLocationInformation IE 1000. The first IE is a Boolean flag labeled "nr-MachineLearningBasedReporting" that indicates whether the UE is to use machine learning based techniques to estimate the features to be reported (e.g., Fig.10 RSTD in the example of ). A value of TRUE (e.g., "1") will indicate that the UE will use a machine learning based approach, and a value of FALSE (e.g., "0") will indicate that the UE will not use a machine learning based approach. Alternatively, the additional IEs may simply not be included to indicate that the UE will not use a machine learning based approach. If the Boolean value is TRUE, these IEs also include a machine learning model identifier called "nr-MachineLearningModelStructureIdentifier" and a parameter set identifier called "nr-MachineLearningModelParameterSetIdentifier", which are included to indicate to the UE which machine learning model to use to estimate the features to be reported.
[0164] In various aspects, the machine learning model indicated to the UE can be TRP-specific, meaning that different machine learning models can be indicated for different TRPs or for different types of TRPs (e.g., small cells versus macro cells). The indicated machine learning model can additionally or alternatively be vendor-specific (e.g., specific to certain base station vendors or UE vendors), feature-specific (e.g., specific to certain types of feature extraction, such as RSTD measurements or Rx-Tx time difference measurements), and the like.
[0165] Fig.11 An example wireless communication method 1100 according to various aspects of the present disclosure is illustrated. In one aspect, the method 1100 may be performed by a first network node (eg, any of the UE or TRP described herein).
[0166] At 1110, the first network node receives one or more request location information messages from a network entity, wherein the one or more request location information messages configure the first network node to use machine learning to derive one or more characteristics of a wireless channel between the first network node and a second network node. In one aspect, operation 1110 may be performed by one or more WWAN transceivers 310, one or more processors 332, memory 340, and / or positioning component 342, any or all of which may be considered as means for performing the operation. In one aspect, operation 1120 may be performed by one or more WWAN transceivers 350, one or more processors 384, memory 386, and / or positioning component 388, any or all of which may be considered as means for performing the operation.
[0167] At 1120, the first network node sends one or more provide location information messages to the network entity, wherein the one or more provide location information messages include the one or more features of the wireless channel, and wherein the one or more features of the wireless channel are derived based on a machine learning model. In one aspect, operation 1120 may be performed by one or more WWAN transceivers 310, one or more processors 332, memory 340, and / or positioning component 342, any or all of which may be considered as components for performing the operation. In one aspect, operation 1120 may be performed by one or more WWAN transceivers 350, one or more processors 384, memory 386, and / or positioning component 388, any or all of which may be considered as components for performing the operation.
[0168] Fig.12 An example communication method 1200 is illustrated in accordance with aspects of the present disclosure. In an aspect, the method 1200 may be performed by a network entity (eg, a location server).
[0169] At 1210, the network entity sends one or more request location information messages to the first network node, wherein the one or more request location information messages configure the first network node to use machine learning to derive one or more characteristics of a wireless channel between the first network node and a second network node. In an aspect, operation 1210 may be performed by one or more network transceivers 390, one or more processors 394, memory 396, and / or positioning component 398, any or all of which may be considered as means for performing the operation.
[0170] At 1220, the network entity receives one or more provide location information messages from the first network node, wherein the one or more provide location information messages include the one or more characteristics of the wireless channel, and wherein the one or more characteristics of the wireless channel are derived based on a machine learning model. In an aspect, operation 1220 may be performed by one or more network transceivers 390, one or more processors 394, memory 396, and / or positioning component 398, any or all of which may be considered as means for performing the operation.
[0171] It should be appreciated that a technical advantage of methods 1100 and 1200 is that it enables the first network node to support machine learning based feature extraction and reporting for positioning purposes.
[0172] In the above specific embodiments, it can be seen that different features are grouped together in each example. This disclosure should not be understood as an intention that the example clauses have more features than the features explicitly mentioned in each clause. On the contrary, various aspects of the present disclosure may include less than all the features of the disclosed individual example clauses. Therefore, the following clauses should be considered to be incorporated into the description accordingly, wherein each clause itself can be used as a separate example. Although each subordinate clause may refer to a specific combination of one clause with other clauses in a clause, the aspects of the subordinate clause are not limited to a specific combination. It should be understood that other example clauses may also include a combination of the subject matter of the subordinate clause aspect with any other subordinate clause or independent clause or any feature with other subordinate clauses and independent clauses. Various aspects disclosed herein explicitly include these combinations, unless it is explicitly expressed or can be easily inferred that a specific combination is not intended to be used (e.g., contradictory aspects, such as defining an element as both an electrical insulator and an electrical conductor). In addition, it is also expected that various aspects of the clause may be included in any other independent clause, even if the clause is not directly dependent on the independent clause.
[0173] Specific implementation examples are described in the following numbered clauses:
[0174] Clause 1. A method of wireless communication performed by a user equipment (UE), the method comprising: receiving one or more request location information messages from a location server, the one or more request location information messages configuring the UE to use a machine learning model to derive one or more characteristics of a wireless channel between the UE and a network node; and sending one or more provide location information messages to the location server, the one or more provide location information messages including the one or more characteristics of the wireless channel, the one or more characteristics of the wireless channel being derived based on the machine learning model.
[0175] Clause 2. A method according to Clause 1, wherein the one or more request location information messages include: an identifier of the machine learning model and an identifier of a parameter set of the machine learning model.
[0176] Clause 3. According to the method described in any one of clauses 1 to 2, the method also includes: obtaining the machine learning model from the location server or the machine learning model repository server.
[0177] Clause 4. A method according to any one of clauses 1 to 3, wherein: the one or more location information request messages include multiple identifiers of multiple machine learning models; and the method also includes selecting the machine learning model to derive the one or more characteristics of the wireless channel based on one or more rules configured for the UE.
[0178] Clause 5. A method according to any one of clauses 1 to 4, wherein: the one or more request location information messages include an identifier of a network-side machine learning model to be used to decode the one or more characteristics of the wireless channel; and the method also includes selecting the machine learning model to derive the one or more characteristics of the wireless channel based on the compatibility of the machine learning model with the network-side machine learning model.
[0179] Clause 6. A method according to any one of clauses 1 to 5, wherein the one or more location information provision messages include: an identifier of the machine learning model and an identifier of a parameter set of the machine learning model.
[0180] Clause 7. A method according to any one of clauses 1 to 6, wherein the one or more provide location information messages include: an identifier of a reference signal measured on the wireless channel for positioning.
[0181] Clause 8. A method according to any one of clauses 1 to 7, wherein the one or more location information providing messages include: an identifier of a network-side machine learning model to be used to decode the one or more characteristics of the wireless channel and an identifier of a parameter set of the network-side machine learning model.
[0182] Clause 9. A method according to any one of clauses 1 to 8, wherein the one or more request location information messages and the one or more provide location information messages are used for a positioning procedure based on machine learning.
[0183] Clause 10. The method of any one of clauses 1 to 8, wherein the one or more request location information messages and the one or more provide location information messages are for a cellular-based positioning procedure.
[0184] Clause 11. A method according to clause 10, wherein the cellular-based positioning procedure includes a downlink time difference of arrival (DL-TDOA) positioning procedure, a round-trip time (RTT) positioning procedure, an enhanced cell identifier (ECID) positioning procedure, a downlink angle of arrival (DL-AOD) positioning procedure, or any combination thereof.
[0185] Clause 12. A method according to any one of clauses 10 to 11, wherein the one or more request location information messages configure the UE to use the machine learning model to derive the one or more characteristics of the wireless channel based on the one or more request location information messages, and the one or more request location information messages include configuring the UE to report the one or more characteristics of the wireless channel as a flag of the positioning measurement results of the cellular-based positioning procedure.
[0186] Clause 13. A method according to any one of clauses 1 to 12, wherein the machine learning model is specific to: the network node; the type of the network node; the vendor of the network node; the type of one or more characteristics of the wireless channel; the type of the wireless channel; or any combination thereof.
[0187] Clause 14. A method as described in any of clauses 1 to 13, wherein the network node is a transmit reception point (TRP).
[0188] Clause 15. A method as described in any of clauses 1 to 13, wherein the network node is a second UE.
[0189] Clause 16. A communication method performed by a location server, the method comprising: sending one or more request location information messages to a user equipment (UE), the one or more request location information messages configuring the UE to use a machine learning model to derive one or more characteristics of a wireless channel between the UE and a network node; and receiving one or more provide location information messages from the UE, the one or more provide location information messages including the one or more characteristics of the wireless channel, the one or more characteristics of the wireless channel being derived based on the machine learning model.
[0190] Clause 17. A method according to Clause 16, wherein the one or more request location information messages include: an identifier of the machine learning model and an identifier of a parameter set of the machine learning model.
[0191] Clause 18. A method according to any one of clauses 16 to 17, wherein the one or more request location information messages include multiple identifiers of multiple machine learning models.
[0192] Clause 19. A method according to any one of clauses 16 to 18, wherein the one or more request location information messages include an identifier of a network-side machine learning model to be used to decode the one or more characteristics of the wireless channel.
[0193] Clause 20. A method according to any one of clauses 16 to 19, wherein the one or more location information provision messages include: an identifier of the machine learning model and an identifier of a parameter set of the machine learning model.
[0194] Clause 21. A method according to any one of clauses 16 to 20, wherein the one or more provide location information messages comprise: an identifier of a reference signal measured on the wireless channel for positioning.
[0195] Clause 22. A method according to any one of clauses 16 to 21, wherein the one or more location information providing messages include: an identifier of a network-side machine learning model to be used to decode the one or more characteristics of the wireless channel and an identifier of a parameter set of the network-side machine learning model.
[0196] Clause 23. A method according to any one of clauses 16 to 22, wherein the one or more request location information messages and the one or more provide location information messages are used for a positioning procedure based on machine learning.
[0197] Clause 24. The method of any one of clauses 16 to 23, wherein the one or more request location information messages and the one or more provide location information messages are for a cellular based positioning procedure.
[0198] Clause 25. A method according to clause 24, wherein the cellular-based positioning procedure includes a downlink time difference of arrival (DL-TDOA) positioning procedure, a round trip time (RTT) positioning procedure, an enhanced cell identifier (ECID) positioning procedure, a downlink angle of arrival (DL-AOD) positioning procedure, or any combination thereof.
[0199] Clause 26. A method according to any one of clauses 24 to 25, wherein the one or more request location information messages configure the UE to use the machine learning model to derive the one or more characteristics of the wireless channel based on the one or more request location information messages, and the one or more request location information messages include configuring the UE to report the one or more characteristics of the wireless channel as a flag of the positioning measurement results of the cellular-based positioning procedure.
[0200] Clause 27. A method according to any one of clauses 16 to 26, wherein the machine learning model is specific to: the network node; the type of the network node; the vendor of the network node; the type of one or more characteristics of the wireless channel; the type of the wireless channel; or any combination thereof.
[0201] Clause 28. A method as described in any of clauses 16 to 27, wherein the network node is a Transmit Reception Point (TRP).
[0202] Clause 29. A method as described in any of clauses 16 to 27, wherein the network node is a second UE.
[0203] Clause 30. A user equipment (UE), comprising: a memory; at least one transceiver; and at least one processor, the at least one processor communicatively coupling the memory and the at least one transceiver, the at least one processor being configured to: receive one or more request location information messages from a location server via the at least one transceiver, the one or more request location information messages configuring the UE to use a machine learning model to derive one or more characteristics of a wireless channel between the UE and a network node; and send one or more provide location information messages to the location server via the at least one transceiver, the one or more provide location information messages including the one or more characteristics of the wireless channel, the one or more characteristics of the wireless channel being derived based on the machine learning model.
[0204] Clause 31. A UE according to Clause 30, wherein the one or more request location information messages include: an identifier of the machine learning model and an identifier of a parameter set of the machine learning model.
[0205] Clause 32. A UE according to any one of clauses 30 to 31, wherein the at least one processor is further configured to: obtain the machine learning model from the location server or the machine learning model repository server.
[0206] Clause 33. A UE according to any one of clauses 30 to 32, wherein: the one or more location information request messages include multiple identifiers of multiple machine learning models; and the at least one processor is further configured to select the machine learning model to derive the one or more characteristics of the wireless channel based on one or more rules configured for the UE.
[0207] Clause 34. A UE according to any one of clauses 30 to 33, wherein: the one or more request location information messages include an identifier of a network-side machine learning model to be used to decode the one or more characteristics of the wireless channel; and the at least one processor is further configured to select the machine learning model to derive the one or more characteristics of the wireless channel based on the compatibility of the machine learning model with the network-side machine learning model.
[0208] Clause 35. A UE according to any one of clauses 30 to 34, wherein the one or more location information provision messages include: an identifier of the machine learning model and an identifier of a parameter set of the machine learning model.
[0209] Clause 36. A UE as described in any of clauses 30 to 35, wherein the one or more provide location information messages include: an identifier of a reference signal measured on the wireless channel for positioning.
[0210] Clause 37. A UE according to any one of clauses 30 to 36, wherein the one or more location information providing messages include: an identifier of a network-side machine learning model to be used to decode the one or more characteristics of the wireless channel and an identifier of a parameter set of the network-side machine learning model.
[0211] Clause 38. A UE according to any of clauses 30 to 37, wherein the one or more request location information messages and the one or more provide location information messages are used for a machine learning based positioning procedure.
[0212] Clause 39. A UE as set out in any of clauses 30 to 37, wherein the one or more request location information messages and the one or more provide location information messages are for a cellular based positioning procedure.
[0213] Clause 40. A UE according to clause 39, wherein the cellular-based positioning procedure comprises a downlink time difference of arrival (DL-TDOA) positioning procedure, a round trip time (RTT) positioning procedure, an enhanced cell identifier (ECID) positioning procedure, a downlink angle of arrival (DL-AOD) positioning procedure, or any combination thereof.
[0214] Clause 41. A UE according to any one of clauses 39 to 40, wherein the one or more request location information messages configure the UE to use the machine learning model to derive the one or more characteristics of the wireless channel based on the one or more request location information messages, and the one or more request location information messages include configuring the UE to report the one or more characteristics of the wireless channel as a flag of the positioning measurement results of the cellular-based positioning procedure.
[0215] Clause 42. A UE according to any one of clauses 30 to 41, wherein the machine learning model is specific to: the network node; the type of the network node; the vendor of the network node; the type of one or more characteristics of the wireless channel; the type of the wireless channel; or any combination thereof.
[0216] Clause 43. A UE as described in any of clauses 30 to 42, wherein the network node is a Transmit Reception Point (TRP).
[0217] Clause 44. A UE as set forth in any of clauses 30 to 42, wherein the network node is a second UE.
[0218] Clause 45. A location server, comprising: a memory; at least one transceiver; and at least one processor, the at least one processor communicatively coupling the memory and the at least one transceiver, the at least one processor being configured to: send one or more request location information messages to a user equipment (UE) via the at least one transceiver, the one or more request location information messages configuring the UE to use a machine learning model to derive one or more characteristics of a wireless channel between the UE and a network node; and receive one or more provide location information messages from the UE via the at least one transceiver, the one or more provide location information messages including the one or more characteristics of the wireless channel, the one or more characteristics of the wireless channel being derived based on the machine learning model.
[0219] Clause 46. A location server according to Clause 45, wherein the one or more request location information messages include: an identifier of the machine learning model and an identifier of a parameter set of the machine learning model.
[0220] Clause 47. A location server according to any one of clauses 45 to 46, wherein the one or more request location information messages include multiple identifiers of multiple machine learning models.
[0221] Clause 48. A location server according to any one of clauses 45 to 47, wherein the one or more request location information messages include an identifier of a network-side machine learning model to be used to decode the one or more characteristics of the wireless channel.
[0222] Clause 49. A location server according to any one of clauses 45 to 48, wherein the one or more location information provision messages include: an identifier of the machine learning model and an identifier of a parameter set of the machine learning model.
[0223] Clause 50. A location server as described in any of clauses 45 to 49, wherein the one or more provide location information messages include: an identifier of a reference signal measured on the wireless channel for positioning.
[0224] Clause 51. A location server according to any one of clauses 45 to 50, wherein the one or more location information providing messages include: an identifier of a network-side machine learning model to be used to decode the one or more characteristics of the wireless channel and an identifier of a parameter set of the network-side machine learning model.
[0225] Clause 52. A location server according to any one of clauses 45 to 51, wherein the one or more request location information messages and the one or more provide location information messages are used for a positioning procedure based on machine learning.
[0226] Clause 53. The location server of any one of clauses 45 to 52, wherein the one or more request location information messages and the one or more provide location information messages are for a cellular-based positioning procedure.
[0227] Clause 54. A location server according to clause 53, wherein the cellular-based positioning procedure comprises a downlink time difference of arrival (DL-TDOA) positioning procedure, a round trip time (RTT) positioning procedure, an enhanced cell identifier (ECID) positioning procedure, a downlink angle of arrival (DL-AOD) positioning procedure, or any combination thereof.
[0228] Clause 55. A location server according to any one of clauses 53 to 54, wherein the one or more request location information messages configure the UE to use the machine learning model to derive the one or more characteristics of the wireless channel based on the one or more request location information messages, and the one or more request location information messages include configuring the UE to report the one or more characteristics of the wireless channel as a flag for the positioning measurement results of the cellular-based positioning procedure.
[0229] Clause 56. A location server according to any one of clauses 45 to 55, wherein the machine learning model is specific to: the network node; the type of the network node; the vendor of the network node; the type of one or more characteristics of the wireless channel; the type of the wireless channel; or any combination thereof.
[0230] Clause 57. A location server as described in any of clauses 45 to 56, wherein the network node is a Transmit Reception Point (TRP).
[0231] Clause 58. A location server as described in any of clauses 45 to 56, wherein the network node is a second UE.
[0232] Clause 59. A user equipment (UE), comprising: a component for receiving one or more request location information messages from a location server, wherein the one or more request location information messages configure the UE to use a machine learning model to derive one or more characteristics of a wireless channel between the UE and a network node; and a component for sending one or more provide location information messages to the location server, wherein the one or more provide location information messages include the one or more characteristics of the wireless channel, and the one or more characteristics of the wireless channel are derived based on the machine learning model.
[0233] Clause 60. A UE according to Clause 59, wherein the one or more request location information messages include: an identifier of the machine learning model and an identifier of a parameter set of the machine learning model.
[0234] Clause 61. A UE according to any one of clauses 59 to 60, wherein the UE further comprises: a component for obtaining the machine learning model from the location server or the machine learning model repository server.
[0235] Clause 62. A UE according to any one of clauses 59 to 61, wherein: the one or more location information request messages include multiple identifiers of multiple machine learning models; and the UE also includes a component for selecting the machine learning model to derive the one or more characteristics of the wireless channel based on one or more rules configured to the UE.
[0236] Clause 63. A UE according to any one of clauses 59 to 62, wherein: the one or more request location information messages include an identifier of a network-side machine learning model to be used to decode the one or more characteristics of the wireless channel; and the UE also includes a component for selecting the machine learning model to derive the one or more characteristics of the wireless channel based on the compatibility of the machine learning model with the network-side machine learning model.
[0237] Clause 64. A UE according to any one of clauses 59 to 63, wherein the one or more location information provision messages include: an identifier of the machine learning model and an identifier of a parameter set for the machine learning model.
[0238] Clause 65. A UE as described in any of clauses 59 to 64, wherein the one or more provide location information messages include: an identifier of a reference signal measured on the wireless channel for positioning.
[0239] Clause 66. A UE according to any one of clauses 59 to 65, wherein the one or more location information providing messages include: an identifier of a network-side machine learning model to be used to decode the one or more characteristics of the wireless channel and an identifier of a parameter set of the network-side machine learning model.
[0240] Clause 67. A UE as described in any of clauses 59 to 66, wherein the one or more request location information messages and the one or more provide location information messages are used for a machine learning based positioning procedure.
[0241] Clause 68. A UE as set forth in any of clauses 59 to 66, wherein the one or more request location information messages and the one or more provide location information messages are for a cellular based positioning procedure.
[0242] Clause 69. A UE according to clause 68, wherein the cellular-based positioning procedure includes a downlink time difference of arrival (DL-TDOA) positioning procedure, a round trip time (RTT) positioning procedure, an enhanced cell identifier (ECID) positioning procedure, a downlink angle of arrival (DL-AOD) positioning procedure, or any combination thereof.
[0243] Clause 70. A UE according to any one of clauses 68 to 69, wherein the one or more request location information messages configure the UE to use the machine learning model to derive the one or more characteristics of the wireless channel based on the one or more request location information messages, and the one or more request location information messages include configuring the UE to report the one or more characteristics of the wireless channel as a flag of the positioning measurement results of the cellular-based positioning procedure.
[0244] Clause 71. A UE according to any one of clauses 59 to 70, wherein the machine learning model is specific to: the network node; the type of the network node; the vendor of the network node; the type of one or more characteristics of the wireless channel; the type of the wireless channel; or any combination thereof.
[0245] Clause 72. A UE as described in any of clauses 59 to 71, wherein the network node is a transmit reception point (TRP).
[0246] Clause 73. A UE as set forth in any of clauses 59 to 71, wherein the network node is a second UE.
[0247] Clause 74. A location server, comprising: a component for sending one or more request location information messages to a user equipment (UE), the one or more request location information messages configuring the UE to use a machine learning model to derive one or more characteristics of a wireless channel between the UE and a network node; and a component for receiving one or more provide location information messages from the UE, the one or more provide location information messages including the one or more characteristics of the wireless channel, the one or more characteristics of the wireless channel being derived based on the machine learning model.
[0248] Clause 75. A location server according to Clause 74, wherein the one or more request location information messages include: an identifier of the machine learning model and an identifier of a parameter set of the machine learning model.
[0249] Clause 76. A location server according to any one of clauses 74 to 75, wherein the one or more request location information messages include multiple identifiers of multiple machine learning models.
[0250] Clause 77. A location server according to any one of clauses 74 to 76, wherein the one or more request location information messages include an identifier of a network-side machine learning model to be used to decode the one or more characteristics of the wireless channel.
[0251] Clause 78. A location server according to any one of clauses 74 to 77, wherein the one or more location information provision messages include: an identifier of the machine learning model and an identifier of a parameter set of the machine learning model.
[0252] Clause 79. A location server as described in any of clauses 74 to 78, wherein the one or more provide location information messages include: an identifier of a reference signal measured on the wireless channel for positioning.
[0253] Clause 80. A location server according to any one of clauses 74 to 79, wherein the one or more location information providing messages include: an identifier of a network-side machine learning model to be used to decode the one or more characteristics of the wireless channel and an identifier of a parameter set of the network-side machine learning model.
[0254] Clause 81. A location server according to any one of clauses 74 to 80, wherein the one or more request location information messages and the one or more provide location information messages are used for a positioning procedure based on machine learning.
[0255] Clause 82. The location server of any one of clauses 74 to 81, wherein the one or more request location information messages and the one or more provide location information messages are for a cellular-based positioning procedure.
[0256] Clause 83. A location server according to clause 82, wherein the cellular-based positioning procedure includes a downlink time difference of arrival (DL-TDOA) positioning procedure, a round trip time (RTT) positioning procedure, an enhanced cell identifier (ECID) positioning procedure, a downlink angle of arrival (DL-AOD) positioning procedure, or any combination thereof.
[0257] Clause 84. A location server according to any one of clauses 82 to 83, wherein the one or more request location information messages configure the UE to use the machine learning model to derive the one or more characteristics of the wireless channel based on the one or more request location information messages, and the one or more request location information messages include configuring the UE to report the one or more characteristics of the wireless channel as a flag for the positioning measurement results of the cellular-based positioning procedure.
[0258] Clause 85. A location server according to any one of clauses 74 to 84, wherein the machine learning model is specific to: the network node; the type of the network node; the vendor of the network node; the type of one or more characteristics of the wireless channel; the type of the wireless channel; or any combination thereof.
[0259] Clause 86. A location server as described in any of clauses 74 to 85, wherein the network node is a Transmit Reception Point (TRP).
[0260] Clause 87. A location server as described in any of clauses 74 to 85, wherein the network node is a second UE.
[0261] Clause 88. A non-transitory computer-readable medium storing computer-executable instructions, which, when executed by a user equipment (UE), causes the UE to: receive one or more request location information messages from a location server, the one or more request location information messages configuring the UE to use a machine learning model to derive one or more characteristics of a wireless channel between the UE and a network node; and send one or more provide location information messages to the location server, the one or more provide location information messages including the one or more characteristics of the wireless channel, the one or more characteristics of the wireless channel being derived based on the machine learning model.
[0262] Clause 89. A non-transitory computer-readable medium as described in clause 88, wherein the one or more request location information messages include: an identifier of the machine learning model and an identifier of a parameter set for the machine learning model.
[0263] Clause 90. A non-transitory computer-readable medium according to any one of clauses 88 to 89, wherein the non-transitory computer-readable medium further comprises computer-executable instructions which, when executed by the UE, cause the UE to obtain the machine learning model from the location server or the machine learning model repository server.
[0264] Clause 91. A non-transitory computer-readable medium according to any one of clauses 88 to 90, wherein: the one or more request location information messages include multiple identifiers of multiple machine learning models; and the non-transitory computer-readable medium also includes computer-executable instructions, which, when executed by the UE, cause the UE to: select the machine learning model to derive the one or more characteristics of the wireless channel based on one or more rules configured for the UE.
[0265] Clause 92. A non-transitory computer-readable medium according to any one of clauses 88 to 91, wherein: the one or more request location information messages include an identifier of a network-side machine learning model to be used to decode the one or more characteristics of the wireless channel; and the non-transitory computer-readable medium also includes computer-executable instructions, which, when executed by the UE, cause the UE to: select the machine learning model to derive the one or more characteristics of the wireless channel based on the compatibility of the machine learning model with the network-side machine learning model.
[0266] Clause 93. A non-transitory computer-readable medium as described in any one of clauses 88 to 92, wherein the one or more location information providing messages include: an identifier of the machine learning model and an identifier of a parameter set for the machine learning model.
[0267] Clause 94. The non-transitory computer-readable medium of any one of clauses 88 to 93, wherein the one or more provide location information messages comprise: an identifier of a reference signal measured on the wireless channel for positioning.
[0268] Clause 95. A non-transitory computer-readable medium according to any one of clauses 88 to 94, wherein the one or more location information providing messages include: an identifier of a network-side machine learning model to be used to decode the one or more characteristics of the wireless channel and an identifier of a parameter set for the network-side machine learning model.
[0269] Clause 96. A non-transitory computer-readable medium as described in any of clauses 88 to 95, wherein the one or more request location information messages and the one or more provide location information messages are used for a positioning procedure based on machine learning.
[0270] Clause 97. The non-transitory computer-readable medium of any one of clauses 88 to 95, wherein the one or more request location information messages and the one or more provide location information messages are for a cellular-based positioning procedure.
[0271] Clause 98. A non-transitory computer-readable medium according to clause 97, wherein the cellular-based positioning procedure comprises a downlink time difference of arrival (DL-TDOA) positioning procedure, a round trip time (RTT) positioning procedure, an enhanced cell identifier (ECID) positioning procedure, a downlink angle of arrival (DL-AOD) positioning procedure, or any combination thereof.
[0272] Clause 99. A non-transitory computer-readable medium according to any one of clauses 97 to 98, wherein the one or more request location information messages configure the UE to use the machine learning model to derive the one or more characteristics of the wireless channel based on the one or more request location information messages, and the one or more request location information messages include configuring the UE to report the one or more characteristics of the wireless channel as a flag for the positioning measurement results of the cellular-based positioning procedure.
[0273] Clause 100. A non-transitory computer-readable medium as described in any of clauses 88 to 99, wherein the machine learning model is specific to: the network node; the type of the network node; the vendor of the network node; the type of one or more characteristics of the wireless channel; the type of the wireless channel; or any combination thereof.
[0274] Clause 101. The non-transitory computer-readable medium of any one of clauses 88 to 100, wherein the network node is a Transmit Reception Point (TRP).
[0275] Clause 102. The non-transitory computer-readable medium of any of clauses 88 to 100, wherein the network node is a second UE.
[0276] Clause 103. A non-transitory computer-readable medium storing computer-executable instructions, which, when executed by a location server, cause the location server to: send one or more request location information messages to a user equipment (UE), the one or more request location information messages configuring the UE to use a machine learning model to derive one or more characteristics of a wireless channel between the UE and a network node; and receive one or more provide location information messages from the UE, the one or more provide location information messages including the one or more characteristics of the wireless channel, the one or more characteristics of the wireless channel being derived based on the machine learning model.
[0277] Clause 104. A non-transitory computer-readable medium as described in clause 103, wherein the one or more request location information messages include: an identifier of the machine learning model and an identifier of a parameter set for the machine learning model.
[0278] Clause 105. A non-transitory computer-readable medium as described in any of clauses 103 to 104, wherein the one or more request location information messages include multiple identifiers of multiple machine learning models.
[0279] Clause 106. A non-transitory computer-readable medium as described in any of clauses 103 to 105, wherein the one or more request location information messages include an identifier of a network-side machine learning model to be used to decode the one or more characteristics of the wireless channel.
[0280] Clause 107. A non-transitory computer-readable medium as described in any one of clauses 103 to 106, wherein the one or more location information providing messages include: an identifier of the machine learning model and an identifier of a parameter set for the machine learning model.
[0281] Clause 108. The non-transitory computer-readable medium of any one of clauses 103 to 107, wherein the one or more provide location information messages comprise: an identifier of a reference signal measured on the wireless channel for positioning.
[0282] Clause 109. A non-transitory computer-readable medium according to any one of clauses 103 to 108, wherein the one or more location information providing messages include: an identifier of a network-side machine learning model to be used to decode the one or more characteristics of the wireless channel and an identifier of a parameter set for the network-side machine learning model.
[0283] Clause 110. A non-transitory computer-readable medium as described in any of clauses 103 to 109, wherein the one or more request location information messages and the one or more provide location information messages are used for a machine learning-based positioning procedure.
[0284] Clause 111. The non-transitory computer-readable medium of any one of clauses 103 to 110, wherein the one or more request location information messages and the one or more provide location information messages are for a cellular-based positioning procedure.
[0285] Clause 112. A non-transitory computer-readable medium according to clause 111, wherein the cellular-based positioning procedure comprises a downlink time difference of arrival (DL-TDOA) positioning procedure, a round trip time (RTT) positioning procedure, an enhanced cell identifier (ECID) positioning procedure, a downlink angle of arrival (DL-AOD) positioning procedure, or any combination thereof.
[0286] Clause 113. A non-transitory computer-readable medium according to any one of clauses 111 to 112, wherein the one or more request location information messages configure the UE to use the machine learning model to derive the one or more characteristics of the wireless channel based on the one or more request location information messages, and the one or more request location information messages include configuring the UE to report the one or more characteristics of the wireless channel as a flag for positioning measurement results of the cellular-based positioning procedure.
[0287] Clause 114. A non-transitory computer-readable medium as described in any of clauses 103 to 113, wherein the machine learning model is specific to: the network node; the type of the network node; the vendor of the network node; the type of one or more characteristics of the wireless channel; the type of the wireless channel; or any combination thereof.
[0288] Clause 115. The non-transitory computer-readable medium of any one of clauses 103 to 114, wherein the network node is a Transmit Reception Point (TRP).
[0289] Clause 116. The non-transitory computer-readable medium of any of clauses 103 to 114, wherein the network node is a second UE.
[0290] Additional specific implementation examples are described in the following numbered clauses:
[0291] Clause 1. A method of wireless communication performed by a first network node, the method comprising: receiving one or more request location information messages from a network entity, wherein the one or more request location information messages configure the first network node to use machine learning to derive one or more characteristics of a wireless channel between the first network node and a second network node; and sending one or more provide location information messages to the network entity, wherein the one or more provide location information messages include the one or more characteristics of the wireless channel, and wherein the one or more characteristics of the wireless channel are derived based on a machine learning model.
[0292] Clause 2. A method according to Clause 1, wherein the one or more request location information messages include: an identifier of the machine learning model and an identifier of a parameter set of the machine learning model.
[0293] Clause 3. According to the method described in any one of Clauses 1 to 2, the method further includes: obtaining the machine learning model from the network entity or the machine learning model repository server.
[0294] Clause 4. A method according to any one of clauses 1 to 3, wherein: the one or more location information request messages include multiple identifiers of multiple machine learning models; and the machine learning model is selected to derive the one or more characteristics of the wireless channel based on one or more rules configured to the first network node.
[0295] Clause 5. A method according to any one of clauses 1 to 4, wherein: the one or more request location information messages include an identifier of a network-side machine learning model to be used to decode the one or more characteristics of the wireless channel; and the machine learning model is selected to derive the one or more characteristics of the wireless channel based on the compatibility of the machine learning model with the network-side machine learning model.
[0296] Clause 6. A method according to any one of clauses 1 to 5, wherein the one or more location information provision messages include: an identifier of the machine learning model and an identifier of a parameter set of the machine learning model.
[0297] Clause 7. A method according to any one of clauses 1 to 6, wherein the one or more location information providing messages include: an identifier of a network-side machine learning model to be used to decode the one or more characteristics of the wireless channel and an identifier of a parameter set of the network-side machine learning model.
[0298] Clause 8. A method according to any one of clauses 1 to 7, wherein the one or more request location information messages and the one or more provide location information messages are used for a positioning procedure based on machine learning.
[0299] Clause 9. The method of any one of clauses 1 to 7, wherein the one or more request location information messages and the one or more provide location information messages are for a cellular-based positioning procedure.
[0300] Clause 10. A method according to clause 9, wherein the cellular-based positioning procedure includes a downlink time difference of arrival (DL-TDOA) positioning procedure, a round trip time (RTT) positioning procedure, an enhanced cell identifier (ECID) positioning procedure, a downlink angle of arrival (DL-AOD) positioning procedure, or any combination thereof.
[0301] Clause 11. A method according to any one of clauses 9 to 10, wherein the one or more request location information messages configure the first network node to use the machine learning model to derive the one or more characteristics of the wireless channel based on the one or more request location information messages, and the one or more request location information messages include configuring the first network node to report the one or more characteristics of the wireless channel as a marker of the positioning measurement results of the cellular-based positioning procedure.
[0302] Clause 12. A method according to any one of clauses 1 to 11, wherein the machine learning model is specific to: the second network node; the type of the second network node; the supplier of the second network node; the type of the one or more characteristics of the wireless channel; the type of the wireless channel; or any combination thereof.
[0303] Clause 13. A method as described in any of clauses 1 to 12, wherein: the first network node is a user equipment (UE); and the second network node is a transmit reception point (TRP).
[0304] Clause 14. A method as described in any of clauses 1 to 12, wherein: the first network node is a TRP; and the second network node is a UE.
[0305] Clause 15. The method of any one of clauses 1 to 14, wherein the network entity is a location server.
[0306] Clause 16. A communication method performed by a network entity, the method comprising: sending one or more request location information messages to a first network node, wherein the one or more request location information messages configure the first network node to use machine learning to derive one or more characteristics of a wireless channel between the first network node and a second network node; and receiving one or more provide location information messages from the first network node, wherein the one or more provide location information messages include the one or more characteristics of the wireless channel, and wherein the one or more characteristics of the wireless channel are derived based on a machine learning model.
[0307] Clause 17. A method according to Clause 16, wherein the one or more request location information messages include: an identifier of the machine learning model and an identifier of a parameter set of the machine learning model.
[0308] Clause 18. A method according to any one of clauses 16 to 17, wherein the one or more request location information messages include multiple identifiers of multiple machine learning models.
[0309] Clause 19. A method according to any one of clauses 16 to 18, wherein the one or more request location information messages include an identifier of a network-side machine learning model to be used to decode the one or more characteristics of the wireless channel.
[0310] Clause 20. A method according to any one of clauses 16 to 19, wherein the one or more location information provision messages include: an identifier of the machine learning model and an identifier of a parameter set of the machine learning model.
[0311] Clause 21. A method according to any one of clauses 16 to 20, wherein the one or more location information providing messages include: an identifier of a network-side machine learning model to be used to decode the one or more characteristics of the wireless channel and an identifier of a parameter set of the network-side machine learning model.
[0312] Clause 22. A method according to any one of clauses 16 to 21, wherein the one or more request location information messages and the one or more provide location information messages are used for a positioning procedure based on machine learning.
[0313] Clause 23. The method of any one of clauses 16 to 22, wherein the one or more request location information messages and the one or more provide location information messages are for a cellular based positioning procedure.
[0314] Clause 24. A method according to clause 23, wherein the one or more request location information messages configure the first network node to use the machine learning model to derive the one or more characteristics of the wireless channel based on the one or more request location information messages, and the one or more request location information messages include configuring the first network node to report the one or more characteristics of the wireless channel as a marker of the positioning measurement results of the cellular-based positioning procedure.
[0315] Clause 25. A method according to any one of clauses 16 to 24, wherein the machine learning model is specific to: the second network node; the type of the second network node; the supplier of the second network node; the type of the one or more characteristics of the wireless channel; the type of the wireless channel; or any combination thereof.
[0316] Clause 26. A method as described in any of clauses 16 to 25, wherein: the first network node is a user equipment (UE); and the second network node is a transmit reception point (TRP).
[0317] Clause 27. A method as described in any of clauses 16 to 25, wherein: the first network node is a TRP; and the second network node is a UE.
[0318] Clause 28. The method of any one of clauses 16 to 27, wherein the network entity is a location server.
[0319] Clause 29. A first network node, the first network node comprising: a memory; at least one transceiver; and at least one processor, the at least one processor communicatively coupling the memory and the at least one transceiver, the at least one processor being configured to: receive one or more request location information messages from a network entity via the at least one transceiver, wherein the one or more request location information messages configure the first network node to use machine learning to derive one or more characteristics of a wireless channel between the first network node and a second network node; and send one or more provide location information messages to the network entity via the at least one transceiver, wherein the one or more provide location information messages include the one or more characteristics of the wireless channel, and wherein the one or more characteristics of the wireless channel are derived based on a machine learning model.
[0320] Clause 30. A first network node according to Clause 29, wherein the one or more request location information messages include: an identifier of the machine learning model and an identifier of a parameter set for the machine learning model.
[0321] Clause 31. A first network node according to any one of clauses 29 to 30, wherein the at least one processor is further configured to: obtain the machine learning model from the network entity or a machine learning model repository server.
[0322] Clause 32. A first network node according to any one of clauses 29 to 31, wherein: the one or more request location information messages include multiple identifiers of multiple machine learning models; and the machine learning model is selected to derive the one or more characteristics of the wireless channel based on one or more rules configured to the first network node.
[0323] Clause 33. A first network node according to any one of clauses 29 to 32, wherein: the one or more request location information messages include an identifier of a network-side machine learning model to be used to decode the one or more characteristics of the wireless channel; and the machine learning model is selected to derive the one or more characteristics of the wireless channel based on the compatibility of the machine learning model with the network-side machine learning model.
[0324] Clause 34. A first network node according to any one of clauses 29 to 33, wherein the one or more provide location information messages include: an identifier of the machine learning model and an identifier of a parameter set for the machine learning model.
[0325] Clause 35. A first network node according to any one of clauses 29 to 34, wherein the one or more location information providing messages include: an identifier of a network-side machine learning model to be used to decode the one or more characteristics of the wireless channel and an identifier of a parameter set of the network-side machine learning model.
[0326] Clause 36. A first network node as described in any of clauses 29 to 35, wherein the one or more request location information messages and the one or more provide location information messages are used for a machine learning based positioning procedure.
[0327] Clause 37. The first network node of any of clauses 29 to 35, wherein the one or more request location information messages and the one or more provide location information messages are for a cellular based positioning procedure.
[0328] Clause 38. A first network node according to clause 37, wherein the cellular-based positioning procedure comprises a downlink time difference of arrival (DL-TDOA) positioning procedure, a round trip time (RTT) positioning procedure, an enhanced cell identifier (ECID) positioning procedure, a downlink angle of arrival (DL-AOD) positioning procedure, or any combination thereof.
[0329] Clause 39. A first network node according to any one of clauses 37 to 38, wherein the one or more request location information messages configure the first network node to use the machine learning model to derive the one or more characteristics of the wireless channel based on the one or more request location information messages, and the one or more request location information messages include configuring the first network node to report the one or more characteristics of the wireless channel as a marker of the positioning measurement results of the cellular-based positioning procedure.
[0330] Clause 40. A first network node according to any one of clauses 29 to 39, wherein the machine learning model is specific to: the second network node; the type of the second network node; the vendor of the second network node; the type of the one or more characteristics of the wireless channel; the type of the wireless channel; or any combination thereof.
[0331] Clause 41. A first network node as described in any of clauses 29 to 40, wherein: the first network node is a user equipment (UE); and the second network node is a transmit reception point (TRP).
[0332] Clause 42. A first network node as described in any of clauses 29 to 40, wherein: the first network node is a TRP; and the second network node is a UE.
[0333] Clause 43. The first network node of any of clauses 29 to 42, wherein the network entity is a location server.
[0334] Clause 44. A network entity, comprising: a memory; at least one transceiver; and at least one processor, the at least one processor being communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: send one or more request location information messages to a first network node via the at least one transceiver, wherein the one or more request location information messages configure the first network node to use machine learning to derive one or more characteristics of a wireless channel between the first network node and a second network node; and receive one or more provide location information messages from the first network node via the at least one transceiver, wherein the one or more provide location information messages include the one or more characteristics of the wireless channel, and wherein the one or more characteristics of the wireless channel are derived based on a machine learning model.
[0335] Clause 45. A network entity according to Clause 44, wherein the one or more request location information messages include: an identifier of the machine learning model and an identifier of a parameter set for the machine learning model.
[0336] Clause 46. A network entity according to any one of clauses 44 to 45, wherein the one or more request location information messages include multiple identifiers of multiple machine learning models.
[0337] Clause 47. A network entity according to any one of clauses 44 to 46, wherein the one or more request location information messages include an identifier of a network-side machine learning model to be used to decode the one or more characteristics of the wireless channel.
[0338] Clause 48. A network entity according to any one of clauses 44 to 47, wherein the one or more location information provision messages include: an identifier of the machine learning model and an identifier of a parameter set for the machine learning model.
[0339] Clause 49. A network entity according to any one of clauses 44 to 48, wherein the one or more location information providing messages include: an identifier of a network-side machine learning model to be used to decode the one or more characteristics of the wireless channel and an identifier of a parameter set of the network-side machine learning model.
[0340] Clause 50. A network entity as described in any of clauses 44 to 49, wherein the one or more request location information messages and the one or more provide location information messages are used for a machine learning based positioning procedure.
[0341] Clause 51. A network entity as set forth in any of clauses 44 to 50, wherein the one or more request location information messages and the one or more provide location information messages are for a cellular based positioning procedure.
[0342] Clause 52. A network entity according to clause 51, wherein the one or more request location information messages configure the first network node to use the machine learning model to derive the one or more characteristics of the wireless channel based on the one or more request location information messages, and the one or more request location information messages include configuring the first network node to report the one or more characteristics of the wireless channel as a marker of the positioning measurement results of the cellular-based positioning procedure.
[0343] Clause 53. A network entity according to any one of clauses 44 to 52, wherein the machine learning model is specific to: the second network node; the type of the second network node; the vendor of the second network node; the type of the one or more characteristics of the wireless channel; the type of the wireless channel; or any combination thereof.
[0344] Clause 54. A network entity as described in any of clauses 44 to 53, wherein: the first network node is a user equipment (UE); and the second network node is a transmit reception point (TRP).
[0345] Clause 55. A network entity as described in any of clauses 44 to 53, wherein: the first network node is a TRP; and the second network node is a UE.
[0346] Clause 56. A network entity as recited in any one of Clauses 44 to 55, wherein the network entity is a location server.
[0347] Clause 57. A first network node, comprising: a component for receiving one or more request location information messages from a network entity, wherein the one or more request location information messages configure the first network node to use machine learning to derive one or more characteristics of a wireless channel between the first network node and a second network node; and a component for sending one or more provide location information messages to the network entity, wherein the one or more provide location information messages include the one or more characteristics of the wireless channel, and wherein the one or more characteristics of the wireless channel are derived based on a machine learning model.
[0348] Clause 58. A first network node according to Clause 57, wherein the one or more request location information messages include: an identifier of the machine learning model and an identifier of a parameter set for the machine learning model.
[0349] Clause 59. The first network node according to any one of clauses 57 to 58, further comprising: a component for obtaining the machine learning model from the network entity or a machine learning model repository server.
[0350] Clause 60. A first network node according to any one of clauses 57 to 59, wherein: the one or more request location information messages include multiple identifiers of multiple machine learning models; and the machine learning model is selected to derive the one or more characteristics of the wireless channel based on one or more rules configured to the first network node.
[0351] Clause 61. A first network node according to any one of clauses 57 to 60, wherein: the one or more request location information messages include an identifier of a network-side machine learning model to be used to decode the one or more characteristics of the wireless channel; and the machine learning model is selected to derive the one or more characteristics of the wireless channel based on the compatibility of the machine learning model with the network-side machine learning model.
[0352] Clause 62. A first network node according to any one of clauses 57 to 61, wherein the one or more provide location information messages include: an identifier of the machine learning model and an identifier of a parameter set for the machine learning model.
[0353] Clause 63. A first network node according to any one of clauses 57 to 62, wherein the one or more location information providing messages include: an identifier of a network-side machine learning model to be used to decode the one or more characteristics of the wireless channel and an identifier of a parameter set of the network-side machine learning model.
[0354] Clause 64. A first network node as described in any of clauses 57 to 63, wherein the one or more request location information messages and the one or more provide location information messages are used for a machine learning based positioning procedure.
[0355] Clause 65. The first network node of any of clauses 57 to 63, wherein the one or more request location information messages and the one or more provide location information messages are for a cellular based positioning procedure.
[0356] Clause 66. A first network node according to clause 65, wherein the cellular-based positioning procedure comprises a downlink time difference of arrival (DL-TDOA) positioning procedure, a round trip time (RTT) positioning procedure, an enhanced cell identifier (ECID) positioning procedure, a downlink angle of arrival (DL-AOD) positioning procedure, or any combination thereof.
[0357] Clause 67. A first network node according to any one of clauses 65 to 66, wherein the one or more request location information messages configure the first network node to use the machine learning model to derive the one or more characteristics of the wireless channel based on the one or more request location information messages, and the one or more request location information messages include configuring the first network node to report the one or more characteristics of the wireless channel as a marker of the positioning measurement results of the cellular-based positioning procedure.
[0358] Clause 68. A first network node according to any one of clauses 57 to 67, wherein the machine learning model is specific to: the second network node; the type of the second network node; the vendor of the second network node; the type of the one or more characteristics of the wireless channel; the type of the wireless channel; or any combination thereof.
[0359] Clause 69. A first network node as described in any of clauses 57 to 68, wherein: the first network node is a user equipment (UE); and the second network node is a transmit reception point (TRP).
[0360] Clause 70. A first network node as described in any of clauses 57 to 68, wherein: the first network node is a TRP; and the second network node is a UE.
[0361] Clause 71. The first network node of any of clauses 57 to 70, wherein the network entity is a location server.
[0362] Clause 72. A network entity, comprising: a component for sending one or more request location information messages to a first network node, wherein the one or more request location information messages configure the first network node to use machine learning to derive one or more characteristics of a wireless channel between the first network node and a second network node; and a component for receiving one or more provide location information messages from the first network node, wherein the one or more provide location information messages include the one or more characteristics of the wireless channel, and wherein the one or more characteristics of the wireless channel are derived based on a machine learning model.
[0363] Clause 73. A network entity according to Clause 72, wherein the one or more request location information messages include: an identifier of the machine learning model and an identifier of a parameter set for the machine learning model.
[0364] Clause 74. A network entity as described in any of clauses 72 to 73, wherein the one or more request location information messages include multiple identifiers of multiple machine learning models.
[0365] Clause 75. A network entity according to any one of clauses 72 to 74, wherein the one or more request location information messages include an identifier of a network-side machine learning model to be used to decode the one or more characteristics of the wireless channel.
[0366] Clause 76. A network entity according to any one of clauses 72 to 75, wherein the one or more location information provision messages include: an identifier of the machine learning model and an identifier of a parameter set for the machine learning model.
[0367] Clause 77. A network entity according to any one of clauses 72 to 76, wherein the one or more location information providing messages include: an identifier of a network-side machine learning model to be used to decode the one or more characteristics of the wireless channel and an identifier of a parameter set for the network-side machine learning model.
[0368] Clause 78. A network entity as described in any of clauses 72 to 77, wherein the one or more request location information messages and the one or more provide location information messages are used for a machine learning based positioning procedure.
[0369] Clause 79. A network entity as set forth in any of clauses 72 to 78, wherein the one or more request location information messages and the one or more provide location information messages are for a cellular-based positioning procedure.
[0370] Clause 80. A network entity according to clause 79, wherein the one or more request location information messages configure the first network node to use the machine learning model to derive the one or more characteristics of the wireless channel based on the one or more request location information messages, and the one or more request location information messages include configuring the first network node to report the one or more characteristics of the wireless channel as a marker of the positioning measurement results of the cellular-based positioning procedure.
[0371] Clause 81. A network entity according to any one of clauses 72 to 80, wherein the machine learning model is specific to: the second network node; the type of the second network node; the vendor of the second network node; the type of the one or more characteristics of the wireless channel; the type of the wireless channel; or any combination thereof.
[0372] Clause 82. A network entity as set forth in any of clauses 72 to 81, wherein: the first network node is a user equipment (UE); and the second network node is a transmit reception point (TRP).
[0373] Clause 83. A network entity as described in any of clauses 72 to 81, wherein: the first network node is a TRP; and the second network node is a UE.
[0374] Clause 84. A network entity as set forth in any one of clauses 72 to 83, wherein the network entity is a location server.
[0375] Clause 85. A non-transitory computer-readable medium storing computer-executable instructions, which, when executed by a first network node, causes the first network node to: receive one or more request location information messages from a network entity, wherein the one or more request location information messages configure the first network node to use machine learning to derive one or more characteristics of a wireless channel between the first network node and a second network node; and send one or more provide location information messages to the network entity, wherein the one or more provide location information messages include the one or more characteristics of the wireless channel, and wherein the one or more characteristics of the wireless channel are derived based on a machine learning model.
[0376] Clause 86. A non-transitory computer-readable medium as described in clause 85, wherein the one or more request location information messages include: an identifier of the machine learning model and an identifier of a parameter set for the machine learning model.
[0377] Clause 87. A non-transitory computer-readable medium according to any one of clauses 85 to 86, wherein the non-transitory computer-readable medium further comprises computer-executable instructions which, when executed by the first network node, cause the first network node to: obtain the machine learning model from the network entity or the machine learning model repository server.
[0378] Clause 88. A non-transitory computer-readable medium according to any one of clauses 85 to 87, wherein: the one or more request location information messages include multiple identifiers of multiple machine learning models; and the machine learning model is selected to derive the one or more characteristics of the wireless channel based on one or more rules configured to the first network node.
[0379] Clause 89. A non-transitory computer-readable medium according to any one of clauses 85 to 88, wherein: the one or more request location information messages include an identifier of a network-side machine learning model to be used to decode the one or more characteristics of the wireless channel; and the machine learning model is selected to derive the one or more characteristics of the wireless channel based on the compatibility of the machine learning model with the network-side machine learning model.
[0380] Clause 90. A non-transitory computer-readable medium as described in any one of clauses 85 to 89, wherein the one or more location information providing messages include: an identifier of the machine learning model and an identifier of a parameter set for the machine learning model.
[0381] Clause 91. A non-transitory computer-readable medium according to any one of clauses 85 to 90, wherein the one or more location information providing messages include: an identifier of a network-side machine learning model to be used to decode the one or more characteristics of the wireless channel and an identifier of a parameter set for the network-side machine learning model.
[0382] Clause 92. A non-transitory computer-readable medium as described in any one of clauses 85 to 91, wherein the one or more request location information messages and the one or more provide location information messages are used for a positioning procedure based on machine learning.
[0383] Clause 93. The non-transitory computer-readable medium of any one of clauses 85 to 91, wherein the one or more request location information messages and the one or more provide location information messages are for a cellular-based positioning procedure.
[0384] Clause 94. A non-transitory computer-readable medium according to clause 93, wherein the cellular-based positioning procedure comprises a downlink time difference of arrival (DL-TDOA) positioning procedure, a round trip time (RTT) positioning procedure, an enhanced cell identifier (ECID) positioning procedure, a downlink angle of arrival (DL-AOD) positioning procedure, or any combination thereof.
[0385] Clause 95. A non-transitory computer-readable medium according to any one of clauses 93 to 94, wherein the one or more request location information messages configure the first network node to use the machine learning model to derive the one or more characteristics of the wireless channel based on the one or more request location information messages, and the one or more request location information messages include configuring the first network node to report the one or more characteristics of the wireless channel as a marker of the positioning measurement results of the cellular-based positioning procedure.
[0386] Clause 96. A non-transitory computer-readable medium as described in any of clauses 85 to 95, wherein the machine learning model is specific to: the second network node; the type of the second network node; the vendor of the second network node; the type of the one or more characteristics of the wireless channel; the type of the wireless channel; or any combination thereof.
[0387] Clause 97. The non-transitory computer-readable medium of any of clauses 85 to 96, wherein: the first network node is a user equipment (UE); and the second network node is a transmit reception point (TRP).
[0388] Clause 98. A non-transitory computer-readable medium as described in any of clauses 85 to 96, wherein: the first network node is a TRP; and the second network node is a UE.
[0389] Clause 99. The non-transitory computer-readable medium of any one of clauses 85 to 98, wherein the network entity is a location server.
[0390] Clause 100. A non-transitory computer-readable medium storing computer-executable instructions, which, when executed by a network entity, causes the network entity to: send one or more request location information messages to a first network node, wherein the one or more request location information messages configure the first network node to use machine learning to derive one or more characteristics of a wireless channel between the first network node and a second network node; and receive one or more provide location information messages from the first network node, wherein the one or more provide location information messages include the one or more characteristics of the wireless channel, and wherein the one or more characteristics of the wireless channel are derived based on a machine learning model.
[0391] Clause 101. A non-transitory computer-readable medium as described in clause 100, wherein the one or more request location information messages include: an identifier of the machine learning model and an identifier of a parameter set for the machine learning model.
[0392] Clause 102. A non-transitory computer-readable medium as described in any of clauses 100 to 101, wherein the one or more request location information messages include multiple identifiers of multiple machine learning models.
[0393] Clause 103. A non-transitory computer-readable medium as described in any of clauses 100 to 102, wherein the one or more request location information messages include an identifier of a network-side machine learning model to be used to decode the one or more characteristics of the wireless channel.
[0394] Clause 104. A non-transitory computer-readable medium as described in any of clauses 100 to 103, wherein the one or more location information providing messages include: an identifier of the machine learning model and an identifier of a parameter set for the machine learning model.
[0395] Clause 105. A non-transitory computer-readable medium according to any one of clauses 100 to 104, wherein the one or more location information providing messages include: an identifier of a network-side machine learning model to be used to decode the one or more characteristics of the wireless channel and an identifier of a parameter set for the network-side machine learning model.
[0396] Clause 106. A non-transitory computer-readable medium as described in any of clauses 100 to 105, wherein the one or more request location information messages and the one or more provide location information messages are used for a machine learning-based positioning procedure.
[0397] Clause 107. The non-transitory computer-readable medium of any one of clauses 100 to 106, wherein the one or more request location information messages and the one or more provide location information messages are for a cellular-based positioning procedure.
[0398] Clause 108. A non-transitory computer-readable medium according to clause 107, wherein the one or more request location information messages configure the first network node to use the machine learning model to derive the one or more characteristics of the wireless channel based on the one or more request location information messages, and the one or more request location information messages include configuring the first network node to report the one or more characteristics of the wireless channel as a marker of the positioning measurement results of the cellular-based positioning procedure.
[0399] Clause 109. A non-transitory computer-readable medium as described in any of clauses 100 to 108, wherein the machine learning model is specific to: the second network node; the type of the second network node; the vendor of the second network node; the type of the one or more characteristics of the wireless channel; the type of the wireless channel; or any combination thereof.
[0400] Clause 110. The non-transitory computer-readable medium of any of clauses 100 to 109, wherein: the first network node is a user equipment (UE); and the second network node is a transmit reception point (TRP).
[0401] Clause 111. The non-transitory computer-readable medium of any of clauses 100 to 109, wherein: the first network node is a TRP; and the second network node is a UE.
[0402] Clause 112. The non-transitory computer-readable medium of any one of clauses 100 to 111, wherein the network entity is a location server.
[0403] Those skilled in the art will appreciate that information and signals may be represented using any of a variety of different techniques and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be mentioned throughout the above description may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or optical particles, or any combination thereof.
[0404] In addition, it will be appreciated by those skilled in the art that the various exemplary logic blocks, modules, circuits and algorithmic steps described in conjunction with the aspects disclosed herein can be implemented as electronic hardware, computer software or a combination of the two. In order to clearly illustrate this interchangeability of hardware and software, various exemplary components, blocks, modules, circuits and steps have been generally described above in terms of their functionality. Whether such functionality is implemented as hardware or software depends on the specific application and the design constraints proposed to the entire system. The technician can implement the described functionality in different ways for each specific application, but such specific implementation decisions should not be interpreted as causing a departure from the scope of the present disclosure.
[0405] The various illustrative logical blocks, modules, and circuits described in conjunction with the various aspects disclosed herein may be implemented or performed with a general purpose processor, a digital signal processor (DSP), an ASIC, a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in an alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, a plurality of microprocessors, a combination of one or more microprocessors and a DSP core, or any other such configuration.
[0406] The methods, sequences and / or algorithms described in conjunction with the various aspects disclosed herein may be directly embodied in hardware, in a software module executed by a processor, or in a combination of the two. The software module may reside in a random access memory (RAM), a flash memory, a read-only memory (ROM), an erasable programmable ROM (EPROM), an electrically erasable programmable ROM (EEPROM), a register, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. An example storage medium is coupled to a processor so that the processor can read information from the storage medium and write information to the storage medium. In an alternative, the storage medium may be integral with the processor. The processor and the storage medium may reside in an ASIC. The ASIC may reside in a user terminal (e.g., UE). In an alternative, the processor and the storage medium may reside in a user terminal as discrete components.
[0407] In one or more example aspects, the function can be implemented in hardware, software, firmware or any combination thereof. If implemented in software, the function can be stored on a computer-readable medium or sent by a computer-readable medium as one or more instructions or codes. Computer-readable media include both computer storage media and communication media, and the communication media include any medium that facilitates the transfer of computer programs from one place to another. Storage media can be any available medium that can be accessed by a computer. By way of example and not limitation, such computer-readable media can include RAM, ROM, EEPROM, CD-ROM or other optical disk storage devices, disk storage devices or other magnetic storage devices, or can be used to carry or store desired program codes in the form of instructions or data structures and any other medium that can be accessed by a computer. In addition, any connection is appropriately referred to as a computer-readable medium. For example, if the software is sent from a website, a server or other remote source using a coaxial cable, a fiber optic cable, a twisted pair, a digital subscriber line (DSL) or wireless technologies such as infrared, radio and microwaves, then coaxial cable, fiber optic cable, twisted pair, DSL or wireless technologies such as infrared, radio and microwaves are included in the definition of the medium. As used herein, disk and disc include: compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc, where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer-readable media.
[0408] Although the foregoing disclosure shows the exemplary aspects of the present disclosure, it should be noted that various changes and modifications may be made herein without departing from the scope of the present disclosure as defined by the appended claims. In addition, the functions, steps and / or actions of the method claims according to the various aspects of the present disclosure described herein do not need to be performed in any particular order. In addition, although the elements of the present disclosure may be described or claimed in the singular, plural forms may also be considered unless explicitly stated to be limited to the singular.
Claims
1. A method of wireless communication performed by a first network node, the method comprising: receiving one or more request location information messages from a network entity, wherein the one or more request location information messages configure the first network node to use machine learning to derive one or more characteristics of a wireless channel between the first network node and a second network node; as well as One or more provide location information messages are sent to the network entity, wherein the one or more provide location information messages include the one or more characteristics of the wireless channel, and wherein the one or more characteristics of the wireless channel are derived based on a machine learning model.
2. The method of claim 1, wherein the one or more request location information messages comprise: an identifier for the machine learning model, and An identifier for the set of parameters for the machine learning model.
3. The method according to claim 1, further comprising: The machine learning model is obtained from the network entity or the machine learning model repository server.
4. The method according to claim 1, wherein: The one or more request location information messages include a plurality of identifiers of a plurality of machine learning models, and The machine learning model is selected to derive the one or more characteristics of the wireless channel based on one or more rules configured to the first network node.
5. The method according to claim 1, wherein: The one or more request location information messages include an identifier of a network-side machine learning model to be used to decode the one or more characteristics of the wireless channel, and The machine learning model is selected to derive the one or more characteristics of the wireless channel based on the machine learning model being compatible with the network-side machine learning model.
6. The method of claim 1, wherein the one or more provide location information messages comprise: an identifier for the machine learning model, and An identifier for the set of parameters for the machine learning model.
7. The method of claim 1, wherein the one or more provide location information messages comprise: an identifier of a network-side machine learning model to be used to decode the one or more characteristics of the wireless channel, and The identifier of the parameter set of the network-side machine learning model.
8. The method of claim 1, wherein the one or more request location information messages and the one or more provide location information messages are used for a positioning procedure based on machine learning.
9. The method of claim 1, wherein the one or more request location information messages and the one or more provide location information messages are used for a cellular-based positioning procedure.
10. The method of claim 9, wherein the cellular-based positioning procedure comprises a downlink time difference of arrival (DL-TDOA) positioning procedure, a round trip time (RTT) positioning procedure, an enhanced cell identifier (ECID) positioning procedure, a downlink angle of arrival (DL-AOD) positioning procedure, or any combination thereof.
11. A method according to claim 9, wherein the one or more request location information messages configure the first network node to use the machine learning model to derive the one or more characteristics of the wireless channel based on the one or more request location information messages, and the one or more request location information messages include configuring the first network node to report the one or more characteristics of the wireless channel as a marker of the positioning measurement results of the cellular-based positioning procedure.
12. The method of claim 1, wherein the machine learning model is specific to: the second network node, a type of the second network node, a supplier of the second network node, a type of the one or more characteristics of the wireless channel, The type of the wireless channel, or Any combination of them.
13. The method of claim 1, wherein: The first network node is a user equipment (UE), and The second network node is a Transmit Reception Point (TRP).
14. The method of claim 1, wherein: The first network node is a TRP, and The second network node is a UE.
15. The method of claim 1, wherein the network entity is a location server.
16. A communication method performed by a network entity, the method comprising: sending one or more request location information messages to a first network node, wherein the one or more request location information messages configure the first network node to use machine learning to derive one or more characteristics of a wireless channel between the first network node and a second network node; as well as One or more provide location information messages are received from the first network node, wherein the one or more provide location information messages include the one or more characteristics of the wireless channel, and wherein the one or more characteristics of the wireless channel are derived based on a machine learning model.
17. The method of claim 16, wherein the one or more request location information messages comprise: an identifier for the machine learning model, and An identifier for the set of parameters for the machine learning model.
18. The method of claim 16, wherein the one or more request location information messages include multiple identifiers of multiple machine learning models.
19. The method of claim 16, wherein the one or more request location information messages include an identifier of a network-side machine learning model to be used to decode the one or more characteristics of the wireless channel.
20. The method of claim 16, wherein the one or more provide location information messages comprise: an identifier for the machine learning model, and An identifier for the set of parameters for the machine learning model.
21. The method of claim 16, wherein the one or more provide location information messages comprise: an identifier of a network-side machine learning model to be used to decode the one or more characteristics of the wireless channel, and The identifier of the parameter set of the network-side machine learning model.
22. The method of claim 16, wherein the one or more request location information messages and the one or more provide location information messages are used for a positioning procedure based on machine learning.
23. The method of claim 16, wherein the one or more request location information messages and the one or more provide location information messages are used for a cellular-based positioning procedure.
24. A method according to claim 23, wherein the one or more request location information messages configure the first network node to use the machine learning model to derive the one or more characteristics of the wireless channel based on the one or more request location information messages, and the one or more request location information messages include configuring the first network node to report the one or more characteristics of the wireless channel as a marker of the positioning measurement results of the cellular-based positioning procedure.
25. The method of claim 16, wherein the machine learning model is specific to: the second network node, a type of the second network node, a supplier of the second network node, a type of the one or more characteristics of the wireless channel, The type of the wireless channel, or Any combination of them.
26. The method of claim 16, wherein: The first network node is a user equipment (UE), and The second network node is a Transmit Reception Point (TRP).
27. The method of claim 16, wherein: The first network node is a TRP, and The second network node is a UE.
28. The method of claim 16, wherein the network entity is a location server.
29. A first network node, the first network node comprising: Memory; at least one transceiver; and at least one processor, the at least one processor being communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: receiving, via the at least one transceiver, one or more request location information messages from a network entity, wherein the one or more request location information messages configure the first network node to use machine learning to derive one or more characteristics of a wireless channel between the first network node and a second network node; as well as One or more provide location information messages are sent to the network entity via the at least one transceiver, wherein the one or more provide location information messages include the one or more characteristics of the wireless channel, and wherein the one or more characteristics of the wireless channel are derived based on a machine learning model.
30. A network entity, comprising: Memory; at least one transceiver; and at least one processor, the at least one processor being communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: sending, via the at least one transceiver, one or more request location information messages to a first network node, wherein the one or more request location information messages configure the first network node to use machine learning to derive one or more characteristics of a wireless channel between the first network node and a second network node; as well as One or more provide location information messages are received from the first network node via the at least one transceiver, wherein the one or more provide location information messages include the one or more characteristics of the wireless channel, and wherein the one or more characteristics of the wireless channel are derived based on a machine learning model.
