Techniques including groups for supporting positioning of mobile user equipments in reduced power state

Abstract

Techniques are described for supporting positioning of a mobile UE in a reduced power state, such as for low power high accuracy positioning (LPHAP). In many embodiments, uplink (UL) and / or UL + downlink (DL) positioning of UEs in an inactive and / or idle state is enabled in a manner that improves positioning services in a 5G network by reducing the need to transition to a higher power state. For example, a set of positioning configurations may be utilized to enable common positioning configurations, or portions thereof, to be used in multiple network cells. In various embodiments, a power metric of a signal may be utilized to determine a network cell in a location configuration group. In another example, various techniques may be utilized to obtain, verify, or update a positioning configuration and / or to activate a positioning transmission at a UE if the UE is in an inactive or idle state.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of and priority to U.S. Provisional Patent Application No. 63 / 484,884, filed on February 14, 2023. The entire contents of this U.S. Provisional Patent Application are incorporated herein by reference. Technical Field

[0003] The present disclosure relates generally to wireless technologies and, more particularly, to supporting positioning of mobile user equipment in a reduced power state. Background Art

[0004] In telecommunications, 5G is the fifth generation technology standard for broadband cellular networks. Like its predecessor, 5G networks are cellular networks in which the service area is divided into small geographic areas called network cells (or cells). The 3rd Generation Partnership Project (3GPP) is an industry consortium that develops standards for 5G. In 5G, many different features are supported, such as positioning. Positioning may refer to the process used to identify the location of a mobile user equipment (UE), whether stationary or moving. Position determination can be achieved using various techniques, such as by determining one or more of the round-trip time (RTT), angle of arrival (AoA), angle of departure (AoD), and time difference of arrival (TDOA) of the signal. In 5G, AoA and AoD positioning techniques can be supported using multi-user multiple-input multiple-output (MIMO) antennas, which provide precise orientation of the signal in a specific direction rather than broadcasting in multiple directions. Summary of the Invention

[0005] Processes, machines, and articles of manufacture are described for supporting location of mobile user equipment in a reduced power state. It should be understood that the embodiments can be combined in any number of ways without departing from the scope of the present disclosure.

[0006] Implementations may include: releasing from a connected state to an inactive or idle state at the UE; determining that a current positioning configuration is invalid; and obtaining an updated positioning configuration at the UE in the inactive or idle state.

[0007] An implementation may include: obtaining a positioning configuration in a first network cell included in a positioning configuration group; releasing from a connected state to an inactive or idle state in the first network cell; switching from the first network cell to a second network cell, wherein the second network cell is included in the positioning configuration group; and based on the first network cell and the second network cell being included in the positioning configuration group, using at least a portion of the positioning configuration obtained in the first network cell in the inactive or idle state for positioning in the second network cell.

[0008] Other processes, machines, and articles of manufacture are also described herein, which may be combined in any number of ways without departing from the scope of the present disclosure, such as with the embodiments of the summary. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] The present disclosure is illustrated by way of example and is not limited to the figures of the accompanying drawings in which like reference numerals indicate like elements. To easily identify the discussion of any particular element or action, one or more of the most significant digits in a reference numeral refers to the figure number that first introduces the element.

[0010] Figure 1 An example wireless communication system is illustrated in accordance with some embodiments.

[0011] Figure 2 A base station (BS) in communication with a user equipment (UE) device is illustrated according to some embodiments.

[0012] Figure 3 An example block diagram of a UE according to some embodiments is illustrated.

[0013] Figure 4 An example block diagram of a BS according to some embodiments is illustrated.

[0014] Figure 5 An example block diagram of cellular communication circuitry is illustrated in accordance with some embodiments.

[0015] Figure 6 An example block diagram of network messaging is illustrated according to some embodiments.

[0016] Figure 7 Various aspects of positioning in a telecommunications network according to some embodiments are illustrated.

[0017] Figure 8 A logic flow for updating a positioning configuration according to some embodiments is illustrated.

[0018] Figure 9A and Figure 9B An exemplary process diagram for updating a positioning configuration in an inactive state is illustrated according to some embodiments.

[0019] Figure 10A and Figure 10B An exemplary process diagram for updating a positioning configuration in an idle state is illustrated according to some embodiments.

[0020] Figures 11A to 11C An exemplary process diagram for positioning an activation process according to some embodiments is illustrated.

[0021] Figure 12Illustrated is a logic flow of an exemplary technique for obtaining an updated positioning configuration according to some embodiments.

[0022] Figure 13 A logic flow is illustrated for an exemplary technique for locating a configuration group according to some embodiments. DETAILED DESCRIPTION

[0023] Techniques for supporting positioning of mobile user equipment in a reduced power state are described. In the following description, numerous specific details are set forth to provide a thorough explanation of the embodiments of the present disclosure. However, it will be apparent to those skilled in the art that the embodiments of the present disclosure may be practiced without these specific details. In other instances, well-known components, structures, and techniques have not been shown in detail in order to avoid obscuring the understanding of this description.

[0024] Reference in this specification to "one embodiment" or "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment can be included in at least one embodiment of the present disclosure. The appearance of the phrase "in one embodiment" in various places in this specification is not necessarily referring to the same embodiment.

[0025] In the following description and claims, the terms "coupled" and "connected," and their derivatives, may be used. It should be understood that these terms are not intended to be synonymous with each other. "Coupled" is used to indicate that two or more elements, which may or may not be in direct physical or electrical contact with each other, cooperate or interact with each other. "Connected" is used to indicate the establishment of communication between two or more elements that are coupled to each other.

[0026] The processes depicted in the following figures are performed by processing logic components that include hardware (e.g., circuitry, dedicated logic components, etc.), software (such as software running on a general-purpose computer system or a dedicated machine), or a combination of both. Although the processes are described below as operating in certain sequential order, it should be understood that some of the operations described may be performed in a different order. Furthermore, some operations may be performed in parallel rather than sequentially.

[0027] The terms "server," "client," and "device" are intended to refer generally to data processing systems and not specifically to specific form factors of a server, client, and / or device.

[0028] In general, the present disclosure describes techniques for supporting positioning of mobile UEs in a reduced power state. For example, the techniques disclosed herein can be used to enable a UE to perform low power high accuracy positioning (LPHAP). In many embodiments, these techniques can facilitate uplink (UL) and / or UL+downlink (DL) positioning of UEs in an inactive and / or idle state in a manner that improves positioning services in 5G networks by reducing the need to transition to a higher power state (e.g., a connected state). For example, SRS enhancement based on a sounding reference signal (SRS) positioning validity area can be used to reduce the need to transition to a connected state for positioning (re)configuration. In some such examples, a positioning configuration group can be utilized to enable a common positioning configuration or portion thereof to be used in multiple network cells. In various embodiments, a signal power metric can be utilized to determine the network cells in the positioning configuration group. In another example, various techniques are utilized to obtain, verify, or update a positioning configuration (e.g., positioning SRS (SRSp) configuration, timing advance (TA) configuration, path loss reference, etc.) and / or activate positioning transmission at the UE when the UE is in an inactive or idle state. It should be understood that various aspects of telecommunication networks, capabilities, protocols and procedures related to the techniques described herein and terminology referenced herein may be found in 3GPP Technical Specifications (TSs), such as TS 38.321, TS 38.331, TS 22.104 and TS 22.261.

[0029] The subject matter described herein provides numerous technical advantages. For example, the computer-based techniques of the present disclosure improve the functionality of telecommunication systems compared to conventional approaches because these techniques implement robust support for LPHAP, which can improve positioning power efficiency, positioning accuracy, accessibility, and efficiency of telecommunication networks, reduce congestion, and provide expanded capabilities compared to conventional approaches. For example, facilitating positioning in an inactive or idle state can enable available radio resources to support more UEs. It can also enable tracking the exact location of a UE in states other than a connected state. In another example, UE battery life can be extended by enabling the UE to spend more time in an inactive or idle state rather than having to transition back to a connected state (such as to update configuration data). In yet another example, positioning configuration validity criteria can be used to extend the availability of positioning configurations, such as by reducing the frequency with which new positioning configurations are required. Therefore, the embodiments disclosed herein can be used to improve the functionality of computers and / or improve the technical fields of telecommunications, 5G positioning services, and / or LPHAP.

[0030] Figure 1 A simplified example wireless communication system according to some embodiments is illustrated. Note that Figure 1The system is only one example of a possible system, and features of the present disclosure may be implemented in any of a variety of systems as desired.

[0031] As shown, the example wireless communication system includes a base station 102A that communicates with one or more user devices 106A, 106B, 106N, etc. via a transmission medium. Each user device may be referred to herein as a "user equipment" (UE) or a UE device. Therefore, user device 106 is referred to as a UE or a UE device.

[0032] Base station (BS) 102A may be a base transceiver station (BTS) or a cell site ("cellular base station") and may include hardware that enables wireless communications with UEs 106A through 106N.

[0033] The communication area (or coverage area) of a base station may be referred to as a "cell". The base station 102A and the UE 106 may be configured to communicate over a transmission medium using any of a variety of radio access technologies (RATs), also known as wireless communication technologies or telecommunication standards, such as GSM, UMTS (associated with, for example, WCDMA or TD-SCDMA air interfaces), LTE, LTE-Advanced (LTE-A), 5G New Radio (5G NR), HSPA, 3GPP2 CDMA2000 (e.g., 1xRTT, 1xEV-DO, HRPD, eHRPD), etc. Note that if the base station 102A is implemented in the context of LTE, it may alternatively be referred to as an 'eNodeB' or an 'eNB'. Note that if the base station 102A is implemented in the context of 5G NR, it may alternatively be referred to as a 'gNodeB' or a 'gNB'. Next generation eNBs (ng-eNBs) may include enhanced versions of eNBs that use the 4G LTE air interface to connect 5G UEs to the 5G core network.

[0034] As shown, base station 102A may also be equipped to communicate with network 100 (e.g., in various possibilities, a core network of a cellular service provider, a telecommunications network such as a public switched telephone network (PSTN), and / or the Internet). Thus, base station 102A may facilitate communication between user devices and / or between user devices and network 100. Specifically, cellular base station 102A may provide UE 106 with various telecommunications capabilities (such as voice, SMS, and / or data services). It should be understood that in various embodiments, the term network may be used to collectively refer to one or more devices and components that form a telecommunications network. For example, reference to a network transmitting or receiving data to / from a UE may refer to one or more portions of a core network of a cellular service provider and / or one or more base stations. In some such examples, data to be transmitted to a UE may be determined by a core network component and then relayed to the UE via a base station. In other such examples, data to be transmitted to a UE may be determined by a base station and transmitted to the UE.

[0035] Base station 102A and other similar base stations (such as base stations 102B...102N) operating according to the same or different cellular communication standards can therefore provide a network of cells that can provide continuous or nearly continuous overlapping service to UEs 106A-N and similar devices over a geographic area via one or more cellular communication standards.

[0036] Thus, although base station 102A may function as Figure 1 106A-N, each UE 106 may also be capable of receiving signals from (and possibly within communication range of) one or more other cells (which may be provided by base stations 102B-N and / or any other base stations), which may be referred to as "neighboring cells." Such cells may also be capable of facilitating communications between user devices and / or between user devices and network 100. Such cells may include "macro" cells, "micro" cells, "pico" cells, and / or cells of any other variety of granularity of service area size. For example, in Figure 1 The base stations 102A-B illustrated in FIG may be macro cells, while the base station 102N may be a micro cell. Other configurations are also possible.

[0037] In some embodiments, base station 102A may be a next-generation base station, such as a 5G New Radio (5G NR) base station or "gNB." In some embodiments, a gNB may be connected to a legacy evolved packet core (EPC) network and / or to an NR core (NRC) network. Furthermore, a gNB cell may include one or more transition and reception points (TRPs). Furthermore, a UE capable of operating in accordance with 5G NR may be connected to one or more TRPs within one or more gNBs.

