Managing positioning reference signal processing window configurations

Abstract

To manage a positioning reference signal (PRS) processing window (PPW) at a user equipment (UE), a central unit (CU) of a distributed base station further comprising a distributed unit (DU) provides (512) a PPW configuration to the UE via the DU; and sending (514) a request to the DU to activate or deactivate the PPW configuration of the UE.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of priority and filing date of Provisional U.S. Patent Application No. 63 / 339,959, entitled “Managing Positioning Reference Signal Processing Window Configuration,” filed on May 9, 2022. The entire contents of the provisional application are hereby expressly incorporated herein by reference. Technical Field

[0003] The present disclosure relates generally to wireless communications, and more particularly to managing positioning reference signal (PRS) processing window configurations for positioning measurements. Background Art

[0004] This background description is provided for the purpose of generally presenting the context of the present disclosure. The work of the presently named inventors, to the extent that it is described in this background section, and aspects of this description that might not have been identified as prior art at the time of filing are neither explicitly nor implicitly admitted to be prior art to the present disclosure.

[0005] Location services (LCS) allow a user equipment unit (UE) and / or a base station to determine the geographic location of the UE, for example when the UE is unable to determine its location due to limited hardware capabilities, the UE receives insufficient satellite or other beacon signals, or the base station attempts to locate the UE in an emergency situation.

[0006] For example, entities supporting LCS in the core network (CN) include a location management function (LMF) and an evolved service mobile location center (E-SMLC). In some examples, the UE exchanges messages with the LMF using a positioning protocol such as the LTE positioning protocol (LPP). Similarly, the UE transmits an LPP message to an access management function (AMF) operating in the CN in an uplink (UL) non-access stratum (NAS) transport message. The AMF then transmits the LPP message to the LMF or E-SMLC. In the downlink direction, the AMF uses a downlink (DL) NAS transport message to transmit the LPP message from the LMF or E-SMLC to the UE.

[0007] The preconfigured PRS processing window (PPW) procedure is specifically used for positioning measurements. More specifically, the LMF sends a measurement preconfiguration required message to the gNB to request the gNB to configure the preconfigured PPW of the UE. After receiving the measurement preconfiguration required message or in response to receiving the measurement preconfiguration required message, the gNB sends an RRC reconfiguration message including the preconfigured PPW configuration to the UE. Later, when the gNB receives a measurement activation message from the LMF, the gNB sends a PPW activation command to the UE to activate the preconfigured PPW configuration. In response to receiving the PPW activation command or after receiving the PPW activation command, the UE activates the preconfigured PPW configuration and uses the preconfigured PPW configuration to perform measurements on DL reference signals (e.g., positioning reference signals (PRS)) for positioning. However, it is unclear how to configure and activate the preconfigured PPW configuration in a distributed base station. Further, it is also unclear how to deactivate and release the preconfigured PPW configuration in a distributed base station. Summary of the invention

[0008] An example embodiment of the technology of the present disclosure is a method for managing a positioning reference signal (PRS) processing window (PPW) at a UE. The method is implemented in a central unit (CU) of a distributed base station, which also includes a distributed unit (DU). The method includes: providing a PPW configuration to the UE via the DU; and sending a request to the DU to activate or deactivate the PPW configuration of the UE.

[0009] Another example embodiment of these techniques is a method for managing a PPW at a UE. The method is implemented in a DU of a distributed base station, which also includes a central unit CU. The method includes: providing a PPW configuration to the UE; receiving a request to activate or deactivate the PPW configuration of the UE from the CU; and sending a PPW activation or deactivation command to the UE.

[0010] Another example embodiment of the techniques is a radio access network (RAN) node comprising processing hardware and configured to implement one of the above methods. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] Figure 1A is a block diagram of an example wireless communication system in which the user devices and base stations of the present disclosure may implement the techniques for managing small data transmissions of the present disclosure;

[0012] Figure 1B is a block diagram of an example base station in which a centralized unit (CU) and a distributed unit (DU) may be Figure 1A Operate in a system

[0013] Figure 2A is a block diagram of an example protocol stack, Figure 1A The UE communicates with the base station according to the example protocol stack;

[0014] Figure 2B is a block diagram of an example protocol stack, Figure 1A The UE communicates with the CU and the DU according to the example protocol stack;

[0015] Figure 3A An example scenario is shown in which the DU and CU send PPW configuration and information for activating and performing PPW measurements;

[0016] Figure 3B Shows something like Figure 3A However, in this example scenario, the CU requests PPW configuration from the DU in a request message;

[0017] Figure 3C Shows something like Figure 3A However, in this example scenario, the DU sends the PPW configuration in the measurement preconfiguration confirmation response;

[0018] Figure 3D Shows something like Figure 3A but in this example scenario, the UE deactivates the PPW configuration after activating the configuration and / or performing measurements using such configuration;

[0019] Figure 3E Shows something like Figure 3A However, in this example scenario, the CU and DU send a message to release the PPW configuration at the UE;

[0020] Figure 3F Shows something like Figure 3E However, in this example scenario, the DU determines to release the PPW configuration at the UE;

[0021] Figure 4A is a flow chart of an example method implemented in a DU for sending a PPW configuration to a CU and then sending a PPW activation command to a UE after receiving a response from the CU;

[0022] Figure 4B is similar to Figure 4A Flowchart of an example method of , but in the example method, the DU receives a request for PPW configuration from the CU;

[0023] Figure 4C is similar to Figure 4A Flowchart of an example method of , but in the example method, the DU sends a PPW configuration to the CU and then sends an activation command to the UE;

[0024] Figure 5A is a flow chart of an example method implemented in a CU for receiving a PPW configuration from a DU and sending a response of the CU including the PPW configuration;

[0025] Figure 5B is similar to Figure 5A Flowchart of an example method of , but in the example method, the CU sends a request for PPW configuration to the DU and receives the configuration from the DU;

[0026] Figure 5C is similar to Figure 5A Flowchart of an example method of , but in the example method, the CU receives a PPW configuration from the DU in response to a request to configure the PPW of the UE;

[0027] Fig. 6A is a flow chart of an example method implemented in a CU for receiving a message including PPW release information from a DU and sending a message including PPW release information to a UE via the DU;

[0028] Figure 6B is similar to Fig. 6A , but in the example method, the CU generates release information for releasing the PPW configuration at the UE; and

[0029] Figure 7 is a flow chart of an example method implemented in a DU for receiving a message from a CU to release a PPW configuration of a UE and sending a release message to the UE. DETAILED DESCRIPTION

[0030] First reference Figure 1A , the example wireless communication system 100 includes a UE 102, a base station (BS) 104, a base station 106, and a core network (CN) 110. The base stations 104 and 106 may operate in a RAN 105 connected to the core network (CN) 110. For example, the CN 110 may be implemented as an evolved packet core (EPC) 111 or a fifth generation (5G) core (5GC) 160. In another example, the CN 110 may also be implemented as a sixth generation (6G) core.

[0031] Base station 104 covers cell 124, and base station 106 covers cell 126. If base station 104 is a gNB, cell 124 is an NR cell. If base station 104 is an ng-eNB, cell 124 is an Evolved Universal Terrestrial Radio Access (E-UTRA) cell. Similarly, if base station 106 is a gNB, cell 126 is an NR cell, and if base station 106 is an ng-eNB, cell 126 is an E-UTRA cell. Cells 124 and 126 may be located in the same radio access network notification area (RNA) or in different RNAs. In general, RAN 105 may include any number of base stations, and each of the base stations may cover one, two, three, or any other suitable number of cells. UE 102 may support at least 5G NR (or simply "NR") or E-UTRA air interface to communicate with base stations 104 and 106. Each of base stations 104 and 106 may be connected to CN110 via an interface (e.g., S1 or NG interface). The base stations 104 and 106 may also be interconnected via an interface for interconnecting NG RAN nodes (e.g., an X2 or Xn interface).

[0032] Among other components, the EPC 111 may include a serving gateway (SGW) 112, a mobility management entity (MME) 114, and a packet data network gateway (PGW) 116. In general, the SGW 112 is configured to deliver user plane packets related to audio calls, video calls, Internet services, etc., and the MME 114 is configured to manage authentication, registration, paging, and other related functions. The PGW 116 provides connectivity from the UE 102 to one or more external packet data networks (e.g., an Internet network and / or an Internet Protocol (IP) Multimedia Subsystem (IMS) network). The 5GC 160 includes a user plane function (UPF) 162 and an access and mobility management function (AMF) 164 and / or a session management function (SMF) 166. Generally speaking, UPF 162 is configured to deliver user plane packets associated with audio calls, video calls, Internet services, etc., AMF 164 is configured to manage authentication, registration, paging and other related functions, and SMF 166 is configured to manage PDU sessions.

