Small data transmission for positioning when UE is in RRC inactive state or RRC idle state
Patent Information
- Application Number
- CN202380029847.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2022-04-01
- Filing Date
- 2023-01-31
- Publication Date
- 2024-11-08
Smart Images

Figure CN118923170A_ABST
Abstract
Description
Technical Field
[0001] Aspects of the present disclosure relate generally to wireless communications. Background Art
[0002] Wireless communication systems have evolved over many 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) services (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.
[0003] 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 a reference signal for positioning (RS-P), such as a downlink, uplink, or sidelink positioning reference signal (PRS)), and other technical enhancements compared to previous standards. These enhancements, along with the use of higher frequency bands, advances in PRS processes and technologies, and high-density deployments of 5G enable high-precision positioning based on 5G. Summary of the invention
[0004] 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 of the mechanisms disclosed herein in a brief form before the detailed embodiments presented below.
[0005] In one aspect, a method of wireless communication performed by a user equipment (UE) includes: measuring one or more positioning reference signal (PRS) resources from one or more network entities during a positioning session while in a radio resource control (RRC) inactive state or an RRC idle state; and reporting the measurement data to a location server while in the RRC inactive state or the RRC idle state during one or more small data transmission (SDT) opportunities based on a response time requirement of the positioning session, a configuration of the UE to remain in the RRC inactive state or the RRC idle state, a number of small data transmission (SDT) opportunities required to report measurement data of the one or more PRS resources, or any combination thereof.
[0006] In one aspect, a user equipment (UE) includes: 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: measure one or more positioning reference signal (PRS) resources from one or more network entities during a positioning session while in a radio resource control (RRC) inactive state or an RRC idle state; and report the measurement data to a location server via the at least one transceiver while in the RRC inactive state or the RRC idle state during one or more small data transmission (SDT) opportunities based on a response time requirement of the positioning session, a configuration of the UE to remain in the RRC inactive state or the RRC idle state, a number of small data transmission (SDT) opportunities required to report measurement data of the one or more PRS resources, or any combination thereof.
[0007] In one aspect, a user equipment (UE) includes: means for measuring one or more positioning reference signal (PRS) resources from one or more network entities during a positioning session while in a radio resource control (RRC) inactive state or an RRC idle state; and means for reporting measurement data of the one or more PRS resources to a location server while in the RRC inactive state or the RRC idle state during one or more small data transmission (SDT) opportunities based on: a response time requirement of the positioning session, a configuration of the UE to remain in the RRC inactive state or the RRC idle state, a number of SDT opportunities required to report the measurement data, or any combination thereof.
[0008] In one aspect, a non-transitory computer-readable medium storing computer-executable instructions that, when executed by a user equipment (UE), causes the UE to: measure one or more positioning reference signal (PRS) resources from one or more network entities during a positioning session while in a radio resource control (RRC) inactive state or an RRC idle state; and report the measurement data to a location server during one or more small data transmission (SDT) opportunities while in the RRC inactive state or the RRC idle state based on a response time requirement for the positioning session, a configuration for the UE to remain in the RRC inactive state or the RRC idle state, a number of small data transmission (SDT) opportunities required to report measurement data of the one or more PRS resources, or any combination thereof.
[0009] 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
[0010] 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.
[0011] Figure 1 An example wireless communication system in accordance with aspects of the present disclosure is illustrated.
[0012] Figure 2A , Figure 2B and Figure 2C Example wireless network structures according to aspects of the present disclosure are illustrated.
[0013] 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.
[0014] Figure 4 An example Long Term Evolution (LTE) Positioning Protocol (LPP) call flow between a UE and a location server for performing positioning operations is illustrated.
[0015] Figure 5 is a diagram illustrating an example frame structure according to aspects of the present disclosure.
[0016] Figure 6 is a diagram illustrating various uplink channels within an example uplink time slot in accordance with aspects of the present disclosure.
[0017] Figure 7is a diagram illustrating an example downlink positioning reference signal (DL-PRS) configuration for two transmit reception points (TRPs) operating in the same positioning frequency layer in accordance with aspects of the present disclosure.
[0018] Figure 8 Different radio resource control (RRC) states available in New Radio (NR) according to aspects of the present disclosure are illustrated.
[0019] Fig. 9 An example call flow for transferring LPP protocol data units (PDUs) between a UE and a location server when the UE is in an RRC_INACTIVE state or an RRC_IDLE state and supports SDT is illustrated in accordance with aspects of the present disclosure.
[0020] Fig.10 An example small data transmission (SDT) procedure invocation according to aspects of the present disclosure is illustrated, wherein positioning measurement data is transmitted by a UE to a location server in a single SDT when the UE is in an RRC inactive state or an RRC idle state.
[0021] Fig.11 Example SDT procedure invocations are illustrated in accordance with aspects of the present disclosure, wherein an initial SDT transmission may be followed by one or more subsequent SDT transmissions.
[0022] Fig.12 is a block diagram of an example system that can be used to implement certain aspects of the present disclosure.
[0023] Fig.13 An example of allocating positioning measurements to multiple TRPs for transmission in multiple SDTs in accordance with aspects of the present disclosure is shown.
[0024] Fig.14 is an example of quality of service (QoS) sequence information that may be received by a UE from a location server in an LPP call during a positioning session in accordance with aspects of the present disclosure.
[0025] Fig.15 is an example of a positioning report format according to aspects of the present disclosure.
[0026] Fig.16 Example methods of wireless communications that may be performed by a UE according to aspects of the present disclosure are illustrated. DETAILED DESCRIPTION
[0027] 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. Additionally, 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.
[0028] 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 superior to 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.
[0029] 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.
[0030] 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 will be appreciated 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. In addition, the sequence of actions described herein may be considered to be fully embodied in any form of non-transitory 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 claimed subject matter. 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".
[0031] As used herein, unless otherwise specified, the terms "user equipment" (UE) and "base station" are not intended to be specific 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 (e.g., at certain times) may be fixed 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 be connected 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.
[0032] 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 provide only 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.
[0033] The term "base station" may refer to a single physical transmit-receive point (TRP) or to 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 the 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 a UE and an adjacent base station whose reference radio frequency (RF) signal the UE is measuring. Because, as used herein, a TRP is a point by which a base station transmits and receives wireless signals, references to transmitting from a base station or receiving at a base station should be understood to refer to a specific TRP of a base station.
[0034] 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 tower (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).
[0035] "RF signals" include electromagnetic waves of a given frequency that transmit 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 RF.
[0036] Figure 1An 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.
[0037] 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 through 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., the AP 150 described below), and the like. For signaling purposes, communications 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.
[0038] Among other functions, the base station 102 can 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 can communicate with each other directly or indirectly (e.g., through EPC / 5GC) on a backhaul link 134, which can be wired or wireless.
[0039] 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 certain 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. Because a cell is supported by a specific base station, the term "cell" may refer to either or both of the logical communication entity and the base station supporting it, depending on the context. In addition, because the TRP is generally the physical transmission point of the cell, the terms "cell" and "TRP" can be used interchangeably. In some cases, the term "cell" can also refer to the geographic coverage area (e.g., sector) of a base station, as long as the carrier frequency can be detected and used for communication within a portion of the geographic coverage area 110.
[0040] Although the geographic coverage areas 110 of neighboring macrocell base stations 102 may partially overlap (e.g., in a handover area), 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) that may provide services to a restricted group referred to as a closed subscriber group (CSG).
[0041] 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).
[0042] 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.
[0043] 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' adopting 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, Licensed Assisted Access (LAA) or MulteFire.
[0044] 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 part of RF in the electromagnetic spectrum. EHF has a range of 30 GHz to 300 GHz, with a wavelength 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 3 GHz, with a wavelength of 100 mm. The super high frequency (SHF) band extends between 3 GHz and 30 GHz, and it is also referred to as centimeter waves. Communications using mmW / near mmW radio frequency bands have high path loss and relatively short distances. The mmW base station 180 and the UE 182 can utilize beamforming (transmitting and / or receiving) on the mmW communication link 184 to compensate for extremely high path loss and short distances. 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.
[0045] 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 (called a "phased array" or "antenna array") that creates RF beams that can be "steered" to point in different directions without actually moving the antennas. 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.
[0046] The transmit beams can be quasi-co-located, meaning that they appear to the receiver (e.g., UE) to have the same parameters, regardless of whether the network node's own transmit antennas are 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.
[0047] In receive beamforming, a receiver uses a receive beam to amplify an RF signal detected on a given channel. For example, a receiver may increase the gain setting of an antenna array in a particular direction and / or adjust the phase setting of an antenna array in a particular direction to amplify (e.g., increase its gain level) the RF signal received from that direction. Thus, when a receiver is said to be beamforming in a certain direction, this means that the beam gain in that direction is high relative to the beam gain along other directions, or that 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.
[0048] 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.
[0049] 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.
[0050] The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc. based on frequency / wavelength. In 5GNR, 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 “below 6 GHz” band in various documents and articles. A similar naming problem sometimes occurs with respect to FR2, which is often (interchangeably) referred to as the “millimeter wave” band in documents and articles, although different from the extremely high frequency (EHF) band (30 GHz–300 GHz) identified as the “millimeter wave” band by the International Telecommunication Union (ITU).
[0051] 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.
[0052] In view of the above aspects, unless otherwise specifically stated, it should be understood that if the term "below 6 GHz" or the like is used herein, it can be broadly referred to as a frequency 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 be broadly referred to as a frequency 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.
[0053] 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), which can be configured and can be 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. Because 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. can be used interchangeably.
[0054] 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.
[0055] 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.
[0056] 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, in which 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.
[0057] In one aspect, the sidelink 160 may operate on a wireless communication medium of interest, which may be shared with other wireless communications between other vehicles and / or infrastructure access points and 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.
[0058] It should be noted 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. 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), and the like. Thus, in some cases, UE 164 and UE 182 may utilize beamforming on sidelink 160.
[0059] 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 ) can receive a signal 124 from one or more earth orbiting space vehicles (SVs) 112 (e.g., satellites). In one aspect, the SV 112 can be part of a satellite positioning system that the UE 104 can use as an independent source of location information. A satellite positioning system typically includes a transmitter system (e.g., SV 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 a transmitter typically transmits a signal of a repeating pseudo-random noise (PN) code marked with a set number of chips. Although typically located in the SV 112, the transmitter can sometimes be located on a ground-based control station, base station 102, and / or other UEs 104. The UE 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 SV 112.
[0060] 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.
[0061] 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 can receive communication signals (e.g., signal 124) from a SV 112.
[0062] 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 D2D P2P 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 D2D P2P 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.
[0063] 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, Internet Protocol (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 another 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, a 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 (or both) the gNB 222 or the ng-eNB 224 may communicate with one or more UEs 204 (e.g., any of the UEs described herein).
[0064] 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).
[0065] 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 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 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 EPS bearer identifiers for interworking with the Evolved Packet System (EPS), and UE 204 mobility event notifications. In addition, the AMF 264 also supports functionality for non-3GPP (Third Generation Partnership Project) access networks.
[0066] 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.
[0067] The functions of SMF 266 include session management, UE IP address allocation and management, selection and control of user plane functions, service steering configuration for routing services to the correct destination at UPF 262, 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.
[0068] 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 convey 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).
[0069] 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., 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 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.
[0070] 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.
[0071] 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 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.
[0072] 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 B node (NB), an evolved NB (eNB), an NR base station, a 5GNB, 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.
[0073] The aggregated base station can be configured to utilize a radio protocol stack physically or logically integrated within a single RAN node. The decomposed base station can 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 (CU), one or more distributed units (DU), or one or more radio units (RU). In some aspects, the CU can be implemented within a RAN node, and one or more DUs can be co-located with the CU, or alternatively, can be geographically or virtually distributed in one or more other RAN nodes. The DU can be implemented to communicate with one or more RUs. Each of the CU, DU, and RU can also be implemented as a virtual unit, namely a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).
[0074] 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.
[0075] Figure 2C2 is a diagram illustrating an example disaggregated base station architecture according to aspects of the present disclosure. The disaggregated base station 250 architecture 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 a core network 267 through one or more disaggregated base station units (e.g., 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 corresponding midhaul links (e.g., F1 interfaces). The DUs 285 may communicate with one or more radio units (RUs) 287 (e.g., gNB-RUs 229) via corresponding fronthaul links. The RU 287 can communicate with a corresponding UE 204 via one or more RF access links. In some implementations, a UE 204 can be served by multiple RUs 287 simultaneously.
[0076] Each of the 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, signals) via a wired or wireless transmission medium. Each of the 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, transmitter, or transceiver (such as an RF transceiver) configured to receive or send signals, or both, to one or more of the other units via a wireless transmission medium.
[0077] In some aspects, CU 280 may host one or more higher layer control functions. Such control functions may include RRC, PDCP, SDAP, etc. Each control function may be implemented with an interface 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, CU280 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.
[0078] 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 the RLC layer, the 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 partitioning such as that defined by the Third Generation Partnership Project (3GPP). In some aspects, DU 285 may also host one or more low PHY layers. Each layer (or module) may be implemented with 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.
[0079] The lower layer functionality may be implemented by one or more RUs 287. In some deployments, the RU 287 controlled by the 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 functional splitting (such as lower layer functional splitting). 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 CU 280 in a cloud-based RAN architecture (such as a vRAN architecture).
[0080] 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 .
[0081] 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.
[0082] 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 creation of RAN management policies (such as A1 policies).
[0083] Figure 3A , Figure 3B and Figure 3C 1 and 2. The exemplary embodiment of the present invention may be incorporated into a UE 302 (which may correspond to any UE described herein), a base station 304 (which may correspond to any base station described herein), and a network entity 306 (which may correspond to or embody any network function described herein, including a location server 230 and a LMF 270, or alternatively may be independent of the location server 230 and the LMF 270. 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 operations as described herein. It should be understood that these components can be implemented in different types of devices with different specific implementations (e.g., 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. In addition, 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.
[0084] 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 may be configured in different ways to transmit and encode signals 318 and 358 (e.g., messages, indications, information, etc.) according to a specified RAT, and conversely, receive and decode signals 318 and 358 (e.g., messages, indications, information, pilots, etc.) respectively. Specifically, the WWAN transceivers 310 and 350 include: one or more transmitters 314 and 354 for transmitting and encoding signals 318 and 358, respectively, and one or more receivers 312 and 352 for receiving and decoding signals 318 and 358, respectively.
[0085] 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), 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 or vehicle-to-vehicle (V2V) and / or vehicle-to-everything (V2X) transceiver.
[0086] At least in some cases, UE 302 and base station 304 also include satellite signal receivers 330 and 370. Satellite signal receivers 330 and 370 may be connected to one or more antennas 336 and 376, respectively, and may provide components for receiving and / or measuring satellite positioning / communication signals 338 and 378, respectively. In the case where satellite signal receivers 330 and 370 are satellite positioning system receivers, satellite positioning / communication signals 338 and 378 may be 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 satellite signal receivers 330 and 370 are NTN receivers, 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 positions of UE 302 and base station 304, respectively.
[0087] 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.
[0088] 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 (e.g., transmitters 314, 324, 354, 364) and a receiver circuit (e.g., receivers 312, 322, 352, 362). In some implementations, the transceiver may be an integrated device (e.g., implementing the transmitter circuit and the receiver circuit in a single device), may include separate transmitter circuits and separate receiver circuits in some implementations, or may be implemented in other ways in other implementations. The transmitter circuit and the receiver circuit 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., receivers 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.
[0089] 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.
[0090] 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 circuits, or various combinations thereof.
[0091] 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.
[0092] 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.
[0093] 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.
[0094] Referring in more detail to the one or more processors 384, 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 the RRC layer, the PDCP layer, the RLC layer, and the 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.
[0095] 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 the transport channel, FEC coding / decoding of the transport channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. The transmitter 354 handles the mapping to the signal constellation 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 decoded 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.
[0096] 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 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.
[0097] 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.
[0098] 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 transfer 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.
[0099] 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.
[0100] 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.
[0101] 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.
[0102] 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 may 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 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 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.
[0103] 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.
[0104] 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). In addition, 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 a UE", "by a base station", "by a 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.).
[0105] 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 differently from a network operator or 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).
[0106] NR supports a variety of cellular network-based positioning techniques, 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. In the OTDOA or DL-TDOA positioning procedure, the UE measures the difference between the arrival time (ToA) of the reference signal (e.g., PRS) received from the paired base stations (referred to as reference signal time difference (RSTD) or arrival time difference (TDOA) measurement), and reports these differences to the 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 the 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, the 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.
[0107] For DL-AoD positioning, the positioning entity uses measurement reports from the UE on received signal strength measurements of multiple downlink transmit beams to determine the angle between the UE and the transmitting base station. The positioning entity can then estimate the UE's position based on the determined angle and the known location of the transmitting base station.
[0108] 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.
[0109] 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.
[0110] 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 the other 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, a first entity (e.g., a UE or base station) performs an RTT positioning procedure with multiple second entities (e.g., multiple base stations or UEs) so that the location of the first entity can be determined based on the distance to the second entity and the known location of the second entity (e.g., using multi-point positioning). RTT and multi-RTT methods may be combined with other positioning techniques (such as UL-AoA and DL-AoD) to improve location accuracy.
[0111] 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.
[0112] Figure 4An example Long Term Evolution (LTE) Positioning Protocol (LPP) procedure 400 is illustrated for performing positioning operations between a UE 404 and a location server (illustrated as LMF 470). Figure 4 As shown, positioning of UE 404 is supported via the exchange of LPP messages between UE 404 and LMF 470. LPP messages may be exchanged between UE 404 and LMF 470 via a serving base station (exemplified as serving gNB 402) of UE 404 and a core network (not shown). LPP procedure 400 may be used to locate UE 404 in order to support various location-related services, such as for UE 404 (or for a user of UE 404), or for routing, or for providing an accurate location to a public safety answering point (PSAP) in association with an emergency call from UE 404 to the PSAP, or for navigation for some other reason. LPP procedure 400 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.).
[0113] Initially, at stage 410, UE 404 may receive a request for its positioning capabilities (e.g., an LPP Request Capabilities message) from LMF 470. At stage 420, UE 404 provides its positioning capabilities with respect to the LPP protocol to LMF 470 by transmitting an LPP Provide Capabilities message to LMF 470 indicating that UE 404 uses the positioning methods supported by 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 UE 404 (e.g., DL-TDOA, RTT, E-CID, etc.) and may indicate the ability of UE 404 to support those positioning types.
[0114] Upon receiving the LPP Provide Capability message, at stage 420, the LMF 470 determines a particular type of positioning method to be used (e.g., DL-TDOA, RTT, E-CID, etc.) based on the indicated positioning types supported by the UE 404, and determines a set of one or more TRPs from which the UE 404 will measure downlink positioning reference signals or to which the UE 404 will send uplink positioning reference signals. At stage 430, the LMF 470 transmits an LPP Provide Assistance Data message to the UE 404 identifying the set of TRPs.
[0115] In some implementations, in response to an LPP request assistance data message ( Figure 4(not shown), the LPP provide assistance data message at stage 430 may be transmitted by LMF 470 to UE 404. The LPP request assistance data message may include an identifier of a serving TRP of UE 404 and a request for positioning reference signal (PRS) configuration of a neighboring TRP.
[0116] At stage 440, LMF 470 transmits a request for location information to UE 404. 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.
[0117] Note that in some implementations, the LPP Provide Assistance Data message transmitted at stage 430 may be transmitted after the LPP Request Location Information at stage 440, for example, if UE 404 transmits a request for assistance data to LMF 470 after receiving the request for location information at stage 440 (e.g., in the LPP Request Assistance Data message, Figure 4 This is the case (not shown).
[0118] At stage 450, UE 404 utilizes the assistance information received at stage 430 and any additional data received at stage 440 (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.
[0119] At stage 460, UE 404 may transmit an LPP Provide Location Information message to LMF 470 that 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 450 and before or at the expiration of any maximum response time (e.g., the maximum response time provided by LMF 470 at stage 440). The LPP Provide Location Information message at stage 460 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 440 and the response at 460 is the "response time" and indicates the latency of the positioning session.
[0120] LMF 470 uses an appropriate positioning technique (eg, DL-TDOA, RTT, E-CID, etc.) to compute an estimated position of UE 404 based at least in part on the measurements received in the LPP Provide Location Information message at stage 460 .
[0121] Various frame structures may be used to support downlink and uplink transmissions between network nodes (eg, base stations and UEs). Figure 5 5 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.
[0122] LTE (and in some cases NR) utilizes 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 sent 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 divided into 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.
[0123] 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.
[0124] exist Figure 5 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 5 , 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.
[0125] 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 5In 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.
[0126] 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 5 Example locations of REs carrying reference signals (labeled "R") are illustrated.
[0127] 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.
[0128] 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 5 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.
[0129] 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 5 ); 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: {0,6,3,9,1,7,4,10,2,8,5,11}.
[0130] 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.
[0131] 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.
[0132] 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".
[0133] 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.
[0134] 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.
[0135] 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."
[0136] Figure 6 6 is a diagram illustrating various uplink channels within an example uplink time slot. Figure 6 In , 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. Figure 6 In the example of , a parameter set of 15 kHz is used. Thus, in the time domain, the illustrated time slot length is one millisecond (ms), divided into 14 symbols.
[0137] The random access channel (RACH), also known as PRACH, may be in one or more time slots within a frame based on the PRACH configuration. The PRACH may include six consecutive RB pairs within a time slot. The PRACH allows the UE to perform initial system access and achieve uplink synchronization. The physical uplink control channel (PUCCH) may be located at the edge of the uplink system bandwidth. The PUCCH carries uplink control information (UCI), such as scheduling requests, CSI reports, channel quality indicators (CQI), precoding matrix indicators (PMI), rank indicators (RI), and HARQ ACK / NACK feedback. The physical uplink shared channel (PUSCH) carries data and may additionally be used to carry buffer status reports (BSRs), power headroom reports (PHRs), and / or UCI.
[0138] Figure 7700 is a diagram illustrating an example PRS configuration for two TRPs (labeled “TRP1” and “TRP2”) operating in the same positioning frequency layer (labeled “Positioning Frequency Layer 1”) in accordance with aspects of the present disclosure. For a positioning session, assistance data indicating the illustrated PRS configuration may be provided to the UE. Figure 7 In the example of , a first TRP ("TRP1") is associated with (e.g., transmits) two PRS resource sets labeled "PRS resource set 1" and "PRS resource set 2", and a second TRP ("TRP2") is associated with one PRS resource set labeled "PRS resource set 3". Each PRS resource set includes at least two PRS resources. Specifically, the first PRS resource set ("PRS resource set 1") includes PRS resources labeled "PRS resource 1" and "PRS resource 2", the second PRS resource set ("PRS resource set 2") includes PRS resources labeled "PRS resource 3" and "PRS resource 4", and the third PRS resource set ("PRS resource set 3") includes PRS resources labeled "PRS resource 5" and "PRS resource 6".
[0139] 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, silent sequence, frequency hopping sequence, reference signal identifier, 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.
[0140] In the case of OTDOA or DL-TDOA positioning procedures, the auxiliary 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.
[0141] The position estimate may be referred to by other names, such as a positioning estimate, a position, a fix, a positioning fix, a fix, and the like. 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 positioning 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).
[0142] After the random access procedure, the UE is in the RRC connected state. The RRC protocol is used on the air interface between the UE and the base station. The main functions of the RRC protocol include connection establishment and release functions, broadcasting of system information, radio bearer establishment, reconfiguration, release, RRC connection mobility procedures, paging notification and release, and outer loop power control. In LTE, the UE can be in one of two RRC states (connected or idle), but in NR, the UE can be in one of three RRC states (connected, idle or inactive). Different RRC states have different radio resources associated with these states, which the UE can use when it is in a given state. It should be noted that, as mentioned above, the different RRC states are usually capitalized; however, this is not necessary, and these states can also be written in lowercase.
[0143] Figure 8 800 is a diagram of different RRC states (also referred to as RRC modes) available in NR according to aspects of the present disclosure. When the UE is powered on, it is initially in the RRC disconnected / idle state 810. After a random access procedure, the UE transitions to the RRC connected state 820. If the UE is inactive for a short period of time, it may suspend its session by moving to the RRC inactive state 830. The UE may resume its session by performing a random access procedure to transition back to the RRC connected state 820. Therefore, the UE needs to perform a random access procedure to transition to the RRC connected state 820 regardless of whether the UE is in the RRC idle state 810 or the RRC inactive state 830.
[0144] Operations performed in the RRC idle state 810 include public land mobile network (PLMN) selection, broadcast of system information, cell reselection mobility, paging for mobile terminal data (initiated and managed by 5GC), discontinuous reception (DRX) for core network paging (configured by NAS). Operations performed in the RRC connected state 820 include 5GC (e.g., 5GC260) and NG-RAN (e.g., NG-RAN 220) connection establishment (both control plane and user plane), UE context storage at NG-RAN and UE, NG-RAN knowledge of the cell to which the UE belongs, unicast data transmission to / from the UE, and network-controlled mobility. Operations performed in the RRC Inactive state 830 include broadcast of system information, cell reselection for mobility, paging (initiated by NG-RAN), RAN-based Notification Area (RNA) management (initiated by NG-RAN), DRX for RAN paging (configured by NG-RAN), 5GC and NG-RAN connection establishment for UE (both control plane and user plane), UE context storage in NG-RAN and UE, and NG-RAN knowledge of the RNA to which the UE belongs.
[0145] While in the RRC connected state, the UE typically transfers data to a network entity (e.g., a base station, a location server, etc.). As described above, the UE performs several procedures to transition from the RRC idle state or the RRC inactive state to the RRC connected state. Once the transition procedure is successfully completed, the UE sends data to the network entity in one or more UL transmissions while in the RRC connected state. While in the RRC connected state, the UE may perform additional procedures (e.g., radio link monitoring (RLM), measurements and measurement reporting, etc.). The UE stays in the RRC connected state until an RRC release message is received from the network entity, at which time the UE transitions back to the RRC idle state or the RRC inactive state.
[0146] Moving the UE to the RRC connected state and maintaining the UE in the RRC connected state may cause the UE to consume a large amount of power. In addition, since the UE cannot send UL data to the network entity until the transition of the UE to the RRC connected state is completed, there may be a large amount of latency before the time when the UE is able to send UL data to the network entity. When the UE has only limited data to send, the power consumption and latency associated with moving the UE to the RRC connected state and maintaining it in the RRC connected state may be wasteful.
[0147] In order to address the inefficiencies associated with moving the UE to and maintaining the RRC connected state when the UE has only a small amount of data to send to a network entity, procedures have been introduced that allow the UE to send a small amount of data while remaining in a non-connected state (such as an RRC inactive state or an RRC idle state). Such procedures are referred to as small data transmission procedures and are used to send data in a small data transmission (SDT). In general, SDT refers to the transmission of data in an RRC inactive state or an RRC idle state. SDT is a short data burst transmission performed by the UE when the UE has only a small amount of data to send to a network entity while the UE is not transitioning in and out of the RRC connected state.
[0148] Certain aspects of the present disclosure are implemented on the premise of the following recognition: positioning measurements made by the UE when it is in an RRC inactive state and / or an RRC idle state can be sent by the UE to a network entity by transitioning to an RRC connected state or sending the measurement as an SDT while remaining in an RRC inactive state or an RRC idle state. Therefore, based on this recognition, certain aspects of the present disclosure are implemented on the premise of the following recognition: the UE can choose to transition to an RRC connected state to send positioning measurements, or send positioning measurements as SDT while remaining in an RRC inactive state or an RRC idle state. According to certain aspects of the present disclosure, the UE measures one or more PRS resources from one or more network entities (e.g., base stations, TRPs, other UEs, etc.) during a positioning session while in an RRC inactive state or an RRC idle state. The UE can report positioning measurement data to a network entity (e.g., a location server) during one or more SDT opportunities while remaining in an RRC inactive state or an RRC idle state. The UE sends positioning measurement data during one or more SDT opportunities based on one or more decision factors.
[0149] One such factor that may be considered for the decision is the response time requirement imposed on the UE for its positioning operations during the positioning session. For example, the UE may be directed to measure PRS resources and report the corresponding positioning measurements to a network entity (e.g., a location server) within a specified response time. If the positioning latency requirement of the positioning session is very strict (e.g., the positioning session requires a short response time from the UE), the UE may decide to send the positioning measurements as SDT, thereby eliminating the time required for the UE to transition to the RRC connected state. For positioning sessions where latency is not a significant factor, the UE may choose to transition to the RRC connected state to send positioning data to the network entity.
[0150] A power policy may be proposed to the UE to reduce the amount of power consumed by the UE during general operation and / or task-specific operation (e.g., positioning operation). The UE may use a power policy (e.g., power consumption constraint) as a factor in determining whether to transmit positioning measurements when operating in an RRC connected state or to transmit positioning measurements as SDT when operating in an RRC inactive state or an RRC idle state. For example, the UE may be configured with a discontinuous reception (DRX) policy that indicates that the UE remains in an RRC inactive state or an RRC idle state during a specified time. When the UE is configured to send positioning measurements during the specified time, the positioning measurements may be sent as SDT while the UE remains in the RRC inactive state or the RRC idle state of its DRX configuration.
[0151] Another determining factor relates to the amount of positioning measurement data that the UE needs to send to the network entity. For example, in a positioning session in which the UE measures relatively few PRS resources, the amount of positioning measurement data may be small (e.g., when the UE is only instructed to measure relatively few PRS resources during the positioning session). Such a small amount of measurement data can be sent in a single SDT (if the amount of data is less than or equal to the amount of data that can be sent during a single SDT opportunity) or divided among multiple SDTs (if the amount of data is greater than the amount of data that can be sent during a single SDT opportunity).
[0152] Even when the amount of positioning measurement data can be divided among multiple SDTs, when the number of SDT opportunities required to send multiple SDTs exceeds the SDT opportunity threshold, the efficiency obtained by sending positioning measurement data while in the RRC inactive state or the RRC idle state may not be guaranteed. Therefore, in some aspects, the UE may use the SDT opportunity threshold to determine whether the UE sends the positioning measurement data as an SDT or transitions to the RRC connected state to send the positioning measurement data. In some instances, the SDT opportunity threshold may be based on efficiency considerations. Alternatively or alternatively, the threshold may be based on the maximum number of SDT opportunities available to the UE limited by the network entity receiving the positioning measurement data. Other factors may also be considered when determining the SDT opportunity threshold. When the amount of positioning measurement data can be divided for transmission during multiple SDT opportunities less than or equal to the SDT opportunity threshold, the UE remains in the RRC inactive state or the RRC idle state and sends the positioning measurement data in multiple SDTs. However, when the amount of positioning measurement data exceeds the amount of data that can be sent during the multiple SDT opportunities specified in the SDT opportunity threshold, the UE may transition to the RRC connected state to send the positioning measurement data to the network entity.
[0153] In some aspects, the UE may use only one of the aforementioned factors to determine whether to send positioning measurement data as SDT when in the RRC inactive state or the RRC idle state. In other aspects, the UE may make such a determination based on any combination of the aforementioned factors. Alternatively or alternatively, the UE may use one or more of the aforementioned factors in combination with additional factors to make this determination.
[0154] Fig. 9 An example call flow 900 for transferring LPP protocol data units (PDUs) between a UE 902 and a location server 912 (labeled "LS") in a UE-triggered situation when the UE 902 is in an RRC_INACTIVE state or an RRC_IDLE state and supports SDT in accordance with various aspects of the present disclosure is illustrated. In this example, the UE 902 initiates an exchange by transmitting an initial transmission 904 to a base station 906 (e.g., a gNB). The initial transmission 904 includes an RRC recovery request and an LPP PDU. At operation 910, the base station 906 forwards the LPP PDU to an access and mobility management function 908 (labeled "AMF"). At operation 910, the base station 906 may transmit the LPP PDU to the AMF 908 using the NG Application Protocol (NGAP) in an NGAP uplink non-access stratum (NAS) transport communication. In one aspect, the NGAP protocol provides control plane signaling between the base station 906 and the AMF 908. The AMF 908 also provides a Network Access and Mobility Function service (NAMF) that serves as a communication interface between the base station 906 and the LS 912. In this example, at operation 914, the LPP PDU is delivered by the AMF 908 to the LS 912 in a NAMF_Communication_N1MessageNotify communication.
[0155] In this example, at operation 916, LS 912 responds to the receipt of the LPP PDU by generating another LPP PDU that is transmitted in a NAMF_Communication_N1N2MessageTransfer communication to AMF 908. At operation 918, AMF 908 communicates the LPP PDU from LS 912 to base station 906 in a NGAP downlink NAS transport communication. At operation 920, SDT communication is terminated by base station 906 when base station 906 transmits an RRC release message to UE 902.
[0156] Fig.10An example SDT procedure call flow 1000 according to various aspects of the present disclosure is illustrated, wherein positioning measurement data is sent by the UE 902 to the LS 912 in a single SDT when the UE 902 is in an RRC inactive state or an RRC idle state. A single SDT transmission may also be referred to as a single-transmission SDT. In this example, the UE 902 initiates an exchange by transmitting an initial transmission 1004 to a base station 906 (e.g., a gNB). The initial transmission 1004 includes an RRC recovery request, a BSR, and positioning measurement data in an SDT (shown here as SDT (1)). SDT (1) may be formatted as an LCS message according to the LPP protocol to transmit positioning measurement data to the LS 912. The BSR is a MAC layer procedure used by the UE 902 to provide the serving base station 906 with information about the amount of data available for transmission in the UL buffer of the UE 902. That is, the BSR indicates how much uplink data the UE must transmit. A portion of the BSR data may be transmitted in the SDT.
[0157] At operation 1010, the base station 906 forwards the SDT (1) to the AMF 908. The base station 906 may transmit the SDT (1) to the AMF 908 using NGAP. At operation 1014, the AMF 908 forwards the SDT (1) to the LS 912 using the NAMF transport service.
[0158] At operation 1016, the SDT communication is terminated by the base station 906 when the base station 906 transmits an RRC release message to the UE 902. According to certain aspects of the present disclosure, as shown in operations 1018 and 1020, the LS 912 may transmit an optional LCS message to the UE 902. The optional LCS message may be sent by the base station 906 together with the RRC release 916.
[0159] The SDT procedure also allows multiple SDT transmissions after the initial SDT transmission. Such multiple SDT transmissions may also be referred to as multi-transmission SDT and may be used when the UL grant for Msg3 / MsgA or pre-configured PUSCH resources is not large enough to accommodate all UL payloads available for transmission and / or when new data may arrive in the UL buffer. Fig.11 An example SDT procedure invocation flow 1100 is illustrated, wherein an initial SDT transmission is followed by one or more subsequent SDT transmissions in accordance with various aspects of the present disclosure. In this example, the UE 902 initiates the SDT procedure by transmitting an initial transmission 1104 to the base station 906. Similar to Fig. 9The initial transmission 904 shown in FIG. 1 includes an RRC recovery request, a BSR, and positioning measurement data in the first SDT (shown here as SDT(1)). In addition, the UE 902 may send assistance information to the base station 906, the assistance information indicating parameters to be used for transmission of subsequent SDTs.
[0160] After correctly receiving the initial transmission 1104, the base station 906 may transmit a reception confirmation to the UE 902 to initiate the transmission of a subsequent SDT (e.g., SDT (2, ..., N), where N corresponds to the total number of SDTs transmitted by the UE 902). In certain aspects, when the UE 902 determines that the number of SDT transmissions N required to transmit the positioning measurement data is greater than the SDT opportunity threshold, the UE 902 autonomously transitions to the RRC connected state to transmit the positioning data.
[0161] SDT (1) and all subsequent SDTs may be formatted as LCS messages according to the LPP protocol and combined using Fig. 9 The protocols and services described and shown at operations 1106 and 1112 are communicated to the LS 912. The base station 906 may respond to the reception of each SDT with an ACK / NACK feedback message indicating whether the SDT was correctly received by the base station 906. Based on the ACK / NACK feedback message, the UE 902 transmits a subsequent SDT or retransmits a previous SDT.
[0162] exist Fig.11 In the illustrated example, the UE 902 transmits an SDT to the base station 906 during one or more operations 1108. At operation 1110, when the UE 902 receives the RRC release message, the SDT session including the initial transmission and one or more subsequent SDTs ends.
[0163] As noted, the BSR is a MAC layer procedure used by the UE 902 to provide information about the amount of data available for transmission to the serving base station 906 in the UL buffer of the UE 902. According to certain aspects of the present disclosure, the base station 906 may use the amount of data reported in the BSR (e.g., the total amount of positioning measurement data available for upload) to determine whether to allow the UE 902 to transmit data using the SDT protocol. If the amount of data reported in the BSR exceeds a data size threshold, the base station 906 may direct the UE 902 to transition to the RRC connected state to transmit the data.
[0164] In order to avoid being transitioned to the RRC connected state by the base station 906, the UE 902 may report an amount of data in the BSR that is less than a data size threshold used by the base station. When the actual amount of positioning measurement data is greater than the data size threshold, the UE 902 may report an amount of data in the BSR that is less than the actual amount of positioning measurement data to be uploaded. In such an instance, the UE 902 may underreport the actual amount of positioning measurement data to be sent to the base station 906. In this way, the UE 902 may send all positioning measurement data in multiple SDT sessions while remaining in the RRC inactive state or the RRC idle state.
[0165] Fig.12 1 is a block diagram of an example system 1200 that can be used to implement certain aspects of the present disclosure. In this example, the system 1200 includes location software 1202 that communicates with multiple protocol layers, shown here as an RRC layer 1204, an NR physical layer 1206 (labeled NR ML1), and a MAC layer 1208. In certain aspects, the location software 1202 communicates with the RRC layer 1204 for NAS message exchanges, including receiving positioning assistance data (AD) 1210 from a location server. The location software 1202 communicates with the NR physical layer 1206 for positioning measurement scheduling. The interface between the location software 1202 and the MAC layer 1208 is an extension of traditional location software. Here, the extension allows the location software 1202 to provide positioning measurement data to the MAC layer 1208. In turn, the MAC layer 1208 receives the positioning measurement data from the location software 1202, generates a corresponding BSR, and sends the BSR and an SDT containing the positioning measurement data to the base station. In certain aspects, the location software 1202 may control the amount of data reported by the MAC layer in the BSR by controlling the flow of positioning measurement data that it communicates to the MAC layer 1208. For example, the location software 1202 may provide positioning measurements to the MAC layer 1208 in a block size that keeps the amount of data reported in the BSR below a transition threshold, thereby allowing the UE to remain in the RRC inactive state or the RRC idle state even if the actual amount of positioning measurement data exceeds the transition threshold. In one aspect, the UE may receive an indication of the transition threshold from the base station (e.g., at the MAC layer 1208) and report this transition threshold to the location software 1202. Alternatively or alternatively, the location software 1202 may heuristically determine the transition threshold based on the base station's response to one or more previous BSR reports (e.g., whether the past BSR reports caused the base station to transition the UE to the RRC connected state or allow the UE to remain in the RRC inactive state or the RRC idle state). For example, the sending threshold may be based on a maximum BSR report transmitted by the UE while in the RRC inactive state or the RRC idle state without triggering the base station to transition the UE out of the RRC inactive state or the RRC idle state.
[0166] In certain aspects, the location software 1202 is responsible for storing positioning measurements and applying various operations for maintaining the UE in an RRC inactive state or an RRC idle state to send positioning measurements as SDT. Therefore, the location software 1202 may include: 1) positioning measurement storage; 2) information related to the power policy implemented by the UE; 3) information related to the transition threshold implemented by the base station; 4) the maximum SDT opportunity allowed to send positioning data while in the RRC inactive state or the RRC idle state; 5) the response time requirements for the positioning session; and 6) data reduction criteria for reducing the amount of positioning measurements to be sent to the location server by the base station.
[0167] Fig.13 An example 1300 of allocating positioning measurements for transmission of measurements of multiple TRPs in multiple SDTs in accordance with various aspects of the present disclosure is shown. In this example, location software executed at a UE has obtained positioning measurements of PRS resources from multiple TRPs (e.g., TRPs 1 to 9). The total amount of positioning measurement data is represented by X bytes of data 1302. It is assumed that X bytes are larger than the amount of data that can be transmitted during a single SDT opportunity. Therefore, the X bytes are divided into multiple byte instances of the SDT. Here, the X bytes have been divided into three equal instances of Y bytes (although the X bytes may optionally be divided into multiple instances of different byte sizes). In this example, a first instance 1304 of the Y bytes includes positioning measurement data for TRPs 1 to 3, which is transmitted at SDT opportunity 1 in SDT-1 1310. A second instance 1306 of the Y bytes includes positioning measurement data for TRPs 4 to 6, which is transmitted at SDT opportunity 2 in SDT-2 1312. The third instance 1308 of the Y byte includes positioning measurement data for TRPs 7 to 9, which are sent at SDT opportunity 3 in SDT-3 1314. In this example, all positioning measurement data measured by the location software are sent to the location server in three SDTs to the base station while the UE remains in the RRC inactive state or the RRC idle state.
[0168] In certain aspects, the UE may obtain the response time requirements for the positioning session by accessing the QoS requirements for positioning communicated to the UE by the location server. Fig.14 is an example of a QoS IE 1400 that may be received by a UE from a location server in an LPP call during a positioning session in accordance with aspects of the present disclosure.
[0169] like Fig.14As shown in the example of , the QoS IE 1400 includes a responseTime field 1402 indicating a response time requirement for the positioning session. When the responseTime field 1402 indicates a response time, the UE can access the response time information indicated in the ResponseTime IE 1404 and use the information when the UE determines whether the UE remains in an RRC inactive state or an RRC idle state to send positioning measurements. To this end, the time field indicates the maximum response time as measured between receiving the RequestLocationInformation IE and sending the ProvideLocationInformation IE. If the unit field is not present, this is given as an integer number of seconds between 1 and 128. If the unit field is present, the maximum response time is given in units of 10 seconds between 10 seconds and 1280 seconds. If the periodicalReporting IE is included in the CommonIEsRequestLocationInformation IE, this field should not be included by the location server and should be ignored by the target device (if included).
[0170] The responseTimeEarlyFix field indicates the maximum response time as measured between receiving the RequestLocationInformation IE and sending the ProvideLocationInformation IE containing the early location measurement or early location estimate. If the unit field is not present, this is given as an integer number of seconds between 1 and 128. If the unit field is present, the maximum response time is given in units of 10 seconds between 10 seconds and 1280 seconds. When this IE is included, the target should transmit a ProvideLocationInformation IE containing early location information according to the responseTimeEarlyFix IE (or more than one ProvideLocationInformation IE in the case where the location information will not fit into a single message), and transmit a subsequent ProvideLocationInformation IE containing the final location information according to the time IE (or more than one ProvideLocationInformation IE in the case where the location information will not fit into a single message). If early location information is not available when the time value in the responseTimeEarlyFix IE expires, the target should ignore transmitting the ProvideLocationInformation. The server SHOULD set the responseTimeEarlyFix IE to a value less than the value of the time IE. If the value of the responseTimeEarlyFix IE is not less than the value of the time IE, the target SHOULD ignore the responseTimeEarlyFix IE. The unit field indicates the unit of the time field and the responseTimeEarlyFix field. The enumeration value "ten-seconds" corresponds to a resolution of 10 seconds. If this field is not present, the unit / resolution is 1 second. Based on the foregoing information, the response time indicated in the QoS requirement can span between 1 second and 128 seconds.
[0171] When the UE uses the QoS information in determining the response time requirement, any of the foregoing information may be used alone or in combination. In certain aspects, the response time requirement may be compared to one or more response time thresholds to determine whether the UE sends the positioning measurement as an SDT or transitions to an RRC connected state to send the positioning measurement.
[0172] In certain aspects, the UE obtains a first amount of measurement data by measuring one or more PRS resources of one or more network entities during a positioning session. The first amount of measurement data obtained by the UE may depend on the assistance data received from the location server and the UE measurement results. For example, the first amount of measurement data may depend on how many PRS resources the UE is configured to measure during the positioning session and / or the ability of the UE to actually measure the PRS resources. When the UE is configured to measure a relatively small number of PRS resources or cannot obtain reliable measurements of all PRS resources, the first amount of measurement data may be relatively small and may be transmitted by the UE to the location server as an SDT. However, when the UE is configured to obtain measurements from a larger number of PRS resources and successfully obtains these measurements, the first amount of measurement data may be greater than the amount of measurement data that can be optimally transmitted as an SDT.
[0173] Regardless of the amount of data in the first amount of measurement data, the UE may perform an operation to reduce the first amount of measurement data to a second amount of measurement data. In such instances, the second amount of measurement data is reported to the location server in one or more SDTs while in an RRC inactive state or an RRC idle state. The data reduction operation achieves various goals. For example, when the first amount of measurement data may exceed the amount of data that can be sent in a threshold number of SDT opportunities, the UE may reduce the first amount of measurement data to an amount that can be sent within a threshold number of SDT opportunities. For another example, when the first amount of measurement data exceeds a transition threshold, the UE may reduce the first amount of measurement data to an amount below the transition threshold to keep the UE in an RRC inactive state or an RRC idle state for sending the second amount of measurement data as an SDT. For another example, when the first amount of measurement data exceeds the amount of measurement data that can be optimally sent as an SDT, the UE may reduce the first amount of measurement data to a second amount of measurement data to optimize the sending of the SDT. Further, the UE may reduce the first amount of measurement data to a second amount of measurement data during a regular process of sending a measurement operation without a specific goal for a target value for the second amount of measurement data.
[0174] The UE may reduce the first amount of measurement data to the second amount of measurement data based on a single criterion or a combination of multiple criteria. In certain aspects, the UE may remove measurement data for one or more TRPs based on a priority ranking of the one or more TRPs as indicated in positioning assistance data, the positioning assistance data being received by the UE for a positioning session. Alternatively or alternatively, the UE may remove measurement data corresponding to PRS resources, TRPs, or PFLs received with signal characteristics below one or more signal characteristic thresholds from the first amount of measurement data.
[0175] Alternatively or alternatively, the UE may remove measurement data corresponding to one or more optional IEs of a measurement report format used to report measurement data to a location server. One such location report IE 1500 may be Fig.15 , where the optional IE is indicated in bold text. As shown in the positioning report IE 1500, the optional IE includes: 1) one or more physical cell identifiers 1502 respectively associated with one or more TRPs of one or more reported measurements associated with the measurement data; 2) one or more globally unique identifiers 1504 respectively associated with one or more TRPs of one or more reported measurements associated with the measurement data; 3) one or more absolute radio frequency channel numbers 1506 respectively associated with one or more TRPs of one or more reported measurements associated with the measurement data; 4) one or more downlink PRS resource identifiers 1508 respectively associated with one or more TRPs of one or more reported measurements associated with the measurement data; 5) one or more downlink PRS resource set identifiers 1510 respectively associated with one or more TRPs of one or more reported measurements associated with the measurement data; 6) one or more additional detection path timing values 1512 respectively associated with one or more TRPs of one or more reported measurements associated with the measurement data; or 7) any combination thereof.
[0176] Fig.16 An example method 1600 of wireless communication that can be performed by a UE according to various aspects of the present disclosure is illustrated. At operation 1602, the UE measures one or more positioning reference signal (PRS) resources from one or more network entities during a positioning session while in a radio resource control (RRC) inactive state or an RRC idle state. In one aspect, operation 1602 can 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 can be considered as means for performing the operation.
[0177] At operation 1604, the UE reports the measurement data to the location server while in the RRC inactive state or the RRC idle state during one or more small data transmission (SDT) opportunities based on the response time requirement of the positioning session, the configuration of the UE to remain in the RRC inactive state or the RRC idle state, the number of small data transmission (SDT) opportunities required to report the measurement data of the one or more PRS resources, or any combination thereof. In one aspect, operation 1604 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.
[0178] As will be appreciated, technical advantages of method 1600 include increasing the ability of a UE to meet response time requirements imposed in a positioning session and / or the ability of a UE to reduce power consumption associated with reporting positioning measurements during a positioning session. Technical advantages may also be achieved due to a reduction in the amount of data sent by the UE to a base station.
[0179] In the above detailed description, 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 deemed to be incorporated into the description accordingly, where each clause itself can be used as a separate example. Although each dependent clause can refer to a specific combination of one clause with other clauses in a clause, the aspects of the dependent 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 dependent clause aspect with any other dependent clause or independent clause or any feature with other dependent clauses and independent clauses. The 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.
[0180] Specific implementation examples are described in the following numbered clauses:
[0181] Clause 1. A method of wireless communication performed by a user equipment (UE), the method comprising: while in a radio resource control (RRC) inactive state or an RRC idle state, measuring one or more positioning reference signal (PRS) resources from one or more network entities during a positioning session; and reporting the measurement data to a location server while in the RRC inactive state or the RRC idle state during one or more small data transmission (SDT) opportunities based on a response time requirement of the positioning session, a configuration of the UE to remain in the RRC inactive state or the RRC idle state, a number of small data transmission (SDT) opportunities required to report measurement data of the one or more PRS resources, or any combination thereof.
[0182] Clause 2. A method according to clause 1, wherein: based on the response time indicated in the quality of service (QoS) requirement being less than or equal to a response time threshold, the measurement data is reported by the UE in the RRC inactive state or the RRC idle state during the one or more SDT opportunities.
[0183] Clause 3. A method according to any one of clauses 1 to 2, wherein: based on the number of SDT opportunities required to report the measurement data being less than or equal to an SDT opportunity threshold, the measurement data is reported by the UE in the RRC inactive state or the RRC idle state during the one or more SDT opportunities.
[0184] Clause 4. The method of any one of clauses 1 to 3, further comprising: reporting the measurement data during multiple SDT opportunities based on the amount of the measurement data being greater than an amount of data that can be sent during a single SDT opportunity.
[0185] Clause 5. According to the method described in any one of clauses 1 to 4, the method further includes: reporting the measurement data to the location server in the RRC connected state based on the response time requirement for reporting the measurement data being greater than a response time threshold, the data volume of the measurement data exceeding the maximum threshold for sending data during the one or more SDT opportunities, or any combination thereof.
[0186] Clause 6. A method according to any one of clauses 1 to 5, wherein the first amount of measurement data is obtained by measuring the one or more PRS resources of the one or more network entities, the method further comprising: reducing the first amount of measurement data to a second amount of measurement data, and reporting the second amount of measurement data to the location server when in the RRC inactive state or the RRC idle state.
[0187] Clause 7. The method of clause 6, wherein reducing the first amount of measurement data comprises removing measurement data corresponding to one or more optional information elements of a measurement reporting format used to report the measurement data to the location server.
[0188] Clause 8. A method according to clause 7, wherein the one or more optional information elements include: one or more physical cell identifiers respectively associated with one or more transmit receive points (TRPs) of one or more reported measurements associated with the measurement data; one or more globally unique identifiers respectively associated with the one or more TRPs of the one or more reported measurements associated with the measurement data; one or more absolute radio frequency channel numbers respectively associated with the one or more TRPs of the one or more reported measurements associated with the measurement data; one or more downlink PRS resource identifiers respectively associated with the one or more TRPs of the one or more reported measurements associated with the measurement data; one or more downlink PRS resource set identifiers respectively associated with the one or more TRPs of the one or more reported measurements associated with the measurement data; one or more additional detection path timing values respectively associated with the one or more TRPs of the one or more reported measurements associated with the measurement data; or any combination thereof.
[0189] Clause 9. A method according to any one of clauses 6 to 8, wherein reducing the first amount of measurement data comprises: removing measurement data for one or more transmit receive points (TRPs) based on a priority ranking of the one or more TRPs as indicated in positioning assistance data, the positioning assistance data being received by the UE for the positioning session.
[0190] Clause 10. A method according to any one of clauses 6 to 9, wherein reducing the first amount of measurement data includes: removing from the first amount of measurement data measurement data corresponding to PRS resources, transmit receive points (TRPs), positioning frequency layers (PFLs), or any combination thereof received with signal characteristics below one or more signal characteristic thresholds.
[0191] Clause 11. A method according to any one of clauses 1 to 10, the method further comprising: sending a buffer status report (BSR), the buffer status report (BSR) indicating the amount of data reported for uplink transmission, wherein the reported amount is less than the actual amount of measurement data to be reported by the UE.
[0192] Clause 12. A method according to clause 11, wherein: the reported amount is less than a transition threshold to allow the UE to remain in the RRC inactive state or the RRC idle state to report the measurement data during the one or more SDT opportunities, and the transition threshold corresponds to the amount of data, exceeding which the UE transitions to the RRC connected state to send uplink data.
[0193] Clause 13. The method according to Clause 12 further includes: transmitting a limited amount of measurement data by location software running on the UE to a medium access control (MAC) layer of the UE, wherein the limited amount of measurement data transmitted by the location software to the MAC layer for transmission during the one or more SDT opportunities causes the reported amount to be less than the transition threshold.
[0194] Clause 14. The method of claim 12, further comprising receiving an indication of the transition threshold from a base station.
[0195] Clause 15. The method according to any one of clauses 12 to 13, further comprising: determining the transition threshold based on a maximum amount of data reported in one or more past BSRs that did not trigger the UE to transition out of the RRC inactive state or the RRC idle state.
[0196] Clause 16. A user equipment (UE), the user equipment (UE) 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: measure one or more positioning reference signal (PRS) resources from one or more network entities during a positioning session while in a radio resource control (RRC) inactive state or an RRC idle state; and report the measurement data to a location server via the at least one transceiver while in the RRC inactive state or the RRC idle state during one or more SDT opportunities based on a response time requirement of the positioning session, a configuration of the UE to remain in the RRC inactive state or the RRC idle state, a number of small data transmission (SDT) opportunities required to report measurement data of the one or more PRS resources, or any combination thereof.
[0197] Clause 17. A UE according to clause 16, wherein: based on the response time indicated in the quality of service (QoS) requirement being less than or equal to a response time threshold, the measurement data is reported by the UE in the RRC inactive state or the RRC idle state during the one or more SDT opportunities.
[0198] Clause 18. A UE according to any one of clauses 16 to 17, wherein: based on the number of SDT opportunities required to report the measurement data being less than or equal to an SDT opportunity threshold, the measurement data is reported by the UE in the RRC inactive state or the RRC idle state during the one or more SDT opportunities.
[0199] Clause 19. A UE according to any one of clauses 16 to 18, wherein the at least one processor is further configured to: report the measurement data via the at least one transceiver during multiple SDT opportunities based on the amount of the measurement data being greater than the amount of data that can be sent during a single SDT opportunity.
[0200] Clause 20. A UE according to any one of clauses 16 to 19, wherein the at least one processor is further configured to: report the measurement data to the location server via the at least one transceiver in an RRC connected state based on the response time requirement for reporting the measurement data being greater than a response time threshold, the data volume of the measurement data exceeding a maximum threshold for sending data during the one or more SDT opportunities, or any combination thereof.
[0201] Clause 21. A UE according to any one of clauses 16 to 20, wherein the first amount of measurement data is obtained by measuring the one or more PRS resources of the one or more network entities, wherein the at least one processor is further configured to: reduce the first amount of measurement data to a second amount of measurement data, and report the second amount of measurement data to the location server via the at least one transceiver when in the RRC inactive state or the RRC idle state.
[0202] Clause 22. A UE according to clause 21, wherein the at least one processor is configured to reduce the first amount of measurement data, including the at least one processor being configured to: remove measurement data corresponding to one or more optional information elements of a measurement reporting format, wherein the measurement reporting format is used to report the measurement data to the location server.
[0203] Clause 23. A UE according to clause 22, wherein the one or more optional information elements include: one or more physical cell identifiers respectively associated with one or more transmit receive points (TRPs) of one or more reported measurements associated with the measurement data; one or more globally unique identifiers respectively associated with the one or more TRPs of the one or more reported measurements associated with the measurement data; one or more absolute radio frequency channel numbers respectively associated with the one or more TRPs of the one or more reported measurements associated with the measurement data; one or more downlink PRS resource identifiers respectively associated with the one or more TRPs of the one or more reported measurements associated with the measurement data; one or more downlink PRS resource set identifiers respectively associated with the one or more TRPs of the one or more reported measurements associated with the measurement data; one or more additional detection path timing values respectively associated with the one or more TRPs of the one or more reported measurements associated with the measurement data; or any combination thereof.
[0204] Clause 24. A UE according to any one of clauses 21 to 23, wherein the at least one processor is configured to reduce the first amount of measurement data, including the at least one processor being configured to: remove measurement data for one or more transmit receive points (TRPs) based on a priority ranking of the one or more TRPs as indicated in positioning assistance data, the positioning assistance data being received by the UE for the positioning session.
[0205] Clause 25. A UE according to any one of clauses 21 to 24, wherein the at least one processor is configured to reduce the first amount of measurement data, including the at least one processor being configured to: remove from the first amount of measurement data measurement data corresponding to PRS resources, transmit receive points (TRPs), positioning frequency layers (PFLs), or any combination thereof received with signal characteristics below one or more signal characteristic thresholds.
[0206] Clause 26. A UE according to any one of clauses 16 to 25, wherein the at least one processor is further configured to: send a buffer status report (BSR) via the at least one transceiver, wherein the buffer status report (BSR) indicates the amount of data reported for uplink transmission, wherein the reported amount is less than the actual amount of measurement data to be reported by the UE.
[0207] Clause 27. A UE according to clause 26, wherein: the reported amount is less than a transition threshold to allow the UE to remain in the RRC inactive state or the RRC idle state to report the measurement data during the one or more SDT opportunities, and the transition threshold corresponds to an amount of data, exceeding which the UE transitions to the RRC connected state to send uplink data.
[0208] Clause 28. A UE according to clause 27, wherein the at least one processor is further configured to: transmit a limited amount of measurement data to a medium access control (MAC) layer of the UE via the at least one transceiver by location software running on the UE, wherein the limited amount of measurement data transmitted by the location software to the MAC layer for transmission during the one or more SDT opportunities causes the reported amount to be less than the transition threshold.
[0209] Clause 29. A UE as described in any of clauses 27 to 28, wherein the at least one processor is further configured to: receive an indication of the transition threshold from a base station via the at least one transceiver.
[0210] Clause 30. A UE according to any one of clauses 27 to 28, wherein the at least one processor is further configured to determine the transition threshold based on a maximum amount of data reported in one or more past BSRs that did not trigger the UE to transition out of the RRC inactive state or the RRC idle state.
[0211] Clause 31. A user equipment (UE), the user equipment (UE) comprising: means for measuring one or more positioning reference signal (PRS) resources from one or more network entities during a positioning session while in a radio resource control (RRC) inactive state or an RRC idle state; and means for reporting measurement data of the one or more PRS resources to a location server while in the RRC inactive state or the RRC idle state during one or more small data transmission (SDT) opportunities based on: a response time requirement of the positioning session, a configuration of the UE to remain in the RRC inactive state or the RRC idle state, a number of SDT opportunities required to report the measurement data, or any combination thereof.
[0212] Clause 32. A UE according to clause 31, wherein: based on the response time indicated in the quality of service (QoS) requirement being less than or equal to a response time threshold, the measurement data is reported by the UE in the RRC inactive state or the RRC idle state during the one or more SDT opportunities.
[0213] Clause 33. A UE according to any one of clauses 31 to 32, wherein: based on the number of SDT opportunities required to report the measurement data being less than or equal to an SDT opportunity threshold, the measurement data is reported by the UE in the RRC inactive state or the RRC idle state during the one or more SDT opportunities.
[0214] Clause 34. A UE as described in any of clauses 31 to 33, the UE further comprising: means for reporting the measurement data during multiple SDT opportunities based on the amount of the measurement data being greater than an amount of data that can be sent during a single SDT opportunity.
[0215] Clause 35. A UE according to any one of clauses 31 to 34, wherein the UE further comprises: a component for reporting the measurement data to the location server in an RRC connected state based on: the response time requirement for reporting the measurement data is greater than a response time threshold, the amount of the measurement data exceeds a maximum threshold for sending data during the one or more SDT opportunities, or any combination thereof.
[0216] Clause 36. A UE according to any one of clauses 31 to 35, wherein the first amount of measurement data is obtained by measuring the one or more PRS resources of the one or more network entities, and the UE also includes: a component for reducing the first amount of measurement data to a second amount of measurement data, and a component for reporting the second amount of measurement data to the location server when in the RRC inactive state or the RRC idle state.
[0217] Clause 37. A UE according to clause 36, wherein the means for reducing the first amount of measurement data comprises means for removing measurement data corresponding to one or more optional information elements of a measurement reporting format used to report the measurement data to the location server.
[0218] Clause 38. A UE according to clause 37, wherein the one or more optional information elements include: one or more physical cell identifiers respectively associated with one or more transmit receive points (TRPs) of one or more reported measurements associated with the measurement data; one or more globally unique identifiers respectively associated with the one or more TRPs of the one or more reported measurements associated with the measurement data; one or more absolute radio frequency channel numbers respectively associated with the one or more TRPs of the one or more reported measurements associated with the measurement data; one or more downlink PRS resource identifiers respectively associated with the one or more TRPs of the one or more reported measurements associated with the measurement data; one or more downlink PRS resource set identifiers respectively associated with the one or more TRPs of the one or more reported measurements associated with the measurement data; one or more additional detection path timing values respectively associated with the one or more TRPs of the one or more reported measurements associated with the measurement data; or any combination thereof.
[0219] Clause 39. A UE according to any one of clauses 36 to 38, wherein the component for reducing the first amount of measurement data includes: a component for removing measurement data for one or more transmit receive points (TRPs) based on a priority ranking of the one or more TRPs as indicated in positioning assistance data, the positioning assistance data being received by the UE for the positioning session.
[0220] Clause 40. A UE according to any one of clauses 36 to 39, wherein the component for reducing the first amount of measurement data includes: a component for removing measurement data corresponding to PRS resources, transmit reception points (TRPs), positioning frequency layers (PFLs), or any combination thereof received with signal characteristics below one or more signal characteristic thresholds from the first amount of measurement data.
[0221] Clause 41. A UE according to any one of clauses 31 to 40, the UE further comprising: a component for sending a buffer status report (BSR), the buffer status report (BSR) indicating the amount of data reported for uplink transmission, wherein the reported amount is less than the actual amount of measurement data to be reported by the UE.
[0222] Clause 42. A UE according to clause 41, wherein: the reported amount is less than a transition threshold to allow the UE to remain in the RRC inactive state or the RRC idle state to report the measurement data during the one or more SDT opportunities, and the transition threshold corresponds to an amount of data, exceeding which the UE transitions to the RRC connected state to send uplink data.
[0223] Clause 43. According to clause 42, the UE also includes: a component for transmitting a limited amount of measurement data to a medium access control (MAC) layer of the UE by location software running on the UE, wherein the limited amount of measurement data transmitted by the location software to the MAC layer for transmission during the one or more SDT opportunities causes the reported amount to be less than the transition threshold.
[0224] Clause 44. A UE as described in any of clauses 42 to 43, the UE further comprising: means for receiving an indication of the transition threshold from a base station.
[0225] Clause 45. A UE according to any one of clauses 42 to 43, the UE further comprising: a component for determining the transition threshold based on a maximum amount of data reported in one or more past BSRs that did not trigger the UE to transition out of the RRC inactive state or the RRC idle state.
[0226] Clause 46. A non-transitory computer-readable medium storing computer-executable instructions that, when executed by a user equipment (UE), cause the UE to: measure one or more positioning reference signal (PRS) resources from one or more network entities during a positioning session while in a radio resource control (RRC) inactive state or an RRC idle state; and report the measurement data to a location server during one or more small data transmission (SDT) opportunities while in the RRC inactive state or the RRC idle state based on a response time requirement for the positioning session, a configuration for the UE to remain in the RRC inactive state or the RRC idle state, a number of small data transmission (SDT) opportunities required to report measurement data of the one or more PRS resources, or any combination thereof.
[0227] Clause 47. A non-transitory computer-readable medium according to clause 46, wherein: based on the response time indicated in the quality of service (QoS) requirement being less than or equal to a response time threshold, the measurement data is reported by the UE in the RRC inactive state or the RRC idle state during the one or more SDT opportunities.
[0228] Clause 48. A non-transitory computer-readable medium according to any one of clauses 46 to 47, wherein: based on the number of SDT opportunities required to report the measurement data being less than or equal to an SDT opportunity threshold, the measurement data is reported by the UE in the RRC inactive state or the RRC idle state during the one or more SDT opportunities.
[0229] Clause 49. A non-transitory computer-readable medium according to any one of clauses 46 to 48, wherein the non-transitory computer-readable medium also includes computer-executable instructions, which, when executed by the UE, cause the UE to: report the measurement data during multiple SDT opportunities based on the amount of the measurement data being greater than the amount of data that can be sent during a single SDT opportunity.
[0230] Clause 50. A non-transitory computer-readable medium according to any one of clauses 46 to 49, wherein the non-transitory computer-readable medium also includes computer-executable instructions, which, when executed by the UE, cause the UE to: report the measurement data to the location server in an RRC connected state based on the response time requirement for reporting the measurement data being greater than a response time threshold, the amount of data of the measurement data exceeding a maximum threshold for sending data during the one or more SDT opportunities, or any combination thereof.
[0231] Clause 51. A non-transitory computer-readable medium according to any one of clauses 46 to 50, wherein the first amount of measurement data is obtained by measuring the one or more PRS resources of the one or more network entities, wherein the computer-executable instructions also include computer-executable instructions that, when executed by the UE, cause the UE to: reduce the first amount of measurement data to a second amount of measurement data, and report the second amount of measurement data to the location server when in the RRC inactive state or the RRC idle state.
[0232] Clause 52. A non-transitory computer-readable medium according to clause 51, wherein the computer executable instructions that, when executed by the UE, cause the UE to reduce the first amount of measurement data include computer executable instructions that, when executed by the UE, cause the UE to: remove measurement data corresponding to one or more optional information elements of a measurement reporting format, wherein the measurement reporting format is used to report the measurement data to the location server.
[0233] Clause 53. A non-transitory computer-readable medium according to clause 52, wherein the one or more optional information elements include: one or more physical cell identifiers respectively associated with one or more transmit receive points (TRPs) of one or more reported measurements associated with the measurement data; one or more globally unique identifiers respectively associated with the one or more TRPs of the one or more reported measurements associated with the measurement data; one or more absolute radio frequency channel numbers respectively associated with the one or more TRPs of the one or more reported measurements associated with the measurement data; one or more downlink PRS resource identifiers respectively associated with the one or more TRPs of the one or more reported measurements associated with the measurement data; one or more downlink PRS resource set identifiers respectively associated with the one or more TRPs of the one or more reported measurements associated with the measurement data; one or more additional detection path timing values respectively associated with the one or more TRPs of the one or more reported measurements associated with the measurement data; or any combination thereof.
[0234] Clause 54. A non-transitory computer-readable medium according to any one of clauses 51 to 53, wherein the computer executable instructions that, when executed by the UE, cause the UE to reduce the first amount of measurement data include computer executable instructions that, when executed by the UE, cause the UE to: remove measurement data for one or more transmit receive points (TRPs) based on a priority ranking of the one or more TRPs as indicated in positioning assistance data, the positioning assistance data being received by the UE for the positioning session.
[0235] Clause 55. A non-transitory computer-readable medium according to any one of clauses 51 to 54, wherein the computer executable instructions that, when executed by the UE, cause the UE to reduce the first amount of measurement data include computer executable instructions that, when executed by the UE, cause the UE to: remove from the first amount of measurement data measurement data corresponding to PRS resources, transmit receive points (TRPs), positioning frequency layers (PFLs), or any combination thereof received with signal characteristics below one or more signal characteristic thresholds.
[0236] Clause 56. A non-transitory computer-readable medium according to any one of clauses 46 to 55, wherein the non-transitory computer-readable medium also includes computer-executable instructions, which, when executed by the UE, cause the UE to: send a buffer status report (BSR), wherein the buffer status report (BSR) indicates a reported amount of data for uplink transmission, wherein the reported amount is less than an actual amount of measurement data to be reported by the UE.
[0237] Clause 57. A non-transitory computer-readable medium according to clause 56, wherein: the reported amount is less than a transition threshold to allow the UE to remain in the RRC inactive state or the RRC idle state to report the measurement data during the one or more SDT opportunities, and the transition threshold corresponds to an amount of data, exceeding which the UE transitions to the RRC connected state to send uplink data.
[0238] Clause 58. A non-transitory computer-readable medium according to Clause 57, wherein the non-transitory computer-readable medium also includes computer-executable instructions, which, when executed by the UE, cause the UE to: transmit a limited amount of measurement data to a medium access control (MAC) layer of the UE by location software running on the UE, wherein the limited amount of measurement data transmitted by the location software to the MAC layer for transmission during the one or more SDT opportunities causes the reported amount to be less than the transition threshold.
[0239] Clause 59. A non-transitory computer-readable medium as described in any of clauses 57 to 58, the non-transitory computer-readable medium further comprising computer-executable instructions which, when executed by the UE, cause the UE to: receive an indication of the transition threshold from a base station.
[0240] Clause 60. A non-transitory computer-readable medium according to any one of clauses 57 to 58, wherein the non-transitory computer-readable medium also includes computer-executable instructions, which, when executed by the UE, cause the UE to: determine the transition threshold based on the maximum amount of data reported in one or more past BSRs that did not trigger the UE to transition out of the RRC inactive state or the RRC idle state.
[0241] 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.
[0242] 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 may 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, frames, modules, circuits, and steps have been generally described in terms of their functionality. Whether such functionality is implemented as hardware or software depends on the specific application and the design constraints proposed for the entire system. Those skilled in the art may 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.
[0243] 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.
[0244] 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 solution, 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 solution, the processor and the storage medium may reside in a user terminal as discrete components.
[0245] 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 may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage devices, disk storage devices or other magnetic storage devices, or any other medium that can be used to carry or store desired program codes in the form of instructions or data structures and can be accessed by a computer. Moreover, 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 disks reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer readable media.
[0246] 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 user equipment (UE), the method comprising: measuring one or more positioning reference signal (PRS) resources from one or more network entities during a positioning session while in a radio resource control (RRC) inactive state or an RRC idle state; as well as and reporting the measurement data of the one or more PRS resources to a location server while in the RRC inactive state or the RRC idle state during one or more small data transmission (SDT) opportunities based on: the response time requirement of the positioning session, The UE remains in the RRC inactive state or the RRC idle state. the number of SDT opportunities required to report the measurement data, or Any combination of them.
2. The method according to claim 1, wherein: The measurement data is reported by the UE in the RRC inactive state or the RRC idle state during the one or more SDT occasions based on a response time indicated in a quality of service (QoS) requirement being less than or equal to a response time threshold.
3. The method according to claim 1, wherein: Based on the number of the SDT occasions required to report the measurement data being less than or equal to an SDT occasion threshold, the measurement data is reported by the UE in the RRC inactive state or the RRC idle state during the one or more SDT occasions.
4. The method according to claim 1, further comprising: Based on the amount of the measurement data being greater than an amount of data that can be transmitted during a single SDT opportunity, the measurement data is reported during a plurality of SDT opportunities.
5. The method according to claim 1, further comprising: Reporting the measurement data to the location server in an RRC connected state based on the following: The response time requirement for reporting the measurement data is greater than a response time threshold, The amount of the measurement data exceeds a maximum threshold for sending data during the one or more SDT opportunities, or Any combination of them.
6. The method according to claim 1, wherein the first amount of measurement data is obtained by measuring the one or more PRS resources of the one or more network entities, the method further comprising: reducing said first amount of measurement data to a second amount of measurement data, and When in the RRC inactive state or the RRC idle state, reporting the second amount of measurement data to the location server.
7. The method of claim 6, wherein reducing the first amount of measurement data comprises: Measurement data corresponding to one or more optional information elements of a measurement reporting format used to report the measurement data to the location server is removed.
8. The method of claim 7, wherein the one or more optional information elements include: one or more physical cell identifiers respectively associated with one or more transmit reception points (TRPs) of one or more reported measurements associated with the measurement data; one or more globally unique identifiers respectively associated with the one or more TRPs associated with the one or more reported measurements of the measurement data; one or more absolute radio frequency channel numbers respectively associated with the one or more TRPs associated with the one or more reported measurements of the measurement data; one or more downlink PRS resource identifiers respectively associated with the one or more TRPs associated with the one or more reported measurements of the measurement data; one or more downlink PRS resource set identifiers respectively associated with the one or more TRPs associated with the one or more reported measurements of the measurement data; one or more additional detection path timing values respectively associated with said one or more TRPs associated with said one or more reported measurements of said measurement data; or Any combination of them.
9. The method of claim 6, wherein reducing the first amount of measurement data comprises: Measurement data for one or more transmit receive points (TRPs) are removed based on a priority ranking of the one or more TRPs as indicated in positioning assistance data, the positioning assistance data being received by the UE for the positioning session.
10. The method of claim 6, wherein reducing the first amount of measurement data comprises: Measurement data corresponding to PRS resources, transmit reception points (TRPs), positioning frequency layers (PFLs), or any combination thereof received with signal characteristics below one or more signal characteristic thresholds is removed from the first amount of measurement data.
11. The method according to claim 1, further comprising: A buffer status report (BSR) is sent, the buffer status report (BSR) indicating a reported amount of data for uplink transmission, wherein the reported amount is less than an actual amount of measurement data to be reported by the UE.
12. The method according to claim 11, wherein: The reported amount is less than a transition threshold to allow the UE to remain in the RRC inactive state or the RRC idle state to report the measurement data during the one or more SDT opportunities, and The transition threshold corresponds to a data amount, exceeding which the UE transitions to an RRC connected state to send uplink data.
13. The method according to claim 12, further comprising: A limited amount of measurement data is transmitted by location software running on the UE to a medium access control (MAC) layer of the UE, wherein the limited amount of measurement data transmitted by the positioning software to the MAC layer for transmission during the one or more SDT opportunities results in a reported amount being less than the transition threshold.
14. The method according to claim 12, further comprising: An indication of the transition threshold is received from a base station.
15. The method according to claim 12, further comprising: The transition threshold is determined based on a maximum amount of data reported in one or more past BSRs that does not trigger the UE to transition out of the RRC inactive state or the RRC idle state.
16. A user equipment (UE), the user equipment (UE) 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: measuring one or more positioning reference signal (PRS) resources from one or more network entities during a positioning session while in a radio resource control (RRC) inactive state or an RRC idle state; as well as and reporting, via the at least one transceiver, measurement data of the one or more PRS resources to a location server during one or more small data transmission (SDT) opportunities while in the RRC inactive state or the RRC idle state based on: the response time requirement of the positioning session, The UE remains in the RRC inactive state or the RRC idle state. the number of SDT opportunities required to report the measurement data, or Any combination of them.
17. The UE according to claim 16, wherein: The measurement data is reported by the UE in the RRC inactive state or the RRC idle state during the one or more SDT occasions based on a response time indicated in a quality of service (QoS) requirement being less than or equal to a response time threshold.
18. The UE according to claim 16, wherein: Based on the number of the SDT occasions required to report the measurement data being less than or equal to an SDT occasion threshold, the measurement data is reported by the UE in the RRC inactive state or the RRC idle state during the one or more SDT occasions.
19. The UE of claim 16, wherein the at least one processor is further configured to: Based on the amount of the measurement data being greater than an amount of data that can be transmitted during a single SDT opportunity, the measurement data is reported via the at least one transceiver during a plurality of SDT opportunities.
20. The UE of claim 16, wherein the at least one processor is further configured to: Reporting the measurement data to the location server via the at least one transceiver in an RRC connected state based on: The response time requirement for reporting the measurement data is greater than a response time threshold, and a data volume of the measurement data exceeds a maximum threshold for sending data during the one or more SDT opportunities, or Any combination of them.
21. The UE of claim 16, wherein the first amount of measurement data is obtained by measuring the one or more PRS resources of the one or more network entities, wherein the at least one processor is further configured to: reducing said first amount of measurement data to a second amount of measurement data, and The second amount of measurement data is reported to the location server via the at least one transceiver while in the RRC inactive state or the RRC idle state.
22. The UE of claim 21 , wherein the at least one processor is configured to reduce the first amount of measurement data comprises the at least one processor being configured to: Measurement data corresponding to one or more optional information elements of a measurement reporting format used to report the measurement data to the location server is removed.
23. The UE of claim 22, wherein the one or more optional information elements include: one or more physical cell identifiers respectively associated with one or more transmit reception points (TRPs) of one or more reported measurements associated with the measurement data; one or more globally unique identifiers respectively associated with the one or more TRPs associated with the one or more reported measurements of the measurement data; one or more absolute radio frequency channel numbers respectively associated with the one or more TRPs associated with the one or more reported measurements of the measurement data; one or more downlink PRS resource identifiers respectively associated with the one or more TRPs associated with the one or more reported measurements of the measurement data; one or more downlink PRS resource set identifiers respectively associated with the one or more TRPs associated with the one or more reported measurements of the measurement data; one or more additional detection path timing values respectively associated with said one or more TRPs associated with said one or more reported measurements of said measurement data; or Any combination of them.
24. The UE of claim 21 , wherein the at least one processor is configured to reduce the first amount of measurement data comprises the at least one processor being configured to: Measurement data for one or more transmit receive points (TRPs) are removed based on a priority ranking of the one or more TRPs as indicated in positioning assistance data, the positioning assistance data being received by the UE for the positioning session.
25. The UE of claim 21 , wherein the at least one processor is configured to reduce the first amount of measurement data comprises the at least one processor being configured to: Measurement data corresponding to PRS resources, transmit reception points (TRPs), positioning frequency layers (PFLs), or any combination thereof received with signal characteristics below one or more signal characteristic thresholds is removed from the first amount of measurement data.
26. The UE of claim 16, wherein the at least one processor is further configured to: A buffer status report (BSR) is sent, via the at least one transceiver, the buffer status report (BSR) indicating a reported amount of data for uplink transmission, wherein the reported amount is less than an actual amount of measurement data to be reported by the UE.
27. The UE according to claim 26, wherein: The reported amount is less than a transition threshold to allow the UE to remain in the RRC inactive state or the RRC idle state to report the measurement data during the one or more SDT opportunities, and The transition threshold corresponds to a data amount, exceeding which the UE transitions to an RRC connected state to send uplink data.
28. The UE of claim 27, wherein the at least one processor is further configured to: A limited amount of measurement data is transmitted by location software running on the UE via the at least one transceiver to a medium access control (MAC) layer of the UE, wherein the limited amount of measurement data transmitted by the location software to the MAC layer for transmission during the one or more SDT opportunities results in a reported amount being less than the transition threshold.
29. A user equipment (UE), the user equipment (UE) comprising: means for measuring one or more positioning reference signal (PRS) resources from one or more network entities during a positioning session while in a radio resource control (RRC) inactive state or an RRC idle state; and Means for reporting measurement data of the one or more PRS resources to a location server while in the RRC inactive state or the RRC idle state during one or more small data transmission (SDT) opportunities based on: the response time requirement of the positioning session, The UE remains in the RRC inactive state or the RRC idle state. the number of SDT opportunities required to report the measurement data, or Any combination of them.
30. A non-transitory computer-readable medium storing computer-executable instructions that, when executed by a user equipment (UE), cause the UE to: While in a radio resource control (RRC) inactive state or an RRC idle state, measuring one or more positioning reference signal (PRS) resources from one or more network entities during a positioning session; and and reporting the measurement data of the one or more PRS resources to a location server while in the RRC inactive state or the RRC idle state during one or more small data transmission (SDT) opportunities based on: the response time requirement of the positioning session, The UE remains in the RRC inactive state or the RRC idle state. the number of SDT opportunities required to report the measurement data, or Any combination of them.