[0038] It is noted that the UE 106 may be capable of communicating using multiple wireless communication standards. For example, the UE 106 may be configured to communicate using wireless networking (e.g., Wi-Fi) and / or peer-to-peer wireless communication protocols (e.g., Bluetooth, Wi-Fi peer-to-peer, etc.) in addition to at least one cellular communication protocol (e.g., GSM, UMTS (associated with, for example, WCDMA or TD-SCDMA air interfaces), LTE, LTE-A, 5G NR, HSPA, 3GPP2 CDMA2000 (e.g., 1xRTT, 1xEV-DO, HRPD, eHRPD), etc.). If desired, the UE 106 may also or alternatively be configured to communicate using one or more global navigation satellite systems (GNSS, such as GPS or GLONASS), one or more mobile television broadcast standards (e.g., ATSC-M / H or DVB-H), and / or any other wireless communication protocols. Other combinations of wireless communication standards (including more than two wireless communication standards) are also possible.

[0039] Figure 2 Illustrated in accordance with some embodiments is a user equipment 106 (e.g., one of devices 106A through 106N) in communication with a base station 102. The UE 106 may be a device with cellular communication capabilities, such as a mobile phone, handheld device, computer or tablet, or virtually any type of wireless device.

[0040] The UE 106 may include a processor configured to execute program instructions stored in a memory. The UE 106 may perform any of the method embodiments described herein by executing such stored instructions. Alternatively or in addition, the UE 106 may include a programmable hardware element, such as an FPGA (field programmable gate array) configured to perform any of the method embodiments described herein or any portion of any of the method embodiments described herein.

[0041] UE 106 may include one or more antennas for communicating using one or more wireless communication protocols or technologies. In some embodiments, UE 106 may be configured to communicate using, for example, 5G NR, CDMA2000 (1xRTT, 1xEV-DO, HRPD, eHRPD), or LTE using a single shared radio and / or GSM or LTE using a single shared radio. The shared radio may be coupled to a single antenna, or may be coupled to multiple antennas (e.g., for MIMO) for performing wireless communications. Generally speaking, the radio may include any combination of a baseband processor, analog RF signal processing circuitry (e.g., including filters, mixers, oscillators, amplifiers, etc.), or digital processing circuitry (e.g., for digital modulation and other digital processing). Similarly, the radio may implement one or more receive chains and transmit chains using the aforementioned hardware. For example, UE 106 may share one or more portions of a receive chain and / or transmit chain between multiple wireless communication technologies (such as those discussed above).

[0042] In some embodiments, the UE 106 may include a separate transmit chain and / or receive chain (e.g., including separate antennas and other radio components) for each wireless communication protocol with which it is configured to communicate. As another possibility, the UE 106 may include one or more radio components shared between multiple wireless communication protocols, and one or more radio components used uniquely by a single wireless communication protocol. For example, the UE 106 may include a shared radio component for communicating using either LTE or 5GNR (or LTE or 1xRTT, or LTE or GSM), and a separate radio component for communicating using each of Wi-Fi and Bluetooth. Other configurations are also possible.

[0043] Figure 3 An example simplified block diagram of a communication device 106 according to some embodiments is illustrated. Note that Figure 3The block diagram of the communication device is only an example of a possible communication device. According to the embodiment, the communication device 106 can be a user equipment (UE) device, a mobile device or mobile station, a wireless device or wireless station, a desktop computer or computing device, a mobile computing device (such as a laptop computer, a notebook or a portable computing device), a tablet computer and / or a combination of devices, in addition to other devices. As shown in the figure, the communication device 106 may include a set of components 300 configured to perform core functions. For example, the set of components can be implemented as a system on a chip (SOC), which can include parts for various purposes. Alternatively, the set of components 300 can be implemented as separate components or groups of components for various purposes. The set of components 300 can be coupled to various other circuits of the communication device 106 (e.g., communicatively; directly or indirectly).

[0044] For example, the communication device 106 may include various types of memory (e.g., including NAND flash memory 310), input / output interfaces such as a connector I / F 320 (e.g., for connecting to a computer system; a docking station; a charging station; input devices such as a microphone, a camera, a keyboard; output devices such as a speaker; etc.), a display 360 that may be integrated with the communication device 106 or external to the communication device, and cellular communication circuitry 330 such as for 5G NR, LTE, GSM, etc., and short-range to medium-range wireless communication circuitry 329 (e.g., Bluetooth TM and WLAN circuitry). In some embodiments, the communication device 106 may include wired communication circuitry (not shown), such as, for example, a network interface card for Ethernet.

[0045] Cellular communication circuitry 330 may be (e.g., communicatively; directly or indirectly) coupled to one or more antennas, such as antennas 335 and 336, as shown. Short-range to medium-range wireless communication circuitry 329 may also be (e.g., communicatively; directly or indirectly) coupled to one or more antennas, such as antennas 337 and 338, as shown. Alternatively, short-range to medium-range wireless communication circuitry 329 may be (e.g., communicatively; directly or indirectly) coupled to antennas 335 and 336 in addition to or in lieu of being (e.g., communicatively; directly or indirectly) coupled to antennas 337 and 338. Short-range to medium-range wireless communication circuitry 329 and / or cellular communication circuitry 330 may include multiple receive chains and / or multiple transmit chains for receiving and / or transmitting multiple spatial streams, such as in a multiple-input, multiple-output (MIMO) configuration.

[0046] In some embodiments, as further described below, the cellular communication circuitry 330 can include dedicated receive chains (including and / or coupled to (e.g., communicatively; directly or indirectly) dedicated processors and / or radios) for multiple radio access technologies (RATs) (e.g., a first receive chain for LTE and a second receive chain for 5G NR). Furthermore, in some embodiments, the cellular communication circuitry 330 can include a single transmit chain that can switch between radios dedicated to specific RATs. For example, a first radio can be dedicated to a first RAT, such as LTE, and can communicate with a dedicated receive chain and a transmit chain shared with an additional radio, such as a second radio that can be dedicated to a second RAT (e.g., 5G NR) and can communicate with both the dedicated receive chain and the shared transmit chain.

[0047] The communication device 106 may also include and / or be configured for use with one or more user interface elements. The user interface elements may include any of a variety of elements, such as a display 360 (which may be a touch screen display), a keyboard (which may be a separate keyboard or may be implemented as part of a touch screen display), a mouse, a microphone and / or speakers, one or more cameras, one or more buttons, and / or any of a variety of other elements capable of providing information to a user and / or receiving or interpreting user input.

[0048] The communication device 106 may also include one or more smart cards 345 , such as one or more UICCs (Universal Integrated Circuit Cards) 345 , having SIM (Subscriber Identity Module) functionality.

[0049] As shown, the SOC 300 may include a processor 302 that may execute program instructions for the communication device 106 and a display circuit 304 that may perform graphics processing and provide display signals to a display 360. The processor 302 may also be coupled to a memory management unit (MMU) 340 (the MMU may be configured to receive addresses from the processor 302 and translate those addresses into locations in memory (e.g., memory 306, read-only memory (ROM) 350, NAND flash memory 310)) and / or to other circuits or devices (such as the display circuit 304, the short-range wireless communication circuit 229, the cellular communication circuit 330, the connector I / F 320, and / or the display 360). The MMU 340 may be configured to perform memory protection and page table translation or setup. In some embodiments, the MMU 340 may be included as part of the processor 302.

[0050] As described above, the communication device 106 can be configured to communicate using wireless and / or wired communication circuitry. The communication device 106 can be configured to send a request to attach to a first network node operating according to a first RAT (e.g., 5G NR, 4G LTE, Bluetooth, Wi-Fi, etc.) and to send an indication that the wireless device is capable of maintaining substantially concurrent connections with the first network node and a second network node operating according to a second RAT (e.g., 5G NR, 4G LTE, Bluetooth, Wi-Fi, etc.). The wireless device can also be configured to send a request to attach to the second network node. The request can include an indication that the wireless device is capable of maintaining substantially concurrent connections with the first and second network nodes. In addition, the wireless device can be configured to receive an indication that dual connectivity has been established with the first network node and the second network node.

[0051] As described herein, the communication device 106 may include hardware and software components for implementing the above-described features for supporting positioning of mobile UEs in a reduced power state. For example, by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium), the processor 302 of the communication device 106 may be configured to implement some or all of the features described herein. Alternatively (or in addition), the processor 302 may be configured as a programmable hardware element such as an FPGA (field programmable gate array) or as an ASIC (application-specific integrated circuit). Alternatively (or in addition), in combination with one or more of the other components 300, 304, 306, 310, 320, 329, 330, 340, 345, 350, 360, the processor 302 of the communication device 106 may be configured to implement some or all of the features described herein.

[0052] Furthermore, as described herein, processor 302 may include one or more processing elements. Thus, processor 302 may include one or more integrated circuits (ICs) configured to perform the functions of processor 302. Furthermore, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of processor 302.

[0053] Furthermore, as described herein, both cellular communication circuitry 330 and short-range wireless communication circuitry 329 may include one or more processing elements. In other words, one or more processing elements may be included in cellular communication circuitry 330, and similarly, one or more processing elements may be included in short-range wireless communication circuitry 329. Thus, cellular communication circuitry 330 may include one or more integrated circuits (ICs) configured to perform the functions of cellular communication circuitry 330. Furthermore, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of cellular communication circuitry 330. Similarly, short-range wireless communication circuitry 329 may include one or more ICs configured to perform the functions of short-range wireless communication circuitry 329. Furthermore, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of short-range wireless communication circuitry 329.

[0054] Figure 4 An example block diagram of a base station 102 according to some embodiments is illustrated. Note that Figure 4 The base station 102 is only one example of a possible base station. As shown, the base station 102 may include a processor 404 that may execute program instructions for the base station 102. The processor 404 may also be coupled to a memory management unit (MMU) 440 that may be configured to receive addresses from the processor 404 and translate those addresses into locations in memory (e.g., memory 460 and read-only memory (ROM) 450) or to other circuits or devices.

[0055] The base station 102 may include at least one network port 470. The network port 470 may be configured to couple to a telephone network and provide access to the telephone network as described above. Figure 1 and Figure 2 Multiple devices of the telephone network described in, such as UE device 106.

[0056] The network port 470 (or an additional network port) may also or alternatively be configured to couple to a cellular network, such as a core network of a cellular service provider. The core network may provide mobility-related services and / or other services to a plurality of devices, such as the UE device 106. In some cases, the network port 470 may be coupled to a telephone network via the core network, and / or the core network may provide a telephone network (e.g., in other UE devices served by the cellular service provider).

[0057] In some embodiments, base station 102 may be a next-generation base station, such as a 5G New Radio (5G NR) base station, or "gNB." In such embodiments, base station 102 may be connected to a legacy evolved packet core (EPC) network and / or to an NR core (NRC) network. Furthermore, base station 102 may be considered a 5G NR cell and may include one or more transition and reception points (TRPs). Furthermore, UEs capable of operating in accordance with 5G NR may be connected to one or more TRPs within one or more gNBs.

[0058] Base station 102 may include at least one antenna 434, and may include multiple antennas. At least one antenna 434 may be configured to operate as a wireless transceiver and may be further configured to communicate with UE device 106 via radio 430. Antenna 434 communicates with radio 430 via communication chain 432. Communication chain 432 may be a receive chain, a transmit chain, or both. Radio 430 may be configured to communicate via various wireless communication standards, including but not limited to 5G NR, LTE, LTE-A, GSM, UMTS, CDMA2000, Wi-Fi, and the like.

[0059] Base station 102 may be configured to communicate wirelessly using multiple wireless communication standards. In some instances, base station 102 may include multiple radio components that enable base station 102 to communicate according to multiple wireless communication technologies. For example, as one possibility, base station 102 may include an LTE radio component for communicating according to LTE and a 5G NR radio component for communicating according to 5G NR. In this case, base station 102 may be capable of operating as both an LTE base station and a 5G NR base station. As another possibility, base station 102 may include a multimode radio component capable of communicating according to any one of multiple wireless communication technologies (e.g., 5G NR and Wi-Fi, LTE and Wi-Fi, LTE and UMTS, LTE and CDMA2000, UMTS and GSM, etc.).