[0033] The location management function (LMF) 168 manages support for different location services for the UE, including positioning of the UE and delivery of assistance data to the UE. The LMF 168 is interconnected with the AMF 164 via an interface (e.g., an NL1 interface). The LMF 168 may interact with a base station (e.g., base station 104 or 106) for a UE (e.g., UE 102) to obtain positioning measurements for the UE, including uplink measurements made by the base station and downlink measurements made by the UE and provided to the base station. The LMF may interact with the UE to deliver assistance data to the UE (if requested by the UE) for a particular location service, or to obtain a position estimate.

[0034] LMF 168 may interact with a plurality of base stations (e.g., base stations 104 and 106) to provide assistance data information for broadcast. The assistance data information for broadcast may optionally be segmented and / or encrypted by LMF 168. LMF 168 may also interact with AMF to provide encryption key data information to the AMF, as described in more detail in TS 23.273.

[0035] For positioning of the UE, LMF 168 decides one or more positioning methods to be used based on factors that may include LCS client type, required QoS, UE positioning capabilities of the UE, and positioning capabilities of the base station serving the UE. LMF 168 then invokes positioning methods in the UE and / or base station. The positioning methods may generate position estimates for UE-based positioning methods and / or positioning measurements for UE-assisted and network-based positioning methods. LMF 168 may combine all received results and determine a single position estimate for the UE (hybrid positioning). Additional information such as the accuracy and speed of the position estimate may also be determined.

[0036] like Figure 1A As shown, base station 104 supports cell 124, and base station 106 supports cell 126. Cells 124 and 126 may partially overlap, so that UE 102 may select, reselect, or switch from one of cells 124 and 126 to the other. In order to directly exchange messages or information, base station 104 and base station 106 may support an X2 or Xn interface. In general, CN 110 may be connected to any suitable number of base stations supporting NR cells and / or EUTRA cells.

[0037] The base station 104 is equipped with processing hardware 130, which may include one or more general-purpose processors (e.g., CPUs) and non-transitory computer-readable memory storing instructions, and the one or more general-purpose processors execute the instructions. Additionally or alternatively, the processing hardware 130 may include a dedicated processing unit. In an example implementation, the processing hardware 130 includes a media access control (MAC) controller 132, which is configured to: perform a random access process with one or more user devices, receive uplink MAC protocol data units (PDUs) of one or more user devices, and send downlink MAC PDUs to one or more user devices. The processing hardware 130 may also include a positioning measurement controller 134, which is configured to manage positioning measurement related processes and manage PPW configurations of one or more UEs communicating with the base station 104. The processing hardware may further include an RRC controller 136 to implement processes and message delivery at the RRC sublayer of the protocol communication stack. In an example implementation, the processing hardware 130 includes an NRPPa controller 138 configured to manage communications with the LMF 168 via the NR Positioning Protocol A (NRPPa) to enable positioning and location services for one or more UEs. The base station 106 may include substantially similar components. In particular, the components 140, 142, 144, 146, and 148 of the base station 106 may be similar to the components 130, 132, 134, 136, and 138, respectively.

[0038] UE 102 is equipped with processing hardware 150, which may include one or more general-purpose processors (such as CPUs) and non-transitory computer-readable memory storing machine-readable instructions that can be executed on one or more general-purpose processors, and / or a dedicated processing unit. In an example implementation, the processing hardware 150 includes an RRC controller 156, which is configured to manage processes and message delivery at the RRC sublayer of the protocol communication stack. In an example implementation, the processing hardware 150 includes an LCS controller 158, which generates outbound (uplink) messages related to positioning, processes inbound (downlink) messages related to positioning, and performs various processes related to positioning. In an example implementation, the processing hardware 150 includes a media access control (MAC) controller 152, which is configured to perform a random access process with a base station, send uplink MAC protocol data units (PDUs) and / or control elements to the base station, and receive downlink MAC PDUs and / or control elements from the base station. The processing hardware 150 may also include a positioning measurement controller 154 configured to manage positioning measurements and PPW configurations configured by the RAN 105. The processing hardware may further include an RRC controller 156 to implement procedures and messaging at the RRC sublayer of the protocol communication stack.

[0039] Figure 1B An example distributed or decentralized implementation of any one or more of the base stations 104, 106 is depicted. In this implementation, the base stations 104, 106 include a central unit (CU) 172 and one or more distributed units (DU) 174. The CU 172 includes processing hardware, such as one or more general-purpose processors (e.g., CPUs) and a computer-readable memory storing machine-readable instructions that can be executed on the general-purpose processors, and / or a dedicated processing unit. For example, the CU 172 may include a PDCP controller, an RRC controller, and / or an RRC inactive controller, such as a PDCP controller 134, 144, an RRC controller 136, 146, and / or an RRC inactive controller 138, 148. In some implementations, the CU 172 includes a radio link control (RLC) controller that is configured to manage or control one or more RLC operations or processes. In further implementations, the CU 172 does not include an RLC controller.

[0040] Each DU in DU 174 also includes processing hardware, which may include one or more general-purpose processors (e.g., CPUs) and computer-readable memory storing machine-readable instructions executable on one or more general-purpose processors, and / or dedicated processing units. For example, the processing hardware may include a MAC controller (e.g., MAC controllers 132, 142) and / or an RLC controller, the MAC controller being configured to manage or control one or more MAC operations or processes (e.g., random access processes), and the RLC controller being configured to manage or control one or more RLC operations or processes. The processing hardware may also include a physical layer controller, which is configured to manage or control one or more physical layer operations or processes.

[0041] In some embodiments, the RAN 105 supports integrated access and backhaul (IAB) functionality. In some implementations, the DU 174 operates as an (IAB) node and the CU 172 operates as an IAB donor.

[0042] In some implementations, the CU 172 includes a logical node CU-CP 172A that hosts a control plane portion of a PDCP protocol of the CU 172. In further implementations, the CU 172 includes a logical node CU-UP 172B that hosts a user plane portion of a PDCP protocol and / or a Service Data Adaptation Protocol (SDAP) protocol of the CU 172. Depending on the implementation, the CU-CP 172A sends control information (e.g., RRC messages, F1 application protocol messages), and the CU-UP 172B sends data packets (e.g., SDAP PDUs or Internet Protocol packets).

[0043] CU-CP 172A may be connected to multiple CU-UPs 172B via an E1 interface. CU-CP 172A selects an appropriate CU-UP 172B for the requested service of UE 102. In some implementations, a single CU-UP 172B is connected to multiple CU-CPs 172A via an E1 interface. CU-CP 172A may be connected to one or more DUs 174 via an F1-C interface. CU-UP 172B may be connected to one or more DUs 174 via an F1-U interface under the control of the same CU-CP 172A. In some implementations, one DU 174 is connected to multiple CU-UPs 172B under the control of the same CU-CP 172A. In such implementations, CU-CP 172A establishes connectivity between CU-UP 172B and DU 174 by using a bearer context management function.

[0044] Figure 2A An example protocol stack 200 is shown in a simplified manner, according to which a UE 102 may communicate with an eNB / ng-eNB or gNB (e.g., one or more of base stations 104, 106).