[0060] As further described later herein, BS 102 may include hardware and software components for implementing or supporting the specific implementation of the features described herein. The processor 404 of the base station 102 may be configured to implement or support implementing part or all of the methods described herein, for example, by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). Alternatively, the processor 404 may be configured as a programmable hardware element such as an FPGA (field programmable gate array), or as an ASIC (application-specific integrated circuit) or a combination thereof. Alternatively (or in addition), in combination with one or more of the other components 430, 432, 434, 440, 450, 460, 470, the processor 404 of the BS 102 may be configured to implement or support implementing part or all of the features described herein.

[0061] Furthermore, as described herein, processor 404 may be comprised of one or more processing elements. In other words, one or more processing elements may be included in processor 404. Thus, processor 404 may include one or more integrated circuits (ICs) configured to perform the functions of processor 404. Furthermore, each integrated circuit may include circuits (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of one or more processors 404.

[0062] Furthermore, as described herein, radio 430 may be comprised of one or more processing elements. In other words, one or more processing elements may be included in radio 430. Thus, radio 430 may include one or more integrated circuits (ICs) configured to perform the functions of radio 430. Furthermore, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of radio 430.

[0063] Figure 5 An example simplified block diagram of a cellular communication circuit according to some embodiments is illustrated. Note that Figure 5 The block diagram of the cellular communication circuitry is only one example of possible cellular communication circuitry. Depending on the embodiment, the cellular communication circuitry 330 may be included in a communication device such as the communication device 106 described above. As described above, the communication device 106 may be a user equipment (UE) device, a mobile device or mobile station, a wireless device or wireless station, a desktop computer or computing device, a mobile computing device (e.g., a laptop, notebook, or portable computing device), a tablet computer, and / or a combination of devices, among other devices.

[0064] Cellular communication circuitry 330 may be (e.g., communicatively; directly or indirectly) coupled to one or more antennas, such as antennas 335a-335b and 336 as shown. In some embodiments, cellular communication circuitry 330 may include dedicated receive chains (including and / or coupled to (e.g., communicatively; directly or indirectly) dedicated processors and / or radio components) for multiple RATs (e.g., a first receive chain for LTE and a second receive chain for 5G NR). For example, Figure 5 As shown, the cellular communication circuitry 330 may include a modem 510 and a modem 520. The modem 510 may be configured for communication according to a first RAT (e.g., such as LTE or LTE-A), and the modem 520 may be configured for communication according to a second RAT (e.g., such as 5G NR).

[0065] As shown, the modem 510 may include one or more processors 512 and a memory 516 in communication with the processor 512. The modem 510 may communicate with a radio frequency (RF) front end 530. The RF front end 530 may include circuitry for transmitting and receiving radio signals. For example, the RF front end 530 may include receive circuitry (RX) 532 and transmit circuitry (TX) 534. In some embodiments, the receive circuitry 532 may communicate with a downlink (DL) front end 550, which may include circuitry for receiving radio signals via antenna 335a.

[0066] Similarly, the modem 520 may include one or more processors 522 and a memory 526 in communication with the processors 522. The modem 520 may communicate with an RF front end 540. The RF front end 540 may include circuitry for transmitting and receiving radio signals. For example, the RF front end 540 may include receive circuitry 542 and transmit circuitry 544. In some embodiments, the receive circuitry 542 may communicate with a DL front end 560, which may include circuitry for receiving radio signals via the antenna 335b.

[0067] In some embodiments, the switch 570 can couple the transmit circuitry 534 to an uplink (UL) front end 572. Furthermore, the switch 570 can couple the transmit circuitry 544 to the UL front end 572. The UL front end 572 can include circuitry for transmitting radio signals via the antenna 336. Thus, when the cellular communication circuitry 330 receives an instruction to transmit according to a first RAT (e.g., via a transmit chain including the transmit circuitry 534 and the UL front end 572), the switch 570 can be switched to a first state that allows the modem 510 to transmit signals according to the first RAT (e.g., via a transmit chain including the transmit circuitry 534 and the UL front end 572). Similarly, when the cellular communication circuitry 330 receives an instruction to transmit according to a second RAT (e.g., via a transmit chain including the transmit circuitry 544 and the UL front end 572), the switch 570 can be switched to a second state that allows the modem 520 to transmit signals according to the second RAT (e.g., via a transmit chain including the transmit circuitry 544 and the UL front end 572).

[0068] As described herein, the modem 510 may include hardware and software components for implementing the above-described features or for supporting positioning of mobile UEs in a reduced power state and various other techniques described herein. For example, by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium), the processor 512 may be configured to implement some or all of the features described herein. Alternatively (or in addition), the processor 512 may be configured as a programmable hardware element such as an FPGA (field programmable gate array) or as an ASIC (application-specific integrated circuit). Alternatively (or in addition), in combination with one or more of the other components 530, 532, 534, 550, 570, 572, 335, and 336, the processor 512 may be configured to implement some or all of the features described herein.

[0069] Furthermore, as described herein, processor 512 may include one or more processing elements. Thus, processor 512 may include one or more integrated circuits (ICs) configured to perform the functions of processor 512. Furthermore, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of processor 512.

[0070] As described herein, the modem 520 may include hardware and software components for implementing the above-described features for supporting positioning of mobile UEs in a reduced power state, as well as various other techniques described herein. The processor 522 may be configured to implement some or all of the features described herein, for example, by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). Alternatively (or in addition), the processor 522 may be configured as a programmable hardware element such as an FPGA (field programmable gate array), or as an ASIC (application-specific integrated circuit). Alternatively (or in addition), in combination with one or more of the other components 540, 542, 544, 550, 570, 572, 335, and 336, the processor 522 may be configured to implement some or all of the features described herein.

[0071] Furthermore, as described herein, processor 522 may include one or more processing elements. Thus, processor 522 may include one or more integrated circuits (ICs) configured to perform the functions of processor 522. Furthermore, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of processor 522.

[0072] Figure 6 A network message 602 is illustrated that includes multiple information elements (IEs) 604a, 604b, 604c, and 604d (collectively, IEs 604). In various embodiments, multiple network messages 602 comprised of one or more information elements may be used for communication between different components. In various such embodiments, one or more network messages 602 in one or more formats may be exchanged between one or more UEs and one or more network components to perform one or more of the processes or techniques disclosed herein. Configuring, activating, and performing positioning in a low-power state may utilize the exchange of multiple network messages 602. For example, the messages discussed herein may include and / or utilize one or more of the LTE Positioning Protocol (LPP), the NR Positioning Protocol a (NRPPa), and RRC messaging. It should be understood that the network messages 602 and IEs 604 may appear in multiple formats and carry a variety of information. Typically, various standards and technical specifications define the various network messages 602, IEs 604, and procedures, such as 3GPP technical specifications (eg, TS 38.321, TS 38.321, TS 22.261, and TS 22.104). The embodiments are not limited in this context.

[0073] Various techniques for supporting positioning of mobile UEs in a reduced power state will be described in more detail below. These techniques can be used to enable UEs to perform low-power, high-accuracy positioning (LPHAP). Several embodiments facilitate uplink (UL) and / or UL+downlink (DL) positioning of UEs in an inactive and / or idle state in a manner that improves positioning services in 5G networks by reducing the need to transition to a higher power state (e.g., a connected state). For example, various aspects of positioning can be performed when the UE is in a radio resource control (RRC) inactive or RRC idle state rather than an RRC connected state. Many embodiments include SRS enhancement based on sounding reference signal (SRS) positioning validity areas that can be used to reduce the need to transition to a connected state for positioning (re)configuration. In some such examples, positioning configuration groups can be used to enable a common positioning configuration or portions thereof to be used in multiple network cells. In various embodiments, a signal power metric can be used to determine the network cells in the positioning configuration group. In many embodiments, techniques are utilized to obtain, verify, or update positioning configurations and / or activate positioning transmissions at UEs in an inactive or idle state. For example, one or more of SRSp, TA, and path loss reference configuration may be obtained and / or utilized by a UE in RRC inactive or RRC idle state.In various embodiments, SRSp may include a signal embedded in the physical layer as a reference signal.

[0074] More generally, LPHAP aims to reduce the power consumption of positioning devices while maintaining high position determination accuracy. Typically, existing technologies fail to meet the requirements of LPHAP, at least in part due to the excessive need for UEs to transition to a connected state to obtain updated positioning configurations to ensure high positioning accuracy. For example, with respect to Use Case 6 defined in TS22.104, LPHAP requirements include horizontal positioning accuracy within 1 meter for 90% of UEs, a positioning interval / duty cycle between 15 seconds and 30 seconds, and a UE battery life of 6 months to 1 year. Use Case 6 involves indoor and outdoor tracking of workpieces in assembly areas and / or warehouses using low power periodicity and a triggered 5G Core Mobile Terminated Location Request (5GC-MT-LR) procedure. The embodiments in the present disclosure may provide methods to ensure that these requirements are met.

[0075] Using existing technology, from the perspective of Radio Layer 1 (RAN1), in the RRC inactive state, reception of a DL Positioning Reference Signal (PRS) has a lower priority than other DL signals / channels, such as Synchronization Signal Blocks (SSBs), System Information Blocks (SIBs), Control Resource Sets (CORSETs), Random Access (RA) responses, paging, and DL Small Data Transmissions (SDTs). A UE may support DL PRS processing both outside and inside the initial DL Bandwidth Part (BWP), depending on its capabilities. For DL ​​PRS processing outside the initial DL BWP, the subcarrier spacing (SCS) and cyclic prefix (CP) type of the DL PRS may be the same as or different from the initial DL BWP. For DL ​​PRS processing inside the initial DL BWP, the SCS and CP type of the DL PRS are the same as the initial DL BWP.

[0076] In addition, the prior art supports the following options for SRS transmission for positioning by a UE in an RRC-inactive state. Depending on UE capabilities, the UE may be configured with an SRS for positioning that is associated with the initial UL BWP and transmitted within the initial UL BWP during the RRC-inactive state with the same CP and SCS as those configured for the initial UL BWP. Depending on UE capabilities, the UE may be configured with an SRS for positioning, where the frequency, location, bandwidth, SCS, and CP length are additionally configured for transmission of the SRS for positioning during the RRC-inactive state. Furthermore, when UL transmission is expected to be performed in the initial UL BWP during the RRC-inactive state, the UE will not transmit the SRS for positioning. Additionally, the prior art may perform TA verification and / or path loss reference derivation as defined in TS 38.321. It should be understood that the various embodiments disclosed herein may utilize, elaborate, modify and / or redefine one or more of the prior art techniques to support positioning of UEs in reduced power states, such as to implement one or more of the LPHAP requirements identified above.

[0077] In various embodiments, the reduced power state may refer to an inactive state (such as NR RRC INACTIVE (i.e., RRC inactive)) and an idle state (such as NR RRC IDLE (i.e., RRC idle) state). More generally, the UE may transition between a connected state (such as NR RRC CONNECTED (i.e., RRC connected)) and a reduced power state. For example, with respect to the NR RRC state, a transition from the connected state to the inactive state may be initiated in response to the UE receiving an RRC Release Network message with SuspendConfig. The UE may use a Resume Network message to initiate a transition from the inactive state back to the connected state. A transition from the inactive state or the connected state to the idle state may be initiated in response to the UE receiving an RRC Release Network message. The UE may use an RRC Establish Network message to initiate a transition from the idle state to the connected state. As will be described in greater detail below, the various embodiments disclosed herein may utilize one or more of an RRC Release Network message, an RRC Release Network message with SuspendConfig, an RRC Resume Network message, and / or an RRC Setup Network message to request and / or receive data regarding positioning configuration without actually transitioning out of an inactive or idle state.

[0078] The RRC Connected state supports full performance, while the RRC Inactive and RRC Idle states support varying levels of reduced performance. For example, when a UE is in the RRC Inactive state, the network (e.g., Access and Mobility Management Function (AMF)) expects a less rapid response to any downlink transactions because the UE must be paged before those transactions can be forwarded to the UE. However, the network can therefore apply longer supervision timers for UEs in the RRC Inactive state, which can reduce resource requirements on the network and improve UE battery life.

[0079] Despite the reduced performance in the inactive and idle states, the UE still performs a number of operations. For example, in both the inactive and idle states, the UE performs operations including: reading system information; monitoring the physical downlink control channel (PDCCH) downlink control information (DCI) using a paging radio network temporary identifier (P-RNTI); and monitoring the paging control channel (PCCH) for core network (CN) paging using a 5G shortened temporary mobile subscriber identity (5G-S-TMSI). Additionally, in the inactive state, the UE can perform RAN paging using an inactive RNTI.

[0080] Figure 7 Various aspects of positioning in a telecommunications network according to some embodiments are illustrated. Figure 7An operating environment 700 is included having a UE 702 and base stations 704a, 704b, and 704c. In the illustrated embodiment, uplink messages 706a, 706b, and 706c are sent from the UE 702 to the base stations 704a, 704b, and 704c, respectively. Similarly, downlink messages 708a, 708b, and 708c are sent from the base stations 704a, 704b, and 704c, respectively, to the UE 702. These uplink and / or downlink messages may be used to determine the UE's position based on one or more of the round-trip time (RTT), angle of arrival (AoA), angle of departure (AoD), and time difference of arrival (TDOA) of the uplink and / or downlink messages. Some positioning techniques may not use two-way messaging. For example, UL positioning may utilize only uplink messages. Various positioning techniques may utilize multiple base stations. Other positioning techniques may utilize a single base station. For example, round trip time (RTT) can be combined with angle of arrival (AoA) and / or angle of departure (AoD) to perform positioning with a single base station. Accurate positioning requires various configurations, settings, and parameters, such as SRSp configuration, TA configuration, and path loss reference. As described in more detail below, many embodiments disclosed herein relate to maintaining and using a valid configuration for positioning at the UE while spending as much time as possible in an inactive or idle state. The embodiments are not limited in this context.

[0081] In the prior art, whenever the positioning configuration is invalid, the UE may have to enter a connected state to obtain a valid positioning configuration, resulting in excessive battery consumption and resource requirements. In addition, one or more positioning configurations in the positioning configuration may invalidate another part (or all) of the positioning configuration. For example, if the TA configuration is invalid, the SRSp configuration may be invalidated. When cell reselection is performed and the UE initiates an RRC recovery process to a cell different from the cell in which the SRSp is configured, the TA timer configuration for the SRS may be released. In addition, when the UE transmits an RRCResumeRequest to a cell other than the cell in which the UE is released to an inactive state, the SRSp configuration may be released. The TA timer configuration of the SRSp may be invalidated at any cell reselection (even if the UE does not initiate an RRC recovery process). It should be understood that the various embodiments disclosed herein may utilize, elaborate, modify and / or redefine one or more prior art techniques to support positioning of UEs in a reduced power state, such as by making the positioning configuration valid in a larger area to reduce the number of times the positioning configuration needs to be updated.

[0082] Therefore, various embodiments update and / or expand the validity criteria for positioning configurations in inactive and idle states to expand the availability of positioning configurations by reducing the frequency with which new positioning configurations are needed. In many embodiments, multiple cells in an area may be defined or configured to have the same SRSp configuration attributes. For example, a positioning configuration group may be used to enable a common positioning configuration or part thereof to be used in multiple network cells. In various embodiments, a power metric of a signal may be used to determine a network cell in a positioning configuration group. For example, a reference signal received power (RSRP) may be compared to a reference SRSp configuration cell to determine whether the cell is in the positioning configuration group.

[0083] Positioning configuration groups, which may refer to or include SRSp valid configuration groups, may be defined and network cells may be assigned to them in a variety of ways. In several embodiments, a UE may receive pre-configured SRS configurations for X cells (where 'X' is a defined amount of one or more cells) around a primary connection cell (e.g., a configuration cell). The UE may decode the cell ID (from the base station for RRC inactive and from the core network for RRC idle) and check the cell ID list in the positioning configuration group again. In some embodiments, the positioning configuration group tag for the core network may be different from the positioning configuration group tag for the base station. For example, the ID for RRC idle may include 5G-S-TSMI and the ID for RRC inactive may include a full RNTI. The format for the pre-configured SRS configuration may be {5G-S-TMSI1, full-RNTI1, 5G-S-TMSI2, full-RNTI2, ..., 5G-S-TMSIn, full-RNTIn}. More generally, the group may be the same or it may be different. In many embodiments, if the groups are the same, the markings are different because the core network is marked with 5G-TSMI and the base station is marked with RTNI. In other words, if the UE is inactive, it uses the base station marking (e.g., RTNI), and if the UE is idle, it uses the core network marking (e.g., RTNI).

[0084] In some embodiments, the UE may store multiple positioning configurations. In some such embodiments, signaling from the network may be used to identify which of the multiple positioning configurations to use. In various embodiments, the base station and / or core network may broadcast a separate positioning configuration group ID. In various such embodiments, the UE may check the broadcast positioning configuration group ID against the current positioning configuration group ID to establish validity. For example, at configuration time, the UE may obtain a positioning configuration group ID, each cell will broadcast its own ID, and when moving to a new cell, the UE checks its current ID against the broadcast ID and determines whether it is in the same positioning configuration group.

[0085] In some embodiments, the UE may periodically check the RSRP against a threshold, and if the RSRP is greater than the threshold, the validity remains. In some such embodiments, the check occurs during the paging process.

[0086] In many embodiments, when a UE is paged, it receives information about which specific positioning configuration group the cell belongs to or which specific SRSp is activated for each base station. For UEs that do not send SRSp in RRC idle or RRC inactive, the network can use the paging function to activate this functionality (see e.g. Figure 11A During paging (e.g., in a paging message), an activation index is transmitted for SRSp configuration. Optionally, this can be piggybacked on an existing paging function, or a new SRSp paging function (with an SRSp RNTI) can be designed to indicate an SRSp configuration update. In some embodiments, a bit in the PDCCH can be used to indicate the need for PDSCH decoding for SRSp configuration or RRCRelease.

[0087] Regarding the cell reselection criteria, when cell reselection is performed and the UE initiates an RRC recovery procedure in a new cell that is different from the cell in which the SRSp is configured, the TA timer configuration for the SRS may be released if the new cell is in a different positioning configuration group. However, if the new cell is in the same positioning configuration group, the TA timer configuration is not released. Regarding the RRCResumeRequest criteria, when the UE transmits an RRCResumeRequest to a new cell other than the cell in which the UE is released to an inactive state or an idle state, the SRSp configuration may be released if the new cell is in a different positioning configuration group. However, if the new cell is in the same positioning configuration group, the SRSp configuration is not released. Regarding the TA timer configuration criteria, upon any cell reselection to a new cell that is not in the same positioning configuration group, the TA timer configuration of the SRSP may be invalidated (even if the UE does not initiate the RRC recovery procedure).

[0088] In some embodiments, TA invalidity can be determined by comparing a stored downlink path loss RSRP value with a current RSRP value of a downlink path loss reference. For example, the TA configuration can remain valid as long as the value has not increased / decreased by a threshold amount (e.g., greater than inactivePosSRS-RSRP-ChangeThreshold) and the time alignment timer (e.g., inactivePosSRS-TimeAlignmentTimer) is still running.

[0089] Several embodiments may update the RSRP change threshold parameter for the inactive state. This may address the issue where a UE may move between cells in the same positioning configuration group but have TA validity issues in the new cell. In some embodiments, a single parameter may be used for each cell in the positioning configuration group (e.g., inactivePosSRS-RSRP-ChangeThreshold-R18). In other embodiments, different parameters may be used for the cell configuring the SRSp and other cells in the same positioning configuration group. In other words, different change thresholds may be used for different network cells in the positioning configuration group (e.g., inactivePosSRS-RSRP-ChangeThreshold-Configuringcell and inactivePosSRS-RSRP-ChangeThreshold-Neighborcell).

[0090] In many embodiments, the TA configuration is valid if the current RSRP has not increased / decreased by more than inactivePosSRS-RSRP-ChangeThreshold-Configuringcell / inactivePosSRS-RRSRP-ChangeThreshold-R18 and the UE initiates an RRC recovery procedure in which the UE transmits an RRCResumeRequest to the cell where the SRSp is configured (i.e., the same cell). Additionally or alternatively, the TA configuration is valid if the current RSRP has not increased / decreased by more than inactivePosSRS-RSRP-ChangeThreshold-Neighborcell / inactivePosSRS-RRSRP-CHangeThreshold-R18 and the UE initiates an RRC recovery procedure in which the UE transmits an RRCResumeRequest to a different cell in the same positioning configuration group. Various such implementations may utilize one or more of inactivePosSRS-RSRP-ChangeThreshold-Configuringcell, inactivePosSRS-RSRP-ChangeThreshold-Neighborcell, and inactivePosSRS-RRSRP-CHangeThreshold-R18 in the SRS-PosRRC-InactiveConfig-Rxx in the RRCRelease message to convey relevant information, such as changing the threshold.

[0091] Similar to the inactive state, several embodiments may update the RSRP change threshold parameter for the idle state. This may address the issue where a UE may move between cells in the same positioning configuration group but have TA validity issues in the new cell. In some embodiments, a single parameter may be used for each cell in the positioning configuration group (e.g., idlePosSRS-RSRP-ChangeThreshold-R18). In other embodiments, different parameters may be used for the cell configuring the SRSp and other cells in the same positioning configuration group. In other words, different change thresholds may be used for different network cells in the positioning configuration group (e.g., idlePosSRS-RSRP-ChangeThreshold-Configuringcell and idlePosSRS-RSRP-ChangeThreshold-Neighborcell).

[0092] In many embodiments, the TA configuration is valid if the current RSRP has not increased / decreased by more than idlePosSRS-RSRP-ChangeThreshold-Configuringcell / inactivePosSRS-RRSRP-CHangeThreshold-R18 and the UE initiates an RRC recovery procedure in which the UE transmits an RRCResumeRequest to the cell where the SRSp is configured (i.e., the same cell). Additionally or alternatively, the TA configuration is valid if the current RSRP has not increased / decreased by more than idlePosSRS-RSRP-ChangeThreshold-Neighborcell / idlePosSRS-RRSRP-ChangeThreshold-R18 and the UE initiates an RRC recovery procedure in which the UE transmits an RRCResumeRequest to a different cell in the same positioning configuration group. Various such implementations may utilize one or more of idlePosSRS-RSRP-ChangeThreshold-Configuringcell, idlePosSRS-RSRP-ChangeThreshold-Neighborcell, and idlePosSRS-RRSRP-CHangeThreshold-R18 in the SRS-PosRRC-idleConfig-Rxx in the RRCRelease message to convey relevant information, such as change thresholds. Alternatively, in some implementations, the inactive state and the idle state may use the same parameters.

[0093] Many embodiments can implement SRSp transmission in the RRC idle state. Many such embodiments include enhancements to SRSp to support UE mobility in the RRC idle state, so that the UE does not need to frequently enter the RRC connected state to update the SRS (re) configuration, thereby reducing the power consumption of the UE. In some embodiments, the same SRSp configuration defined in RRCRelease can be used for RRC inactive and RRC idle states. In other embodiments, different SRSp configurations can be defined for the RRC idle state. Exemplary definitions are provided below for the RRC inactive state and the RRC idle state in Tables 1 and 2, respectively.

[0094]

[0095] Table 1

[0096]

[0097] Table 2

[0098] Several embodiments support SRS configuration for positioning in multiple cells by implementing coordinated configuration across multiple cells. In order to prevent problems such as interference or to take into account different spatial relationship information for SPS configuration when the UE transmits to different cells, the embodiment may include some cell-common parameters and / or some cell-specific parameters in the configuration. In some embodiments, all parameters may be public. In other embodiments, a predetermined set of parameters may be public. In various embodiments, the configuration may include information indicating which parameters are public. In one example, the SRSp configuration in the coordinated set of cells may be configured by coordinating the spatial relationship (beam) sent at the same time or by ensuring that the SRSp for the UE is sent at different times to limit interference. For example, if the first UE and the second UE have a spatial relationship configuration (beam) that will cause interference, the first UE may be configured to transmit at time t1, t2, ..., tn, and the second UE may be configured to transmit at time t1+n1, t2+n2, ..., tn+nn. The UEs may be configured individually, or they may be configured in the same group with common times t1, t2, ..., tn, but with the second UE having a UE-specific parameter delta_n to enable n1, n2 and nn.

[0099] Figure 8800 illustrates a logic flow for updating a positioning configuration according to some embodiments. In some embodiments, different parts of a positioning configuration may be processed together (e.g., if one is updated, all are updated). However, in other embodiments, different parts of a positioning configuration may be processed separately. For example, TA configuration validity may be considered a separate issue from the positioning configuration group. In some such examples, if the TA configuration is invalid, a TA configuration process for updating the TA and / or TA validation parameters may be initiated instead of invalidating the SRSp configuration. Logic flow 800 illustrates a flow diagram for determining when and which parts of a positioning configuration to update in a manner that separates TA configuration validity from the positioning configuration group. Embodiments are not limited in this context.

[0100] Logic flow 800 begins at block 802. At block 802, configuration validity is checked. For example, the validity of the TA configuration and the positioning configuration group can be determined. Proceeding to decision block 804, a determination can be made as to whether the TA configuration or the positioning configuration group is valid. For example, the TA configuration can be determined to be invalid based on an RSRP value in the second network cell being outside a change threshold relative to a stored downlink path loss reference RSRP value. In another example, a determination can be made as to whether the current network cell is included in the same positioning configuration group as the configuring network cell.

[0101] If both the TA configuration and the positioning configuration group are invalid, the logic flow 800 may proceed to block 806. At block 806, the TA configuration, path loss reference, and SRSp configuration may be updated. However, if either the TA configuration or the positioning configuration group is valid, the logic flow 800 may proceed to decision block 808. At decision block 808, if the positioning configuration group is invalid, the logic flow proceeds to block 816 and the SRSp configuration is updated. Otherwise, the logic flow 800 proceeds to decision block 810. At block 810, if the TA configuration group is invalid, the logic flow proceeds to block 814 and the TA configuration and path loss reference are updated. Otherwise, the logic flow 800 proceeds to block 812 and no updates are performed.

[0102] In other words, if the TA configuration and positioning configuration group are valid, no update is performed. If the TA configuration is valid and the positioning configuration group is invalid, the SRSp configuration is updated. If the TA configuration is invalid and the positioning configuration group is valid, the TA configuration (e.g., TA parameters) and path loss reference are updated. If the TA configuration and positioning configuration group are invalid, the TA configuration, path loss reference, and SRSp configuration are updated.

[0103] As previously mentioned, transitioning to the RRC connected state to obtain an SRS (re)configuration increases power consumption. Thus, various embodiments disclosed herein extend the availability of positioning configurations, such as by reducing the frequency with which a new positioning configuration is needed. Additionally or alternatively, several embodiments disclosed herein utilize techniques and procedures to obtain, verify, or update positioning configurations (e.g., positioning SRS (SRSp) configurations, timing advance (TA) configurations, path loss references, etc.) and / or activate positioning transmissions at a UE when the UE is in an inactive or idle state. As discussed in more detail below, such as with respect to 9A to 10B In several such embodiments, the UE may use a random access channel (RACH) based procedure to request an update to the positioning configuration (e.g., SRS) from the base station when in the RRC inactive state, and to request an update to the positioning configuration (e.g., SRS) from the core network when in the RRC idle state. For example, a request to update the SRS configuration may be transmitted by an RRC ResumeRequest when in the inactive state, and by an RRC SetupRequest when in the idle state. The update (e.g., a new positioning configuration including TA parameters and / or SRSp configuration) may be transmitted by an RRC Release IE. Other examples may work in the opposite manner, such as the network initiating the update. For example, a mini RRCRelease may be used to create an Update SRSPconfig message. In this and other cases, the mini RRCRelease may be utilized to reduce the size of the message.

[0104] Figure 9A and Figure 9B Illustrated are exemplary process diagrams 900a, 900b for updating a positioning configuration in an inactive state 906 according to some embodiments. More specifically, Figure 9A The four-step RACH procedure for updating the positioning configuration in the inactive state 906 is illustrated, and Figure 9B A two-step RACH procedure for updating a positioning configuration in an inactive state 906 is illustrated. Both process diagrams 900a, 900b include a UE 902, a base station 904, an inactive state 906, and a validity criterion failure 908. Furthermore, each of the process diagrams 900a, 900b begins with the UE 902 being in the inactive state 906 and having a validity criterion failure 908 (e.g., one or more portions of the positioning configuration are invalid (see, e.g., FIG. 1 )). Figure 8 )).