[0045] In the example stack 200, the physical layer (PHY) 202A of EUTRA provides transport channels to the EUTRA MAC sublayer 204A, which in turn provides logical channels to the EUTRA RLC sublayer 206A. The EUTRA RLC sublayer 206A in turn provides RLC channels to the EUTRA PDCP sublayer 208 and, in some cases, to the NR PDCP sublayer 210. Similarly, the NR PHY 202B provides transport channels to the NR MAC sublayer 204B, which in turn provides logical channels to the NR RLC sublayer 206B. The NR RLC sublayer 206B in turn provides data delivery services to the NR PDCP sublayer 210. In some implementations, the NR PDCP sublayer 210 then provides data to the Service Data Adaptation Protocol (SDAP) 212 or the Radio Resource Control (RRC) sublayer ( Figure 2A (not shown) provides data transfer services. In some implementations, such as Figure 2A As shown, UE 102 supports both EUTRA and NR stacks to support handover between EUTRA and NR base stations and / or support DC implemented through EUTRA and NR interfaces. Figure 2A As shown, the UE 102 may support the layering of the NR PDCP 210 above the EUTRA RLC 206A, and the layering of the SDAP sublayer 212 above the NR PDCP sublayer 210.

[0046] The EUTRA PDCP sublayer 208 and the NR PDCP sublayer 210 receive packets, which may be referred to as service data units (SDUs) (e.g., from an Internet Protocol (IP) layer layered directly or indirectly on the PDCP layer 208 or 210), and output packets, which may be referred to as protocol data units (PDUs) (e.g., to the RLC layer 206A or 206B). For simplicity, this disclosure refers to both SDUs and PDUs as "packets", except where the distinction between SDUs and PDUs is relevant.

[0047] In some implementations, on the control plane, the EUTRA PDCP sublayer 208 and the NR PDCP sublayer 210 provide a signaling radio bearer (SRB) or an RRC sublayer ( Figure 2A 208 and NR PDCP sublayer 210 provide data radio bearers (DRBs) to support data exchange. The data exchanged on the NR PDCP sublayer 210 may be SDAPPDUs, Internet Protocol (IP) packets, or Ethernet packets.

[0048] Figure 2B An example protocol stack 250 is shown in a simplified manner, via which the UE 102 can communicate with a DU (e.g., DU 174) and a CU (e.g., CU 172). The radio protocol stack 200 is functionally divided, such as Figure 2B 206B, NR MAC 204B, and NR PHY 202B) are delegated to the DU. To support the connection to the 5GC, the NR PDCP 210 provides SRBs to the RRC 214, and the NR PDCP 210 provides DRBs to the SDAP 212 and SRBs to the RRC 214.

[0049] Reference now Figure 2CIn a known wireless communication system, the UE and the gNB / ng-eNB support a physical layer (PHY) 202 of EUTRA or NR. The PHY layer 202 provides a transport channel to a medium access control (MAC) 204 sublayer, which in turn provides a logical channel to a radio link control (RLC) sublayer 206, and the RLC sublayer provides an RLC channel to a packet data convergence protocol (PDCP) sublayer 210. The PDCP sublayer 210 provides a signaling radio bearer (SRB) / or a data radio bearer (DRB) to the radio resource control (RRC) sublayer 210.

[0050] The UE and the AMF operating in the core network exchange messages of the non-access stratum (NAS) sublayer 216 via the gNB / ng-eNB, and the UE and the LMF also operating in the core network exchange messages of the LPP layer 218 via the gNB / ng-eNB and the AMF. In other words, the UE and the LMF encapsulate the LPP message in the NAS message and the NAS message in the RRC message. The gNB / ng-eNB according to the architecture provides tunneling of layers 216 and 218 and does not route or otherwise process messages at layers 216, 218.

[0051] Next, refer to FIG. 3A to FIG. 5C Discussion Figure 1A and several example scenarios related to sending data in an inactive or idle state. FIG. 3A to FIG. 5C Similar events in the Figure 3A Event 302 in is similar to Figure 3B To event 302 in FIG. 3G, FIG. 4A to FIG. 4C Event 402 and FIG. 5A to FIG. 5C 502 in FIG. 504 ), with differences discussed below where appropriate. In addition to the differences shown in the figures and discussed below, any of the alternative implementations discussed with respect to a particular event (e.g., for message delivery and processing) may be applied to events labeled with similar reference numbers in other figures, and may also be applied to both integrated base stations and distributed base stations.

[0052] To simplify the following description, an “inactive state” is used and may refer to an RRC_INACTIVE or RRC_IDLE state, and a “connected state” is used and may refer to an RRC_CONNECTED state.

[0053] First reference Figure 3A , which shows a scenario 300A in which a base station 104 includes a central unit (CU) 172 and a distributed unit (DU) 174. Depending on the implementation, the DU 174 operates one or more transmit-receive points (TRPs) ( Figure 3A 300). In the scenario 300, the UE 102 initially operates in a connected state 302 and communicates 304 with the DU 174, such as by using a DU configuration. While communicating 304 with the DU 174, the UE 102 receives an uplink grant and a downlink assignment from the DU 174 using a cell radio network temporary identifier (C-RNTI). The UE 102 uses the uplink grant to send UL data to the DU 174 and uses the downlink assignment to receive DL data from the DU 174. The UE 102 further communicates 304 with the CU 172 via the DU 174 by using a CU configuration. The UE 102 communicates 304 LPP messages with the LMF 168 via the CU 172 and the DU 174. In some implementations, the CU 172 exchanges LPP messages with the LMF 168 directly or via the AMF 164. Depending on the implementation, before or simultaneously with the UE communicating 304 with the base station 104, the LMF 68 performs 306 a TRP information exchange process with the base station 104 to obtain detailed information of the TRP hosted by the base station 104.