[0105] refer to Figure 9AIn process diagram 900a, in response to a validity criterion failure 908, UE 902 may send a network message 910 to base station 904 in inactive state 906. In various embodiments, network message 910 may include Msg1: PRACH Preamble. In response to first network message 910, base station 904 (or the network) may transmit a network message 912 to base station 904. In some embodiments, network message 912 may include Msg2: RA Response. In response to network message 912, UE 902 may transmit a network message 914 to base station 904. In many embodiments, network message 914 may include Msg3: RRC ResumeRequest + {SRSpConfig, SRSpTA}. In response to network message 914, base station 904 may transmit a network message 916 to UE 902. In several embodiments, network message 916 may include Msg4: RRC Release with SuspendConfig. In several such embodiments, the RRC Release may include an updated SRSp configuration and / or other positioning configuration data. During the process of process diagram 900a, UE 902 may remain in inactive state 906. In many embodiments, process diagram 900a may be enabled by the ResumeCause defined in the RRC ResumeRequest message specification. For example, ResumeCause Enumerated{SRSpConfig,SRSpTA,SRPpConfigTA} ​​may be utilized.

[0106] refer to Figure 9B In process diagram 900b , in response to a validity criterion failure 908 , UE 902 may send a network message 918 to base station 904 . In various embodiments, network message 918 may include MsgA: PRACH preamble + PUSCH carrying RRC resume request + {SRSpConfig, SRSpTA}. In response to network message 918 , base station 904 (or the network) may transmit a network message 920 to base station 904 . In some embodiments, network message 920 may include MsgB: Successful RA Response carrying RRC Release with SuspendConfig. In some such embodiments, the RRC release may include an updated SRSp configuration and / or other positioning configuration data. In some embodiments, the RRC release may use SRS-PosRRC-inactiveConfig-r17 for positioning configuration data. During the process of process diagram 900a , UE 902 may remain in an inactive state 906 . In several embodiments, the updated positioning configuration may be provided in a successful random access response network message.

[0107] Figure 10A and Figure 10BIllustrated are exemplary process diagrams 1000a, 1000b for updating a positioning configuration in an idle state 1006 according to some embodiments. More specifically, Figure 10A The four-step RACH procedure for updating the positioning configuration in the idle state 1006 is illustrated, and Figure 10B A two-step RACH procedure for updating a positioning configuration in an idle state 1006 is illustrated. Both process diagrams 1000a, 1000b include a UE 1002, a base station 1004, an idle state 1006, and a validity criterion failure 1008. Furthermore, each of process diagrams 1000a, 1000b begins with the UE 1002 being in the idle state 1006 and having a validity criterion failure 1008 (e.g., one or more portions of the positioning configuration are invalid (see, e.g., FIG. 1004 )). Figure 8 )).

[0108] refer to Figure 10A In process diagram 1000a, in response to a validity criterion failure 1008, UE 1002 may send a network message 1010 to base station 1004 in idle state 1006. In various implementations, network message 1010 may include Msg1: PRACH Preamble. In response to first network message 1010, base station 1004 (or the network) may transmit a network message 1012 to base station 1004. In some implementations, network message 1012 may include Msg2: RA Response. In response to network message 1012, UE 1002 may transmit a network message 1014 to base station 1004. In many implementations, network message base station 1004 may include Msg3: RRC Setup Request + {SRSpConfig, SRSpTA}. In response to network message 1014, base station 1004 may transmit a network message 1016 to UE 1002. In several implementations, network message 1016 may include Msg4: RRC Release. In several such embodiments, the RRC release may include an updated SRSp configuration and / or other positioning configuration data. During the process of process diagram 1000a, UE 1002 may remain in idle state 1006. In many embodiments, process diagram 1000a may be enabled by an EstablishmentCause defined in the RRC SetupRequest message specification. For example, EstablishmentCause Enumerated {SRSpConfig, SRSpTA, SRPpConfigTA} ​​may be utilized.

[0109] refer to Figure 10BIn process diagram 1000b, in response to a validity criterion failure 1008, UE 1002 may send a network message 1018 to base station 1004. In various embodiments, network message 1018 may include MsgA: PRACH preamble + PUSCH carrying RRC setup request + {SRSpConfig, SRSpTA}. In response to network message 1018, base station 1004 (or the network) may transmit a network message 1020 to base station 1004. In some embodiments, network message 1020 may include MsgB: Successful RA Response carrying RRC release. In several such embodiments, the RRC release may include an updated SRSp configuration and / or other positioning configuration data. In some embodiments, the RRC release may use SRS-PosRRC-IdleConfig-r18 for positioning configuration data. During the process of process diagram 1000b, UE 1002 may remain in idle state 1006.

[0110] Figures 11A to 11C Example process diagrams 1100a, 1100b, and 1100c for a positioning activation procedure according to some embodiments are illustrated. The processes of process diagrams 1100a, 1100b, and 1100c may enable the SRS positioning activation procedure to be performed while the UE is in an idle or inactive state. In several embodiments, the network may activate a specific SRS configuration (set) in a UE in an RRC idle or RRC inactive state. Figure 11A FIG1100a illustrates a process for the network to enable the UE 1102 to activate positioning transmission. Figure 11B FIG1100B illustrates a process for the network to enable the UE 1102 to update the configuration and activate the positioning transmission, and Figure 11C A process diagram 1100C is illustrated for the network to cause UE 1102 to verify configuration and activate positioning transmission. Process diagrams 1100a, 1100b, and 1100c each include UE 1102, base station 1104, and idle / inactive state 1106. It should be understood that in this embodiment and other embodiments, the base station (e.g., base station 1104) can simply relay data from other network components (such as the core network) to UE 1102. In addition, each of process diagrams 1100a, 1100b, and 1100c begins with UE 1102 being in an idle or inactive state (e.g., idle / inactive state 1106).

[0111] refer to Figure 11A, process diagram 1100a may correspond to an initial activation, such as a scenario where UE 1102 is not transmitting an SRSp in an idle or inactive state and the network wants UE 1102 to begin doing so. Accordingly, base station 1104 may send a network message 1108 to UE 1102. In various embodiments, network message 1108 may include a network activation indication with or without a positioning configuration (e.g., an SRSp configuration). If network message 1108 does not include a positioning configuration, then in response to network message 1108, UE 1102 may transmit a network message 1110 with a configuration request to base station 1104, such as using a PRACH. In response to network message 1110, base station 1104 may transmit a network message 1112 to base station 1104. In several embodiments, network message 1112 may include a configuration response. In several such embodiments, the configuration response may include a positioning configuration (e.g., an SRSp configuration and / or a TA configuration). However, if the network message 1108 includes a positioning configuration (e.g., an SRSp configuration), the network messages 1110, 1112 may not be exchanged. Regardless, the network messages 1114, 1116 may include an SRSp transmission sent from the UE 1102 to the base station 1104 according to the positioning configuration. In many embodiments, the SRSp transmission may be transmitted on a periodic basis.

[0112] refer to Figure 11B , process diagram 1100b may correspond to a periodic activation, such as a scenario where UE 1102 is transmitting an SRSp in an idle or inactive state and the network wants UE 1102 to update the configuration and start SRSp transmission based on the updated configuration. In various embodiments, the new SRSp configuration may be transmitted to the UE without initiating any new request. Thus, UE 1102 may send network messages 1118, 1120 to base station 1104 as SRSp transmissions. In response to the network determining that it wants to update the positioning configuration of UE 1102, base station 1104 may transmit a network message 1122 to base station 1104. In various embodiments, network message 1122 may include a network activation indication with a positioning configuration (e.g., an SRSp configuration). In response, UE 1102 may send network messages 1124, 1126 to base station 1104 based on the positioning configuration received in network message 1122. In many embodiments, network messages 1124, 1126 include SRSp transmissions. In many such implementations, SRSp transmissions may be transmitted on a periodic basis.

[0113] refer to Figure 11C, process diagram 1100c may correspond to on-demand activation, such as a scenario where the network (e.g., a base station) transmits an explicit positioning configuration validity indicator. In some embodiments, the validity indicator may include a positioning configuration group ID. For example, UE 1102 may transmit an SRSp in an idle or inactive state, and then the UE may receive a new SRSp indicator (e.g., corresponding to a positioning configuration group), and the UE may compare the indicator with its current indicator to determine whether to request an updated configuration.

[0114] Thus, UE 1102 may send network messages 1128 and 1130 as SRSp transmissions to base station 1104. Subsequently, base station 1104 may transmit a network message 1132 to UE 1102. Network message 1132 may include an activation indication associated with the positioning configuration (e.g., SRSp configuration) that the network wants UE 1102 to use. In response, UE 1102 may check the indication against its current configuration. If the current configuration is different, UE 1102 may transmit a configuration request to base station 1104 in a network message 1134 and receive a configuration response from 1104 in a network message 1136, where the configuration response has a configuration corresponding to the activation indication received in network message 1132. However, if the current configuration is the same, network messages 1134 and 1136 may not be exchanged. Regardless, network messages 1138 and 1140 may include SRSp transmissions sent from UE 1102 to base station 1104 according to the positioning configuration corresponding to the activation indication. In many implementations, SRSp transmissions may be transmitted on a periodic basis.

[0115] More generally, Figures 11A to 11C The positioning activation process can be UE-specific, network cell-specific, and / or multi-cell specific (e.g., positioning configuration group). In various embodiments, a particular UE may have the same or different configurations conveyed to it during paging procedures on different cells. In some embodiments, a particular UE may have some common configuration across multiple cells and different cell-specific information in each cell. In addition, signaling (e.g., exchange of network messages) may utilize one or more of a paging message, a SIB message, an RRC release message, and / or an SPSpConfig message.

[0116] In various embodiments, positioning configuration (e.g., SRSp configuration information) may be conveyed in an existing SIB. For example, the information may be added to the SIB, and the UE may request the information using a RACH procedure when needed. In some embodiments, the information may be added to CellAccessRelatedInfo in SIB1. In some such embodiments, the TrackingArea field: BitString{24 bits} may be used. In various embodiments, RANAreaCode{0 to 255} may be used. In many embodiments, a new field SRSpArea may be created using SRSp validity{0 to 255}. In many embodiments, the information may be added to SIB3 / SIB4. For example, IntraFreqNeighborList: SRSpArea may be used. In several embodiments, for periodic SIB updates, the si-SchedulingInfo parameter may be set for SIB3 / SIB4 in SIB 1. For example, systemInformationAreaID: BitString{24 bits} may be used. In another example, a new field SRSpAreaID: BitString{x bits} or integer {0 to 255} may be used. In various embodiments, periodic SIBs may be used for the embodiments associated with process diagram 1100b, while periodic or on-demand SIBs may be used for the embodiments associated with process diagram 1100c.

[0117] In some embodiments, the positioning configuration (e.g., SRSp configuration information) may be conveyed in an S1-like message. In some such embodiments, the S1-like message may be used to convey area information (e.g., activation indication or positioning configuration group) or the entire configuration. For example, a new SRSp-specific SIB may be specified. In another embodiment, an updated RRC release message may be utilized. In yet another embodiment, a new SRSpRRCRelease message containing only SRSp-specific information may be utilized. The S1-like message may be used for embodiments related to one or more of initial activation (e.g., process diagram 1100a), periodicity (e.g., process diagram 1100b), or on-demand (e.g., process diagram 1100c).

[0118] In many embodiments, a paging process may be used to deliver positioning configurations (e.g., SRSp configuration information) to activate SRSp transmission in an idle or inactive state. For example, a positioning configuration group (e.g., SRSp valid configuration group) parameter ID may be added to a paging record list. In some embodiments, for initial activation and / or on demand, the UE may compare the ID with its current ID. In various embodiments, for initial activation and / or periodically, the UE may activate a (pre) configured positioning configuration based on parameters. In another example, a medium access control (MAC) control element (CE) may be added that includes information for activating a (pre) configured positioning configuration (e.g., from a set of pre-configured positioning configurations stored by the UE). In yet another example, a separate RRCRelease message may be added to the payload of the paging PDSCH to transmit the positioning configuration (e.g., SRSp configuration) therein.

[0119] In various embodiments, the payload of the paging PDCCH may be updated to signal the UE to request a new positioning configuration change. In various such embodiments, the UE may initiate a PRACH procedure to request a new positioning configuration (e.g., an SRSp configuration). In other embodiments, a new PDCCH (separate from the paging PDCCH) may be created to indicate the need for a configuration update, such as for initial activation. For example, the new PDCCH may indicate that the UE should initiate a request for an updated configuration. In another example, the new PDCCH may indicate the resources of a PDSCH containing the actual SRSpConfig (e.g., in RRCRelease) or a MAC CE payload to activate a previously (pre) configured SRSpConfig.

[0120] Figure 12 Logic flow 1200 is illustrated for an exemplary technique for obtaining an updated positioning configuration according to some embodiments. Aspects of logic flow 1200 may relate to various embodiments described herein. Logic flow 1200 may begin at block 1202. Block 1202 may include releasing a connected state to an inactive or idle state at a UE. For example, UE 702 may transition from a connected state to an inactive state. Continuing at block 1204, a current positioning configuration may be determined to be invalid. For example, UE 702 may implement logic flow 800 to determine that the current positioning configuration is invalid. Proceeding to block 1206, while the UE is in an inactive or idle state, an updated positioning configuration may be obtained at the UE. For example, the UE may utilize a RACH procedure (see, e.g., process diagrams 900a, 900b, 1000a, 1000b) to obtain the updated positioning configuration.

[0121] Figure 13Logic flow 1300 is illustrated for an exemplary technique for positioning configuration groups according to some embodiments. Aspects of logic flow 1300 may relate to various embodiments described herein. Logic flow 1300 may begin at block 1302. Block 1302 may include obtaining a positioning configuration for a first network cell included in a positioning configuration group. For example, UE 702 may obtain a positioning configuration for a first network cell corresponding to base station 704a. Additionally, the first network cell may belong to a first positioning configuration group.

[0122] Continuing to block 1304, the UE may be released from a connected state to an inactive or idle state in the first network cell. For example, the UE 702 may be released from the connected state to an inactive state in response to receiving an RRC release network message with SuspendConfig from the base station 704a. Proceeding to block 1306, the UE may transition (e.g., cell reselection, etc.) from the first network cell to a second network cell included in the positioning configuration group. For example, the UE 702 may transition from the first network cell corresponding to the base station 704a to the second network cell corresponding to the base station 704b. In addition, the second network cell corresponding to the base station 704b may be included in the same positioning configuration group as the first network cell corresponding to the base station 704a. At block 1308, the UE may, based on the first network cell and the second network cell being included in the positioning configuration group, use at least a portion of the positioning configuration obtained in the first network cell for positioning in the second network cell in the inactive or idle state. For example, the UE 702 may utilize the positioning configuration obtained in the first network cell to perform SRSp transmission in the second network cell.

[0123] The part of the above content can be realized by utilizing a logic circuit such as a dedicated logic circuit or utilizing a microcontroller or other form of processing core for executing program code instructions.Thus, program code such as machine executable instructions can be utilized to execute the process taught by the above discussion, and the machine executable instructions make the machine execute these instructions to perform certain functions.In this context, "machine" can be a machine that converts an intermediate form (or "abstract") instruction into an instruction specific to a processor (for example, an abstract execution environment such as a "virtual machine" (for example, a Java virtual machine), an interpreter, a common language runtime, a high-level language virtual machine, etc.), and / or an electronic circuit that is arranged on a semiconductor chip (for example, a "logic circuit" realized using a transistor), and the electronic circuit is designed to execute instructions, and the processor is such as a general-purpose processor and / or a special-purpose processor.The process taught by the above discussion can also be executed by (as a substitute of a machine or in combination with a machine) an electronic circuit, and the electronic circuit is designed to execute a process (or a part thereof) without executing program code.

[0124] The present disclosure also relates to an apparatus for performing the operations described herein. The apparatus may be specially constructed for the desired purpose, or may comprise a general-purpose computer selectively activated or reconfigured by a computer program stored in the computer. Such a computer program may be stored in a computer-readable storage medium, such as, but not limited to, any type of disk, including floppy disks, optical disks, CD-ROMs and magneto-optical disks, read-only memory (ROM), RAM, EPROM, EEPROM, magnetic or optical cards, or any type of medium suitable for storing electronic instructions, and each coupled to a computer system bus.

[0125] A machine-readable medium includes any mechanism for storing or transmitting information in a form readable by a machine (e.g., a computer). For example, machine-readable media include read-only memory ("ROM"); random access memory ("RAM"); magnetic disk storage media; optical storage media; flash memory devices; and the like.

[0126] Articles of manufacture can be used to store program code. Articles of manufacture storing program code can be implemented as, but not limited to, one or more memories (e.g., one or more flash memories, random access memories (static, dynamic, or other)), optical disks, CD-ROMs, DVD ROMs, EPROMs, EEPROMs, magnetic or optical cards, or other types of machine-readable media suitable for storing electronic instructions. Program code can also be downloaded from a remote computer (e.g., a server) to a requesting computer (e.g., a client) via a data signal contained in a propagation medium (e.g., via a communication link (e.g., a network connection)).

[0127] Various example implementations are described herein.

[0128] Embodiment 1 is a computer-implemented method, comprising: obtaining a positioning configuration in a first network cell included in a positioning configuration group; releasing from a connected state to an inactive or idle state in the first network cell; switching from the first network cell to a second network cell, wherein the second network cell is included in the positioning configuration group; and based on the first network cell and the second network cell being included in the positioning configuration group, using at least a portion of the positioning configuration obtained in the first network cell in the inactive or idle state for positioning in the second network cell.

[0129] Embodiment 2 is a computer-implemented method according to embodiment 1, and the computer-implemented method may optionally include: determining that the timing advance (TA) configuration is invalid in the second network cell; and using a physical random access channel (PRACH) process to update the TA configuration of the second network cell.

[0130] Embodiment 3 is a computer-implemented method according to embodiment 2, which may optionally include determining that the TA configuration is invalid based on a reference signal received power (RSRP) value in the second network cell being outside a change threshold relative to a stored downlink path loss reference RSRP value.

[0131] Embodiment 4 is a computer-implemented method according to embodiment 3, optionally including the change threshold being different for each network cell in the positioning configuration group.

[0132] Embodiment 5 is a computer-implemented method according to embodiment 4, optionally including the change threshold being the same for each network cell in the positioning configuration group.