[0054] In some implementations, LMF 168 sends a TRP information request message (i.e., an LMF to BS message or an NRPPa message) to CU 172 to perform the TRP information exchange process. In response to receiving the LMF to BS message or after receiving the LMF to BS message, CU 172 sends at least one TRP information request message (i.e., a CU to DU message or an F1AP message) to DU 174 to request DU 174 to provide detailed information of a TRP hosted by DU 174. In response to each of the CU to DU messages, DU 174 sends a TRP information response message (i.e., a DU to CU message or an F1AP message) including TRP information of a specific TRP to CU 172. In some implementations, CU 172 sends a TRP information response message (i.e., a DU to CU message or an F1AP message) to other DUs ( Figure 3A In response to each of the at least one CU-to-DU message received by a specific DU among the other DUs, the specific DU sends a TRP information response message (i.e., a DU-to-CU message or an F1AP message) including TRP information of the specific TRP to CU 172.

[0055] After receiving all of at least one DU-to-CU message from DU 174 and / or other DUs, CU 172 sends a BS-to-LMF message (e.g., a TRP information response message) including the TRP information received from DU 174 and / or other DUs to LMF 168. In some implementations, the TRP information for a particular TRP includes a positioning reference signal (PRS) configuration, a physical cell identity (PCI), and / or a cell global identifier (CGI). In some implementations, the DU-to-CU message includes a TRP ID for a particular TRP and the TRP information for the TRP, and CU 172 includes the TRP ID and the TRP information in a BS-to-LMF message.

[0056] After performing 306 the TRP information exchange procedure, the LMF 168 sends 308 a measurement-needed preconfiguration message (i.e., an LMF-to-BS message or an NRPPa message) to the CU 172 to request configuration of a PRS processing window (PPW) of the UE 102 to measure the PRS sent by the TRP. In some implementations, the LMF 168 includes TRP PRS information items (e.g., TRP-PRS-Information-List-Item IE) in the measurement-needed preconfiguration message at event 308. In some implementations, each of the TRP PRS information items includes a PRS configuration, PCI, CGI, and / or TRP ID of a specific TRP among the TRPs operated by the DU 174. In some implementations, the LMF 168 determines the TRP PRS information items based on at least one DU-to-CU message (e.g., TRP ID and TRP information) of the TRP information exchange procedure. In further implementations, LMF 168 includes PPW information in the measurement pre-configuration message required at event 308 to instruct CU 172 to configure the PPW of UE 102. DU 174 generates a PPW configuration taking into account the PPW information. In some implementations, the PPW information includes the PRS processing capability of UE 102. Depending on the implementation, the PRS processing capability is associated with one or more frequency bands supported by UE 102. In other implementations, the PPW information includes PPW configuration parameters.

[0057] After receiving 308 the message or in response to receiving the message, the CU 172 sends 310 a measurement preconfiguration required message (i.e., a CU to DU message or a F1AP message) including a TRPPRS information item to the DU 174 to request configuration of the PPW of the UE 102. In some implementations, the CU 172 includes the PPW information in the measurement preconfiguration required message. In response, the DU 174 sends 312 a measurement preconfiguration confirmation message (i.e., a DU to CU message or a F1AP message) to the CU 172 to confirm the configuration of the PPW of the UE 102. After receiving 312 the measurement preconfiguration confirmation message or in response to receiving the measurement preconfiguration confirmation message, the DU 174 sends 314 a UE context modification required message including the PPW configuration of the UE 102 to the CU 172. The PPW configuration configures the PPW for the UE 102 in the absence of a measurement gap or outside of a measurement gap for measuring the PRS sent by the TRP. In some implementations, the DU 174 generates a PPW configuration based on the TRP PRS information item and / or the PPW information. In some implementations, the DU 174 generates a container configuration (e.g., CellGroupConfig IE, BWP-DownlinkDedicatedIE, DL-PRS-ProcessingWindowPreConfigAddModList IE, or DL-PRS-ProcessingWindowPreConfigAddModList-r17 IE) including the PPW configuration (e.g., DL-PRS-ProcessingWindowPreConfig or DL-PRS-ProcessingWindowPreConfig-r17 IE), and includes the container configuration in the UE context modification required message. In some implementations, the DU 174 sends 314 the UE context modification required message before or after sending 312 the measurement preconfiguration confirmation message. In some implementations, the DU 174 generates the container configuration and / or the PPW configuration as an RRC IE and / or an RRC IE, respectively.

[0058] In some implementations, the DU 174 does not include the PPW configuration as an interface IE (e.g., F1AP IE) in the measurement preconfiguration confirmation message. In some such implementations, the PPW configuration is transparent to the CU 172. In other implementations, the DU 174 includes at least some of the PPW information as an interface IE (e.g., F1AP IE) in the measurement preconfiguration confirmation message. In some such implementations, the PPW configuration is opaque to the CU 172.

[0059] In response to receiving 314 the UE context modification required message or after receiving the UE context modification required message, the CU 172 sends 316 a UE context modification confirmation message to the DU 174. After receiving 312 the measurement preconfiguration confirmation message, receiving 314 the UE context modification required message, or sending 316 the UE context modification confirmation message, the CU 172 sends 318 a measurement preconfiguration confirmation message (i.e., a BS to LMF message or an NRPPa message) to the LMF 168 to confirm the configuration of the PPW of the UE 102.

[0060] In some implementations, DU 174 assigns a PPW ID to each of the PPW configurations. In some implementations, DU 174 includes the PPW ID in the corresponding PPW configuration. In other implementations, DU 174 includes the PPW ID and the PPW configuration in the container configuration. In some implementations, DU 174 includes the PCI in each of the PPW configurations. DU 174 sets the PCI to the PCI in a specific TRP PRS information item associated with the PPW configuration. In some implementations, DU 174 associates the PPW ID and / or the PPW configuration with the TRP PRS information item. In some implementations, DU 174 associates a specific PPW ID and the corresponding PPW configuration with a specific one of the TRP PRS information items. In other implementations, DU 174 associates a specific PPW ID and / or the corresponding PPW configuration with some of the TRP PRS information items. In still other implementations, the DU 174 associates a specific PPW ID and / or a corresponding PPW configuration with a specific one of the TRP PRS information items.

[0061] In some implementations, the DU 174 determines the serving cell ID based on the PCI in the TRP PRS information item and includes the serving cell ID in the container configuration or in the CellGroupConfig IE including the container configuration. In some implementations, the DU 174 creates a table to store the association between the PPW ID, the serving cell ID and / or the PPW configuration and the TRP PRS information item.

[0062] In other implementations, CU 172 assigns a PPW ID to each of the PPW configurations. In some implementations, CU 172 includes the PPW ID in the corresponding PPW configuration. In other implementations, CU 172 includes the PPW ID and the PPW configuration in the container configuration. In some implementations, CU 172 associates the PPW ID with the TRP PRS information item. In some implementations, CU 172 associates a specific one of the PPW IDs with a specific one of the TRP PRS information items. In other implementations, CU 172 associates a specific one of the PPW IDs with some of the TRP PRS information items. In yet other implementations, CU 172 associates a specific PPW ID and / or a corresponding PPW configuration with a specific one of the TRP PRS information items. In some implementations, CU 172 creates a table to store the association between the PPW ID and the TRP PRS information item. In further implementations, CU 172 includes the PCI in each of the PPW configurations. Depending on the implementation, the CU 172 sets the PCI to the PCI in the TRP PRS information item associated with the PPW configuration. In some implementations, the CU 172 determines the serving cell ID for the PCI and includes the serving cell ID in the container configuration or in the CellGroupConfig IE that includes the container configuration.

[0063] Events 310, 312, 314, and 316 are Figure 3A It is collectively referred to as the PPW (pre) configuration process 392A.

[0064] After receiving the PPW configuration or container configuration, the CU 172 generates an RRC reconfiguration message (e.g., an RRCReconfiguration message) including the PPW configuration or container configuration, and sends 320 a CU-to-DU message (e.g., a DL RRC messaging message) including the RRC reconfiguration message to the DU 174. In turn, the DU 174 sends 322 the RRC reconfiguration message to the UE 102. In response, the UE 102 sends 324 an RRC reconfiguration complete message (e.g., an RRCReconfigurationComplete message) to the DU 174, which in turn sends 326 a DU-to-CU message (e.g., an UL RRC messaging message) including the RRC reconfiguration complete message to the CU 172.

[0065] Events 320, 322, 324, and 326 are Figure 3A 394. Events 308, 310, 312, 314, 316, 318, 320, 322, 324, and 326 are collectively referred to as RRC reconfiguration process 394. Figure 3A In some implementations, additional PPW configuration procedures are performed to configure additional PPW configurations for UE 102, similar to PPW configuration procedure 390A.

[0066] In some implementations, later, the LMF 168 sends 328 a measurement activation message (i.e., an LMF to BS message or an NRPPa message) to the CU 172 to activate at least one of the PPW configurations of the UE 102. In some implementations, the measurement activation message of event 328 includes PRS measurement information items (e.g., PRS-Measurements-Info-List-Item IEs), each of which includes a reference point (e.g., pointA), a measured PRS periodicity (e.g., measPRSPeriodicity), a measured PRS offset (e.g., measPRSOffset), and / or a measured PRS length (e.g., measurementPRSLength). In further implementations, in response to or after receiving the measurement activation message 328, the CU 172 sends 330 a measurement activation message (i.e., a CU to DU message or an F1AP message) to the DU 174 to activate at least one of the PPW configurations of the UE 102. In some implementations, the measurement activation message of event 330 includes PRS measurement information items (e.g., PRS-Measurements-Info-List-Item IE), each of which includes a reference point (e.g., pointA), a measured PRS periodicity (e.g., measPRSPeriodicity), a measured PRS offset (e.g., measPRSOffset), and / or a measured PRS length (e.g., measurementPRSLength). The PRS measurement information items of event 328 may be similar or identical to the PRS measurement information items of event 330.

[0067] Depending on the implementation, in response to receiving 330 the measurement activation message or after receiving the measurement activation message, the DU 174 sends 332 a PPW activation command to the UE 102 to activate at least one of the PPW configurations. In other scenarios or implementations, the CU 172 sends 330 the measurement activation message to the DU 174 in response to receiving an LMF to BS message (e.g., measurement pre-configuration message 308 required) other than the measurement activation message of event 328 or after receiving the LMF to BS message. In some implementations, the PPW activation command is a DL MAC control element (e.g., PPW activation / deactivation command MAC CE). In such implementations, the DU 174 generates a DL MAC PDU that includes a DL MAC control element and a subheader for the DL MAC control element, and sends 332 the DL MAC PDU to the UE 102. In some implementations, the subheader includes a logical channel ID for the DL MAC control element.

[0068] Alternatively, the UE 102 sends 329 a PPW activation request to the DU 174 to request activation of at least one of the PPW configurations. In some implementations, in response to receiving the 329 PPW activation request or after receiving the PPW activation request, the DU 174 sends 332 a PPW activation command to the UE 102. In some implementations, the PPW activation request is a UL MAC control element (e.g., a PPW activation / deactivation request MAC control element). In such implementations, the UE 102 generates a UL MAC PDU that includes a UL MAC control element and a subheader for the UL MAC control element, and sends 329 the UL MAC PDU to the DU 174. In some implementations, the subheader includes a logical channel ID for the UL MAC control element. In some implementations, the UE 102 includes at least one PPW ID in the PPW activation request indicating the PPW configuration that the UE 102 requests activation. In some implementations, the UE 102 includes at least one PCI or serving cell ID associated with at least one PPW ID in the PPW activation request. In other implementations, the UE 102 does not include the PPW ID in the PPW activation request in order to request activation of all PPW configurations in the PPW configuration. In still other implementations, the UE 102 includes a specific field with a specific value instead of all PPW IDs in the PPW ID in the PPW activation request in order to request activation of all PPW configurations in the PPW configuration.

[0069] In some implementations, the DU 174 includes in the PPW activation command at least one PPW ID indicating the PPW configuration to be activated. In some implementations, the DU 174 includes in the PPW activation command at least one PCI or serving cell ID associated with the at least one PPW ID. In some implementations, the DU 174 determines (e.g., identifies, selects, or derives) at least one PPW ID and / or at least one PCI or serving cell ID based on the TRP PRS information items and / or associations received at event 330. In some implementations, the DU 174 performs a table lookup to determine at least one PPW ID and / or at least one PCI or serving cell ID based on the TRP PRS information items received at event 330. In some cases, such as receiving 329 a PPW activation request, the DU 174 sets the at least one PPW ID in the PPW activation command to the value of the PPW ID in the PPW activation request. In some implementations, DU 174 determines the serving cell ID based on the PCI in the TRP PRS information item received at event 330 and includes the serving cell ID and at least one PPW ID in the PPW activation command.

[0070] In some implementations, the DU 174 does not include a PPW ID in the PPW activation command in order to activate all PPW configurations in the PPW configuration. In further implementations, the UE 102 includes a specific field with a specific value in the PPW activation request instead of including all PPW IDs in the PPW ID to request activation of all PPW configurations in the PPW configuration.

[0071] In some implementations, the DU 174 sends 334 a DU-to-CU message to the CU 172 after sending the PPW activation command to the UE 102, the DU-to-CU message including a PPW status indicating the status of the PPW configuration (e.g., activated or deactivated). Therefore, the CU 172 determines that the UE 102 activates at least one of the PPW configurations and / or starts performing measurements on the PRS sent by the TRP based on the PPW status. In some implementations, the CU 172 sends 336 a BS-to-LMF message including the PPW status to the LMF 168. Therefore, the LMF 168 determines that the UE 102 activates the PPW configuration and / or starts performing measurements on the PRS sent by the TRP based on the PPW status.

[0072] Events 328, 330, 329, 332, 334, and 336 are Figure 3A390A or an additional PPW configuration process, similar to PPW activation process 396.

[0073] In response to receiving 332 the PPW activation command or after receiving the PPW activation command, the UE 102 activates 338 at least one PPW configuration according to the PPW activation command. In some implementations, the UE 102 identifies the PPW configuration according to the PPW ID and / or at least one PCI or serving cell ID in the PPW activation command. After activating the PPW configuration, the UE 102 performs 338 measurement on the PRS sent by the TRP using at least one PPW in the at least one activated PPW configuration. In some implementations, the UE 102 obtains a measurement result from the measurement and sends 340 the measurement result to the LMF 168 via the base station 104 (i.e., the DU 174 and the CU 172). In some implementations, the UE 102 generates an LPP message (e.g., a ProvideLocationInformation message) including the measurement result and sends 340 the LPP message to the LMF 168 via the base station 104.

[0074] In some implementations, the CU configuration includes configuration parameters in a RadioBearerConfig information element (IE) and / or a MeasConfig IE (e.g., as defined in 3GPP specification 38.331 version 16.7.0 or higher). In some implementations, the CU configuration is or includes the RadioBearerConfig IE and / or the MeasConfig IE, and the second CU configuration is or includes the RadioBearerConfig IE and / or the MeasConfig IE. In some implementations, the DU configuration includes configuration parameters related to the operation of the RRC, RLC, MAC, and / or PHY protocol layers (e.g., RLC 206B, MAC 204B, and / or PHY 202B), which the UE 102 and the DU 174 use to communicate with each other when the UE 102 operates in a connected state. In some implementations, the DU configuration includes configuration parameters in a CellGroupConfig IE (e.g., as defined in 3GPP specification 38.331 version 16.7.0). In some implementations, the DU configuration is the CellGroupConfig IE.

[0075] Next reference Figure 3B, scenario 300B is generally similar to scenario 300A, except that CU 172 sends 315 a UE context modification request message to DU 174 to request PPW configuration, and in response, DU 174 sends 317 a UE context modification response message including the PPW configuration. In scenario 300B, DU 174 avoids sending a UE context modification required message including the PPW configuration to CU 172. In some implementations, CU 172 sends 315 a UE context modification request message to DU 174 after sending 310 a measurement preconfiguration required message.

[0076] In some implementations, CU 172 includes an indication in the UE context modification request message, which indicates that DU 174 generates a PPW configuration for positioning measurements. In response to the indication, DU 174 generates a PPW configuration based on the TRP PRS information item and includes the PPW configuration in the UE context modification response message. In other implementations, the UE context modification request message does not include the indication. In some such implementations, CU 172 sends the UE context modification request message immediately after sending 310 the measurement preconfiguration required message, so that DU 174 can correlate the UE context modification request message with the measurement preconfiguration required message.

[0077] In some implementations, the DU 174 generates a container configuration (e.g., CellGroupConfig IE, BWP-DownlinkDedicatedIE, DL-PRS-ProcessingWindowPreConfigAddModList IE, or DL-PRS-ProcessingWindowPreConfigAddModList-r17 IE) including a PPW configuration (e.g., DL-PRS-ProcessingWindowPreConfig or DL-PRS-ProcessingWindowPreConfig-r17 IE), and includes the container configuration in a UE context modification response message.

[0078] Events 310, 312, 315, and 317 are Figure 3B 392B. Events 308, 310, 312, 315, 317, 318, 320, 322, 324, and 326 are collectively referred to as PPW (pre) configuration process 392B. Figure 3B It is collectively referred to as PPW configuration process 390B.

[0079] Next reference Figure 3C, scenario 300C is generally similar to scenarios 300A and 300B, except that DU 174 sends 313 a measurement preconfiguration confirm message including a PPW configuration in response to the measurement preconfiguration required message of event 310. In scenario 300C, DU 174 avoids sending a UE context modification required message including a PPW configuration to CU 172.

[0080] In some implementations, DU 174 generates a container configuration (e.g., CellGroupConfig IE, BWP-DownlinkDedicatedIE, DL-PRS-ProcessingWindowPreConfigAddModList IE, or DL-PRS-ProcessingWindowPreConfigAddModList-r17 IE) including a PPW configuration (e.g., DL-PRS-ProcessingWindowPreConfig or DL-PRS-ProcessingWindowPreConfig-r17 IE), and includes the container configuration in the measurement pre-configuration required message of event 313.

[0081] Events 310 and 313 in Figure 3C 392C. Events 308, 310, 313, 318, and 394 are collectively referred to as PPW (pre) configuration process 392C. Figure 3C This is collectively referred to as the PPW configuration process 390C.

[0082] Next reference Figure 3D , scenario 300D is generally similar to scenarios 300A-C. The differences between scenario 300D and scenarios 300A-C are discussed below.

[0083] In scenario 300D, events 304, 306, 390A / 390B / 390C, 396, 338, and 340 are Figure 3D388. In some implementations, after the positioning measurement process 388, the LMF 168 sends 342 an LMF to BS message to the CU 172, causing the CU 172 to deactivate at least one of the activated PPW configurations. In some implementations, the LMF to BS message is a new NRPPa message (e.g., a measurement deactivation message). In other implementations, the LMF to BS message is an existing NRPPa message (e.g., a measurement termination message). In response to receiving the LMF to BS message or after receiving the LMF to BS message, the CU 172 sends 344 a CU to DU message to the DU 174, causing the DU 174 to deactivate at least one of the activated PPW configurations. In response to receiving the CU to DU message or after receiving the CU to DU message, the DU 174 sends 348 a PPW deactivation command to the UE 102 to deactivate at least one of the activated PPW configurations. In some implementations, the PPW deactivation command is a DL MAC control element (e.g., a PPW activation / deactivation command MAC control element). In such implementations, the DU 174 generates a DL MAC PDU that includes the DL MAC control element and a subheader for the DL MAC control element, and sends 348 the DL MAC PDU to the UE 102. In some implementations, the subheader includes a logical channel ID for the DL MAC control element.

[0084] In some implementations, CU 172 does not include information in the CU-to-DU message at event 344 that DU 174 can use to derive which PPW configuration(s) to deactivate. In such implementations, DU 174 deactivates all of the activated PPW configurations of UE 102 in response to the CU-to-DU message at event 344. In other implementations, CU 172 includes information (e.g., a PRS measurement information item) in the CU-to-DU message at event 344 that DU 174 can use to derive which PPW configuration(s) to deactivate.

[0085] In some implementations, the CU to DU message of event 344 is a new F1AP message (e.g., a measurement deactivation message). In other implementations, the CU to DU message of event 344 is an existing F1AP message (e.g., a measurement preconfiguration termination message). In yet other implementations, the CU to DU message of event 344 is a measurement activation message that does not include a PRS measurement information item (e.g., a PRS-Measurements-Info-List-Item IE). In such implementations, the measurement activation message is considered a measurement deactivation message. In yet other implementations, the CU to DU message of event 344 is a measurement activation message that includes a PRS measurement information item (e.g., a PRS-Measurements-Info-List-Item IE) and a deactivation indication of each of the PRS measurement information items.

[0086] Alternatively, the UE 102 sends 346 a PPW deactivation request to the DU 174 to request deactivation of at least one of the activated PPW configurations. Depending on the implementation, in response to receiving 346 the PPW deactivation request or after receiving the PPW deactivation request, the DU 174 sends 348 a PPW deactivation command to the UE 102. In some implementations, the PPW deactivation request is a UL MAC control element (e.g., a PPW activation / deactivation request MAC control element). In such implementations, the UE 102 generates a UL MAC PDU that includes a UL MAC control element and a subheader for the UL MAC control element, and sends 346 the UL MAC PDU to the DU 174. In some implementations, the UE 102 includes in the PPW deactivation request a PPW ID indicating the activated PPW configuration that the UE 102 requests to deactivate.

[0087] In some implementations, the DU 174 includes in the PPW deactivation command a PPW ID indicating the PPW configuration to be deactivated. In some implementations, the DU 174 determines the PPW ID based on the PRS measurement information item (if included) included in the CU-to-DU message of event 344. In some implementations, the DU 174 performs a table lookup (e.g., as for Figure 3A 346 ) to determine the PPW ID based on the PRS measurement information item. In some cases, such as when a PPW deactivation request is received 346 , the DU 174 sets the PPW ID in the PPW deactivation command to the value of the PPW ID in the PPW deactivation request.

[0088] In some implementations, after sending 348 the PPW deactivation command to the UE 102 or in response to sending the PPW deactivation command to the UE, the DU 174 sends 350 a DU to CU message to the CU 172, the DU to CU message including a PPW status indicating that the PPW configuration of the UE 102 has been deactivated. Thus, the CU 172 determines that the UE 102 deactivates the PPW configuration and / or stops performing measurements on the PRS sent by the TRP based on the PPW status. In some implementations, the DU to CU message of event 350 is an existing F1AP message (e.g., as defined in 3GPP specification 38.473). In other implementations, the DU to CU message is a new F1AP message (e.g., a measurement status message or a PPW status message).

[0089] In some implementations, CU 172 sends 352 a BS-to-LMF message including the PPW status to LMF 168. Thus, LMF 168 determines that UE 102 deactivates PPW configuration and / or stops performing measurements on PRS sent by TRP based on the PPW status. In some implementations, the BS-to-LMF message of event 352 is an existing NRPPa message (e.g., as defined in 3GPP specification 38.455). In other implementations, the BS-to-LMF message is a new NRPPa message (e.g., a measurement status message or a PPW status message).

[0090] Events 342, 344, 346, 348, 350, and 3752 Figure 3D This is collectively referred to as the PPW deactivation process 398.

[0091] Later, depending on the implementation, the LMF 168, the CU 172, and / or the DU 174 perform 395 a PPW activation procedure with the UE 102 to activate the deactivated PPW configuration. In some implementations, in response to the PPW activation procedure 395, the UE 102 activates 339 the PPW configuration identified by the PPW ID in the PPW activation command in the procedure 395. After activating the PPW configuration, the UE 102 performs 339 measurement on the PRS sent by the TRP using the PPW in the activated PPW configuration. In some implementations, the UE 102 obtains a measurement result from the measurement and sends 341 the measurement result to the LMF 168 via the base station 104 (i.e., the DU 174 and the CU 172). In some implementations, the UE 102 generates an LPP message (e.g., a ProvideLocationInformation message) including the measurement result and sends 341 the LPP message to the LMF 168 via the base station 104.

[0092] Next reference Figure 3E, scenario 300E is generally similar to scenarios 300A-D. The differences between scenario 300E and scenarios 300A-D are discussed below.

[0093] In some implementations, after the positioning measurement process 388, the LMF 168 sends 343 an LMF to BS message to the CU 172, causing the CU 172 to release the PPW configuration. In some implementations, the LMF to BS message is an existing NRPPa message (e.g., as defined in 3GPP specification 38.455). For example, the LMF to BS message is a measurement preconfiguration required message, a measurement abort message, or an error indication message. In other implementations, the LMF to BS message is a new NRPPa message. For example, the LMF to BS message is a measurement deactivation message, a measurement preconfiguration release required message, or a measurement preconfiguration release request message.

[0094] In response to receiving 343 the LMF to BS message or after receiving the LMF to BS message, CU 172 sends 345 a CU to DU message to DU 174, causing DU 174 to release at least one of the PPW configurations. In response to receiving 345 the CU to DU message or after receiving the CU to DU message, DU 174 releases at least one of the PPW configurations of UE 102. In some implementations, the CU to DU message is an existing F1AP message (e.g., as defined in 3GPP specification 38.473). For example, the CU to DU message is a positioning measurement termination message, a measurement preconfiguration required message, or a UE context modification request message. In other implementations, the CU to DU message is a new F1AP message (e.g., a measurement deactivation message, a measurement preconfiguration release required message, or a measurement preconfiguration release request message). Depending on the implementation, DU 174 sends 347 a DU to CU message to CU 172 in response to the CU to DU message. In some implementations, the DU-to-CU message of event 347 is an existing F1AP message (eg, a Measurement Preconfiguration Confirm message or a UE Context Modification Response message).

[0095] In response to or after receiving the LMF to BS message, CU 172 generates an RRC reconfiguration message (e.g., RRCReconfiguration message) to release the PPW configuration, and sends 321 a CU to DU message (e.g., DL RRC messaging message) including the RRC reconfiguration message to DU 174. Then, DU 174 sends 323 the RRC reconfiguration message to UE 102. In response to or after receiving the RRC reconfiguration message 323, UE 102 releases the PPW configuration.

[0096] In some implementations, the RRC reconfiguration message includes PPW release information, which includes a PPW ID of at least one of the PPW configurations to release the PPW configuration. For example, the PPW release information is a PPW release list IE. In such implementations, the UE 102 identifies at least one of the PPW configurations according to the PPW ID, and releases the identified PPW configuration in response to the RRC reconfiguration message or the PPW release information. In some implementations, the CU 172 generates the PPW release information and includes the PPW release information in the CU to DU message of event 345. In such implementations, the DU 174 identifies the PPW configuration according to the PPW ID, and releases the identified PPW configuration in response to the CU to DU message or the PPW release information.

[0097] In response to the RRC reconfiguration message, UE 102 sends 325 an RRC reconfiguration complete message (e.g., an RRCReconfigurationComplete message) to DU 174, which in turn sends 327 a DU to CU message (e.g., an UL RRC messaging message) including the RRC reconfiguration complete message to CU 172. In some implementations, after receiving 327 the DU to CU message of event 327, CU 172 sends 353 a BS to LMF message to LMF 168 in response to the LMF to BS message of event 343. Alternatively, CU 172 sends 353 a BS to LMF message before receiving the DU to CU message of event 327.

[0098] In some implementations, CU 172 autonomously determines to release at least one of the PPW configurations without receiving an LMF to BS message like event 343. In such implementations, CU 172 sends 345 a CU to DU message to DU 174 and / or sends 321 an RRC reconfiguration message in response to the determination.

[0099] In some implementations, later, LMF 168 , CU 172 , and / or DU 174 perform 389 a positioning measurement process with UE 102 , similar to process 388 .

[0100] In some implementations, the LMF 168, CU 172, and / or DU 174 perform 398 a PPW deactivation procedure after performing 388 a positioning measurement procedure and before receiving 343 a LMF to BS message or sending 345 a CU to DU message.

[0101] Next reference Figure 3F , scenario 300F is generally similar to scenarios 300A-E. The differences between scenario 300F and scenarios 300A-E are discussed below.

[0102] In scenario 300F, after receiving 345 the CU to DU message or in response to receiving the CU to DU message, DU 174 sends 354 a UE context modification required message including PPW release information indicating release of the PPW configuration. In response, CU 172 sends 356 a UE context modification confirmation message to DU 174. In some implementations, CU 172 includes the PPW release information received from DU 174 in the RRC reconfiguration message. In some such implementations, CU 172 does not include the PPW release information in the CU to DU message of event 345.

[0103] Next, refer to FIG. 4A to FIG. 7 Several example methods that can be implemented in a DU of a BS or a CU of a BS are discussed. Each of these methods can be implemented using processing hardware (such as one or more processors) to execute instructions stored on a non-transitory computer-readable medium (such as a computer memory).

[0104] First reference Figure 4A , method 400A is a method for configuring a PPW of a UE (eg, UE 102) and is implemented in a DU (eg, DU 174).

[0105] Method 400A begins at block 402, where a DU communicates with a UE and a CU (e.g., CU 172). At block 404, the DU receives a first CU-to-DU message from the CU requesting configuration of a PPW of the UE (e.g., event 310). At block 406, the DU sends a first DU-to-CU message to the CU in response to the first CU-to-DU message (e.g., event 312). In some implementations, the CU sends the first CU-to-DU message to the DU to confirm the successful configuration of the PPW. At block 408, the DU sends a second DU-to-CU message to the CU including the PPW configurations 1, ..., M of the UE in response to the first CU-to-DU message (e.g., event 314), where M is an integer and greater than zero. At block 410, the DU receives a second CU-to-DU message from the CU in response to the second DU-to-CU message (e.g., event 316). At block 412, the DU sends a PPW activation command to the UE to activate at least one of one or more of the PPW configurations (e.g., event 332).

[0106] In some implementations, the first CU to DU message includes TRP PRS information items 1, ..., N, where N is an integer and greater than zero. In some implementations, the DU generates a PPW configuration (e.g., MeasPPWConfig IE) including PPW configurations 1, ..., M (e.g., DL-PRS-ProcessingWindowPreConfig-r17IE 1, ..., M), and includes the PPW configuration in the second DU to CU message. In some implementations, the DU generates a PPW configuration for positioning measurement (e.g., the UE uses a PPW in PPW configuration 1, ..., M to measure PRS).

[0107] In some implementations, the DU assigns PPW IDs 1, ..., M to PPW configurations 1, ..., M, respectively. In some implementations, the DU includes PPW IDs 1, ..., M in PPW configurations 1, ..., M, respectively. In other implementations, the DU includes PPW IDs 1, ..., M and PPW configurations 1, ..., M in the PPW configurations. In some implementations, the DU associates PPW IDs 1, ..., M with TRP PRS information items 1, ..., N. In some implementations, the DU associates a specific one of the PPW IDs with a specific one of the TRP PRS information items. In other implementations, the DU 174 associates a specific one of the PPW IDs with some of the TRP PRS information items. In some implementations, the DU creates a table to store associations between PPW IDs and TRP PRS information items.

[0108] In some implementations, the DU includes at least one of PPW IDs 1, ..., M in the PPW activation command. Each of the at least one PPW ID identifies a specific one of at least one PPW configuration of PPW configurations 1, ..., M.

[0109] In some implementations, the DU generates a container configuration (e.g., CellGroupConfig IE, BWP-DownlinkDedicated IE, DL-PRS-ProcessingWindowPreConfigAddModList IE, or DL-PRS-ProcessingWindowPreConfigAddModList-r17IE) including PPW configurations 1, ..., M (e.g., PPWConfig IE 1, ..., M), and includes the container configuration in a second DU to CU message.

[0110] Figure 4B4 is a flow chart of an example method 400B similar to method 400A, except that method 400B includes blocks 409 and 411 instead of blocks 408 and 410. At block 409, the DU receives a second CU-to-DU message from the CU requesting configuration of the PPW of the UE (e.g., event 315). At block 411, the DU sends a second DU-to-CU message including the PPW configurations 1, ..., M of the UE to the CU in response to the second CU-to-DU message (e.g., event 317).

[0111] Figure 4C 4 is a flow chart of an example method 400C that is similar to method 400A, except that method 400C includes block 407 instead of blocks 406, 408, and 410. At block 407, the DU sends a first DU-to-CU message including the UE's PPW configuration 1, ..., M to the CU in response to the first CU-to-DU message to confirm the successful configuration of the PPW (e.g., event 313).

[0112] In some implementations, the DU generates a container configuration (e.g., CellGroupConfig IE, BWP-DownlinkDedicated IE, DL-PRS-ProcessingWindowPreConfigAddModList IE, or DL-PRS-ProcessingWindowPreConfigAddModList-r17 IE) including PPW configurations 1, ..., M (e.g., PPWConfig IE 1, ..., M) and includes the container configuration in the first DU to CU message.

[0113] In the previous figures (e.g., FIG. 3A to FIG. 3F The examples and implementations described in ) can be applied to FIG. 4A to FIG. 4C .

[0114] Next reference Figure 5A , method 500A is a method for configuring a PPW of a UE (eg, UE 102) and is implemented in a CU (eg, CU 172).

[0115] Method 500A begins at box 502, where the CU communicates with the UE and the DU (e.g., DU 174). At box 504, the CU sends a first CU-to-DU message to the DU requesting configuration of the UE's PPW (e.g., event 310). At box 506, the CU receives a first DU-to-CU message from the DU in response to the first CU-to-DU message (e.g., event 312). In some implementations, the first DU-to-CU message confirms the successful configuration of the PPW. At box 508, the CU receives a second DU-to-CU message from the DU including PPW configurations 1, ..., M after sending the first CU-to-DU message (e.g., event 314), where M is an integer and greater than zero. At box 510, the CU sends a second CU-to-DU message to the DU in response to the second DU-to-CU message (e.g., event 316). At box 512, the CU sends a message including PPW configurations 1, ..., M to the UE via the DU (e.g., events 320, 322). At block 514, the CU sends a third CU-to-DU message to the DU to command the DU to activate at least one of PPW configurations 1, ..., M (eg, event 330). At block 516, the CU receives one or more measurement results from the UE via the DU (eg, event 340).

[0116] In some implementations, the first CU-to-DU message includes TRP PRS information items 1, ..., N, where N is an integer and is greater than 0. In some implementations, the second DU-to-CU message includes a container configuration (e.g., CellGroupConfig IE, BWP-DownlinkDedicated IE, DL-PRS-ProcessingWindowPreConfigAddModList IE, or DL-PRS-ProcessingWindowPreConfigAddModList-r17 IE), which includes PPW configurations 1, ..., M (e.g., DL-PRS-ProcessingWindowPreConfig or DL-PRS-ProcessingWindowPreConfig-r17 IE).

[0117] Figure 5B is a flow chart of an example method 500B that is similar to method 500A, except that method 500B includes blocks 509 and 511 instead of blocks 508 and 510. At block 509, the CU sends a second CU-to-DU message to the DU after sending the first CU-to-DU message (e.g., event 315). At block 511, the CU receives a second DU-to-CU message including PPW configurations 1, ..., M from the DU in response to the second CU-to-DU message (e.g., event 317).

[0118] Figure 5C is a flow chart of an example method 500C that is similar to method 500A, except that method 500C includes block 507 instead of blocks 506, 508, and 510. At block 507, the CU receives a first DU-to-CU message including the UE's PPW configurations 1, ..., M from the DU in response to the first CU-to-DU message (e.g., event 313). In some implementations, the first DU-to-CU message confirms the successful configuration of the PPW.

[0119] In the previous figures (e.g., FIG. 3A to FIG. 4C The examples and implementations described in ) can be applied to FIG. 5A to FIG. 5C .

[0120] Next reference Fig. 6A , method 600A is a method for configuring a PPW of a UE (eg, UE 102) and is implemented in a CU (eg, CU 172).

[0121] Method 600A starts at box 602, where the process performs at least one of methods 500A, 500B, or 500C. At box 604, the CU sends a first CU-to-DU message to the DU to release the PPW configuration of the UE (e.g., event 345). At box 606, the CU receives a first DU-to-CU message from the DU in response to the first CU-to-DU message (e.g., event 347). At box 608, the CU receives a second DU-to-CU message from the DU after sending the first CU-to-DU message (e.g., event 354), the second DU-to-CU message including PPW release information for releasing at least one of PPW configurations 1, ..., M. At box 610, the CU sends a second CU-to-DU message to the DU in response to the second DU-to-CU message (e.g., event 356). At box 612, the CU sends an RRC message including PPW release information to the UE via the DU (e.g., events 321, 323). At block 614, the CU receives an RRC Complete message from the UE via the DU (eg, events 325, 327).

[0122] In some implementations, the PPW release information includes a PPW ID identifying at least one PPW configuration. Each of the PPW IDs identifies a specific one of the PPW configurations. In some implementations, the DU identifies the released PPW configuration based on the first CU-to-DU message.

[0123] In some implementations, the CU receives a PPW ID from the DU at block 602 (e.g., when performing method 500A, 500B, or 500C). In some implementations, the CU includes the PPW ID of at least one PPW configuration in the first CU-to-DU message. Thus, in some such implementations, the DU identifies the at least one PPW configuration based on the PPW ID and releases the PPW configuration accordingly. Alternatively, the CU does not include the PPW ID in the first CU-to-DU message.

[0124] In some implementations, the CU sends a first TRP PRS information item to the DU at box 602. In some implementations, the CU includes zero TRP PRS information items in the first CU to DU message (i.e., the CU does not include a TRPPRS information item in the first CU to DU message). In some implementations, the CU includes zero TRP PRS information items to indicate or request the release of all PPW configurations in the PPW configurations. When, after, or in response to receiving zero TRP PRS information items in the first CU to DU message, the DU releases all PPW configurations. In some implementations, when, after, or in response to receiving zero TRP PRS information items in the first CU to DU message, the DU generates PPW release information including PPW IDs of all PPW configurations in the PPW configurations.

[0125] In other implementations, the CU sends a first CU-to-DU message to the DU to indicate that positioning measurements are not required or configured. In such implementations, upon, after, or in response to receiving the first CU-to-DU message, the DU releases all PPW configurations. In some implementations, upon, after, or in response to receiving the first CU-to-DU message, the DU generates PPW release information including PPW IDs of all PPW configurations in the PPW configuration.

[0126] In other implementations, the CU includes a second TRP PRS information item of the first TRP PRS information item in the first CU to DU message. In some such implementations, the DU identifies the released PPW configuration based on the second TRP PRS information item and the first TRP PRS information item. For example, the released PPW configuration is associated with a TRP PRS information item not included in the second TRP PRS information item. In some implementations, the DU generates PPW release information including the PPW ID of the released PPW configuration after identifying the released PPW configuration.

[0127] In some implementations, the CU sends a first CU-to-DU message to the DU in response to receiving the LMF-to-BS message. For example, the LMF-to-BS message is Figure 3E or Figure 3F In other implementations, the CU sends the first CU-to-DU message to the DU in response to receiving the third DU-to-CU message from the DU. For example, the third DU-to-CU message is Figure 3D In another example, the third DU-to-CU message is a positioning measurement failure indication message.

[0128] Figure 6B is a flow chart of an example method 600B that is similar to method 600A, except that method 600B includes block 609 instead of blocks 608 and 610. At block 609, the CU generates PPW release information for releasing at least one PPW configuration after sending the first CU-to-DU message.

[0129] In the previous figures (e.g., FIG. 3A to FIG. 5C The examples and implementations described in ) can be applied to Fig. 6A and Figure 6B .

[0130] Next reference Figure 7 , method 700 is a method for configuring a PPW of a UE (eg, UE 102) and is implemented in a DU (eg, DU 174).

[0131] Method 700 starts at block 702, where the process performs at least one of 400A, 400B, or 400C. At block 704, the DU receives a first CU-to-DU message from the DU to release the PPW configuration of the UE (e.g., event 345). At block 706, the DU sends a first DU-to-CU message to the DU in response to the first CU-to-DU message (e.g., event 347). At block 708, the DU sends a second DU-to-CU message to the CU in response to the first CU-to-DU message (e.g., event 354), the second DU-to-CU message including PPW release information for releasing at least one of PPW configurations 1, ..., M. At block 710, the DU receives a second CU-to-DU message from the CU in response to the second DU-to-CU message (e.g., event 356). At block 712, the DU receives an RRC message from the CU including a PPW release indication (e.g., event 321). At block 714, the DU sends an RRC message to the UE (e.g., event 323).

[0132] In the previous figures (e.g., FIG. 3A to FIG. 6B The examples and implementations described in ) can be applied to Figure 7 .

[0133] The following description can be applied to the above description.

[0134] In general, the description of one of the above figures may apply to another of the above figures. Events or boxes described above may be optional or omitted. For example, an event or box with a dashed line in a figure may be optional or omitted. In some cases, if an event or box with a solid line in a figure is not required, the event or box may still be optional or omitted. In some implementations, "message" is used and "information element (IE)" may be replaced with "message", and vice versa. In some implementations, "IE" is used and "field" may be replaced with "IE", and vice versa. In some implementations, "configuration" may be replaced with "configurations" or "configuration parameters", and vice versa. In some implementations, "PPW configuration" may be replaced with "pre-configured PPW configuration".

[0135] The user device (e.g., UE 102) in which the technology of the present disclosure can be implemented can be any suitable device capable of wireless communication, such as a smart phone, a tablet computer, a laptop computer, a mobile game console, a point of sale (POS) terminal, a health monitoring device, a drone, a camera, a media streaming dongle or another personal media device, a wearable device such as a smart watch, a wireless hotspot, a femtocell, or a broadband router. Further, in some cases, the user device can be embedded in an electronic system, such as a head unit or an advanced driver assistance system (ADAS) of a vehicle. Still further, the user device can be operated as an Internet of Things (IoT) device or a mobile Internet device (MID). Depending on the type, the user device may include one or more general-purpose processors, a computer-readable memory, a user interface, one or more network interfaces, one or more sensors, etc.

[0136] Certain embodiments are described in the present disclosure as including logic or multiple components or modules. A module may be a software module (e.g., a code or machine-readable instruction stored on a non-transitory machine-readable medium) or a hardware module. A hardware module is a tangible unit that is capable of performing certain operations and can be configured or arranged in a particular manner. A hardware module may include a dedicated circuit system or logic that is permanently configured to perform certain operations (e.g., as a dedicated processor, such as a field programmable gate array (FPGA) or an application-specific integrated circuit (ASIC), a digital signal processor (DSP), etc.). A hardware module may also include a programmable logic or circuit system that is temporarily configured by software to perform certain operations (e.g., as contained in a general-purpose processor or other programmable processor). The decision to implement a hardware module with a dedicated and permanently configured circuit system or with a temporarily configured circuit system (e.g., configured by software) may be driven by cost and time considerations.

[0137] When implemented in software, the techniques may be provided as part of an operating system, a library used by multiple applications, a specific software application, etc. The software may be executed by one or more general-purpose processors or one or more special-purpose processors.

Claims

1. A method for managing a positioning reference signal (PRS) processing window (PPW) at a UE, the method being implemented in a central unit (CU) of a distributed base station, the distributed base station further comprising a distributed unit (DU), the method comprising: providing PPW configuration to the UE via the DU; as well as and sending a request to the DU to activate or deactivate the PPW configuration of the UE.

2. The method according to claim 1, wherein: The request to activate the PPW configuration includes a PRS measurement information item.

3. The method according to claim 2, wherein the PRS measurement information item indicates at least one of the following: (i) reference point, (ii) measuring the PRS periodicity, (iii) measure the PRS offset, or (iv) Measure the PRS length.

4. The method according to claim 1, wherein: The request to deactivate the PPW configuration comprises a measurement pre-configuration stop message.

5. The method according to any one of claims 1 to 3, further comprising: receiving a measurement activation message from a location management function (LMF); Wherein the sending of the request to activate the PPW configuration is in response to the receiving of the measurement activation message.

6. The method according to claim 1 or 4, further comprising: Receive a measurement abort message from the LMF; Wherein the sending of the request to deactivate the PPW configuration is in response to the receiving of the measurement suspend message.

7. A method according to any one of the preceding claims, wherein: Sending the request to activate or deactivate the PPW includes sending one of a CU-to-DU message or a F1 Application Protocol (F1AP) message.

8. The method according to claim 1 or 6, wherein: The providing of the configuration for the PPW comprises providing a plurality of configurations for a plurality of respective PPWs; and The sending of the request to deactivate the PPW configuration includes requesting deactivation of all of the plurality of configurations.

9. A method according to any one of the preceding claims, wherein: The providing of the configuration for the PPW comprises providing a plurality of configurations for a plurality of respective PPWs; the method further comprising: Each of the plurality of configurations is assigned a respective PPW identifier (ID).

10. A method for managing a positioning reference signal (PRS) processing window (PPW) at a UE, the method being implemented in a distributed unit (DU) of a distributed base station, the distributed base station further comprising a central unit (CU), the method comprising: providing a PPW configuration to the UE; receiving, from a CU, a request to activate or deactivate the PPW configuration of the UE; as well as Sending a PPW activation or deactivation command to the UE.

11. The method according to claim 10, wherein: The sending of the PPW activation or deactivation command includes sending a downlink (DL) medium access control (MAC) control element (CE).

12. The method according to claim 10 or 11, further comprising: receiving a PPW activation request from the UE; wherein the sending of the PPW activation is in response to the receiving of the PPW activation request.

13. A method according to any one of the preceding claims, wherein: Receiving the request to activate or deactivate the PPW configuration includes receiving a PPW ID from a DU; and The PPW ID is sent in the activation or deactivation command.

14. The method according to any one of claims 10 to 12, wherein: Receiving the request to activate or deactivate the PPW configuration includes receiving transmit-receive point (TRP) positioning reference signal (PRS) information from a DU; The method further comprises: At least one of (i) a PPW ID corresponding to the PPW configuration, (ii) a physical cell identifier (PCI) of the UE, or (iii) a serving cell ID of the UE is determined based on the TRP PRS information for use in the sending of the PPW activation or deactivation command.

15. A Radio Access Network (RAN) node comprising processing hardware and configured to implement the method according to any one of the preceding claims.

Images