[0133] Embodiment 6 is a computer-implemented method according to embodiment 3, optionally including utilizing a PRACH procedure to update a path loss reference for the second network cell.

[0134] Embodiment 7 is a computer-implemented method according to embodiment 1, wherein the computer-implemented method may optionally include the positioning configuration comprising a positioning sounding reference signal (SRSp) configuration and a timing advance (TA) configuration.

[0135] Embodiment 8 is a computer-implemented method according to embodiment 1, which may optionally include the positioning configuration comprising a positioning sounding reference signal (SRSp) configuration.

[0136] Embodiment 9 is a computer-implemented method according to embodiment 1, and the computer-implemented method may optionally include: releasing from the connected state to the inactive state in the first network cell; and in the inactive state, determining that the second network cell is in the positioning configuration group based on a core network cell identifier.

[0137] Embodiment 10 is the computer-implemented method of embodiment 9, optionally including the core network cell identifier comprising a radio network temporary identifier (RNTI).

[0138] Embodiment 11 is a computer-implemented method according to embodiment 1, and the computer-implemented method may optionally include: releasing from the connected state to the idle state in the first network cell; and in the idle state, determining that the second network cell is in the positioning configuration group based on a base station cell identifier.

[0139] Embodiment 12 is a computer-implemented method according to embodiment 11, optionally including the base station cell identifier comprising a temporary mobile subscriber identity (TMSI).

[0140] Embodiment 13 is a computer-implemented method according to embodiment 1, and the computer-implemented method may optionally include: identifying a set of network cell identifiers corresponding to the positioning configuration group; receiving a network cell identifier corresponding to the second network cell; and determining that the second network cell is in the positioning configuration group based on the set of network cell identifiers including the network cell identifier corresponding to the second network cell.

[0141] Embodiment 14 is a computer-implemented method according to embodiment 13, optionally including receiving the network cell identifier in a broadcast message.

[0142] Embodiment 15 is a computer-implemented method according to embodiment 13, optionally including receiving the network cell identifier in a unicast message.

[0143] Embodiment 16 is a computer-implemented method according to embodiment 1, which may optionally include: determining a reference signal received power (RSRP) value in the second network cell; and comparing the RSRP value with a threshold to determine that the second network cell is in the positioning configuration group.

[0144] Embodiment 17 is a computer-implemented method according to embodiment 1, which may optionally include: releasing from a connected state to the idle state; and sending a positioning sounding reference signal (SRSp) in the idle state.

[0145] Embodiment 18 is a computer-implemented method according to embodiment 17, optionally including the idle state comprising a radio resource control (RRC) idle state.

[0146] Embodiment 19 is a computer-implemented method according to embodiment 1, optionally including sharing a portion of the positioning configuration for the first network cell by each network cell in the positioning configuration group.

[0147] Embodiment 20 is a computer-implemented method according to embodiment 19, which may optionally include indicating the portion of the positioning configuration for the first network cell that is shared by each network cell in the positioning configuration group when obtaining the positioning configuration.

[0148] Embodiment 21 is a computer-implemented method according to embodiment 19, which may optionally include that the portion of the positioning configuration for the first network cell shared by each network cell in the positioning configuration group includes sounding reference signal (SRS) parameters.

[0149] Embodiment 22 is a user equipment (UE) comprising one or more processors configured to perform the computer-implemented method according to any one of embodiments 1 to 21.

[0150] Embodiment 23 is a non-transitory machine-readable medium having executable instructions for causing one or more processing units to perform the computer-implemented method according to any one of embodiments 1 to 21.

[0151] Embodiment 24 is a computer-implemented method, comprising: providing a positioning configuration to a UE in a first network cell included in a positioning configuration group; releasing the UE from a connected state to an inactive or idle state in the first network cell; and based on the first network cell and the second network cell being included in the positioning configuration group, enabling the UE to utilize at least a part of the positioning configuration obtained in the first network cell to perform positioning in the second network cell in the inactive or idle state.

[0152] Embodiment 25 is a computer-implemented method according to embodiment 24, which may optionally include utilizing a physical random access channel (PRACH) procedure to update the TA configuration of the UE of the second network cell.

[0153] Embodiment 26 is a computer-implemented method according to embodiment 25, which may optionally include utilizing a PRACH process to update the TA configuration in response to a determination that the TA configuration is invalid based on a reference signal received power (RSRP) value in the second network cell being outside a change threshold relative to a stored downlink path loss reference RSRP value.

[0154] Embodiment 27 is the computer-implemented method of embodiment 26, optionally including the change threshold being different for each network cell in the positioning configuration group.

[0155] Embodiment 28 is the computer-implemented method of embodiment 27, optionally including the change threshold being the same for each network cell in the positioning configuration group.

[0156] Embodiment 29 is a computer-implemented method according to embodiment 26, optionally including utilizing a PRACH procedure to update a path loss reference for the second network cell.

[0157] Embodiment 30 is a computer-implemented method according to embodiment 24, which may optionally include that the positioning configuration includes a positioning sounding reference signal (SRSp) configuration and a timing advance (TA) configuration.

[0158] Embodiment 31 is a computer-implemented method according to embodiment 24, which may optionally include the positioning configuration comprising a positioning sounding reference signal (SRSp) configuration.

[0159] Embodiment 32 is a computer-implemented method according to embodiment 24, which may optionally include: releasing the UE from the connected state to the inactive state in the first network cell; and determining that the second network cell is in the positioning configuration group based on a core network cell identifier when the UE is in the inactive state.

[0160] Embodiment 33 is a computer-implemented method according to embodiment 32, optionally including the core network cell identifier comprising a radio network temporary identifier (RNTI).

[0161] Embodiment 34 is a computer-implemented method according to embodiment 24, and the computer-implemented method may optionally include: releasing the UE from the connected state to the idle state in the first network cell; and determining that the second network cell is in the positioning configuration group based on a base station cell identifier when the UE is in the idle state.

[0162] Embodiment 35 is a computer-implemented method according to embodiment 34, optionally including the base station cell identifier comprising a temporary mobile subscriber identity (TMSI).

[0163] Embodiment 36 is a computer-implemented method according to embodiment 24, optionally including conveying a network cell identifier in a broadcast message, wherein the network cell identifier corresponds to a specific positioning configuration group.

[0164] Embodiment 37 is a computer-implemented method according to embodiment 24, optionally including communicating the network cell identifier in a unicast message, wherein the network cell identifier corresponds to a specific positioning configuration group.

[0165] Embodiment 38 is a computer-implemented method according to embodiment 24, which may optionally include: determining a reference signal received power (RSRP) value in the second network cell; and comparing the RSRP value with a threshold to determine that the second network cell is in the positioning configuration group.

[0166] Embodiment 39 is a computer-implemented method according to embodiment 24, which may optionally include: releasing the UE from the connected state to the idle state; and causing the UE to send a positioning sounding reference signal (SRSp) in the idle state.

[0167] Embodiment 40 is a computer-implemented method according to embodiment 39, optionally including the idle state comprising a radio resource control (RRC) idle state.

[0168] Embodiment 41 is a computer-implemented method according to embodiment 24, optionally including sharing a portion of the positioning configuration for the first network cell by each network cell in the positioning configuration group.

[0169] Embodiment 42 is a computer-implemented method according to embodiment 41, which may optionally include indicating in the positioning configuration the portion of the positioning configuration for the first network cell that is shared by each network cell in the positioning configuration group.

[0170] Embodiment 43 is a computer-implemented method according to embodiment 41, which may optionally include that the portion of the positioning configuration for the first network cell shared by each network cell in the positioning configuration group includes sounding reference signal (SRS) parameters.

[0171] Embodiment 44 is a base station (BS), comprising one or more processors configured to perform the computer-implemented method according to any one of embodiments 24 to 43.

[0172] Embodiment 45 is a non-transitory machine-readable medium having executable instructions for causing one or more processing units to perform the computer-implemented method according to any one of embodiments 24 to 43.

[0173] Embodiment 46 is a computer-implemented method comprising: releasing from a connected state to an inactive or idle state at a user equipment (UE); determining that a current positioning configuration is invalid; and obtaining an updated positioning configuration while the UE is in the inactive or idle state.

[0174] Embodiment 47 is a computer-implemented method according to embodiment 46, which may optionally include obtaining the updated positioning configuration from a base station in the inactive state.

[0175] Embodiment 48 is a computer-implemented method according to embodiment 47, optionally including requesting the updated positioning configuration from the base station via a radio resource control (RRC) ResumeRequest network message in the inactive state.

[0176] Embodiment 49 is a computer-implemented method according to embodiment 47, which may optionally include obtaining the updated positioning configuration in an RRC release network message with suspension configuration.

[0177] Embodiment 50 is a computer-implemented method according to embodiment 46, which may optionally include obtaining the updated positioning configuration from the 5G core network in the idle state.

[0178] Embodiment 51 is a computer-implemented method according to embodiment 50, which may optionally include requesting the updated positioning configuration from the 5G core network via RRC SetupRequest in the idle state.

[0179] Embodiment 52 is a computer-implemented method according to embodiment 50, which may optionally include obtaining the updated positioning configuration in an RRC release network message.

[0180] Embodiment 53 is a computer-implemented method according to embodiment 46, which may optionally include obtaining the updated positioning configuration using a random access channel (RACH) procedure.

[0181] Embodiment 54 is a computer-implemented method according to embodiment 53, optionally including that the RACH procedure comprises a two-step RACH procedure.

[0182] Embodiment 55 is a computer-implemented method according to embodiment 54, optionally including receiving the updated positioning configuration in a successful random access response network message.

[0183] Embodiment 56 is a computer-implemented method according to embodiment 53, wherein the computer-implemented method may optionally include the RACH procedure comprising a four-step RACH procedure.

[0184] Embodiment 57 is a computer-implemented method according to embodiment 56, optionally including receiving the updated positioning configuration in a radio resource control (RRC) release network message.

[0185] Embodiment 58 is a computer-implemented method according to embodiment 46, which may optionally include that the updated positioning configuration includes one or more of a timing advance (TA) parameter and a positioning sounding reference signal (SRSp) configuration.

[0186] Embodiment 59 is a computer-implemented method according to embodiment 46, which may optionally include using at least a portion of the updated positioning configuration for a positioning process in the inactive or idle state to determine the position of the UE based on the communication of one or more network messages between the UE and at least one base station.

[0187] Embodiment 60 is a computer-implemented method according to embodiment 59, which may optionally include the positioning process including sending a positioning sounding reference signal (SRSp) based on receiving an activation indication.

[0188] Embodiment 61 is a computer-implemented method according to embodiment 60, which may optionally include obtaining the updated positioning configuration in response to the activation indication.

[0189] Embodiment 62 is a computer-implemented method according to embodiment 60, which may optionally include obtaining the updated positioning configuration from the activation indication.

[0190] Embodiment 63 is a computer-implemented method according to embodiment 60, and the computer-implemented method may optionally include that the activation indication includes a positioning configuration indicator, and the computer-implemented method further includes: determining that the current positioning configuration is invalid based on the failure of the positioning configuration indicator to correspond to the current positioning configuration; and obtaining the updated positioning configuration in response to determining that the current positioning configuration is invalid based on the failure of the positioning configuration indicator to correspond to the current positioning configuration, wherein the updated positioning configuration corresponds to the positioning configuration indicator.

[0191] Embodiment 64 is a computer-implemented method according to embodiment 60, which may optionally include that the activation indication is received in one or more of a paging network message, a system information block (SIB) network message, a radio resource control (RRC) release network message, and an SRSp configuration network message.

[0192] Embodiment 65 is a computer-implemented method according to embodiment 64, which may optionally include the activation indication being included in one or more of a CellAccessRelatedInfo information element (IE), a tracking area IE, a radio access network (RAN) area code IE, an SRSp validity IE, an IntraFreqNeighborList IE, a SystemInformationAreaID IE, or an SRSpAreaID IE of a SIB network message.

[0193] Embodiment 66 is a computer-implemented method according to embodiment 64, which may optionally include the activation indication being included in one or more payloads of a payload of a paging physical downlink shared channel (PDSCH) network message.

[0194] Embodiment 67 is a computer-implemented method according to embodiment 64, which may optionally include including the activation indication in one or more payloads of a physical downlink control channel (PDCCH) network message.

[0195] Embodiment 68 is a computer-implemented method according to embodiment 67, optionally including the PDCCH network message comprising a paging PDCCH network message.

[0196] Embodiment 69 is a user equipment (UE) comprising one or more processors configured to perform the computer-implemented method according to any one of embodiments 46 to 68.

[0197] Embodiment 70 is a non-transitory machine-readable medium having executable instructions for causing one or more processing units to perform the computer-implemented method according to any one of embodiments 46 to 68.

[0198] Embodiment 71 is a computer-implemented method comprising: releasing a user equipment (UE) from a connected state to an inactive or idle state; and providing an updated positioning configuration to the UE in the inactive or idle state in response to a determination that a current positioning configuration is invalid.

[0199] Embodiment 72 is a computer-implemented method according to embodiment 71, which may optionally include a base station providing the updated positioning configuration to the UE in the inactive state.

[0200] Embodiment 73 is a computer-implemented method according to embodiment 72, which may optionally include receiving a request for the updated positioning configuration from the UE in the inactive state via a radio resource control (RRC) ResumeRequest network message.

[0201] Embodiment 74 is a computer-implemented method according to embodiment 72, which may optionally include providing the updated positioning configuration in an RRC release network message with suspension configuration.

[0202] Embodiment 75 is a computer-implemented method according to embodiment 71, and the computer-implemented method may optionally include a 5G core network providing the updated positioning configuration to the UE in the idle state.

[0203] Embodiment 76 is a computer-implemented method according to embodiment 75, which may optionally include providing the updated positioning configuration to the UE in the idle state via an RRC SetupRequest.

[0204] Embodiment 77 is a computer-implemented method according to embodiment 75, which may optionally include providing the updated positioning configuration in an RRC release network message.

[0205] Embodiment 78 is a computer-implemented method according to embodiment 71, which may optionally include providing the updated positioning configuration via a random access channel (RACH) procedure.

[0206] Embodiment 79 is a computer-implemented method according to embodiment 78, optionally including wherein the RACH procedure comprises a two-step RACH procedure.

[0207] Embodiment 80 is a computer-implemented method according to embodiment 79, which may optionally include providing the updated positioning configuration in a successful random access response network message.

[0208] Embodiment 81 is a computer-implemented method according to embodiment 78, wherein the computer-implemented method may optionally include a RACH procedure comprising a four-step RACH procedure.

[0209] Embodiment 82 is a computer-implemented method according to embodiment 81, which may optionally include providing the updated positioning configuration in a radio resource control (RRC) release network message.

[0210] Embodiment 83 is a computer-implemented method according to embodiment 71, which may optionally include that the updated positioning configuration includes one or more of a timing advance (TA) parameter and a positioning sounding reference signal (SRSp) configuration.

[0211] Embodiment 84 is a computer-implemented method according to embodiment 71, which may optionally include utilizing a positioning process to determine the position of the UE based on communication of one or more network messages between the UE and at least one base station and based on at least a portion of the updated positioning configuration when the UE is in the inactive or idle state.

[0212] Embodiment 85 is a computer-implemented method according to embodiment 84, which may optionally include that the positioning process includes sending an activation indication to cause the UE to transmit a positioning sounding reference signal (SRSp).

[0213] Embodiment 86 is a computer-implemented method according to embodiment 85, which may optionally include the activation indication causing the UE to obtain the updated positioning configuration.

[0214] Embodiment 87 is a computer-implemented method according to embodiment 85, which may optionally include providing the updated positioning configuration in the activation indication.

[0215] Embodiment 88 is a computer-implemented method according to embodiment 85, wherein the computer-implemented method may optionally include the activation indication including a positioning configuration indicator, and the computer-implemented method further includes sending the updated positioning configuration to the UE in response to the UE determining that the current positioning configuration is invalid based on the positioning configuration indicator failing to correspond to the current positioning configuration, wherein the updated positioning configuration corresponds to the positioning configuration indicator.

[0216] Embodiment 89 is a computer-implemented method according to embodiment 85, and the computer-implemented method may optionally include that the activation indication is transmitted in one or more of a paging network message, a system information block (SIB) network message, a radio resource control (RRC) release network message, and an SRSp configuration network message.

[0217] Embodiment 90 is a computer-implemented method according to embodiment 89, which may optionally include the activation indication being included in one or more of a CellAccessRelatedInfo information element (IE), a tracking area IE, a radio access network (RAN) area code IE, an SRSp validity IE, an IntraFreqNeighborList IE, a SystemInformationAreaID IE, or an SRSpAreaID IE of a SIB network message.

[0218] Embodiment 91 is a computer-implemented method according to embodiment 89, which may optionally include the activation indication being included in one or more payloads of a payload of a paging physical downlink shared channel (PDSCH) network message.

[0219] Embodiment 92 is a computer-implemented method according to embodiment 89, which may optionally include the activation indication being included in one or more payloads of a payload of a physical downlink control channel (PDCCH) network message.

[0220] Embodiment 93 is a computer-implemented method according to embodiment 92, optionally including the PDCCH network message comprising a paging PDCCH network message.

[0221] Embodiment 94 is a base station (BS), comprising one or more processors configured to perform the computer-implemented method according to any one of embodiments 71 to 93.

[0222] Embodiment 95 is a non-transitory machine-readable medium having executable instructions for causing one or more processing units to perform a computer-implemented method according to any one of embodiments 71 to 93.

[0223] The foregoing detailed description has been presented in terms of algorithms and symbolic representations of operations on data bits within a computer memory. These algorithmic descriptions and representations are the tools used by those skilled in the data processing arts to most effectively convey the substance of their work to others skilled in the art. An algorithm, as used here and generally, refers to a self-consistent sequence of operations leading to a desired result. These operations are those requiring physical manipulation of physical quantities. Typically, but not necessarily, these quantities take the form of electrical or magnetic signals capable of being stored, transferred, combined, compared, and otherwise manipulated. It has proven convenient, primarily for common sense, to refer to these signals as bits, values, elements, symbols, characters, terms, numbers, or the like.

[0224] It should be borne in mind, however, that all of these and similar terms are to be associated with the appropriate physical quantities and are merely convenient labels applied to these quantities. Unless otherwise specifically stated, it will be apparent from the foregoing discussion that discussions throughout this specification using terms such as "select," "determine," "receive," "form," "group," "aggregate," "generate," "remove," and the like will be understood to refer to actions and processes on a computer system or similar electronic computing device that manipulates data represented as physical (electronic) quantities in the computer system's registers and memories and converts it into other data similarly represented as physical quantities in the computer system's memories or registers or other such information storage, transmission, or display devices.

[0225] The process presented herein and display are not inherently relevant to any particular computer or other device. According to the teachings herein, various general-purpose systems can be used together with programs, or it can be proved that they are convenient to construct a more specialized device for performing the operations. According to the description below, the required structure for various these systems will be apparent. In addition, the present disclosure is not described with reference to any specific programming language. It should be understood that a variety of programming languages ​​can be used to implement the teachings of the present disclosure as described herein.

[0226] It is understood that the use of personally identifiable information should be subject to privacy policies and practices that are generally recognized to meet or exceed industry or government requirements for maintaining user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of authorized use should be clearly stated to users.

[0227] The foregoing discussion describes only some exemplary embodiments of the present disclosure. Those skilled in the art will readily recognize from these discussions, the accompanying drawings, and the appended claims that various modifications can be made without departing from the spirit and scope of the present disclosure.

Claims

1. A computer-implemented method, comprising: Obtaining a positioning configuration in a first network cell included in a positioning configuration group; releasing from a connected state to an inactive or idle state in the first network cell; switching from the first network cell to a second network cell, wherein the second network cell is included in the positioning configuration group; as well as Based on the first network cell and the second network cell being included in the positioning configuration group, at least a portion of the positioning configuration obtained in the first network cell in the inactive or idle state is used for positioning in the second network cell.

2. The computer-implemented method of claim 1 , further comprising: determining that a timing advance (TA) configuration is invalid in the second network cell; as well as The TA configuration of the second network cell is updated using a physical random access channel (PRACH) procedure.

3. The computer-implemented method of claim 2, further comprising: The TA configuration is determined to be invalid based on a reference signal received power (RSRP) value in the second network cell being outside a change threshold relative to a stored downlink path loss reference RSRP value. 4 . The computer-implemented method of claim 3 , wherein the change threshold is different for each network cell in the positioning configuration group. 5 . The computer-implemented method of claim 4 , wherein the change threshold is the same for each network cell in the positioning configuration group.

6. The computer-implemented method of claim 3, further comprising utilizing a PRACH procedure to update a path loss reference for the second network cell.

7. The computer-implemented method of claim 1 , wherein the positioning configuration comprises a positioning sounding reference signal (SRSp) configuration and a timing advance (TA) configuration.

8. The computer-implemented method of claim 1 , wherein the positioning configuration comprises a positioning sounding reference signal (SRSp) configuration.

9. The computer implementation of claim 1 , further comprising: Release from the connected state to the idle state; as well as A positioning sounding reference signal (SRSp) is sent in the idle state.

10. The computer implementation of claim 9, wherein the idle state comprises a radio resource control (RRC) idle state.

11. The computer-implemented method of claim 1 , wherein a portion of the positioning configuration for the first network cell is shared by each network cell in the group of positioning configurations.

12. The computer-implemented method of claim 11, wherein when obtaining the positioning configuration, the portion of the positioning configuration for the first network cell that is shared by each network cell in the positioning configuration group is indicated.

13. The computer-implemented method of claim 11, wherein the portion of the positioning configuration for the first network cell shared by each network cell in the positioning configuration group includes sounding reference signal (SRS) parameters.

14. A user equipment (UE), comprising one or more processors configured to perform operations comprising: Obtaining a positioning configuration in a first network cell included in a positioning configuration group; releasing from a connected state to an inactive or idle state in the first network cell; switching from the first network cell to a second network cell, wherein the second network cell is included in the positioning configuration group; and Based on the first network cell and the second network cell being included in the positioning configuration group, at least a portion of the positioning configuration obtained in the first network cell in the inactive or idle state is used for positioning in the second network cell.

15. The UE of claim 14, wherein the one or more processors are further configured to perform operations comprising: determining that a timing advance (TA) configuration is invalid in the second network cell; and The TA configuration of the second network cell is updated using a physical random access channel (PRACH) procedure.

16. The computer-implemented method of claim 14, wherein a portion of the positioning configuration for the first network cell is shared by each network cell in the group of positioning configurations. 17 . The UE of claim 16 , wherein when obtaining the positioning configuration, the portion of the positioning configuration for the first network cell shared by each network cell in the positioning configuration group is indicated.

18. A non-transitory machine-readable medium having executable instructions for causing one or more processing units to perform a method comprising: Obtaining a positioning configuration in a first network cell included in a positioning configuration group; releasing from a connected state to an inactive or idle state in the first network cell; switching from the first network cell to a second network cell, wherein the second network cell is included in the positioning configuration group; as well as Based on the first network cell and the second network cell being included in the positioning configuration group, at least a portion of the positioning configuration obtained in the first network cell in the inactive or idle state is used for positioning in the second network cell.

19. The non-transitory machine-readable medium of claim 18, the non-transitory machine-readable medium having instructions for causing one or more processing units to perform the method, the method further comprising: determining that a timing advance (TA) configuration is invalid in the second network cell; as well as The TA configuration of the second network cell is updated using a physical random access channel (PRACH) procedure.

20. The non-transitory machine-readable medium of claim 18, wherein a portion of the positioning configuration for the first network cell is shared by each network cell in the group of positioning configurations.

Images